[kdenlive] [Bug 353537] Can't add multiple clips at once anymore

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |UPSTREAM

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

[kdenlive] [Bug 353537] Can't add multiple clips at once anymore

[Michał via KDE Bugzilla]

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

--- Comment #3 from Michał  ---
Works now 16.04.2. :-)

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

[kdenlive] [Bug 351407] KDE/kactivitymanagerd crashes when moving playhead with mouse

[Michał via KDE Bugzilla]

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

--- Comment #3 from Michał  ---
Tried with the newest version and it doesn't reproduce anymore. :-)

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

[plasmashell] [Bug 365298] New: Flickering display / compositor problem

[Michał via KDE Bugzilla]

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

Bug ID: 365298
   Summary: Flickering display / compositor problem
   Product: plasmashell
   Version: 5.6.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: m...@op.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

Display shows previous and last frames of animation switching between them
randomly.
Example: moving cursor in Dolphin suddenly starts alternating highlights
between two files.
Another example: after writing some text in Vim I see that text appearing and
disappearing.

Video of unminimizing animation when this happened - looks like it started
alternating between two last frames of animation → https://youtu.be/SpZdhF2WVXM

Happens from time to time… every 5 or 15 minutes maybe.
Started happening with Plasma 5.6.5.
Clicking on background image or other kind of interaction with the environment
usually fixes the problem.

Reproducible: Always

Steps to Reproduce:
Do your usual stuff and wait patiently. ;-)



Two monitor setup - one is notebook display - 2.5K, second is external 4K
display. Compositor effects are enabled.
Plasma version is 5.6.5.
Qt version is 5.7.
Graphics card: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
Notebook type: Levono X1 Carbon (version 3)

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

[plasmashell] [Bug 353975] Black screen on second display.

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||m...@op.pl

--- Comment #33 from Michał  ---
This happens to me since I started using Plasma 5, it's still there in
plasma-5.7. It doesn't reproduce immediately, but rather after some time
(0.5…couple of hours). Just like for other users, the background gets black and
is not clickable, but otherwise the other monitor is fully usable.

Killing and restarting plasma helps, until next reproduction after some time.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michał via KDE Bugzilla]

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

--- Comment #100 from Michał  ---
It's possible that there's something wrong with X, but Alberto's hint to
"force" panel to always be on screen in KDE settings made problem disappear for
me. So Plasma somehow must be aware which screen is which. Also, in my case
when panel went to the wrong screen it didn't look like just screen confusion,
since wallpapers stayed on correct screens and the panel didn't "take" the
space on the wrong screen - applications behaved like there wasn't any panel at
all.

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

[plasmashell] [Bug 358244] KDE Plasma 5.5.3 with dual monitor: one screen has no wallpaper but left black on login

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||m...@op.pl

--- Comment #5 from Michał  ---
I have similar issue, but the wallpaper disappears after some time. The screen
gets blank. i'll have to check whether the black background reacts to mouse
clicks.

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

[drkonqi] [Bug 361160] drkonqi crash loop in QInternal::activateCallbacks(QInternal::Callback, void**)

[Michał via KDE Bugzilla]

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

--- Comment #1 from Michał  ---
I played around a bit, installed older Qt, then reinstalled the newer one and
the problem disappeared. So it looks like it was Qt, moreover it could be a
problem with my installation it seems.

Please close.

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

[drkonqi] [Bug 361160] New: drkonqi crash loop in QInternal::activateCallbacks(QInternal::Callback, void**)

[Michał via KDE Bugzilla]

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

Bug ID: 361160
   Summary: drkonqi crash loop in
QInternal::activateCallbacks(QInternal::Callback,
void**)
   Product: drkonqi
   Version: 5.6.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: m...@op.pl

I just updated system to get new Qt hoping that it will eliminate never-ending
crashes of plasmashell. But it looks like with plasma-5.6.1 and Qt-5.6 every
KDE application crashes on exit. It doesn't affect non-KDE apps. DrKonqi gets
into infinite crash-report-crash loop.

It may be a bug in Qt - I have no idea, but some Qt apps that aren't
KDE-related don't have this problem.

Since I didn't know where to report general bug, I chose drkonqi. If possible,
please move it to the right section.

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05d2163800 (LWP 1401))]

Thread 2 (Thread 0x7f05b72fd700 (LWP 1403)):
[KCrash Handler]
#5  0x7f05b688b930 in ?? ()
#6  0x7f05cdee4b52 in QInternal::activateCallbacks(QInternal::Callback,
void**) () from /usr/lib/libQt5Core.so.5
#7  0x7f05ce0d4495 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7f05ce107f97 in QObjectPrivate::setParent_helper(QObject*) () from
/usr/lib/libQt5Core.so.5
#9  0x7f05ce108558 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#10 0x7f05ce10d3e9 in QSocketNotifier::~QSocketNotifier() () from
/usr/lib/libQt5Core.so.5
#11 0x7f05cf5401af in ?? () from /usr/lib/libQt5DBus.so.5
#12 0x7f05cb172583 in _dbus_watch_list_remove_watch () from
/usr/lib/libdbus-1.so.3
#13 0x7f05cb170a1e in ?? () from /usr/lib/libdbus-1.so.3
#14 0x7f05cb170a99 in ?? () from /usr/lib/libdbus-1.so.3
#15 0x7f05cb16f85b in ?? () from /usr/lib/libdbus-1.so.3
#16 0x7f05cb15a422 in ?? () from /usr/lib/libdbus-1.so.3
#17 0x7f05cf542042 in ?? () from /usr/lib/libQt5DBus.so.5
#18 0x7f05cf5421d4 in ?? () from /usr/lib/libQt5DBus.so.5
#19 0x7f05cf5424e9 in ?? () from /usr/lib/libQt5DBus.so.5
#20 0x7f05cf532b0e in ?? () from /usr/lib/libQt5DBus.so.5
#21 0x7f05cdf00de8 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x7f05cb5b2424 in start_thread () from /usr/lib/libpthread.so.0
#23 0x7f05cd81acbd in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f05d2163800 (LWP 1401)):
#0  0x7f05cb5b803f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f05cdf01c8b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f05cdf0099e in QThread::wait(unsigned long) () from
/usr/lib/libQt5Core.so.5
#3  0x7f05cf5328c6 in ?? () from /usr/lib/libQt5DBus.so.5
#4  0x7f05cf532959 in ?? () from /usr/lib/libQt5DBus.so.5
#5  0x7f05cd768c38 in __run_exit_handlers () from /usr/lib/libc.so.6
#6  0x7f05cd768c85 in exit () from /usr/lib/libc.so.6
#7  0x7f05cd753717 in __libc_start_main () from /usr/lib/libc.so.6
#8  0x0041d6c9 in _start ()

I'll try to recompile Qt with debug symbols, but I can't promise it'll work
since the last time I failed to do this.

Reproducible: Always

Steps to Reproduce:
Quit any KDE application.

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

[konsole] [Bug 360424] KPart doesn't remember font/profile settings after restart

[Michał via KDE Bugzilla]

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

--- Comment #1 from Michał  ---
KPart is the module that's also used by Konsole, right?

I tried changing font in Konsole, the same way as described for Yakuake and it
worked with no problem. Restarted Konsole does remember font settings, as
opposed to Yakuake.

In konsolerc I found [DesktopEntry]/DefaultProfile=Fixed.profile, but in
yakuakerc that setting was empty. I added there =Fixed.profile manually and it
seems to work after restart (i.e. I have now the same settings as in Konsole,
which is what I want). So maybe this the bug is specifically about not writing
that setting to yakuakerc file after changes? But where exactly those profiles
are saved?

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

[yakuake] [Bug 360424] New: Yakuake doesn't remember font/profile settings after restart

[Michał via KDE Bugzilla]

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

Bug ID: 360424
   Summary: Yakuake doesn't remember font/profile settings after
restart
   Product: yakuake
   Version: 3.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: m...@op.pl

Yakuake doesn't remember font settings between restarts. Goes to default Oxygen
Mono 7,0.

Reproducible: Always

Steps to Reproduce:
>From popup menu select Edit current profile.
On Appereance tab select Font: Fixed [Misc] and size 6,0.
Press Ok.

Restart Yakuake.

See that font changed back to Oxygen Mono and size 7,0.



>From Yakuake "about" window:
KDE frameworks 5.19.0
Qt 5.5.1
Windowing system "xcb" whatever that means.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michał via KDE Bugzilla]

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

--- Comment #17 from Michał  ---
kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up

Good to know there's nice way to quit plasma as currently I use a keyboard
shortcut to execute "killall -9 plasmashell; plasmashell" :D This works for me
pretty well. ;-)

About fixing the issue, maybe none of developers has DisplayPort, so they can't
really reproduce it to start with?

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

[kio] [Bug 351913] since version 15.08 some file types previews no longer available (pdf for instance)

[Michał via KDE Bugzilla]

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

--- Comment #20 from Michał  ---
I have just installed it *and* I needed to enable previews in menu again
(disable then enable) and it started to work. Thank you. :-)

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

[kio] [Bug 351913] since version 15.08 some file types previews no longer available (pdf for instance)

[Michał via KDE Bugzilla]

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

--- Comment #18 from Michał  ---
I see that this bug is resolved and from last comment I conclude that this
should be fixed in kde-applications 15.12, is this correct?
I have version 15.12 and I still don't have any thumbnails. I rechecked that I
have previews enabled in Dolphin's configuration. Is there anything else I need
to do?

I use Arch Linux.

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

[plasmashell] [Bug 358819] New: Plasmashell - very frequent SIGSEGV when closing any windows

[Michał via KDE Bugzilla]

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

Bug ID: 358819
   Summary: Plasmashell - very frequent SIGSEGV when closing any
windows
   Product: plasmashell
   Version: 5.5.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: m...@op.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.2.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Just closed a window. Or it was closed by an application. Generally closing
windows triggers this bug.

I saw many duplicates posted here, but they didn't have full debugging
information, so I complied plasmashell from AUR (in Arch) to help with
debugging.

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f95a5b39700 (LWP 13067)):
#0  0x7f95bc15918d in poll () from /usr/lib/libc.so.6
#1  0x7f95b90d2fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f95b90d30cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f95bca7c54f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f95bca2357a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f95bc83fbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f95bf158055 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f95bc844b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f95bb9614a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f95bc16213d in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f959d39c700 (LWP 13068)):
#0  0x7f95bc15918d in poll () from /usr/lib/libc.so.6
#1  0x7f95b90d2fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f95b90d30cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f95bca7c54f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f95bca2357a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f95bc83fbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f95bf158055 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f95bc844b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f95bb9614a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f95bc16213d in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f959760c700 (LWP 13069)):
#0  0x7f95bc15918d in poll () from /usr/lib/libc.so.6
#1  0x7f95b90d2fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f95b90d30cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f95bca7c54f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f95bca2357a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f95bc83fbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f95bf158055 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f95bc844b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f95bb9614a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f95bc16213d in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f9595d2f700 (LWP 13070)):
#0  0x7f95bb96707f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f95c1580934 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f95c1580979 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f95bb9614a4 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f95bc16213d in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f950f20f700 (LWP 13071)):
#0  0x7f95bc15918d in poll () from /usr/lib/libc.so.6
#1  0x7f95b90d2fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f95b90d30cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f95bca7c56b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f95bca2357a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f95bc83fbe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f95bfb08136 in ?? () from /usr/lib/libQt5Quick.so.5
#7  0x7f95bc844b8e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f95bb9614a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f95bc16213d in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f94fd636700 (LWP 13083)):
#0  0x7f95bc15918d in poll () from /usr/lib/libc.so.6
#1  0x7f95b90d2fbc in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f95b90d30cc in 

[plasmashell] [Bug 356720] Panel displayed on wrong monitor on login

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||m...@op.pl

--- Comment #1 from Michał  ---
I have exactly same problem. xrandr says that my internal display (of a
notebook) is set as primary, which agrees with what's set in Plasma settings.
But at the moment I connect external monitor through DisplayPort, my only panel
moves to the external monitor.

It's worse when I disconnect external monitor, because sometimes the panel
seems to remain on nonexistent screen. I have to either plugin the monitor
back, unlock widgets, move panel, lock widgets or `killall -9 plasmashell;
plasmashell&`.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||m...@op.pl

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

[plasmashell] [Bug 356553] Panel of one monitor moves to the other monitor after login

[Michał via KDE Bugzilla]

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

--- Comment #2 from Michał  ---
Is there any way to configure how panels should behave when monitors are added
or removed? Can I pinpoint panel to a screen? Can I define what should happen
to a panel if it's on a screen which gets unplugged?

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

[plasmashell] [Bug 356553] Panel of one monitor moves to the other monitor after login

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||m...@op.pl

--- Comment #1 from Michał  ---
I have plasma-workspace 5.5.2

I have very similar problem. I have dual monitor setup, my notebook screen is
set as "primary" in systemsettings, and I have my panel there. When I connect
external monitor via DisplayPort, the panel moves from my notebook screen to my
external monitor. Why? This doesn't always happen, sometimes the panel stays on
my primary (notebook) screen as I want.

Also, when I unplug the external monitor, the panel seems to remain on it, and
it doesn't move back to my notebook screen, at least most of the time. It does
it very rarely.

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

[plasmashell] [Bug 356553] Panel of one monitor moves to the other monitor after login

[Michał via KDE Bugzilla]

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

--- Comment #3 from Michał  ---
Actually I found a better fitting bug for my problem:
https://bugs.kde.org/show_bug.cgi?id=356225

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

[gwenview] [Bug 356599] 15.08.3 Crash in QGraphicsProxyWidget::focusNextPrevChild

[Michał via KDE Bugzilla]

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

--- Comment #2 from Michał  ---
Stopped reproducing in 15.12.0. The CR2 file is now loaded and shown properly.

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

[KScreen] [Bug 350874] After login, my dual head config is stubbornly messed up.

[Michał via KDE Bugzilla]

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

Michał  changed:

   What|Removed |Added

 CC||kice...@gmail.com

--- Comment #2 from Michał  ---
I've same problem: two monitors, before login everything is ok, views are
separated. After login second monitor becomes a clone of the first one and both
monitors are falling back to common resolution.

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

[gwenview] [Bug 356599] New: 15.08.3 Crash in QGraphicsProxyWidget::focusNextPrevChild

[Michał via KDE Bugzilla]

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

Bug ID: 356599
   Summary: 15.08.3 Crash in
QGraphicsProxyWidget::focusNextPrevChild
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: m...@op.pl
CC: myr...@kde.org

Version is 15.08.3
Image attached (CR2 file)

Gwenview shows red message that it could not read Meta Information (kind of
expected).
What's unexpected is that when trying to navigate to the next image, Gwenview
crashes.

GDBed stack trace:
(gdb) run .
Starting program: /usr/bin/gwenview .
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1049700 (LWP 25188)]
[New Thread 0x7fffd7e6e700 (LWP 25191)]
QImageReader::read() using format hint "cr2" failed: "Unsupported image format"
QImageReader::read() without format hint failed: "Unsupported image format"
[New Thread 0x7fffd766d700 (LWP 25192)]
Could not generate thumbnail for file "file:///home/mcv/+gwenview
crash/IMG_7597.CR2"

Program received signal SIGSEGV, Segmentation fault.
0x748479b0 in ?? () from /usr/lib/libQt5Widgets.so.5
(gdb) whe
#0  0x748479b0 in ?? () from /usr/lib/libQt5Widgets.so.5
#1  0x7484cd8f in QGraphicsProxyWidget::focusNextPrevChild(bool) ()
from /usr/lib/libQt5Widgets.so.5
#2  0x74832c0b in QGraphicsItemPrivate::setVisibleHelper(bool, bool,
bool, bool) () from /usr/lib/libQt5Widgets.so.5
#3  0x7484b542 in QGraphicsProxyWidget::eventFilter(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#4  0x7332e75c in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/libQt5Core.so.5
#5  0x7452fffc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#6  0x745354f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#7  0x7332e96b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7456e0a3 in QWidgetPrivate::hide_helper() () from
/usr/lib/libQt5Widgets.so.5
#9  0x74572870 in QWidget::setVisible(bool) () from
/usr/lib/libQt5Widgets.so.5
#10 0x7456e271 in
QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7456e863 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#12 0x7456e939 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#13 0x7484725a in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from
/usr/lib/libQt5Widgets.so.5
#14 0x74847299 in QGraphicsProxyWidget::~QGraphicsProxyWidget() () from
/usr/lib/libQt5Widgets.so.5
#15 0x74838876 in QGraphicsItem::~QGraphicsItem() () from
/usr/lib/libQt5Widgets.so.5
#16 0x74838b03 in QGraphicsObject::~QGraphicsObject() () from
/usr/lib/libQt5Widgets.so.5
#17 0x74888325 in QGraphicsWidget::~QGraphicsWidget() () from
/usr/lib/libQt5Widgets.so.5
#18 0x7768faf9 in Gwenview::DocumentView::~DocumentView() () from
/usr/lib/libgwenviewlib.so.5
#19 0x7335dfc0 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#20 0x7488980b in QGraphicsWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#21 0x7453001c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#22 0x745354f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#23 0x7332e96b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#24 0x73330d66 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#25 0x73384f03 in ?? () from /usr/lib/libQt5Core.so.5
#26 0x7fffec9d4dc7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#27 0x7fffec9d5020 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x7fffec9d50cc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#29 0x7338530f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#30 0x7332c33a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#31 0x733342fc in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#32 0x0043e570 in main ()

Reproducible: Always

Steps to Reproduce:
1. Open attached image
2. Try to navigate to another image in directory (by pressing space or arrows)



Can't attach the image right now, will do it soon (after I get better
connection).

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

[gwenview] [Bug 356599] 15.08.3 Crash in QGraphicsProxyWidget::focusNextPrevChild

[Michał via KDE Bugzilla]

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

--- Comment #1 from Michał  ---
Hmm, I can't upload 22 MB file, beacuse of 4 MB size limit. But I think any CR2
file should do the trick…

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

[kmymoney] [Bug 356399] New: crash while saving file after report change with data loss

[Michał via KDE Bugzilla]

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

Bug ID: 356399
   Summary: crash while saving file after report change with data
loss
   Product: kmymoney
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: kice...@gmail.com

I've edited one of existing report templates (Income and Expenses By Year).
After that I pressed Ctrl+S and it caused application to crash. What is worse
my .kmy file become 0 bytes in size (luckly I had fresh backup).

It happens every time I try to reproduce it.

Reproducible: Always

Steps to Reproduce:
1. edit Income and Expenses By Year report template
2. save kmy file
3. crash

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

[kdevelop] [Bug 355685] Kdevelop C++ parser crash

[Michał via KDE Bugzilla]

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

--- Comment #12 from Michał  ---
@Milian Wolff: I did it before starting KDevelop. My KDevelop was crashing
every time, but then it somehow dealt with the problem and was not crashing
anymore (I guess cache had all the data so there was no need to parse all files
again). To reproduce the problem again I had to remove cache.

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