from:"Alex Dănilă"

[kde] [Bug 470944] New: Plasma "Desktop and panel management" confuses display ids

2023-06-12 Thread Alex Dănilă

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

Bug ID: 470944
   Summary: Plasma "Desktop and panel management" confuses display
ids
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: alex.danila@protonmail.com
  Target Milestone: ---

SUMMARY
Upon connecting and disconnecting displays on a laptop, the displays get mixed
and panels jump around. 

Initial situation with xrandr:
- eDP-1 connected 1920x1080+0+324 (normal left inverted right x axis y axis)
344mm x 194mm
- VGA-1 connected 2048x1152+4480+288 (normal left inverted right x axis y axis)
510mm x 287mm
- HDMI-1 connected primary 2560x1440+1920+0 (normal left inverted right x axis
y axis) 527mm x 296mm
In "Panels and desktop management" appears ordered as: HDMI-1, VGA-1, eDP-1
(with taskbar panel).

Disconnecting the display at HDMI-1 will mix the ordering in the desktop
management: VGA-1, eDP-1 (taskbar panel is missing), Disconnected Screen 3
(with panel). 

Same will happen if I disconnect VGA-1.

STEPS TO REPRODUCE
1. Connect 2 external displays to a laptop, extending them to the right
2. Put a default panel on the integrated display
3. Disconnect one of the displays and notice that the desktops are reordered in
"Panels and Desktops Management", with the panel no longer on the integrated
display.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 12
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[korganizer] [Bug 466973] Events can overlap such as one hides the other

2023-03-07 Thread Alex Dănilă

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

--- Comment #1 from Alex Dănilă  ---
Comment on attachment 157065
  --> https://bugs.kde.org/attachment.cgi?id=157065
Screenshot

event3 is under event1 even though it is selected.

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

[korganizer] [Bug 466973] New: Events can overlap such as one hides the other

2023-03-06 Thread Alex Dănilă

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

Bug ID: 466973
   Summary: Events can overlap such as one hides the other
Classification: Applications
   Product: korganizer
   Version: 5.22.3
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: monthview
  Assignee: kdepim-b...@kde.org
  Reporter: alex.danila@protonmail.com
  Target Milestone: ---

Created attachment 157065
  --> https://bugs.kde.org/attachment.cgi?id=157065=edit
Screenshot

SUMMARY
When working with a few events that extend over more than one day, it is easy
to get into a situation when one event hides the other


STEPS TO REPRODUCE
1. Create a couple of multi-day events. E.g. in the screenshot:
   - event1: 06-03 - 06-04
   - event2: 06-04 - 06-05
   - event4: 06-26 - 07-03
   - event5: 07-06 - 0709
2. Notice the event 3 may or may no be visible, depending on the order of
creation and interaction.

OBSERVED RESULT


EXPECTED RESULT
Easier to distinguish and interact with the different events.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 12, 6.1.0-5-amd64
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[korganizer] [Bug 466971] Korganizer crashes when dragging the edge of an event in the month view

2023-03-06 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 Attachment #157064|Crash dump, other can be|Crash stack, other can be
description|produced on request |produced on request

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

[korganizer] [Bug 466971] New: Korganizer crashes when dragging the edge of an event in the month view

2023-03-06 Thread Alex Dănilă

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

Bug ID: 466971
   Summary: Korganizer crashes when dragging the edge of an event
in the month view
Classification: Applications
   Product: korganizer
   Version: 5.22.3
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: monthview
  Assignee: kdepim-b...@kde.org
  Reporter: alex.danila@protonmail.com
  Target Milestone: ---

Created attachment 157064
  --> https://bugs.kde.org/attachment.cgi?id=157064=edit
Crash dump, other can be produced on request

SUMMARY
Crashes when dragging an edge of an event, such as to extend or shorten it.


STEPS TO REPRODUCE
1. Open month view
2. Add a few events
3. Click on the edge of one event and start dragging to extend and shorten it
4. After a succession of such ”resizes” the crash will likely happen.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 12, 6.1.0-5-amd64
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[kwin] [Bug 444536] Compositor slows down to ~1fps after changing any of the compositor settings or restarting kwin

2022-10-06 Thread Alex Dănilă

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

--- Comment #13 from Alex Dănilă  ---
For me this used to reproduce every time, now it cannot reproduce anymore. Up
to date Debian Unstable.

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

[marble] [Bug 409399] Crash while loading Temperature map

2022-10-06 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #2 from Alex Dănilă  ---
Can't reproduce with current build.

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

[marble] [Bug 405006] Crash when browsing Vector OSM

2022-10-06 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Alex Dănilă  ---
Hi, I can't reproduce this bug with current build in Debian.

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

[kwin] [Bug 444536] Compositor slows down to ~1fps after changing any of the compositor settings or restarting kwin

2022-01-07 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||alex.danila.web@protonmail.
   ||com

--- Comment #1 from Alex Dănilă  ---
I can reproduce this exactly as reported, here is my relevant part of the
reporter's log:

OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 4600 (HSW
GT2)
OpenGL version string:  4.5 (Core Profile) Mesa 21.3.3
OpenGL shading language version string: 4.50
Driver: Intel
GPU class:  Haswell
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   21.3.3
X server version:   1.20.13
Linux kernel version:   5.15
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_core: XCB error: 10 (BadAccess), sequence: 6512, resource id: 408, major
code: 142 (Composite), minor code: 2 (RedirectSubwindows)

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

[drkonqi] [Bug 435490] bugs.kde.org Socket operation timed out, but bugs.kde.org is accessible from browser

2021-12-08 Thread Alex Dănilă

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

--- Comment #9 from Alex Dănilă  ---
Hi,
I can access bugstest.kde.org in Mozilla and even in Konqueror without a
problem. I don't have a proxy and in SystemSettings the „No proxy” option is
selected. I'm not sure what else to test.
Could it be that incompatible library versions are shipped with Debian? This
happened a few times over the years, but I'm not sure how to check it now.
Alex

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

[drkonqi] [Bug 435490] bugs.kde.org Socket operation timed out, but bugs.kde.org is accessible from browser

2021-11-22 Thread Alex Dănilă

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

--- Comment #6 from Alex Dănilă  ---
(In reply to Harald Sitter from comment #5)
> Was that around the time of your comment or earlier?

Yes, it was a 2-3 minutes earlier. But I can still replicate it now.

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

[drkonqi] [Bug 435490] bugs.kde.org Socket operation timed out, but bugs.kde.org is accessible from browser

2021-11-20 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---
 CC||nuor...@gmail.com

--- Comment #4 from Alex Dănilă  ---
Hi,
I have the copied here logs from the terminal running drkonqi. Please note this
is a Debian Unstable, in case any distro customisation may create this problem.
If needed, I can try to provide more info.
Alex

[20.040](47057)/(kf.kio.slaves.http) unknown:
QUrl("https://bugstest.kde.org/rest/product/kde;)
[20.040](47057)/(kf.kio.slaves.http) unknown:
QUrl("https://bugstest.kde.org/rest/product/kde;)
[20.040](47057)/(kf.kio.slaves.http) unknown: Window Id = ""
[20.040](47057)/(kf.kio.slaves.http) unknown: ssl_was_in_use = ""
[20.040](47057)/(kf.kio.slaves.http) unknown: 
[20.040](47057)/(kf.kio.slaves.http) unknown: 
[20.040](47057)/(kf.kio.slaves.http) unknown: 
[20.040](47057)/(kf.kio.slaves.http) unknown: 
[20.040](47057)/(kf.kio.slaves.http) unknown: 
[20.040](47057)/(kf.kio.slaves.http) unknown: Proxy URLs: ()
[20.019](47060)/(kf.kio.slaves.http) unknown: keepAlive = true
[20.020](47060)/(kf.kio.slaves.http) unknown: 
[20.020](47060)/(kf.kio.slaves.http) unknown: keep alive ( 60 )
[20.020](47060)/(kf.kio.slaves.http) unknown: Couldn't connect, oopsie!
[20.259](47003)/(org.kde.drkonqi.bugzilla) unknown: ProtocolException:
"bugstest.kde.org: Socket operation timed out" 149 "bugstest.kde.org: Socket
operation timed out" "bugstest.kde.org: Socket operation timed out"
[20.259](47003)/(org.kde.drkonqi) unknown: "bugstest.kde.org: Socket
operation timed out"
[20.018](47062)/(kf.kio.slaves.http) unknown: keepAlive = true
[20.018](47062)/(kf.kio.slaves.http) unknown: 
[20.018](47062)/(kf.kio.slaves.http) unknown: keep alive ( 60 )
[20.018](47062)/(kf.kio.slaves.http) unknown: Couldn't connect, oopsie!
[20.272](47003)/(org.kde.drkonqi.bugzilla) unknown: ProtocolException:
"bugstest.kde.org: Socket operation timed out" 149 "bugstest.kde.org: Socket
operation timed out" "bugstest.kde.org: Socket operation timed out"
[20.272](47003)/(org.kde.drkonqi) unknown: "bugstest.kde.org: Socket
operation timed out"
[40.060](47057)/(kf.kio.slaves.http) unknown: keepAlive = true
[40.060](47057)/(kf.kio.slaves.http) unknown: 
[40.060](47057)/(kf.kio.slaves.http) unknown: keep alive ( 60 )
[40.060](47057)/(kf.kio.slaves.http) unknown: Couldn't connect, oopsie!
[40.219](47003)/(org.kde.drkonqi.bugzilla) unknown: ProtocolException:
"bugstest.kde.org: Socket operation timed out" 149 "bugstest.kde.org: Socket
operation timed out" "bugstest.kde.org: Socket operation timed out"
[40.219](47003)/(org.kde.drkonqi) unknown: "bugstest.kde.org: Socket
operation timed out"

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

[frameworks-kglobalaccel] [Bug 332222] executes 2 key combo when firing 3 key combo (keyboard layout related?!)

2021-03-08 Thread Alex Dănilă

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

--- Comment #4 from Alex Dănilă  ---
I'm not the original reporter, but reporter of 348528: that issue has been
fixed many releases ago.

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

[marble] [Bug 386085] Crash when setting a bookmark

2021-01-03 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #3 from Alex Dănilă  ---
Hi,
I retried with the vector map activated and reproduced after moving the map and
setting more bookmarks. If relevant, currently I am running Debian Unstable
instead of Testing.

Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault

[KCrash Handler]
#4  0x7f4cc7b67829 in Marble::geodata_cast
(node=0x556de7abb630) at ./src/lib/marble/geodata/data/GeoDataObject.h:139
#5  Marble::MarbleWidgetPopupMenu::Private::mouseCoordinates
(this=0x556ddf05bfb0, dataContainer=0x556ddeee2d80) at
./src/lib/marble/MarbleWidgetPopupMenu.cpp:850
#6  0x7f4cc7b6dfd3 in Marble::MarbleWidgetPopupMenu::addBookmark
(this=0x556ddeebf8c0) at ./src/lib/marble/MarbleWidgetPopupMenu.cpp:884
#7  0x7f4cc61b9540 in doActivate (sender=0x556ddf050900,
signal_index=4, argv=argv@entry=0x7ffcfdca2ab0) at kernel/qobject.cpp:3898
#8  0x7f4cc61b2860 in QMetaObject::activate
(sender=sender@entry=0x556ddf050900, m=m@entry=0x7f4cc713ad40
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffcfdca2ab0) at kernel/qobject.cpp:3946
#9  0x7f4cc6c3cb62 in QAction::triggered (this=this@entry=0x556ddf050900,
_t1=) at .moc/moc_qaction.cpp:376
#10 0x7f4cc6c3f3a1 in QAction::activate (this=this@entry=0x556ddf050900,
event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1161
#11 0x7f4cc6db94fa in QMenuPrivate::activateCausedStack
(this=this@entry=0x556ddf050940, causedStack=...,
action=action@entry=0x556ddf050900, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at widgets/qmenu.cpp:1384
#12 0x7f4cc6dc0a22 in QMenuPrivate::activateAction (this=0x556ddf050940,
action=0x556ddf050900, action_e=QAction::Trigger, self=) at
widgets/qmenu.cpp:1461
#13 0x7f4cc6c82f9e in QWidget::event (this=0x556ddf05c000,
event=0x7ffcfdca3130) at kernel/qwidget.cpp:9019
#14 0x7f4cc6c4315f in QApplicationPrivate::notify_helper
(this=this@entry=0x556ddeba13b0, receiver=receiver@entry=0x556ddf05c000,
e=e@entry=0x7ffcfdca3130) at kernel/qapplication.cpp:3632
#15 0x7f4cc6c4a04b in QApplication::notify (this=0x7ffcfdca2e30,
receiver=0x556ddf05c000, e=0x7ffcfdca3130) at kernel/qapplication.cpp:3076
#16 0x7f4cc6182f2a in QCoreApplication::notifyInternal2
(receiver=0x556ddf05c000, event=0x7ffcfdca3130) at
kernel/qcoreapplication.cpp:1063
#17 0x7f4cc6c49076 in QApplicationPrivate::sendMouseEvent
(receiver=0x556ddf05c000, event=event@entry=0x7ffcfdca3130, alienWidget=0x0,
nativeWidget=0x556ddf05c000, buttonDown=buttonDown@entry=0x7f4cc71699f0
, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#18 0x7f4cc6c9b573 in QWidgetWindow::handleMouseEvent (this=0x556ddf139a90,
event=0x7ffcfdca33f0) at kernel/qwidgetwindow.cpp:580
#19 0x7f4cc6c9e32e in QWidgetWindow::event (this=0x556ddf139a90,
event=0x7ffcfdca33f0) at kernel/qwidgetwindow.cpp:300
#20 0x7f4cc6c4315f in QApplicationPrivate::notify_helper (this=, receiver=0x556ddf139a90, e=0x7ffcfdca33f0) at
kernel/qapplication.cpp:3632
#21 0x7f4cc6182f2a in QCoreApplication::notifyInternal2
(receiver=0x556ddf139a90, event=0x7ffcfdca33f0) at
kernel/qcoreapplication.cpp:1063
#22 0x7f4cc655b553 in QGuiApplicationPrivate::processMouseEvent
(e=0x556df4ca3740) at kernel/qguiapplication.cpp:2282
#23 0x7f4cc653164c in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#24 0x7f4cc126c7da in xcbSourceDispatch (source=) at
qxcbeventdispatcher.cpp:105
#25 0x7f4cc4689d3b in g_main_dispatch (context=0x7f4cbc005000) at
../../../glib/gmain.c:3325
#26 g_main_context_dispatch (context=0x7f4cbc005000) at
../../../glib/gmain.c:4043
#27 0x7f4cc4689fe8 in g_main_context_iterate
(context=context@entry=0x7f4cbc005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4119
#28 0x7f4cc468a09f in g_main_context_iteration (context=0x7f4cbc005000,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4184
#29 0x7f4cc61da47f in QEventDispatcherGlib::processEvents
(this=0x556ddecd4800, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x7f4cc61818eb in QEventLoop::exec (this=this@entry=0x7ffcfdca3720,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#31 0x7f4cc6189b60 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#32 0x7f4cc654ebac in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#33 0x7f4cc6c430d5 in QApplication::exec () at kernel/qapplication.cpp:2824
#34 0x556dddaca06a in main (argc=, argv=) at
./src/apps/marble-kde

[systemsettings] [Bug 418360] System Settings crashing

2020-10-19 Thread Alex Dănilă

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

--- Comment #4 from Alex Dănilă  ---
(In reply to Nate Graham from comment #3)
> Just by moving the window, yikes. Does this happen with a newer version of
> Plasma? Like 5.19 or 5.20?

Not the original reporter and I'm not sure mine is the exact same crash, but I
haven't seen this is the last couple of months.

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

[marble] [Bug 378885] Marble crashes sometime when using the vector map theme

2020-08-25 Thread Alex Dănilă

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

--- Comment #13 from Alex Dănilă  ---
Created attachment 131170
  --> https://bugs.kde.org/attachment.cgi?id=131170=edit
New crash information added by DrKonqi

marble (2.2.20 (2.3 development version)) using Qt 5.14.2

- What I was doing when the application crashed:
Panning/dragging the map while it was loading, this time with the regula tile
map.

-- Backtrace (Reduced):
#4  0x7f2bc41731cb in QPixmap::size() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x7f2bc57a8de9 in Marble::VisiblePlacemark::symbolRect
(this=this@entry=0x55e6d506ecf0) at ./src/lib/marble/VisiblePlacemark.cpp:172
#6  0x7f2bc57aabab in Marble::PlacemarkLayout::hasPlacemarkAt
(this=0x55e6cd96a258, pos=...) at ./src/lib/marble/PlacemarkLayout.cpp:555
#7  0x7f2bc56ea4e9 in Marble::PlacemarkLayer::hasPlacemarkAt
(this=, pos=...) at
./src/lib/marble/layers/PlacemarkLayer.cpp:218
#8  0x7f2bc5717d0b in Marble::MarbleMap::hasFeatureAt (this=0x55e6cd9075e0,
position=...) at ./src/lib/marble/MarbleMap.cpp:483

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

[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them

2020-03-21 Thread Alex Dănilă

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

--- Comment #3 from Alex Dănilă  ---
Sorry, I've only seen this once and I am unable to reproduce it again (I just
retried). Hopefully Túlio can help.

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

[systemsettings] [Bug 418360] System Settings crashing

2020-03-21 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[systemsettings] [Bug 418360] System Settings crashing

2020-03-21 Thread Alex Dănilă

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

--- Comment #2 from Alex Dănilă  ---
Created attachment 126921
  --> https://bugs.kde.org/attachment.cgi?id=126921=edit
New crash information added by DrKonqi

systemsettings5 (5.17.5) using Qt 5.12.5

- What I was doing when the application crashed:
This is generally a crash on close. I made a couple of changes in System
Settings and pressed the close button, then drkonqi appeared. If I don't do
anything in System Settings then it will probably not crash.

-- Backtrace (Reduced):
#6  QQuickWindowPrivate::dirtyItem (this=0xa7963340164) at
items/qquickwindow.cpp:1158
#7  0x7f02c948d705 in QQuickItemPrivate::dirty (this=,
type=type@entry=QQuickItemPrivate::Content) at items/qquickwindow.h:78
#8  0x7f02c948da9e in QQuickItem::update (this=this@entry=0x55a4968a4e80)
at items/qquickitem.cpp:4439
#9  0x7f02c94f5f32 in QQuickText::setColor (this=0x55a4968a4e80, color=...)
at items/qquicktext.cpp:1715
#10 0x7f02c94febcd in QQuickText::qt_static_metacall
(_o=_o@entry=0x55a4968a4e80, _c=_c@entry=QMetaObject::WriteProperty,
_id=_id@entry=2, _a=_a@entry=0x7ffd00342ea0) at .moc/moc_qquicktext_p.cpp:883

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

[kwin] [Bug 172615] Gimp 2.6 utility windows do not stay on top of the main window

2020-03-17 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them

2020-03-07 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[okular] [Bug 198566] Slow on some documents when using big zoom and search

2020-02-24 Thread Alex Dănilă

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

--- Comment #8 from Alex Dănilă  ---
Regarding the document I originally indicated when posting the bug: it now
works very well. However, this computer is probably 5 times faster even on
single thread and I don't have a slower one around.

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

[okular] [Bug 415261] Okular crash when trying to open certain djvu file

2020-01-05 Thread Alex Dănilă

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

--- Comment #8 from Alex Dănilă  ---
You are right. Sorry for all this noise, I used to remember to check this stuff
before reporting bugs (I often use KDE from Unstable to get newer versions of
software).

$ dpkg -s okular | grep '^Version:'
Version: 4:18.04.0-1
$ dpkg -s okular-extra-backends | grep '^Version:'
Version: 4:17.12.2-2.2+b1

I installed a tested with a compatible okular-extra-backends from Experimental
and it worked.

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

[okular] [Bug 415261] Okular crash when trying to open certain djvu file

2020-01-05 Thread Alex Dănilă

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

--- Comment #6 from Alex Dănilă  ---
Created attachment 124901
  --> https://bugs.kde.org/attachment.cgi?id=124901=edit
valgrind output

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

[okular] [Bug 415261] Okular crash when trying to open certain djvu file

2020-01-05 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[okular] [Bug 415261] New: Okular crash when trying to open certain djvu file

2019-12-16 Thread Alex Dănilă

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

Bug ID: 415261
   Summary: Okular crash when trying to open certain djvu file
   Product: okular
   Version: 1.4.0
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: okular (1.4.0)

Qt Version: 5.12.5
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-2-amd64 x86_64
Distribution: Debian GNU/Linux bullseye/sid

-- Information about the crash:
- What I was doing when the application crashed:
Tried to open a .djvu file. This replicates every time. The file is 90 MiB, but
I can provide it privately. I'm almost sure I was able to open this file
previously, less than a year ago.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f676ff96800 (LWP 564425))]

Thread 4 (Thread 0x7f675700 (LWP 564428)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x55b4550b8448) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55b4550b83f8,
cond=0x55b4550b8420) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55b4550b8420, mutex=0x55b4550b83f8) at
pthread_cond_wait.c:655
#3  0x7f67648873eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f6764887007 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f6772fdcfb7 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f6773a9a2df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f6767df1700 (LWP 564427)):
#0  0x7f6773a8fd1f in __GI___poll (fds=0x7f6760004e30, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f677260309e in g_main_context_poll (priority=,
n_fds=1, fds=0x7f6760004e30, timeout=, context=0x7f676bf0)
at ../../../glib/gmain.c:4216
#2  g_main_context_iterate (context=context@entry=0x7f676bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:3912
#3  0x7f67726031bf in g_main_context_iteration (context=0x7f676bf0,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3978
#4  0x7f677400d80b in QEventDispatcherGlib::processEvents
(this=0x7f676b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f6773fb671b in QEventLoop::exec (this=this@entry=0x7f6767df0d70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f6773df7751 in QThread::exec (this=this@entry=0x7f677430bd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f677428a4e6 in QDBusConnectionManager::run (this=0x7f677430bd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f6773df88d2 in QThreadPrivate::start (arg=0x7f677430bd80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#9  0x7f6772fdcfb7 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f6773a9a2df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f676ef8b700 (LWP 564426)):
#0  0x7f6773a8fd1f in __GI___poll (fds=fds@entry=0x7f676ef8aca8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6773204cf7 in poll (__timeout=-1, __nfds=1, __fds=0x7f676ef8aca8)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x55b454f16ea0, cond=cond@entry=0x55b454f16ee0,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:479
#3  0x7f677320691a in xcb_wait_for_event (c=c@entry=0x55b454f16ea0) at
../../src/xcb_in.c:697
#4  0x7f676fb87cd0 in QXcbEventQueue::run (this=0x55b454f06610) at
qxcbeventqueue.cpp:228
#5  0x7f6773df88d2 in QThreadPrivate::start (arg=0x55b454f06610) at
thread/qthread_unix.cpp:361
#6  0x7f6772fdcfb7 in start_thread (arg=) at
pthread_create.c:486
#7  0x7f6773a9a2df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f676ff96800 (LWP 564425)):
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at
/usr/include/c++/9/bits/atomic_base.h:413
#7  QAtomicOps::load (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8  QBasicAtomicInteger::load (this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
#9  QtPrivate::RefCount::deref (this=) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:66
#10 QString::operator= (this=0x5, other=...) at tools/qstring.cpp:2417
#11 0x7f675f761c19 in

[kontact] [Bug 403065] Akregator crashes when adding link

2019-11-12 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[kontact] [Bug 403065] Akregator crashes when adding link

2019-11-12 Thread Alex Dănilă

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

--- Comment #2 from Alex Dănilă  ---
Created attachment 123867
  --> https://bugs.kde.org/attachment.cgi?id=123867=edit
New crash information added by DrKonqi

akregator (5.9.3) using Qt 5.12.5

- What I was doing when the application crashed:

Like the original reporter, tried to add a link to a website feed, but with
right click add.

-- Backtrace (Reduced):
#6  0x7f1145978dbf in
Akregator::Feed::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from
/usr/lib/x86_64-linux-gnu/libakregatorprivate.so.5
#7  0x7f114598dff1 in
Akregator::Folder::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from
/usr/lib/x86_64-linux-gnu/libakregatorprivate.so.5
#8  0x7f114437f528 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc3e814b0,
r=0x563f19e1e170, this=0x563f19c9f0d0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
[...]
#10 0x7f114438c147 in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:204
#11 0x7f114437fd85 in QObject::event (this=0x563f19d6c7b0, e=) at kernel/qobject.cpp:1282

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

[marble] [Bug 409399] New: Crash while loading Temperature map

2019-07-02 Thread Alex Dănilă

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

Bug ID: 409399
   Summary: Crash while loading Temperature map
   Product: marble
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

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

-- Information about the crash:
- What I was doing when the application crashed:
- started Marble and immediately clicked on Temperature (July) to
change the map
- the map download progress bar started to move to 100% (and may have
reached 100%)
- I think the temperature map may have displayed before the crash, but
I might have misseen.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd90167c940 (LWP 13961))]

Thread 8 (Thread 0x7fd89ba25700 (LWP 13993)):
#0  0x7fd90b256819 in __GI___poll (fds=0x7fd86800adc0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fd906e71136 in g_main_context_poll (priority=,
n_fds=1, fds=0x7fd86800adc0, timeout=, context=0x7fd868005d40)
at ../../../glib/gmain.c:4221
#2  0x7fd906e71136 in g_main_context_iterate
(context=context@entry=0x7fd868005d40, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3915
#3  0x7fd906e7125c in g_main_context_iteration (context=0x7fd868005d40,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
#4  0x7fd90b783393 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd8682237c0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7fd90b730d4b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd89ba24c60, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7fd90b580e36 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7fd90b58aa27 in QThreadPrivate::start(void*) (arg=0x560f3387c290) at
thread/qthread_unix.cpp:367
#8  0x7fd90787dfa3 in start_thread (arg=) at
pthread_create.c:486
#9  0x7fd90b2614cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fd89aa23700 (LWP 13983)):
#0  0x7fd90b256819 in __GI___poll (fds=0x7fd87b20, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fd906e71136 in g_main_context_poll (priority=,
n_fds=1, fds=0x7fd87b20, timeout=, context=0x7fd870005d40)
at ../../../glib/gmain.c:4221
#2  0x7fd906e71136 in g_main_context_iterate
(context=context@entry=0x7fd870005d40, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3915
#3  0x7fd906e7125c in g_main_context_iteration (context=0x7fd870005d40,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
#4  0x7fd90b783393 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd870139a40, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7fd90b730d4b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd89aa22c60, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7fd90b580e36 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7fd90b58aa27 in QThreadPrivate::start(void*) (arg=0x560f33ab2610) at
thread/qthread_unix.cpp:367
#8  0x7fd90787dfa3 in start_thread (arg=) at
pthread_create.c:486
#9  0x7fd90b2614cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fd8a37fe700 (LWP 13977)):
#0  0x7fd906e6e056 in g_source_iter_next (iter=iter@entry=0x7fd8a37fda60,
source=source@entry=0x7fd8a37fda58) at ../../../glib/gmain.c:969
#1  0x7fd906e70a3f in g_main_context_check
(context=context@entry=0x7fd88c002e20, max_priority=2147483647,
fds=fds@entry=0x7fd88c003880, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:944
#2  0x7fd906e710e0 in g_main_context_iterate
(context=context@entry=0x7fd88c002e20, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3917
#3  0x7fd906e7125c in g_main_context_iteration (context=0x7fd88c002e20,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
#4  0x7fd90b783393 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd88c004800, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7fd90b730d4b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd8a37fdc30, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7fd90b580e36 in QThread::exec() (this=) at

[marble] [Bug 403961] segfault in QNetworkAccessM

2019-03-17 Thread Alex Dănilă

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

--- Comment #5 from Alex Dănilă  ---
Created attachment 118864
  --> https://bugs.kde.org/attachment.cgi?id=118864=edit
New crash information added by DrKonqi

marble (2.2.20 (2.3 development version)) using Qt 5.11.3

- What I was doing when the application crashed:
Used Marble not being aware of the redirections to the login portal.

-- Backtrace (Reduced):
#6  0x7f8787719ba4 in QHttpNetworkConnectionChannel::sendRequest
(this=) at access/qhttpnetworkconnectionchannel.cpp:251
#7  0x7f8787718c69 in QHttpNetworkConnectionPrivate::_q_startNextRequest
(this=0x7f86e40404a0) at access/qhttpnetworkconnection.cpp:1044
#8  0x7f8786432182 in QObject::event (this=0x7f86e40e47c0, e=) at kernel/qobject.cpp:1251
#9  0x7f8786e214b1 in QApplicationPrivate::notify_helper
(this=this@entry=0x565195467680, receiver=receiver@entry=0x7f86e40e47c0,
e=e@entry=0x7f86e40703e0) at kernel/qapplication.cpp:3726
#10 0x7f8786e28950 in QApplication::notify (this=0x7ffc54c90130,
receiver=0x7f86e40e47c0, e=0x7f86e40703e0) at kernel/qapplication.cpp:3485

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

[marble] [Bug 403961] segfault in QNetworkAccessM

2019-03-17 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[marble] [Bug 405006] New: Crash when browsing Vector OSM

2019-03-02 Thread Alex Dănilă

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

Bug ID: 405006
   Summary: Crash when browsing Vector OSM
   Product: marble
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-2-amd64 x86_64
Distribution: Debian GNU/Linux buster/sid

-- Information about the crash:
- What I was doing when the application crashed:
Switched to Vector OSM from OpenTopoMap and dragged the map a couple of time.
The crash seemed to have happened during filling with data.

I don't know if this is relevant, but there where a couple of „measure points”
set on the map (a few tens).

Reproducibility:
Crashes seem to happen sometimes (rarely )when using the vector OSM, and I
don't remember having crashes recently with the bitmap maps.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4c831ef940 (LWP 1944))]

Thread 12 (Thread 0x7f4c28e29700 (LWP 2660)):
#0  0x7f4c8d9d1b49 in __GI___poll (fds=0x7f4bf8146830, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4c895d9136 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f4bf8146830, timeout=, context=0x7f4bf8004a60)
at ../../../glib/gmain.c:4221
#2  g_main_context_iterate (context=context@entry=0x7f4bf8004a60,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:3915
#3  0x7f4c895d925c in g_main_context_iteration (context=0x7f4bf8004a60,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3981
#4  0x7f4c8df0104b in QEventDispatcherGlib::processEvents
(this=0x7f4bf800b180, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f4c8deae14b in QEventLoop::exec (this=this@entry=0x7f4c28e28c60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f4c8dcfd0d6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f4c8dd06c77 in QThreadPrivate::start (arg=0x7f4c6c00acf0) at
thread/qthread_unix.cpp:367
#8  0x7f4c89e99fa3 in start_thread (arg=) at
pthread_create.c:486
#9  0x7f4c8d9dc80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f4c2b514700 (LWP 2638)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f4c8262205c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4c82622008,
cond=0x7f4c82622030) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f4c82622030, mutex=0x7f4c82622008) at
pthread_cond_wait.c:655
#3  0x7f4c8db743bc in
std::condition_variable::wait(std::unique_lock&) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f4c8b5d01ff in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7f4c8ad530f6 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#6  0x7f4c2b513b50 in ?? ()
#7  0x7fff612e5bfc in clock_gettime ()
#8  0x007f4c827fb0 in ?? ()
#9  0x407f4c827c70 in ?? ()
#10 0x11003f00 in ?? ()
#11 0x in ?? ()

Thread 10 (Thread 0x7f4c2bd15700 (LWP 2637)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f4c8262b05c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4c8262b008,
cond=0x7f4c8262b030) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f4c8262b030, mutex=0x7f4c8262b008) at
pthread_cond_wait.c:655
#3  0x7f4c8db743bc in
std::condition_variable::wait(std::unique_lock&) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f4c8b5d01ff in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7f4c8ad53285 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#6  0x00018ca6a501 in ?? ()
#7  0x7f4c8262b008 in ?? ()
#8  0x7f4c827ed001 in ?? ()
#9  0x7f4c2bd14b30 in ?? ()
#10 0x in ?? ()

Thread 9 (Thread 0x7f4c1affd700 (LWP 2636)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f4c8261d05c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4c8261d008,
cond=0x7f4c8261d030) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f4c8261d030, mutex=0x7f4c8261d008) at
pthread_cond_wait.c:655
#3  0x7f4c8db743bc in
std::condition_variable::wait(std::unique_lock&) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f4c8b5d01ff in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7f4c8ad53285 in ??

[gwenview] [Bug 294184] Crash when accessing videos from slow media [QDBusConnectionPrivate::~QDBusConnectionPrivate ]

2018-11-30 Thread Alex Dănilă

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

--- Comment #5 from Alex Dănilă  ---
(In reply to Andrew Crouthamel from comment #2)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!


Hi, unfortunately I can't find any slow SD (or any other storage), did it work
well for you? 

Otherwise, I'm not sure what is the point of these changes
(->NEEDSINFO->WORKSFORME). Is it just to decrease the number of bugs reported
by this tracker?

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

[marble] [Bug 401503] New: May crash when dragging and it still loads tiles

2018-11-28 Thread Alex Dănilă

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

Bug ID: 401503
   Summary: May crash when dragging and it still loads tiles
   Product: marble
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.11.2
Frameworks Version: 5.49.0
Operating System: Linux 4.18.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Was dragging with the mouse. There was nothing particular, but it seems Marble
was having some background activity (loading more tiles).

This type of crash reproduces from time to time. This is a VirtualBox VM and
Marble runs slowly, sometimes lagging in downloading tiles and responding to
mouse input, which may be the reason why this happens more often on the VM that
on native.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9962c61940 (LWP 5049))]

Thread 11 (Thread 0x7f9900907700 (LWP 16647)):
#0  0x7f996f35719a in futex_reltimed_wait_cancelable (private=, reltime=0x7f9900906b10, expected=0, futex_word=0x55d99e3e4954) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f996f35719a in __pthread_cond_wait_common (abstime=0x7f9900906bd0,
mutex=0x55d99e3e4900, cond=0x55d99e3e4928) at pthread_cond_wait.c:533
#2  0x7f996f35719a in __pthread_cond_timedwait (cond=0x55d99e3e4928,
mutex=0x55d99e3e4900, abstime=0x7f9900906bd0) at pthread_cond_wait.c:667
#3  0x7f99733a832c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f99733a0192 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f99733a7c97 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f996f350f2a in start_thread (arg=0x7f9900907700) at
pthread_create.c:463
#7  0x7f9973080edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f9902ffd700 (LWP 5517)):
#0  0x7f9973076739 in __GI___poll (fds=0x7f98d43eec90, nfds=1,
timeout=116027) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f996e501e46 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f996e501f6c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f99735a1d2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f997354ed0b in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f997339e0c6 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f99733a7c97 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f996f350f2a in start_thread (arg=0x7f9902ffd700) at
pthread_create.c:463
#8  0x7f9973080edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f98e37fe700 (LWP 5109)):
#0  0x7f996f356e6c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f996224b05c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f996f356e6c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f996224b008, cond=0x7f996224b030) at pthread_cond_wait.c:502
#2  0x7f996f356e6c in __pthread_cond_wait (cond=0x7f996224b030,
mutex=0x7f996224b008) at pthread_cond_wait.c:655
#3  0x7f997321638c in
std::condition_variable::wait(std::unique_lock&) () at
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f9970a7b1ff in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7f9970a79a22 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#6  0x7f9970a79af6 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#7  0x7f9970a7d9d8 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#8  0x7f9970aa1fba in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#9  0x7f996f350f2a in start_thread (arg=0x7f98e37fe700) at
pthread_create.c:463
#10 0x7f9973080edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f9903fff700 (LWP 5108)):
#0  0x7f996f356e6c in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f9962251058) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f996f356e6c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f9962251008, cond=0x7f9962251030) at pthread_cond_wait.c:502
#2  0x7f996f356e6c in __pthread_cond_wait (cond=0x7f9962251030,
mutex=0x7f9962251008) at pthread_cond_wait.c:655
#3  0x7f997321638c in
std::condition_variable::wait(std::unique_lock&) () at
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f9970a7b1ff in  () at

[plasma4] [Bug 214205] Kickoff menus cannot come in front of normal windows

2018-09-04 Thread Alex Dănilă

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

--- Comment #3 from Alex Dănilă  ---
I haven't seen this type of problem in years, for me it's ok to close it as
fixed.

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

[dolphin] [Bug 290747] Column view is not available anymore in Dolphin 2.0

2018-07-14 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

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

[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box

2018-06-17 Thread Alex Dănilă

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

--- Comment #6 from Alex Dănilă  ---
Note:
go to Settings->General->Calendar, select "Personal Calendar" click modify,
press OK in the calendar modification window without actually modifying
anything. The new calendar may be available for use.

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

[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box

2018-06-17 Thread Alex Dănilă

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

Alex Dănilă  changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #5 from Alex Dănilă  ---
Can confirm with 5.7.3. What is a good workaround?

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

[plasmashell] [Bug 395123] New: Plasmashell and KScreenLocker hang in _xcb_conn_wait

2018-06-07 Thread Alex Dănilă

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

Bug ID: 395123
   Summary: Plasmashell and KScreenLocker hang in _xcb_conn_wait
   Product: plasmashell
   Version: 5.12.5
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: nuor...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Plasmashell and kscreenlocker_greet may freeze with a stack (below) that is
similar in the upper part. It is not clear to me if this is KDE, Qt or XCB, so
I'd need some with reporting in the correct place.

Plasmashell freezes when showing popups, the kscreenlocker_greet freezes when
resuming suspend to RAM. Also reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900373 with a
kscreenlocker_greet stack.

Plasmashell stack:
(gdb) where
#0  0x7f7ff847a5d9 in __GI___poll (fds=fds@entry=0x7ffd2906c3e8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f7ffd4f00f7 in poll (__timeout=-1, __nfds=1, __fds=0x7ffd2906c3e8)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7f7ffd4f00f7 in _xcb_conn_wait (c=c@entry=0x560a9b26a270,
cond=cond@entry=0x560a9e9154b8, vector=vector@entry=0x0, count=count@entry=0x0)
at ../../src/xcb_conn.c:479
#3  0x7f7ffd4f1e0a in xcb_wait_for_special_event (c=0x560a9b26a270,
se=0x560a9e915490) at ../../src/xcb_in.c:795
#4  0x7f7fd274296b in dri3_wait_for_event_locked (draw=0x560aa0656888) at
../../../src/loader/loader_dri3_helper.c:431
#5  0x7f7fd2742ac8 in dri3_find_back (draw=draw@entry=0x560aa0656888) at
../../../src/loader/loader_dri3_helper.c:557
#6  0x7f7fd274340e in dri3_get_buffer (format=format@entry=4107,
buffer_type=buffer_type@entry=loader_dri3_buffer_back,
draw=draw@entry=0x560aa0656888, driDrawable=0x7f7fe00062d0)
at ../../../src/loader/loader_dri3_helper.c:1399
#7  0x7f7fd2744081 in loader_dri3_get_buffers
(driDrawable=driDrawable@entry=0x7f7fe00062d0, format=4107,
stamp=stamp@entry=0x7f7fe0006300,
loaderPrivate=loaderPrivate@entry=0x560aa0656888, buffer_mask=,
buffer_mask@entry=1, buffers=buffers@entry=0x7ffd2906c6a0) at
../../../src/loader/loader_dri3_helper.c:1603
#8  0x7f7fd0c9459f in intel_update_image_buffers (drawable=0x7f7fe00062d0,
brw=0x560a9cd013a0) at
../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1722
#9  0x7f7fd0c9459f in intel_update_renderbuffers
(context=context@entry=0x560a9ca54c70, drawable=drawable@entry=0x7f7fe00062d0)
at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1398
#10 0x7f7fd0c948a1 in intel_prepare_render (brw=brw@entry=0x560a9cd013a0)
at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1419
#11 0x7f7fd0c8ffac in brw_clear (ctx=0x560a9cd013a0, mask=50) at
../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:278
#12 0x7f7ffc8fe158 in QSGBatchRenderer::Renderer::renderBatches() () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f7ffc903a84 in QSGBatchRenderer::Renderer::render() () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7f7ffc8f4220 in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f7ffc8f46db in QSGRenderer::renderScene(unsigned int) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7f7ffc92dc20 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x7f7ffc9918b8 in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#18 0x7f7ffc9201b9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#19 0x7f7ffc99c296 in QQuickWindow::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#20 0x7f7ff9d426cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f7ff9d49e84 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f7ff8d5b938 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f7ff955d291 in QWindowPrivate::deliverUpdateRequest() () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#24 0x7f7ff955d7b9 in QWindow::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#25 0x7f7ffc99c235 in QQuickWindow::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#26 0x7f7ff9d426cc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f7ff9d49e84 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7f7ff8d5b938 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f7ff8db563e in

[akregator] [Bug 394946] New: Delete key no longer works in articles list after using search - keyboard focus stays in search field

2018-06-02 Thread Alex Dănilă

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

Bug ID: 394946
   Summary: Delete key no longer works in articles list after
using search - keyboard focus stays in search field
   Product: akregator
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

After typing into the „Search articles” field, the keyboard focus seems to
remain there, so the delete key won't delete articles anymore.

Steps:
1. select an article in the articles list and press delete, notice it is
deleted
2. click and type a text in the search field, then clear the text
3. click an article in the articles list
4. press delete and notice nothing happens; right click will still work

5. click in the article contents area and press the delete key, notice that now
delete works.


Akregator 5.7.3

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

[kontact] [Bug 376045] Non-functional "Details" button when Akonadi fails to start

2018-05-27 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Alex Dănilă <nuor...@gmail.com> ---
Can still reproduce with 17.12.3 of Debian Testing.

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

[Akonadi] [Bug 394768] „Details” button of „The akonadi [...] service is not operational" does nothing”

2018-05-27 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
Should have noticed already reported bug.

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

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

[kontact] [Bug 376045] Non-functional "Details" button when Akonadi fails to start

2018-05-27 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
*** Bug 394768 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 394768] New: „Details” button of „The akonadi [...] service is not operational" does nothing”

2018-05-27 Thread Alex Dănilă

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

Bug ID: 394768
   Summary: „Details” button of „The akonadi [...] service is not
operational" does nothing”
   Product: Akonadi
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

When KAddressBook/Korganizer fail to start they show a grey window with a
„Details” button. Pressing that doesn't show any more information (I assume
corruption) or do anything at all.

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

[plasmashell] [Bug 391063] Memory Leak in Plasmashell

2018-03-26 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #7 from Alex Dănilă <nuor...@gmail.com> ---
Hi,
I recently started to notice this on Debian (plasma-workspace 5.12.3) with all
of Intel/Nouveau/Virtualbox. If there's any  information I could share apart
from the Valgrind memcheck I'll atach?

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

[marble] [Bug 382072] Bookmark Manager doesn't show bookmarks

2018-03-25 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||nuor...@gmail.com

--- Comment #3 from Alex Dănilă <nuor...@gmail.com> ---
I can confirm this on Debian (version 2.2.20 (2.3 development version), KDE
Frameworks 5.44.0, Qt 5.9.2 (built against 5.9.2)).

I remember being able to use bookmarks correctly sometime before having more
than one bookmarks folder.

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

[marble] [Bug 392296] New: Crash when dragged after setting a bookmark

2018-03-25 Thread Alex Dănilă

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

Bug ID: 392296
   Summary: Crash when dragged after setting a bookmark
   Product: marble
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.9.2
Frameworks Version: 5.44.0
Operating System: Linux 4.16.0-rc6-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Set a bookmark then immediately dragged the map (left mouse). Did not manage to
reproduce the crash, but I have seen crashes with a similar stack before.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f992c3e2400 (LWP 29152))]

Thread 13 (Thread 0x7f988ceac700 (LWP 3672)):
#0  0x7f992124a81a in futex_reltimed_wait_cancelable (private=, reltime=0x7f988ceabb00, expected=0, futex_word=0x5584f7c02940) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f992124a81a in __pthread_cond_wait_common (abstime=0x7f988ceabbc0,
mutex=0x5584f7c028f0, cond=0x5584f7c02918) at pthread_cond_wait.c:533
#2  0x7f992124a81a in __pthread_cond_timedwait (cond=0x5584f7c02918,
mutex=0x5584f7c028f0, abstime=0x7f988ceabbc0) at pthread_cond_wait.c:667
#3  0x7f9928047518 in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x5584f7c028f0) at thread/qwaitcondition_unix.cpp:133
#4  0x7f9928047518 in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x5584f7c028f0) at thread/qwaitcondition_unix.cpp:141
#5  0x7f9928047518 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x5584f8847f50, mutex=mutex@entry=0x5584f6c8c950, time=3)
at thread/qwaitcondition_unix.cpp:215
#6  0x7f992804275c in QThreadPoolThread::run() (this=0x5584f8847f40) at
thread/qthreadpool.cpp:133
#7  0x7f992804622d in QThreadPrivate::start(void*) (arg=0x5584f8847f40) at
thread/qthread_unix.cpp:368
#8  0x7f99212445aa in start_thread (arg=0x7f988ceac700) at
pthread_create.c:463
#9  0x7f9927742cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f98877fe700 (LWP 3640)):
#0  0x7f992124a81a in futex_reltimed_wait_cancelable (private=, reltime=0x7f98877fdb00, expected=0, futex_word=0x5584f7bbd190) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f992124a81a in __pthread_cond_wait_common (abstime=0x7f98877fdbc0,
mutex=0x5584f7bbd140, cond=0x5584f7bbd168) at pthread_cond_wait.c:533
#2  0x7f992124a81a in __pthread_cond_timedwait (cond=0x5584f7bbd168,
mutex=0x5584f7bbd140, abstime=0x7f98877fdbc0) at pthread_cond_wait.c:667
#3  0x7f9928047518 in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x5584f7bbd140) at thread/qwaitcondition_unix.cpp:133
#4  0x7f9928047518 in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x5584f7bbd140) at thread/qwaitcondition_unix.cpp:141
#5  0x7f9928047518 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x5584f8bcd270, mutex=mutex@entry=0x5584f6d62d20, time=3)
at thread/qwaitcondition_unix.cpp:215
#6  0x7f992804275c in QThreadPoolThread::run() (this=0x5584f8bcd260) at
thread/qthreadpool.cpp:133
#7  0x7f992804622d in QThreadPrivate::start(void*) (arg=0x5584f8bcd260) at
thread/qthread_unix.cpp:368
#8  0x7f99212445aa in start_thread (arg=0x7f98877fe700) at
pthread_create.c:463
#9  0x7f9927742cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f98afaa1700 (LWP 30002)):
#0  0x7f992124a4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f9912028058) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f992124a4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f9912028008, cond=0x7f9912028030) at pthread_cond_wait.c:502
#2  0x7f992124a4ec in __pthread_cond_wait (cond=0x7f9912028030,
mutex=0x7f9912028008) at pthread_cond_wait.c:655
#3  0x7f9927cd261c in
std::condition_variable::wait(std::unique_lock&) () at
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7f9924919b87 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () at
../Source/WTF/wtf/ParkingLot.cpp:570
#5  0x7f99249183af in WTF::ConditionBase::waitUntil(WTF::Lock&,
std::chrono::time_point > >) () at

[okular] [Bug 201092] Drag to scroll in Okular's text mode and KDE wide

2018-03-04 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #4 from Alex Dănilă <nuor...@gmail.com> ---
Moving from NEEDSINFO back to unconfirmed.

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

[okular] [Bug 201092] Drag to scroll in Okular's text mode and KDE wide

2018-03-04 Thread Alex Dănilă

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

--- Comment #3 from Alex Dănilă <nuor...@gmail.com> ---
It is a feature idea to have drag scrolling („Browse tool”) available also in
the „Text selection” mode of Okular.

When you activate „Text selection”, the drag scrolling feature is not available
because the left mouse button (LMB) will select text instead of dragging. Thus
I'm thinking of a mouse+keyboard combination: whenever you press a certain key
combination (say Ctrl+Alt) and LMB, you drag the document instead of selecting
text.

Steps:
1. Open document in Okular and press button „Browse tool” (Ctrl+1)
2. Press left mouse button over the document and move the mouse -> the document
is dragged.
3. Press button „Text selection” (Ctrl+4)
4. Press left mouse button over document and move the mouse -> text is selected
in the document.
5. (the proposed feature) Press Ctrl+Alt, press left mouse button over document
and move the mouse -> the document is dragged like in step 2.

However, because now touchscreens are so common, I guess this kind of thing
should be available as a global feature.

Please ask if there's something I did not explain well.

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

[plasmashell] [Bug 381174] Tray icons context menu appears on top of screen under Wayland

2018-01-13 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #8 from Alex Dănilă <nuor...@gmail.com> ---
Can reproduce on Debian Unstable and Experimental:
KWin 5.11.4
Plasma 5.11.4
Qt 5.9.2

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

[ktorrent] [Bug 387368] Ktorrent freezes after starting

2017-12-29 Thread Alex Dănilă

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

--- Comment #3 from Alex Dănilă <nuor...@gmail.com> ---
It worked, thanks.

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

[ktorrent] [Bug 387368] Ktorrent freezes after starting

2017-12-24 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
Debian bug report with some stack info:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884488

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

[marble] [Bug 214201] Drag stops when the cursor leaves the globe | missing infinite panning (like Gwenview, Okular)

2017-12-09 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #11 from Alex Dănilă <nuor...@gmail.com> ---
You are correct, there are at least 3 functionalities and I was wrong in
closing the bug:

1. Drag to continue after leaving the widget/window (which I think I originally
reported, and for which I closed the bug);

2. Drag to continue after leaving the globe surface;

3. Drag to continue after the cursor hits the screen edge.

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

[marble] [Bug 387731] New: Crash when dragging the map very fast

2017-12-09 Thread Alex Dănilă

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

Bug ID: 387731
   Summary: Crash when dragging the map very fast
   Product: marble
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.13.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
This is a one time crash. I dragged the map (OpenStreetMap) very fast and
Marble crashed. Trying again did not replicate the crash.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f48d6008140 (LWP 31907))]

Thread 14 (Thread 0x7f47faffd700 (LWP 27170)):
#0  0x7f48cb72fb0c in futex_reltimed_wait_cancelable (private=, reltime=0x7f47faffcb10, expected=0, futex_word=0x7f4818004550) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f48cb72fb0c in __pthread_cond_wait_common (abstime=0x7f47faffcbd0,
mutex=0x7f4818004500, cond=0x7f4818004528) at pthread_cond_wait.c:533
#2  0x7f48cb72fb0c in __pthread_cond_timedwait (cond=0x7f4818004528,
mutex=0x7f4818004500, abstime=0x7f47faffcbd0) at pthread_cond_wait.c:667
#3  0x7f48d1c2d588 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f48d1c287cc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f48d1c2c29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f48cb729518 in start_thread (arg=0x7f47faffd700) at
pthread_create.c:465
#7  0x7f48d132a97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f48227fc700 (LWP 27169)):
#0  0x7f48cb72fb0c in futex_reltimed_wait_cancelable (private=, reltime=0x7f48227fbb10, expected=0, futex_word=0x55bea41371f0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f48cb72fb0c in __pthread_cond_wait_common (abstime=0x7f48227fbbd0,
mutex=0x55bea41371a0, cond=0x55bea41371c8) at pthread_cond_wait.c:533
#2  0x7f48cb72fb0c in __pthread_cond_timedwait (cond=0x55bea41371c8,
mutex=0x55bea41371a0, abstime=0x7f48227fbbd0) at pthread_cond_wait.c:667
#3  0x7f48d1c2d588 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f48d1c287cc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f48d1c2c29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f48cb729518 in start_thread (arg=0x7f48227fc700) at
pthread_create.c:465
#7  0x7f48d132a97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f48237fe700 (LWP 465)):
#0  0x7f48c964d5a9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f48c9608258 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f48d1e6241b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f48d1e07dba in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f48d1c273ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f48d1c2c29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f48cb729518 in start_thread (arg=0x7f48237fe700) at
pthread_create.c:465
#7  0x7f48d132a97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f485dc70700 (LWP 31921)):
#0  0x7f48cb72f7dd in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f48a0cf0d3c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f48cb72f7dd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f48a0cf0ce8, cond=0x7f48a0cf0d10) at pthread_cond_wait.c:502
#2  0x7f48cb72f7dd in __pthread_cond_wait (cond=0x7f48a0cf0d10,
mutex=0x7f48a0cf0ce8) at pthread_cond_wait.c:655
#3  0x7f48cf926243 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#4  0x7f48cfc6cd91 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7f48cb729518 in start_thread (arg=0x7f485dc70700) at
pthread_create.c:465
#6  0x7f48d132a97f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f485e471700 (LWP 31920)):
#0  0x7f48cb72f7dd in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f48a0cf0d3c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f48cb72f7dd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f48a0cf0ce8, cond=0x7f48a0cf0d10) at pthread_cond_wait.c:502
#2  0x7f48cb72f7dd in __pthread_cond_wait (cond=0x7f48a0cf0d10,

[kwin] [Bug 387469] Compositing does not work with Nouveau

2017-12-01 Thread Alex Dănilă

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

--- Comment #2 from Alex Dănilă <nuor...@gmail.com> ---
(In reply to Martin Flöser from comment #1)
> I'm sorry but this is a rather corner case setup and we don't implement new
> features on X11.

Not to disagree with the wontfix solution, but what is the new feature that
should be implemented?

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

[plasma4] [Bug 279528] Some tray icons (non KDE4) get hidden "beneath" the panel

2017-11-30 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
Doesn't reproduce anymore.

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

[marble] [Bug 337141] Crash on close

2017-11-30 Thread Alex Dănilă

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

--- Comment #2 from Alex Dănilă <nuor...@gmail.com> ---
Marble hasn't crashed since a long time, can be closed.

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

[marble] [Bug 214201] Drag stops when the cursor leaves the globe | missing infinite panning (like Gwenview, Okular)

2017-11-30 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Alex Dănilă <nuor...@gmail.com> ---
Hi, this feature is implemented since long ago. I'll mark it as Resolved.

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

[kwin] [Bug 387469] New: Compositing does not work with Nouveau

2017-11-30 Thread Alex Dănilă

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

Bug ID: 387469
   Summary: Compositing does not work with Nouveau
   Product: kwin
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

On a laptop with both integrated Intel and an Nvidia card, Kwin cannot enable
OpenGL compositing on the Nouveau driver. OpenGL compositing also works when
using the integrated Intel. OpenGL compositing also used to work with the
Nvidia drivers, but broke sometime this year.

Devices:
$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 3 outputs: 4 associated providers: 1 name:modesetting
Provider 1: id: 0x5f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs:
0 associated providers: 1 name:nouveau

Kwin started under Nouveau:
$ DRI_PRIME=1 kwin --replace &
[3] 1864
alex@debian:~$ OpenGL vendor string:   nouveau
OpenGL renderer string: NV108
OpenGL version string:  4.3 (Core Profile) Mesa 17.3.0-rc5
OpenGL shading language version string: 4.30
Driver: Unknown
GPU class:  Unknown
OpenGL version: 4.3
GLSL version:   4.30
Mesa version:   17.3
X server version:   1.19.5
Linux kernel version:   4.13
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_core: Failed to initialize compositing, compositing disabled
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3127, resource id: 192,
major code: 3 (GetWindowAttributes), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3128, resource id: 192,
major code: 14 (GetGeometry), minor code: 0

Support information:
$ qdbus org.kde.KWin /KWin supportInformation 
Version
===
KWin version: 5.10.5
Qt Version: 5.9.1
Qt compile version: 5.9.1
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11905000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: false
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,5,50,0,0,0,0,0,Regular
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 1
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 750
delayFocusInterval: 100
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 2
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0

[marble] [Bug 386085] New: Crash when setting a bookmark

2017-10-22 Thread Alex Dănilă

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

Bug ID: 386085
   Summary: Crash when setting a bookmark
   Product: marble
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Application: marble (2.0.3 (stable release))

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.13.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Set a bookmark over a city with "Add bookmark" context menu. This happened more
often with the previous version of Marble, but with the current one is the only
time this happened.

- Custom settings of the application:
The map was "Vector OSM".

The crash can be reproduced sometimes.

-- Backtrace:
Application: Marble Virtual Globe (marble), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff620084400 (LWP 8083))]

Thread 14 (Thread 0x7ff589695700 (LWP 17189)):
#0  0x7ff6150e7508 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7ff61bf03588 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7ff61befe7cc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7ff61bf0229d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff6150e1494 in start_thread (arg=0x7ff589695700) at
pthread_create.c:333
#5  0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 13 (Thread 0x7ff55bfff700 (LWP 17184)):
#0  0x7ff6150e7508 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7ff61bf03588 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7ff61befe7cc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7ff61bf0229d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff6150e1494 in start_thread (arg=0x7ff55bfff700) at
pthread_create.c:333
#5  0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 12 (Thread 0x7ff59bfff700 (LWP 8108)):
#0  0x7ff61b5fe6dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff613023230 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff612fdebfb in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff612fdf0c0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff612fdf22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff61c13841b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff61c0dddba in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff61befd3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff61bf0229d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7ff6150e1494 in start_thread (arg=0x7ff59bfff700) at
pthread_create.c:333
#10 0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 11 (Thread 0x7ff5a27fc700 (LWP 8095)):
#0  0x7ff6150e715f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff618d52243 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7ff619098d91 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7ff6150e1494 in start_thread (arg=0x7ff5a27fc700) at
pthread_create.c:333
#4  0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 10 (Thread 0x7ff5a2ffd700 (LWP 8094)):
#0  0x7ff6150e715f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff618d52243 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7ff619098d91 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7ff6150e1494 in start_thread (arg=0x7ff5a2ffd700) at
pthread_create.c:333
#4  0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7ff5a37fe700 (LWP 8093)):
#0  0x7ff6150e715f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff618d52243 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7ff619098d91 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7ff6150e1494 in start_thread (arg=0x7ff5a37fe700) at
pthread_create.c:333
#4  0x7ff61b60babf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7ff5a3fff700 (LWP 8092)):

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2017-05-07 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

Version|5.8.2   |5.8.6

--- Comment #17 from Alex Dănilă <nuor...@gmail.com> ---
I got this happening quite often again with 5.8.6 of Debian. The freezes are
shorter this time, and the „frame back” only stays for very short instant.

I think this _may_ have to do something with the i915 driver. If I run
plasmashell on the discrete Nvidia card ("optirun plasmashell &" details at
https://wiki.debian.org/Bumblebee ), this problem doesn't happen any more.
However, when running with Nvidia plasma has a strange colour tint
notifications have unpainted areas, so I might be comparing apples to oranges.

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

[plasmashell] [Bug 377583] New: High processor usage while taking a snapshot in Back In Time

2017-03-13 Thread Alex Dănilă

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

Bug ID: 377583
   Summary: High processor usage while taking a snapshot in Back
In Time
   Product: plasmashell
   Version: 5.8.5
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: nuor...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Whenever running a back-up in Back In Time Plasmashell will take a core close
to maximum usage.

Steps:
1. Add directory to back-up in Back In Time.
2. Press Snapshot->Take snapshot
3. Open top or KSysGuard or top and notice that process plasmashell takes close
100% of a core, more than the rsync of Back In Time.

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

[akregator] [Bug 377233] New: Deleting a message should select next message below

2017-03-05 Thread Alex Dănilă

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

Bug ID: 377233
   Summary: Deleting a message should select next message below
   Product: akregator
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: ---

When deleting a message Akregator selects the message above the deleted one.
This is the opposite of the usual moving down to the next object, e.g. deleting
a message in Thunderbird moves down (more extreme: pressing delete in text
editor will keep deleting letters from the right of the cursor).

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

[blogilo] [Bug 376636] New: Cannot connect to wordpress.com: Host not found

2017-02-18 Thread Alex Dănilă

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

Bug ID: 376636
   Summary: Cannot connect to wordpress.com: Host not found
   Product: blogilo
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: mehrdad.mom...@gmail.com
  Reporter: nuor...@gmail.com
  Target Milestone: ---

Trying to connect to a wordpress.com blog I get one of the two errors each time
I try to add the blog:

a)Unknown host alecs1.wordpress.com: Host not found
b)access to restricted port in post.

Error b) happened only a couple of time, I can't reproduce any more. I've tried
with both http:// and https:// addresses, the error is the same.

The same address works with QTM.

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

[kaddressbook] [Bug 376610] New: Name changes are not applied in either the names list or the person view

2017-02-18 Thread Alex Dănilă

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

Bug ID: 376610
   Summary: Name changes are not applied in either the names list
or the person view
   Product: kaddressbook
   Version: 5.2.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: nuor...@gmail.com
CC: to...@kde.org
  Target Milestone: ---

Created attachment 104091
  --> https://bugs.kde.org/attachment.cgi?id=104091=edit
Screenshot of KAddressBook showing the correct name only in "Edit Contact"
window

When updating names of people in KAddressBook the changes are saved and appear
correctly in the edit window, but they stay the same in both the people list
(the scroll list with the header "Name") and the contact view.

In the screenshot you can see the person is displayed with "Ceausu", but in the
"Edit Contact" window it is displayed with the corrected family name "Ceaușu".

Seems similar to #371195, but not sure it's the same, as the other bug seems to
request an editor feature.

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

[plasmashell] [Bug 374393] Radeon: Freeze for long periods, until an action like Alt+Shift+F12 wakes it up

2017-01-01 Thread Alex Dănilă

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

--- Comment #2 from Alex Dănilă <nuor...@gmail.com> ---
plasmashell process can be stopped with "kill", there's no need for "kill -9",
I just notice today.

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

[plasmashell] [Bug 374393] Radeon: Freeze for long periods, until an action like Alt+Shift+F12 wakes it up

2016-12-31 Thread Alex Dănilă

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

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
More notes:
- Alt+F2 (Krunner) works correctly during this type of freeze
- right click on the desktop has no effect and the small square with three
lines on the upper left doesn't work (but showing the window list by moving the
cursor in the corner works correctly).

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

[plasmashell] [Bug 374393] New: Radeon: Freeze for long periods, until an action like Alt+Shift+F12 wakes it up

2016-12-31 Thread Alex Dănilă

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

Bug ID: 374393
   Summary: Radeon: Freeze for long periods, until an action like
Alt+Shift+F12 wakes it up
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: 1.0

On 2 laptops with Radeon graphics, all things related to Plasma panel (taskbar,
clock, launcher, tray) freeze for an indefinite period of time; actually hang,
they may start working again. The processor usage stays at 0, and Plasma can
also be triggered to work correctly again:
- press Ctrl+Alt+F1 and Ctrl+Alt+F7 again
- press Alt+shift+f12 to change compositing settings
- restart process plasmashell

Other functions appear to work correctly (Alt+Tab switches windows correctly,
Alt+CapsLock switches the input language, although the indicator remains
still).

May be Radeon related, doesn't happen on other computers with Intel or Nvidia
graphics. Also seems more likely to happen if an video is displayed in a
browser, but may not be relevant.

Both on Debian Testing and Unstable.

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

[systemsettings] [Bug 374150] Crash when opening system settings options then backing out.

2016-12-26 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 CC||nuor...@gmail.com

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
A mee too here. Going back to "all settings" after making a change almost
surely results in crash. I remember going back without crashes, but now I
replicate everytime.
Debian Unstable, 4.8.2.



Application: Configurări de sistem (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6f9bdd48c0 (LWP 2141))]

Thread 6 (Thread 0x7f6f73fff700 (LWP 2155)):
#0  g_mutex_unlock (mutex=0x7f6f6c000990) at ././glib/gthread-posix.c:1348
#1  0x7f6fa254db16 in g_main_context_iteration (context=0x7f6f6c000990,
may_block=) at ././glib/gmain.c:3991
#2  0x7f6fa7d73f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f6fa7d1d8da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6fa7b4b0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fa64cc6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f6fa7b4fda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6fa466b464 in start_thread (arg=0x7f6f73fff700) at
pthread_create.c:333
#8  0x7f6fa74699df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f6f82a3b700 (LWP 2146)):
#0  0x7f6fa746056d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fa254d9f6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f6f7c002e70, timeout=, context=0x7f6f7c000990)
at ././glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f6f7c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
././glib/gmain.c:3924
#3  0x7f6fa254db0c in g_main_context_iteration (context=0x7f6f7c000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f6fa7d73f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fa7d1d8da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6fa7b4b0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6fa64cc6a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6fa7b4fda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6fa466b464 in start_thread (arg=0x7f6f82a3b700) at
pthread_create.c:333
#10 0x7f6fa74699df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f6f8670b700 (LWP 2144)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6f8a9d62bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f6f8a9d6117 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f6fa466b464 in start_thread (arg=0x7f6f8670b700) at
pthread_create.c:333
#4  0x7f6fa74699df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f6f909d9700 (LWP 2143)):
#0  0x7f6fa746056d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fa254d9f6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f6f8c003020, timeout=, context=0x7f6f8c000990)
at ././glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f6f8c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
././glib/gmain.c:3924
#3  0x7f6fa254db0c in g_main_context_iteration (context=0x7f6f8c000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f6fa7d73f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fa7d1d8da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6fa7b4b0f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6faae7f6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f6fa7b4fda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6fa466b464 in start_thread (arg=0x7f6f909d9700) at
pthread_create.c:333
#10 0x7f6fa74699df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f6f99456700 (LWP 2142)):
#0  0x7f6fa746056d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fa4ee5150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6fa4ee6ee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6f9b9b5b69 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f6fa7b4fda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fa466b464 in start_thread (arg=0x7f6f99456700) at
pthread_create.c:333

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-11-05 Thread Alex Dănilă

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #15 from Alex Dănilă <nuor...@gmail.com> ---
I confirm this continues to happen. Only twice in some 8 hours, so it's
intruding a lot less. If there's a way to get some debug information, other
than ssh in the precise seconds this happens, I'll gladly do.

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

[plasmashell] [Bug 372050] New: No scroll in the window of hidden tray entries

2016-11-03 Thread Alex Dănilă

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

Bug ID: 372050
   Summary: No scroll in the window of hidden tray entries
   Product: plasmashell
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: nuor...@gmail.com
  Target Milestone: 1.0

The hidden tray entries (title "Status and Notifications") doesn't react to
scroll over its elements, although it is a scrollable view and shows a
scroollbar.

This happens with both mouse and touchpad. The scrollbar works correctly if
dragged.

Reproduce:
-start lots of programs with tray entries
-select those entries to be hidden
-press the small upwards triangle to trigger the hidden entries window
-move cursor over entries and scroll.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-11-03 Thread Alex Dănilă

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

--- Comment #13 from Alex Dănilă <nuor...@gmail.com> ---
After upgrading Debian to latest Testing (new kernel, KDE and Qt stuff) I don't
see this anymore.

Also, doing ssh precisely during those 5 seconds of freeze looks pretty
difficult. Should this reproduce, I would need an easier method to debug.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-24 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #11 from Alex Dănilă <nuor...@gmail.com> ---
Hi, 
there doesn't seem to be any Intel driver loading. I've attached the entire
file, as it doesn't seem to containing anything private.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-24 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #10 from Alex Dănilă <nuor...@gmail.com> ---
Created attachment 101751
  --> https://bugs.kde.org/attachment.cgi?id=101751=edit
Xorg.0.log

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-24 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #8 from Alex Dănilă <nuor...@gmail.com> ---
Hi,

Unfortunately Xorg.0.log says nothing about possible errors.

Dmesg says at random times things such as:
[9.404406] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun
[9.417934] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
[9.417950] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
[9.468543] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[9.473467] i915 :00:02.0: fb0: inteldrmfb frame buffer device

But it has been saying it for years.

Unfortunately, even after looking on the internet I don't know how to 
determine if this is the modesetting driver or not. One more detail is 
that if I run optirun kwin --replace &, this bug will disappear until 
the next restart.


On 24/10/16 09:03, Martin Gräßlin via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=371537
>
> --- Comment #7 from Martin Gräßlin <mgraess...@kde.org> ---
> are you using the intel xorg driver or the modesettings xorg driver? Can you
> check in dmesg whether you see anything related to the freeze (e.g. hung gpu)?
> Can you check in /var/log/Xorg.0.log for any errors which might be related.
>

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-24 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #6 from Alex Dănilă <nuor...@gmail.com> ---
Correction: the cursor _is_ still movable.

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-23 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #5 from Alex Dănilă <nuor...@gmail.com> ---
KWin. Everything that is displayed, on both displays, follows that 
"frame sequence": f0, f1, f2 (freeze here, f2 shown for 5 seconds), f1, 
f3, f4 . The cursor which is still movable.


On 24/10/16 08:31, Martin Gräßlin via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=371537
>
> --- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
> What I don't really understand from your bug report: is plasma freezing or
> KWin? Is it a problem of just the rendering of the notifications or is e.g.
> glxgears no longer updated as well? Can you still move the mouse cursor while
> the freeze happens?
>

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

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-23 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #3 from Alex Dănilă <nuor...@gmail.com> ---
Version
===
KWin version: 5.8.2
Qt Version: 5.6.1
Qt compile version: 5.6.1
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11804000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme:
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 1
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 750
delayFocusInterval: 100
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 2
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 101
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
-
Name: VGA-1
Geometry: 0,0,2048x1152
Refresh Rate: 59.9087

Screen 1:
-
Name: eDP-1
Geometry: 2048,0,1920x1080
Refresh Rate: 60.0073


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL version string: 3.3 (Core Profile) Mesa 12.0.3
OpenGL platform interface: GLX
OpenGL shading language version string: 3.30
Driver: Intel
GPU class: Haswell
OpenGL version: 3.3
GLSL version: 3.30
Mesa version: 12.0.3
X server version: 1.18.4
Linux kernel version: 4.3
Direct rendering: Requires strict binding: yes
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
slide
screenshot
flipswitch
kwin4_effect_windowaperture
desktopgrid
coverswitch
kwin4_effect_morphingpopups
presentwindows
highlightwindow
kwin4_effect_dialogparent
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 150
fadeOutTime: 250

slide:

screenshot:

flipswitch:
tabBox: false
tabBoxAlternative: false
duration: 200
angle: 30
xPosition: 0.3301311302185
yPosition: 1
windowTitle: true

kwin4_effect_windowaperture:

desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true

coverswitch:
animationDuration: 200
animateSwitch: true
animateStart: true
animateStop: true
reflection: true
windowTitle: true
zPosition: 1353
primaryTabBox: true
secondaryTabBox: false

kwin4_effect_morphingpopups:

presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMin

[kwin] [Bug 371537] Temporary freeze when showing multiple tray notifications

2016-10-23 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #1 from Alex Dănilă <nuor...@gmail.com> ---
Forgotten details:
Computer: ThinkPad Edge E540:
Graphics: 4th Gen Core Processor Integrated Graphics Controller [8086:416]
video module: i915

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

[ksmserver] [Bug 279215] Log-out dialog is visually broken, and has no focus

2016-10-23 Thread Alex Dănilă via KDE Bugzilla

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #8 from Alex Dănilă <nuor...@gmail.com> ---
Please close, this is fixed.

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

[kwin] [Bug 371537] New: Temporary freeze when showing multiple tray notifications

2016-10-23 Thread Alex Dănilă via KDE Bugzilla

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

Bug ID: 371537
   Summary: Temporary freeze when showing multiple tray
notifications
   Product: kwin
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nuor...@gmail.com

The entire screens freeze for some 5 seconds when notifications from the tray
are about to scroll down or disappear. This only affects drawing of screen
content, it doesn't affect sound
or cursor motion.

If relevant, the particular tray notifications are about bluetooth devices. The
particular order is like this:
-two messages (M1 - connection deactivated, M2 - connection timed out) appear
one above the other
-2-3 seconds pass
-freeze for 5 seconds
-M1 disappears, M2 animates going down
-messages reappear and animate again, but without freezes.

When the freeze ends, the first image drawn on the displays is actually a
"frame" before the one seen during the freeze. Suppose we have a sequence of
frames: f0, f1, f2 (freeze here, f2 shown for 5 seconds), f1, f3, f4, etc. 

If plasmashell is stopped, this bug does not happen and the notifications are
shown in small windows at the top of the main screen.

Reproducible: Always




Original bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840141

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

[plasma4] [Bug 349915] Moving the mouse while clicking an entry in the taskbar starts drag instantly (usability)

2016-10-10 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #5 from Alex Dănilă <nuor...@gmail.com> ---
Christoph Feck - indeed, increasing that drag distance has an effect and mostly
solved it for me (20 pixels isn't really that much on these high PPI laptops).

João Vidal - I've only seen the "locked drag" with a laptop's touchpad, never
with a mouse. This behaviour is so elusive.

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

[plasma4] [Bug 289318] Panel with "auto-hide" has a "twin" that is always visible

2016-08-20 Thread Alex Dănilă via KDE Bugzilla

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

Alex Dănilă <nuor...@gmail.com> changed:

   What|Removed |Added

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

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

[plasma4] [Bug 289318] Panel with "auto-hide" has a "twin" that is always visible

2016-08-20 Thread Alex Dănilă via KDE Bugzilla

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

--- Comment #4 from Alex Dănilă <nuor...@gmail.com> ---
I haven't seen this problem for a long time. Bug video reuploaded:
https://www.youtube.com/watch?v=blvm7uMWPY4=youtu.be

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

84 matches

Mail list logo