[valgrind] [Bug 453044] gbserver_tests failures in aarch64

[Jesus Checa]

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

--- Comment #6 from Jesus Checa  ---
(In reply to Paul Floyd from comment #4)
> (In reply to Jesus Checa from comment #3)
> > (In reply to Paul Floyd from comment #2)
> > > Which version of gdb was this with?
> > 
> > This was gdb 8.2
> 
> I just tried building gdb and couldn't reproduce. Quite likely this is due
> to the glibc version. I only have access to systems that are older or newer
> than 2.18. The patch looks safe, I'll do some tests and if nothing breaks
> I'll push it.

Yes this happens with glibc 2.28, but not with newer, for example 2.34. With
glibc 2.28, it reproduces when debuginfo is available, else it doesn't.

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

[valgrind] [Bug 453044] gbserver_tests failures in aarch64

[Jesus Checa]

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

--- Comment #3 from Jesus Checa  ---
(In reply to Paul Floyd from comment #2)
> Which version of gdb was this with?

This was gdb 8.2

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

[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings

[Jesus]

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

--- Comment #17 from Jesus  ---
(In reply to Nate Graham from comment #15)
> This is fixed for Plasma 6.0.3.

Hi Nate, I just updated to version 6.0.3 and I don't see the desktop grid
option in the corner settings, does it have to be activated from somewhere else
or has the change not been applied yet?

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

[kwin] [Bug 482575] Desktop Grid doesn't work, and unavailable

[Jesus]

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

--- Comment #6 from Jesus  ---
(In reply to Nate Graham from comment #3)
> It's called "Grid" now. Does that work? It works for me.
> 
> Does Meta+G work to open the grid?

Yes, Meta+G works but the Grid not appears in the Edges configuration, only
overview but only show one desktop

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

[konsole] [Bug 482215] Konsole crash when trying to open terminal from Dolphin

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||mapatr...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Jesus  ---
The same behavior and error output on archlinux

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

[plasmashell] [Bug 482575] Desktop Grid doesn't work, and unavailable

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||mapatr...@gmail.com

--- Comment #1 from Jesus  ---
Same here with archlinux, but the shortcut Meta+G works but it's uncomfortable

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

[Powerdevil] [Bug 476540] Screens dims but doesn't un-dim after screens were switched off

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||mapatr...@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #6 from Jesus  ---
Same here, AMDGPU and archlinux, plasma 5.27.10 . When the screen goes to sleep
or after a while dims to 30% and have to move the slider to restore the
brightness

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

[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling

[jesus]

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

jesus  changed:

   What|Removed |Added

 CC|kdeb...@ar21.de |

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

[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core

[Jesus]

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

--- Comment #11 from Jesus  ---
Confirmed too, it's fixed in kernel 6.4.8

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

[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core

[Jesus]

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

--- Comment #8 from Jesus  ---
(In reply to Martin Schnitkemper from comment #7)
> (In reply to Jesus from comment #6)
> > The same on arch linux, one core at 100% but htop shows all cores at 0%
> In 'htop' press 'F2', then check in the "Display Options" the option
> "Detailed CPU time", and after that you see the IO-Wait for the core in the
> meters panel. 
> The problem is, that in opposite to other tools like 'htop' the KDE system
> monitor reports IO-Waits as CPU usage; and that should be fixed.

Ok, that shows one core at 100% but in gray color like disabled. Well it's not
a critical bug, it will be fixed when someone who knows how to fix it has time
to do it. Thank you

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

[plasma-systemmonitor] [Bug 472522] Plasma System monitor falsely shows 100% CPU usage on one core

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||mapatr...@gmail.com

--- Comment #6 from Jesus  ---
The same on arch linux, one core at 100% but htop shows all cores at 0%

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

[skrooge] [Bug 471145] Crash on startup KDE/Slackware

[Jesus M Diaz]

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

--- Comment #4 from Jesus M Diaz  ---
You mean trace activation with "export SKGTRACE=XX"?

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

[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling

[jesus]

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

jesus  changed:

   What|Removed |Added

 CC||kdeb...@ar21.de

--- Comment #36 from jesus  ---
I have the same issue still with 23.04.2 on Arch Linux. Display is 4k skaled to
150% connected via Display Port. I am using wayland.

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

[skrooge] [Bug 471145] Crash on startup KDE/Slackware

[Jesus M Diaz]

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

--- Comment #2 from Jesus M Diaz  ---
There's no Skrooge package for Slackware. I compile it from the sources, and
hence it is compiled against the libraries already in the system.

Would you have idea what library could be the issue with? libQt5Core?

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

[skrooge] [Bug 471145] New: Crash on startup KDE/Slackware

[Jesus M Diaz]

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

Bug ID: 471145
   Summary: Crash on startup KDE/Slackware
Classification: Applications
   Product: skrooge
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: jesusm.diazpe...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

Application: skrooge (2.30.0BETA)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.1.31 x86_64
Windowing System: X11
Distribution: Slackware 15.0 x86_64 (post 15.0 -current)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
ALmost every time Skrooge is open, a crash happens, although the application
seems to open fine.
Skrooge built from current source.

The crash can be reproduced every time.

-- Backtrace:
Application: Skrooge (skrooge), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2f257666d8 in SKGMainPanel::processArguments(QStringList const&) ()
at /usr/lib64/libskgbasegui.so.2
#5  0x00405b0b in
QtPrivate::QFunctorSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#6  0x7f2f19eea7e2 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f2f25869ee7 in KDBusService::activateRequested(QStringList const&,
QString const&) () at /usr/lib64/libKF5DBusAddons.so.5
#8  0x7f2f2586c60b in  () at /usr/lib64/libKF5DBusAddons.so.5
#9  0x7f2f2587513d in  () at /usr/lib64/libKF5DBusAddons.so.5
#10 0x7f2f240cdd7b in  () at /usr/lib64/libQt5DBus.so.5
#11 0x7f2f240d1758 in  () at /usr/lib64/libQt5DBus.so.5
#12 0x7f2f240d2115 in  () at /usr/lib64/libQt5DBus.so.5
#13 0x7f2f240d42f8 in  () at /usr/lib64/libQt5DBus.so.5
#14 0x7f2f19edf860 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#15 0x7f2f239703ce in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#16 0x7f2f19eb5598 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#17 0x7f2f19eb8271 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#18 0x7f2f19f0a433 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7f2f1451841d in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#20 0x7f2f145186a8 in  () at /usr/lib64/libglib-2.0.so.0
#21 0x7f2f1451872c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#22 0x7f2f19f09b56 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#23 0x7f2f19eb417b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#24 0x7f2f19ebbc82 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#25 0x00405843 in main ()
[Inferior 1 (process 12641) detached]

Reported using DrKonqi

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

[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||mapatr...@gmail.com

--- Comment #11 from Jesus  ---
The same on Arch Linux and kDE Plasma 5.27.5

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

[valgrind] [Bug 467714] New: fdleak_* and rlimit tests fail when parent process has more than 64 descriptors opened.

[Jesus Checa]

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

Bug ID: 467714
   Summary: fdleak_* and rlimit tests fail when parent process has
more than 64 descriptors opened.
Classification: Developer tools
   Product: valgrind
   Version: 3.19.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

We found out that none/tests/fdleak_* and note/tests/rlimit{,64}_nofile tests
fail if the parent process has more than 64 opened file descriptors.

These tests starts by closing all the inherited descriptors to have a known
state at start/end of the test by calling.
However this macro only closes the range [3,64] as defined in
none/tests/fdleak.h:

#define CLOSE_INHERITED_FDS { int i; for (i = 3; i < 64; i++) close(i); }

It would be great to close up to MAXFDS instead.

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

[skrooge] [Bug 467599] New: Issue with reconciliation of portfolio accounts

[Jesus M Diaz]

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

Bug ID: 467599
   Summary: Issue with reconciliation of portfolio accounts
Classification: Applications
   Product: skrooge
   Version: Trunk from git
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: jesusm.diazpe...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

SUMMARY
***
Following https://forum.kde.org/viewtopic.php?f=210=177371

Broken reconciliation messages don't make sense for portfolio accounts as the
total balance is based on the exchange rate to the base currency.
***

STEPS TO REPRODUCE
1. Reconcile a portfolio account.
2. Download/update units values
3. 

OBSERVED RESULT
Message warning of broken reconciliation

EXPECTED RESULT
Nothing. If the units in the portfolio account remain the same, there should
not be any warning, even if the counter-value in the base currency changed.

SOFTWARE/OS VERSIONS

ADDITIONAL INFORMATION

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

[kio-gdrive] [Bug 467428] New: Expired or missing access tokens for account

[Jesus Delgadillo]

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

Bug ID: 467428
   Summary: Expired or missing access tokens for account
Classification: Frameworks and Libraries
   Product: kio-gdrive
   Version: 22.12.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: jesusdelgadil...@hotmail.com
  Target Milestone: ---

Created attachment 157323
  --> https://bugs.kde.org/attachment.cgi?id=157323=edit
Dolphin displaying the mentioned error.

I recently set 2 google accounts in Dolphin and attempted to access both
Drives. Sometimes it does work and I'm able to traverse folders and access
files, but for a short amount of time, after it I get an "Expired or missing
access tokens for account..." error. After some time without  any interaction,
the refresh button is able to access the Drive and load available files and
folders, but the issue persists and repeats constantly.
***

STEPS TO REPRODUCE
I tried to obtain a little more insight about the problem so I did the
following 
1.  ran 
kioclient5 exec gdrive:/mygoogleacco...@entity.com 
, after it dolphin opened a new instance
2. I traversed the tree.

Terminal throws the following:
kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/gdrive" not
found
"Failed to I/O session data to/from the signon daemon."
kf5.kio.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from
the signon daemon."
"Casting SessionData into subclass failed."
kf5.kio.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass
failed."
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf.kio.core: error() called twice! Please fix the kio_gdrive KIO worker.
kf.kio.core: "Expired or missing access tokens for account
myaccou...@entity.com"
kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the
"kio_gdrive" KIO worker.
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf.kio.core: error() called twice! Please fix the kio_gdrive KIO worker.
kf.kio.core: "Expired or missing access tokens for account
myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf.kio.core: error() called twice! Please fix the kio_gdrive KIO worker.
kf.kio.core: "Expired or missing access tokens for account
myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
org.kde.dolphin: The model is in an inconsistent state.
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
org.kde.dolphin: m_items.count()== 2
org.kde.dolphin: m_itemData.count() == 3
org.kde.dolphin: Multiple items found with the URL
QUrl("gdrive:/myaccou...@entity.com/Shared Drives")
org.kde.dolphin: index 1 : [KFileItem for
QUrl("gdrive:/myaccou...@entity.com/Shared Drives")]
org.kde.dolphin: index 0 : [KFileItem for
QUrl("gdrive:/myaccou...@entity.com/Shared Drives")]
kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the
"kio_gdrive" KIO worker.
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
"Failed to I/O session data to/from the signon daemon."
kf5.kio.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from
the signon daemon."
"Casting SessionData into subclass failed."
kf5.kio.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass
failed."
"Failed to I/O session data to/from the signon daemon."
kf5.kio.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from
the signon daemon."
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf.kio.core: error() called twice! Please fix the kio_gdrive KIO worker.
kf5.kio.gdrive: Expired or missing access/refresh token for account
"myaccou...@entity.com"
kf.kio.core: error() called twice! Please 

[skrooge] [Bug 467153] New: Skrooge crash opening dashboard, after QML dashboard only introduced

[Jesus M Diaz]

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

Bug ID: 467153
   Summary: Skrooge crash opening dashboard, after QML dashboard
only introduced
Classification: Applications
   Product: skrooge
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: jesusm.diazpe...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

Application: skrooge (2.30.0BETA)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.15 x86_64
Windowing System: X11
Distribution: Slackware 15.0 x86_64 (post 15.0 -current)
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = skrooge path = /usr/bin pid = 6416
KCrash: Arguments: /usr/bin/skrooge
KCrash: Attempting to start /usr/lib64/libexec/drkonqi

The crash can be reproduced every time.

-- Backtrace:
Application: Skrooge (skrooge), signal: Segmentation fault

[KCrash Handler]
#4  0x7f188278cdc6 in KCoreConfigSkeleton::findItem(QString const&) const
() at /usr/lib64/libKF5ConfigCore.so.5
#5  0x7f184f44e335 in SKGUnitPlugin::getDashboardWidget(int) () at
/usr/lib64/qt5/plugins/skg_gui/skrooge_unit.so
#6  0x7f184f48887c in SKGDashboardWidget::addItem(SKGInterfacePlugin*, int,
int, QString const&) [clone .part.0] () at
/usr/lib64/qt5/plugins/skg_gui/skg_dashboard.so
#7  0x7f184f4894d2 in SKGDashboardWidget::setState(QString const&) () at
/usr/lib64/qt5/plugins/skg_gui/skg_dashboard.so
#8  0x7f184f486651 in SKGDashboardPluginWidget::setState(QString const&) ()
at /usr/lib64/qt5/plugins/skg_gui/skg_dashboard.so
#9  0x7f1883d77c07 in SKGMainPanel::openPage(SKGInterfacePlugin*, int,
QString const&, QString const&, QString const&, bool) () at
/usr/lib64/libskgbasegui.so.2
#10 0x7f185c053b70 in
SKGBookmarkPluginDockWidget::openBookmark(SKGNodeObject const&, bool, bool) ()
at /usr/lib64/qt5/plugins/skg_gui/skg_bookmark.so
#11 0x7f185c0540b4 in
SKGBookmarkPluginDockWidget::onOpenBookmark(QModelIndex const&) () at
/usr/lib64/qt5/plugins/skg_gui/skg_bookmark.so
#12 0x7f18784ea6a2 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f18821bd752 in QAbstractItemView::pressed(QModelIndex const&) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7f18821c33a6 in QAbstractItemView::mousePressEvent(QMouseEvent*) ()
at /usr/lib64/libQt5Widgets.so.5
#15 0x7f1881faec28 in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7f188205697e in QFrame::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f18784b51eb in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f1881f703be in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f1881f78262 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#20 0x7f18784b5458 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#21 0x7f1881f7640b in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /usr/lib64/libQt5Widgets.so.5
#22 0x7f1881fc6eb9 in  () at /usr/lib64/libQt5Widgets.so.5
#23 0x7f1881fca019 in  () at /usr/lib64/libQt5Widgets.so.5
#24 0x7f1881f703ce in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#25 0x7f18784b5458 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#26 0x7f18791492cc in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib64/libQt5Gui.so.5
#27 0x7f187911df3c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib64/libQt5Gui.so.5
#28 0x7f186f6529ca in  () at /usr/lib64/libQt5XcbQpa.so.5
#29 0x7f1874d1dd79 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#30 0x7f1874d1dfe8 in  () at /usr/lib64/libglib-2.0.so.0
#31 0x7f1874d1e06c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#32 0x7f1878509a16 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#33 0x7f18784b403b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#34 0x7f18784bbb42 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#35 0x00405843 in main ()
[Inferior 1 (process 6028) detached]

Reported using DrKonqi

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

--- Comment #8 from Jesus M Diaz  ---
I sent it to the email address you have here, let's see if you can open it that
way, because it should not be password protected, and I can open it without any
password.

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

--- Comment #6 from Jesus M Diaz  ---
That's what you said for the first file, but I uploaded a second one. Have you
tried with this?

Let me know if you were able to open it or not. If it still fails, I can try
any other way to send you the file.

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

[kwin] [Bug 428357] Night color does not activate after session start

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||mapatr...@gmail.com

--- Comment #7 from Jesus  ---
Same here with Arch Linux, KDE Plasma 5.26.4, this also happens when you
connect a secondary screen, after connect the night color is disabled.

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

[kwin] [Bug 455422] Desktop grid effects flickers on one screen depending on which VD it's opened

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||bonje...@hotmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #5 from Jesus  ---
(In reply to bastimeyer123 from comment #4)
> Looks like a duplicate of BUG 453993

I think it is not the same because in my case in version 5.24 the effect was
smooth and now with 5.25 flickers

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

[kwin] [Bug 455350] Regression in 5.25: present windows can't be deactivated for desktop grid

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||bonje...@hotmail.com

--- Comment #1 from Jesus  ---
It happens to me too, it is not possible to change a single window to another
virtual desktop, it is only possible to move them all, although when you pass
the mouse over one a blue border appears, but when you drag they all move.

Plasma 5.25 and Arch linux

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

[Jesus]

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

--- Comment #77 from Jesus  ---
(In reply to Kishore Gopalakrishnan from comment #70)
> Can someone confirm if disabling Plasma's systemd-based startup fixes the
> issue? To disable it, run
> kwriteconfig5 --file startkderc --group General --key systemdBoot false
> in a terminal and reboot.
> At least for me, session restore seems to work perfectly (remembers which
> virtual desktops and activities windows were on) on X11 when this is
> disabled.

Nothing change with Archlinux Plasma 5.24.5 but for a couple of weeks almost
all the windows remember their position but in the case of dolphin after
restarting, all the windows have the size of the last one I changed the size
of.

Also for dolphin it maintains the same ordering system for all folders even if
it has "remember the display style for each folder" activated. On the other
hand, in the latest updates when you navigate through the directory tree in the
top bar of dolphin, it does not keep the folder it comes from selected. I guess
these last two points are new dolphin bugs and are not related to the problem
of restoring the session.

As for starting windows on the wrong virtual desktops, at least in my case I
have never had this problem.

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

[valgrind] [Bug 453087] New: [ppc64le] nlgone_abrt and nlpasssigalrm test failures in glibc-2.28

[Jesus Checa]

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

Bug ID: 453087
   Summary: [ppc64le] nlgone_abrt and nlpasssigalrm test failures
in glibc-2.28
   Product: valgrind
   Version: 3.19.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

Created attachment 148413
  --> https://bugs.kde.org/attachment.cgi?id=148413=edit
Patch for filter_gdb.in

SUMMARY
nlgone_abrt and nlpasssigalrm gdbserver tests fail in ppc64le, due to an output
mismatch in the gdb end. Both tests has the exact same difference, I'm pasting
only nlgone_abrt diff to keep it shorter:

--- nlgone_abrt.stdoutB.exp 2022-04-11 10:27:12.0 -0400
+++ nlgone_abrt.stdoutB.out 2022-04-26 04:05:08.015213804 -0400
@@ -1,6 +1,7 @@
 Continuing.
 Program received signal SIGABRT, Aborted.
-0x in syscall ...
+kill () at ../sysdeps/unix/syscall-template.S:79
+79 ret
 Continuing.
 Program terminated with signal SIGABRT, Aborted.
 The program no longer exists.

I've found this in a RHEL-8.6 environment, with glibc2.28
(glibc-2.28-189.1.el8.ppc64le) and valgrind 3.18.1. Also checked with valgrind
3.19 and 3.20 compiled from source, and the issue persists.

Apparently this is caused because when glibc debug info is available the
address won't be printed. That causes that filter_gdb cannot replace the line
with the expected anonymized syscall. This gdb's raw output with glibc
debuginfo:
Program received signal SIGABRT, Aborted.
kill () at ../sysdeps/unix/syscall-template.S:79
79  ret
(gdb) (gdb) Continuing.

vs without debuginfo:
Program received signal SIGABRT, Aborted.
0x04939a28 in kill () from /lib64/glibc-hwcaps/power9/libc-2.28.so
(gdb) (gdb) Continuing.

The other mismatch is that filter_gdb expects a T_PSEUDO macro line, but it's
seeing a "ret" instead. It just happens to be the previous line. This is the
code:

 78 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
 79 ret
 80 T_PSEUDO_END (SYSCALL_SYMBOL)

The attached patch for filter_gdb should format the output properly. After
applying it both tests passed.

Still, I'm not sure what the implications of the kill() syscall not showing up
any address, or if it's symptom of an underlying bug.

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

[valgrind] [Bug 453055] New: shared_timed_mutex drd test fails with "Lock shared failed" message

[Jesus Checa]

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

Bug ID: 453055
   Summary: shared_timed_mutex drd test fails with "Lock shared
failed" message
   Product: valgrind
   Version: 3.19.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: drd
  Assignee: bart.vanassche+...@gmail.com
  Reporter: jch...@redhat.com
  Target Milestone: ---

Created attachment 148388
  --> https://bugs.kde.org/attachment.cgi?id=148388=edit
Proposed fix for drd/tests/shared_timed_mutex

SUMMARY
drd/tests/shared_timed_mutex test fails in 3.19.0 during `make regtest`. This
is also reproducible in 3.20.0.GIT:
=
drd/tests/shared_timed_mutex.stderr.diff
=
--- shared_timed_mutex.stderr.exp   2022-04-11 10:27:12.0 -0400
+++ shared_timed_mutex.stderr.out   2022-04-26 03:53:54.116981437 -0400
@@ -1,3 +1,4 @@

+Lock shared failed

 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Running the test without valgrind seems to fail always as well. The problem
seems to come from this code from the test itself:
```
for (i = 0; i < 3 && std::chrono::steady_clock::now() < then; ++i)
{
if (test_mutex.try_lock_shared_until(then))
{
test_mutex.unlock_shared();
}
}
if (i == 3)
{
std::cerr << "Lock shared failed\n";
}
```

IIUIC, variable `i` will always be 3 in this code, hence the test will always
print "Lock shared failed" and will mismatch the expected output.  Adding a
break as in the proposed patch fixes the issue. Tested in rhel-8 in x86_64,
aarch64 and s390x.

STEPS TO REPRODUCE
1. git clone git://sourceware.org/git/valgrind.git
2. cd valgrind && ./autogen.sh && ./configure
3. make -j$(nproc) regtest

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

[valgrind] [Bug 453044] gbserver_tests failures in aarch64

[Jesus Checa]

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

--- Comment #1 from Jesus Checa  ---
Some additional info: The valgrind, kernel and glibc package versions are
these:
kernel-4.18.0-384.el8.aarch64
valgrind-3.19.0-1.el8.aarch64
glibc-2.28-197.el8.aarch64

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

[valgrind] [Bug 453044] New: gbserver_tests failures in aarch64

[Jesus Checa]

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

Bug ID: 453044
   Summary: gbserver_tests failures in aarch64
   Product: valgrind
   Version: 3.19.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

Created attachment 148381
  --> https://bugs.kde.org/attachment.cgi?id=148381=edit
filter_gdb patch to handle "result = SYSCALL_CANCEL" pattern

SUMMARY
mcinfcallWSRU, nlcontrolc and nlvgdbsigqueue tests failed in aarch64 in rhel-8.
The cause is the same in the three tests, an extra line in the output which is
not expected. Using nlcontrolc diff output as example:

=
gdbserver_tests/nlcontrolc.stdoutB.diff
=
--- nlcontrolc.stdoutB.exp  2022-04-11 10:27:12.0 -0400
+++ nlcontrolc.stdoutB.out  2022-04-26 03:44:40.597663940 -0400
@@ -10,12 +10,14 @@
 Continuing.
 Program received signal SIGTRAP, Trace/breakpoint trap.
 0x in syscall ...
+53   result = SYSCALL_CANCEL (pselect6, nfds, readfds, writefds,
exceptfds, tsp,
 * 1 Thread  (tid 1 VgTs_WaitSys)  0x in syscall ...
 $3 = 0
 reset to sleeping parameters
 Continuing.
 Program received signal SIGTRAP, Trace/breakpoint trap.
 0x in syscall ...
+53   result = SYSCALL_CANCEL (pselect6, nfds, readfds, writefds,
exceptfds, tsp,
 * 1 Thread  (tid 1 VgTs_WaitSys)  0x in syscall ...
  > > > >4
 Kill the program being debugged? (y or n) [answered Y; input not from
terminal]

>From glibc's git branch release/2.28/master, the responsible line can be found
in sysdeps/unix/sysv/linux/select.c:53.

Following the same approach as seen in commit 3eba47604df8, adding a new
pattern to gdbserver_tests/filter_gdb.in should suffice. After rerunning with
it, the tests are passing. I'm attaching a proposed patch.

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

[kiofuse] [Bug 446077] VLC player does not stream video from Samba share with kio-fuse

[Jesus]

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

--- Comment #16 from Jesus  ---
(In reply to a.saoutkin from comment #15)
> (In reply to Jesus from comment #14)
> > The same thing happens for a couple of months if you try to play a video
> > through  sftp://  with dolphin, the entire file is downloaded before it
> > starts to play.
> 
> You are referring to this bug which is now fixed:
> https://bugs.kde.org/show_bug.cgi?id=450198

Yes, now it's working again

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

[krita] [Bug 452811] Issue with certain MyPaint brushes

[jesus]

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

--- Comment #1 from jesus  ---
Created attachment 148275
  --> https://bugs.kde.org/attachment.cgi?id=148275=edit
the repetitive pattern of a Ink Pen (mypaint) when using stabilizer after
changing its Slow Tracking parameter to 0

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

[krita] [Bug 452811] New: Issue with certain MyPaint brushes

[jesus]

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

Bug ID: 452811
   Summary: Issue with certain MyPaint brushes
   Product: krita
   Version: 5.0.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: qb-ray_...@hotmail.com
  Target Milestone: ---

Created attachment 148273
  --> https://bugs.kde.org/attachment.cgi?id=148273=edit
here's a screenshot of the affected brushes, strokes made with "stabilizer"
mode, sample count 70

SUMMARY
***
The Pencil 2B and Ink Pen brushes in the MyPaint bundle produce rather
polygonal strokes when using the "Stabilizer" mode even at the lowest "Sample
Count" values.
"Basic" and "Weighted" smoothing modes are unaffected.
This seems to happen regardless of Input device, giving the same result with
tablet or mouse.
This seems to happen with the default brush settings of said presets.
However, changing the affected brushes' Slow Tracking parameter to 0 seems to
apparently fix the issue, although the Ink Pen brush then *suffers a side
effect* from this workaround, producing a repetitive pattern all across a
stroke

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

STEPS TO REPRODUCE
1. Select Pencil 2b (mypaint) or Ink Pen (mypaint) brush
2. Select Stabilizer smoothing mode with a minimum to medium Sample Count value
3. Try making round shapes like spirals or circles, using swift motions

OBSERVED RESULT
Resulting strokes look oddly polygonal

EXPECTED RESULT
Smooth and round strokes, like every other brush does under the same
circumstances

SOFTWARE/OS VERSIONS
Windows: 10 Pro Ver 21H1 (Build 19043.1645)
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Using Wacom CTL-472, driver ver. 6.3.46-1

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

[valgrind] [Bug 451827] [ppc64le] VEX temporary storage exhausted with several vbpermq instructions

[Jesus Checa]

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

--- Comment #4 from Jesus Checa  ---
Hi Carl,

Thanks for the quick patch. I verified it with a fresh valgrind repo and all
looks good now. FTR, these are the steps I followed for the verification:
```
$ gcc reproducer.c -o reproducer # This is the reproducer presented in bug
description
$ curl https://bugsfiles.kde.org/attachment.cgi?id=147709 > vbpermq.patch
$ git clone git://sourceware.org/git/valgrind.git && cd valgrind
$ git apply ../vbpermq.patch
$ ./autogen.sh && ./configure && make -j$(nproc)
$ ./vg-in-place ../reproducer
```

No temporary storage exhausted messages now. To give it a twist, I added a
ridiculously high number of vbpermq instructions (~1000) to the reproducer, and
valgrind still runs perfectly, so the patch is fine from my side.

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

[valgrind] [Bug 451827] New: [ppc64le] VEX temporary storage exhausted with several vbpermq instructions

[Jesus Checa]

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

Bug ID: 451827
   Summary: [ppc64le] VEX temporary storage exhausted with several
vbpermq instructions
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

SUMMARY
Valgrind will fail with "VEX temporary storage exhausted" when running a
ppc64le binary which contains several vbpermq instructions together. The
following C source reproduces the issue:
```
int main(){
asm("vbpermq 6,6,10");
asm("vbpermq 7,7,10");
asm("vbpermq 8,8,10");
// if this doesn't trigger the issue, just copy-paste some asm lines.
return 0;
}
```
Building and running this will produce the following output:
```
# ./vg-in-place ../a.out 
==592850== Memcheck, a memory error detector
==592850== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==592850== Using Valgrind-3.19.0.GIT and LibVEX; rerun with -h for copyright
info
==592850== Command: ../a.out
==592850== 
VEX temporary storage exhausted.
Pool = TEMP,  start 0x598a5528 curr 0x59d5b420 end 0x59d6a067 (size 500)

vex: the `impossible' happened:
   VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 164492400 bytes allocated
vex storage: P total 192 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

host stacktrace:
==592850==at 0x58056FD8: show_sched_status_wrk (m_libcassert.c:406)
==592850==by 0x5805718F: report_and_quit (m_libcassert.c:477)
==592850==by 0x5805740B: panic (m_libcassert.c:553)
==592850==by 0x5805740B: vgPlain_core_panic_at (m_libcassert.c:558)
==592850==by 0x5805745B: vgPlain_core_panic (m_libcassert.c:563)
==592850==by 0x58076D37: failure_exit (m_translate.c:761)
==592850==by 0x581867FB: vpanic (main_util.c:253)
==592850==by 0x581868AB: private_LibVEX_alloc_OOM (main_util.c:181)
==592850==by 0x5827C0C3: LibVEX_Alloc_inline (main_util.h:176)
==592850==by 0x5827C0C3: addHInstr_SLOW (host_generic_regs.c:332)
==592850==by 0x58250F7F: addHInstr (host_generic_regs.h:402)
==592850==by 0x58252B8B: emit_instr (host_generic_reg_alloc3.c:301)
==592850==by 0x58252B8B: doRegisterAllocation_v3
(host_generic_reg_alloc3.c:1320)
==592850==by 0x58183FE3: libvex_BackEnd (main_main.c:1133)
==592850==by 0x58183FE3: LibVEX_Translate (main_main.c:1236)
==592850==by 0x5807A82F: vgPlain_translate (m_translate.c:1831)
==592850==by 0x580CD1FB: handle_tt_miss (scheduler.c:1141)
==592850==by 0x580CD1FB: vgPlain_scheduler (scheduler.c:1503)
==592850==by 0x5812209F: thread_wrapper (syswrap-linux.c:101)
==592850==by 0x5812209F: run_a_thread_NORETURN (syswrap-linux.c:154)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 592850)
==592850==at 0x15CC: main (in /root/a.out)
client stack range: [0x1FFEFF 0x1FFF00] client SP: 0x1FFF00E740
valgrind stack range: [0x1002DF 0x1002EE] top usage: 15728 of 1048576
```

Originally found in rhel-9 with valgrind 3.18.1, but reproducible in fresh git
build (see https://bugzilla.redhat.com/show_bug.cgi?id=2067187)

I found this similar to this already fixed issue:
https://bugs.kde.org/show_bug.cgi?id=375839

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

[dolphin] [Bug 441401] Since the latest version, when a video is played through sftp from a server, the streaming does not work, instead the entire file is downloaded and then played.

[Jesus]

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

Jesus  changed:

   What|Removed |Added

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

--- Comment #1 from Jesus  ---
Since the last update it works again so I'm going to change the status to
resolved.

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

[valgrind] [Bug 450962] helgrind reports false races for printfs using mempcpy manipulating FILE* state in glibc-2.26+

[Jesus Checa]

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

--- Comment #1 from Jesus Checa  ---
Created attachment 147188
  --> https://bugs.kde.org/attachment.cgi?id=147188=edit
Patch adding suppression + testcase

Attaching a patch that adds the corresponding suppression and a testcase with
Mark Wielaard's reproducer from bug 352130

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

[valgrind] [Bug 450962] New: helgrind reports false races for printfs using mempcpy manipulating FILE* state in glibc-2.26+

[Jesus Checa]

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

Bug ID: 450962
   Summary: helgrind reports false races for printfs using mempcpy
manipulating FILE* state in glibc-2.26+
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: helgrind
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

Created attachment 147187
  --> https://bugs.kde.org/attachment.cgi?id=147187=edit
valgrind run in RHEL 8.5 with glibc 2.28

Description of the issue:

Helgrind reports again false races for printfs as described in bug 352130. This
happens in newer glibc versions.
More specifically I've reproduced this in RHEL-8.5 with
glibc-2.28-164.el8.x86_64 and valgrind-3.17.0-5.el8.x86_64,
and also in Fedora 34 with glibc-2.33-21.fc34.x86_64 and
valgrind-3.18.1-1.fc34.x86_64.

In RHEL-8.5 (with glibc 2.28) I've built and run the reproducer that Mark wrote
originally in bug 352130,
which produces the output shown in the attachment.

It seems that in newer glibc versions mempcpy is used instead __GI_mempcpy,
making
the suppresion from the original bug obsolete. I tracked down the changes to
__GI_mempcpy to the following glibc's commit:
commit 5c3e322d3be3803636e38bcaf083fb59b3a34f0c
Author: H.J. Lu 
Date:   Wed Jun 14 12:10:57 2017 -0700

x86-64: Implement memmove family IFUNC selectors in C

Implement memmove family IFUNC selectors in C.

All internal calls within libc.so can use IFUNC on x86-64 since unlike
x86, x86-64 supports PC-relative addressing to access the GOT entry so
that it can call via PLT without using an extra register.  For libc.a,
we can't use IFUNC for functions which are called before IFUNC has been
initialized.  Use IFUNC internally reduces the icache footprint since
libc.so and other codes in the process use the same implementations.
This patch uses IFUNC for memmove family functions within libc.

>From there, in glibc repo:
$ git branch --contains 5c3e322d3be3803636e38bcaf083fb59b3a34f0c
  master
  release/2.26/master
  release/2.27/master
  release/2.28/master
  release/2.29/master
  release/2.30/master
  release/2.31/master
  release/2.32/master
  release/2.33/master
  release/2.34/master

To check my assumption, I grabbed glibc 2.25 and 2.26 sources, and
built/installed
into /opt/glibc-2.2[5|6], built the reproducer and patched the elf to use my
custom
built glibc:
[root@localhost ~]# gcc -g t.c -o t -lpthread
[root@localhost ~]# cp t t-glibc2.25
[root@localhost ~]# cp t t-glibc2.26
[root@localhost ~]# patchelf --set-interpreter
/opt/glibc-2.25/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc-2.25/lib
t-glibc2.25
[root@localhost ~]# patchelf --set-interpreter
/opt/glibc-2.26/lib/ld-linux-x86-64.so.2 --set-rpath /opt/glibc-2.26/lib
t-glibc2.26
[root@localhost ~]# ldd t-glibc2.2{5,6}
t-glibc2.25:
linux-vdso.so.1 (0x7ffce19ea000)
libpthread.so.0 => /opt/glibc-2.25/lib/libpthread.so.0
(0x7fe09abc3000)
libc.so.6 => /opt/glibc-2.25/lib/libc.so.6 (0x7fe09a824000)
/opt/glibc-2.25/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
(0x7fe09ade1000)
t-glibc2.26:
linux-vdso.so.1 (0x7ffe3a5c3000)
libpthread.so.0 => /opt/glibc-2.26/lib/libpthread.so.0
(0x7f7fa3f38000)
libc.so.6 => /opt/glibc-2.26/lib/libc.so.6 (0x7f7fa3b86000)
/opt/glibc-2.26/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
(0x7f7fa4156000)
[root@localhost ~]# valgrind --tool=helgrind ./t-glibc2.25 > /dev/null
==115881== Helgrind, a thread error detector
==115881== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==115881== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==115881== Command: ./t-glibc2.25
==115881== 
==115881== 
==115881== Use --history-level=approx or =none to gain increased speed, at
==115881== the cost of reduced accuracy of conflicting-access information
==115881== For lists of detected and suppressed errors, rerun with: -s
==115881== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2898 from 51)
[root@localhost ~]# valgrind --tool=helgrind ./t-glibc2.25 > /dev/null  
==115881== Helgrind, a thread error detector
==115881== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.  
==115881== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==115881== Command: ./t-glibc2.25   
==115881==  
==115881==  
==115881== Use --history-level=approx or =none to gain increased speed, at  
==115881== the cost of reduced accuracy of conflicting-access information
==115881== For lists of detected and suppressed errors, 

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

[Jesus]

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

--- Comment #54 from Jesus  ---
(In reply to Brian Kaye from comment #53)
> (In reply to Nicolas Pomarede from comment #52)
> > (In reply to Brian Kaye from comment #48)
> > > I think we need a kde developer to get involved, but they seem to be 
> > > quiet on this bug.
> > 
> > same for me, I have the feeling that since it's a known thing that session
> > restore doesn't work properly with wayland, then no one pay attention to
> > this bug.
> > but it has nothing to do with wayland, it's plain X11 that used to work for
> > years (well, maybe some commits to fix wayland broke the X11 case, can't
> > really say), if I get some spare time I could try to look at the ksmserver
> > commits before plasma 5.21 was released.
> > anyway, for me it's major regression since several months / releases, it's
> > sad no one among KDE dev is noticing this ...
> 
> Surely at some point in the development process someone on the development
> team has a test program to verify the contents of .config/session and
> .config/ksmserverrc. Such a program would help to determine whether its is a
> session save or session restore problem.

Surely  it's a session save because I made a copy of the config/session folder
before deleting it to see if that would solve the problem and the other day I
realized that before December 11, 2021 in the files that starting with dolphin*
the information of the position of each window was saved. On day 11 I updated
and from there that information is no longer saved:

DP-3 Height 3840x2160=680
DP-3 Width 3840x2160=1252
DP-3 XPosition 3840x2160=329
DP-3 YPosition 3840x2160=1237

I think it's a dolphin problem since the other programs like konsole or kwrite
save the positions.

I am a C++ programmer but I have no experience in KDE development, even so I
looked at the dolphin commits around that date since it seems that each program
is responsible for saving the session information through the kconfig library.

One reason could be that in order for a window to save its position, it uses
the kconfig library that has the saveWindowPosition method, in this method
there is:

if (!window || QGuiApplication::platformName() == QLatin1String{"wayland"}) {
return;
}

This means that in case the application uses wayland, it does not save the
position information since session restoration is not implemented in wayland.
It may be that due to some change it believes that even if you are using X11 it
believes that it uses Wayland since the other data such as the Tabs are saved.
(I don't know, I'm just guessing)

Looking at the commits from two months before Dec 11 I had no luck, I don't see
any changes that could cause this, I'm stuck.

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

[Jesus]

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

--- Comment #37 from Jesus  ---
(In reply to Brian Kaye from comment #36)
> The issue with the dolphin restarts may have something with the
> dolphin_dolphin_dolphin file in .config/session. That file seems to be
> updated when dolphin is closed and started again. It may be a separate but
> related issue if multiple dolphin windows are restarted at incorrect size(s).
> 
> I have noted in the past that Firefox is restarted in the correct window.
> Since I don't use it often ( I use waterfox) , I did not notice if it was
> the correct size.

Confirmed, it's a dolphin issue. I have done what you said to create a new user
and open several applications on different desktops and the only windows that
have the problem are the dolphin windows.

I thought it also happened with konsole and kwrite but it was because when you
disconnect a second monitor the windows are not in the same place they were
before.

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

[Jesus]

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

--- Comment #34 from Jesus  ---
(In reply to Brian Kaye from comment #32)
> What linux distribution are you using? How many virtual desktops. I have
> found that deleting the .config/session files sometime corrects the problem
> for  one or several login/logouts or not at all. 
> 
> Dolphin also  adds an entry "dolphin_dolphin_dolphin" in .config/session
> when a dolphin window is closed. It seems to be used when dolphin is
> restarted.
> 
> The question still remains is why more people are not having this problem.  
> 
> According to the bug report this problem is assigned to "David Edmunson" .
> Sure wish we could get some suggestions from him.

Sure, more information is better

I use Arch linux on all my computers, on the mini PC I have 4 virtual desktops,
on the laptop I have 9 virtual desktops and on the PC 16 .

I have noticed that on every reboot the stacked dolphin windows are all the
same size and each time the stack of windows is in a different place, it may
have to do with the position of the last window you moved before the reboot.

Session restore had always worked fine until a couple of months ago, I don't
remember the exact date but I remember it was when they announced that they had
improved restoring the position of windows when you disconnect a second
monitor, this may be a good starting point to find the bug.

What is restored correctly is in which virtual desktop each window belongs.

Because I work in several fields at the same time, I am very used to session
restore, this is the main reason why I haven't switched to wayland. 

Thanks to all of you who are working on fixing these bugs, anything you need me
to check or make a change to check if it works, I am at your disposal.

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

[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||bonje...@hotmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #31 from Jesus  ---
It also happens to me on the laptop, on the PC and on a mini PC. On every
reboot I have to sort the windows of each virtual desktop because they are
stacked. Specifically, the dolphin windows are stacked and the rest, like
konsole or kwrite are in different places. I have tried deleting the session
files and although at first it seems to work then it fails again.

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

[valgrind] [Bug 447991] s390x: Valgrind indicates illegal instruction on wflrx

[Jesus Checa]

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

--- Comment #6 from Jesus Checa  ---
(In reply to Andreas Arnez from comment #3)
> Right, m3 == 0 is not a valid format code.  The z/Architecture Principle of
> Operation states:
> 
>   The M3 field specifies the floating-point format.  The floating-point
>   format determines the size of the elements within the second operand.
>   If a reserved value is specified, a specification exception is
>   recognized.
> 
> And then declares the values 3 and 4 as representing the long and extended
> formats, respectively, and all other values as reserved.
> 
> So I'd say that Valgrind is correct in raising a SIGILL for m3 == 0.

Oh, I understand now. Thanks for the clarification!

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

[valgrind] [Bug 447991] s390x: Valgrind indicates illegal instruction on wflrx

[Jesus Checa]

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

Jesus Checa  changed:

   What|Removed |Added

 CC||jch...@redhat.com

--- Comment #2 from Jesus Checa  ---
I've tested this patch with the following source:
-
int main(){
asm("wflrx %v0,%v0,0,0");
return 0 ;
}
-
Built with "gcc -march=z14 main.c -o main" and tested with a valgrind build
that contains this patch. Now valgrind works correctly and doesn't report "IR:
specification exception" anymore.

I wanted to do a bit more in-depth testing and I moved to another instruction,
so I changed my program to this one:
-
int main(){
asm("vflr %v0,%v0,0,0,0");
return 0 ;
}
-
Building and running the same way as the aforementioned, this executable will
make that valgrind prints again a specification exception message such as this:
vex s390->IR: specification exception: E700  00C5
==52001== valgrind: Unrecognised instruction at address 0x1000558.

Checking s390x opcodes, it feels like s390_irgen_VFLR  is missing the case for
when m3 == 0 (provided my inline asm is right).

I did the same test with VFLL (e700  xxc4) opcodes with the same result,
VFLL instruction makes valgrind report a specification exception, whereas
VFLLS/WFLLS/WFLLD instructions work correctly.

FTR, this is the link where I checked the opcodes:
https://fossies.org/linux/binutils/opcodes/s390-opc.txt

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

--- Comment #6 from jesus  ---
Created attachment 144889
  --> https://bugs.kde.org/attachment.cgi?id=144889=edit
Ink Pen (mypaint) stroke artifacts with Slow Tracking 0 and Stabilizer

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

--- Comment #5 from jesus  ---
glad to be of help!
there's one more little thing about this issue:
Ink Pen (mypaint) produces slight artifacts when reducing Slow Tracking to 0
and using Stabilizer, it looks like it tries to paint the little round spot it
makes at the beginning of the stroke several times across the stroke, resulting
in a bumpy line.
i'll update with a relevant attachment

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

--- Comment #3 from jesus  ---
hello, your suggestions 1 and 3 didn't seem to offer any noticeable changes,
bad or good

however it looks like changing Slow Tracking to 0 in the affected brushes
solves the problem.
i looked at the parameters you named and switched back and forth between the
presets to see if there was a possible difference in values between them.
For example, "Pencil 1 sketch (mypaint)" had Slow Tracking 0 but "Pencil 2b
(mypaint)" has Slow Tracking 1.03, so i matched it to the former preset's value
of 0 and it works like i wanted now.
in other words, mypaint presets can make polygonal strokes by increasing Slow
Tracking, being the culprit here.
do the reported brushes on your end come with Slow Tracking 0 *by default*?

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

jesus  changed:

   What|Removed |Added

 Attachment #144885|here's a screenshot of the  |here's a screenshot of the
description|affected brushes, strokes   |affected brushes, strokes
   |made with "basic" smoothing |made with "basic" and
   |mode|"weighted" smoothing mode

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

--- Comment #1 from jesus  ---
Created attachment 144886
  --> https://bugs.kde.org/attachment.cgi?id=144886=edit
here's a screenshot of the affected brushes, strokes made with "stabilizer"
mode, sample count 70

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

[krita] [Bug 447562] Issue with certain MyPaint brushes

[jesus]

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

jesus  changed:

   What|Removed |Added

 Attachment #144885|here's a screenshot of the  |here's a screenshot of the
description|affected brushes, strokes   |affected brushes, strokes
   |made with "stabilizer"  |made with "basic" smoothing
   |mode, sample count 70   |mode

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

[krita] [Bug 447562] New: Issue with certain MyPaint brushes

[jesus]

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

Bug ID: 447562
   Summary: Issue with certain MyPaint brushes
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: qb-ray_...@hotmail.com
  Target Milestone: ---

Created attachment 144885
  --> https://bugs.kde.org/attachment.cgi?id=144885=edit
here's a screenshot of the affected brushes, strokes made with "stabilizer"
mode, sample count 70

SUMMARY
***
The Pencil 2B and Ink Pen brushes in the MyPaint bundle produce noticeable
jagged strokes, which look different depending on the Smoothing mode in use,
most notably using the "Stabilizer" mode even at the lowest "Sample Count"
values.
This seems to happen regardless of Input device, giving the same result with
tablet or mouse.
This seems to happen with the default brush settings of said presets.

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

STEPS TO REPRODUCE
1. Select Pencil 2b (mypaint) or Ink Pen (mypaint) brush
2. Select Stabilizer smoothing mode with a minimum to medium Sample Count value
3. Try making round shapes like spirals or circles, using swift motions

OBSERVED RESULT
Resulting strokes look jagged and polygonal

EXPECTED RESULT
Smooth strokes like every other brush does under the same circumstances

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

ADDITIONAL INFORMATION
Using Wacom CTL-472, driver ver. 6.3.45-1

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

[kiofuse] [Bug 446077] VLC player does not stream video from Samba share with kio-fuse

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||bonje...@hotmail.com

--- Comment #14 from Jesus  ---
The same thing happens for a couple of months if you try to play a video
through  sftp://  with dolphin, the entire file is downloaded before it starts
to play.

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

[valgrind] [Bug 446123] New: Segfault when running a program that calls backtrace() [ppc64le]

[Jesus Checa]

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

Bug ID: 446123
   Summary: Segfault when running a program that calls backtrace()
[ppc64le]
   Product: valgrind
   Version: 3.18.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

Packages used:
valgrind-3.18.1-1.el9.ppc64le
gcc-11.2.1-6.el9.ppc64le
glibc-2.34-8.el9.ppc64le
kernel-5.14.0-17.el9.ppc64le

Reproducer:

#include 
#include 

void call_backtrace(){
void * callstack[128];
backtrace(callstack, 128);
}

int main(){
call_backtrace();
return 0;
}


Description of the problem:

I'm seeing a segfault when running a program that calls backtrace() under
valgrind, but not when I run it standalone. The segfault is ppc64le specific, I
doesn't reproduce in other platforms. It seems related to the fact that
valgrind removes the vDSO from the process, but glibc is still checking symbols
related to it.
The glibc code related to the segfault is the following
(sysdeps/powerpc/powerpc64/backtrace.c)

67  static inline bool
68  is_sigtramp_address (void *nip)
69  {
70  #ifdef HAVE_SIGTRAMP_RT64
71if (nip == GLRO (dl_vdso_sigtramp_rt64) ||
72nip == GLRO (dl_vdso_sigtramp_rt64) + 4)
73  return true;
74  #endif
75return false;
76  }
77
78  int
79  __backtrace (void **array, int size)
80  {
81struct layout *current;
82int count;
83
84/* Force gcc to spill LR.  */
85asm volatile ("" : "=l"(current));
86
87/* Get the address on top-of-stack.  */
88asm volatile ("ld %0,0(1)" : "=r"(current));
89
90for ( count = 0;
91 current != NULL &&   count < size;
92 current = current->next, count++)
93  {
94array[count] = current->return_address;
95
96/* Check if the symbol is the signal trampoline and get the
interrupted
97 * symbol address from the trampoline saved area.  */
98if (is_sigtramp_address (current->return_address))
99  {
100   struct signal_frame_64 *sigframe = (struct signal_frame_64*)
current;
101   if (count + 1 == size)
102 break;
103   array[++count] = (void*)
sigframe->uc.uc_mcontext.gp_regs[PT_NIP];
104   current = (void*) sigframe->uc.uc_mcontext.gp_regs[PT_R1];
105 }
106 }
--

In each stack frame the function checks if the return address corresponds to
the signal trampoline by calling is_sigtramp_address (lines 98, 71).
When the program reaches the first of the frames, the return_address is 0x0.
Since valgrind is not holding any vDSO information, the symbol that holds the
signal trampoline is NULL, which causes that is_sigtramp_address returns true
(when it should return false). Then the block in line 99 is executed, filling
"current" with invalid data that will point to invalid memory and cause the
segfault. I ran this using gdb/vgdb:

(gdb) target remote | vgdb
Remote debugging using | vgdb
relaying data between gdb and process 33117
warning: remote target does not support file transfer, attempting to access
files from local filesystem.
Reading symbols from /lib64/ld64.so.2...
0x040016e0 in _start () from /lib64/ld64.so.2
(gdb) b backtrace.c:94
No source file named backtrace.c.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (backtrace.c:94) pending.
(gdb) c
Continuing.

Breakpoint 1, __GI___backtrace (array=0x1fff00e540, size=128) at
../sysdeps/powerpc/powerpc64/backtrace.c:94
94array[count] = current->return_address;
(gdb) p current->return_address
$1 = (void *) 0x1678 
(gdb) c
Continuing.

Breakpoint 1, __GI___backtrace (array=0x1fff00e540, size=128) at
../sysdeps/powerpc/powerpc64/backtrace.c:94
94array[count] = current->return_address;
(gdb) p current->return_address
$2 = (void *) 0x16c0 
(gdb) c
Continuing.

Breakpoint 1, __GI___backtrace (array=0x1fff00e540, size=128) at
../sysdeps/powerpc/powerpc64/backtrace.c:94
94array[count] = current->return_address;
(gdb) p current->return_address
$3 = (void *) 0x4127ca4 <__libc_start_call_main+148>
(gdb) c
Continuing.

Breakpoint 1, __GI___backtrace (array=0x1fff00e540, size=128) at
../sysdeps/powerpc/powerpc64/backtrace.c:94
94array[count] = current->return_address;
(gdb) p current->return_address
$4 = (void *) 0x4127e80 <__libc_start_main_impl+336>
(gdb) c
Continuing.

Breakpoint 1, __GI___backtrace (array=0x1fff00e540, size=128) at

[frameworks-kio] [Bug 442248] webdav ioslave does not implement random access, forcing kio-fuse-accessed files to be read in their entirety, rather than streamed

[Jesus]

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

Jesus  changed:

   What|Removed |Added

 CC||bonje...@hotmail.com

--- Comment #4 from Jesus  ---
I have observed the same behavior with sftp and fish. For a few months, the
entire file is downloaded first and then the video plays

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

[dolphin] [Bug 441401] New: Since the latest version, when a video is played through sftp from a server, the streaming does not work, instead the entire file is downloaded and then played.

[Jesus]

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

Bug ID: 441401
   Summary: Since the latest version, when a video is played
through sftp from a server, the streaming does not
work, instead the entire file is downloaded and then
played.
   Product: dolphin
   Version: 21.08.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bonje...@hotmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Since the latest version, when a video is played through sftp from a server,
the streaming does not work, instead the entire file is downloaded and then
played.

STEPS TO REPRODUCE
1. Type in the dolphin address bar a link of sftp server
2. Go to an address that contains videos 
3. Open a video file (for example with VLC) 

OBSERVED RESULT
Video is downloaded in full before playing 

EXPECTED RESULT
The video should be played by streaming 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux(Last version) kernel 5.13.12
(available in About System)
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
In two of my fully updated computers the same problem occurs but in my laptop
the streaming works, the only difference is that the KDE Frameworks version is
5.84.0 but KDE Plasma is the same 5.22.4 could be that the problem had
something to do with the latest update of the KDE Frameworks 5.85.0

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

[valgrind] [Bug 440670] New: unhandled ppc64le-linux syscall: 252 and unhandled ppc64le-linux syscall:253

[Jesus Checa]

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

Bug ID: 440670
   Summary: unhandled ppc64le-linux syscall: 252 and unhandled
ppc64le-linux syscall:253
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: jch...@redhat.com
  Target Milestone: ---

SUMMARY
Running valgrind with certain programs on Fedora Rawhide will trigger a message
"WARNING: unhandled ppc64le-linux syscall:" for syscalls 252 (statfs64) and 253
(fstatfs64). Reproduced using glibc-2.34-1.fc35.ppc64le and
systemd-249.2-1.fc35.ppc64le

STEPS TO REPRODUCE
1. valgrind --log-file=logfile /usr/bin/busctl --version  /dev/null
2>&1
2. cat logfile

OBSERVED RESULT
==166394== Memcheck, a memory error detector
==166394== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==166394== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==166394== Command: /usr/bin/busctl --version
==166394== Parent PID: 161493
==166394== 
--166394-- WARNING: unhandled ppc64le-linux syscall: 253
--166394-- You may be able to write your own handler.
--166394-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--166394-- Nevertheless we consider this a bug.  Please report
--166394-- it at http://valgrind.org/support/bug_reports.html.
--166394-- WARNING: unhandled ppc64le-linux syscall: 252
--166394-- You may be able to write your own handler.
--166394-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--166394-- Nevertheless we consider this a bug.  Please report
--166394-- it at http://valgrind.org/support/bug_reports.html.
--166394-- WARNING: unhandled ppc64le-linux syscall: 252
--166394-- You may be able to write your own handler.
--166394-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--166394-- Nevertheless we consider this a bug.  Please report
--166394-- it at http://valgrind.org/support/bug_reports.html.
--166394-- WARNING: unhandled ppc64le-linux syscall: 252
--166394-- You may be able to write your own handler.
--166394-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--166394-- Nevertheless we consider this a bug.  Please report
--166394-- it at http://valgrind.org/support/bug_reports.html.
==166394== 
==166394== HEAP SUMMARY:
==166394== in use at exit: 0 bytes in 0 blocks
==166394==   total heap usage: 11 allocs, 11 frees, 13,189 bytes allocated
==166394== 
==166394== All heap blocks were freed -- no leaks are possible
==166394== 
==166394== For lists of detected and suppressed errors, rerun with: -s
==166394== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

EXPECTED RESULT
No warnings about unhandled syscalls should be printed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide


ADDITIONAL INFORMATION

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

[kwin] [Bug 436720] Plasma Composer Activation: The PC takes 90 seconds to restart or shutdown.

[Jesus]

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

--- Comment #1 from Jesus  ---
KDE Plasma Version: 5.20.5
KDE Frameworks Version: KDE Frameworks 5.54.0
Qt Version: Qt 5.11.3 (compiled with 5.11.3)
System window xcb

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

[kwin] [Bug 436720] New: Plasma Composer Activation: The PC takes 90 seconds to restart or shutdown.

[Jesus]

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

Bug ID: 436720
   Summary: Plasma Composer Activation: The PC takes 90 seconds to
restart or shutdown.
   Product: kwin
   Version: 5.20.5
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sug...@movistar.es
  Target Milestone: ---

SUMMARY
In the summary everything is said.

Occurs in Debian 11 (Bullseye - testing). But I suppose it will also happen to
others. It took me almost a month to find out where the culprit was. I have
looked at logs and could not find the cause.

To this day the problem continues. I have verified it on two other PCs that did
not suffer from this problem. Activating the composer the problem also appears
on those PCs.

I have changed the OpenGl 3.1, 2.0 and XRender rendering engine but the same
thing happens.

Fixed temporarily using DefaultTimeoutStopSec = 10s option in
/etc/systemd/system.conf file

My graphics card are a NVIDIA Geforce GTX 690
On the other PC I have a GTX 980 Ti with the same problem.

STEPS TO REPRODUCE
1. Installed Debian 11 Bullseye (actually testing) and KDE Plasma. Graphics
NVIDIA
2. Enable composer (systemd -> Hardware -> Screen and monitor -> Composer ..
Select Enable composer at startup.
3. Exit the session once. Re-login and restart or shut down the PC. 

OBSERVED RESULT
The PC delay 90 seconds to reboot or power off.

EXPECTED RESULT
It should turn off quickly even if the composer is selected.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian 11 Bullseye (testing)/KDE Plasma 5.20.5
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: I do not understand.
Qt Version: Package: qtbase5-dev (5.15.2+dfsg-5)

ADDITIONAL INFORMATION
I have been with this problem for more than a month but they have not solved
it. Debian 11 is about to be released as stable, but it looks like a beta. I
think I should contribute by communicating this problem.

Greetings.

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

[skrooge] [Bug 436081] Help text needs to be escaped

[Jesus M Diaz]

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

Jesus M Diaz  changed:

   What|Removed |Added

 CC||jesusm.diazpe...@gmail.com

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

[skrooge] [Bug 436081] New: Help text needs to be escaped

[Jesus M Diaz]

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

Bug ID: 436081
   Summary: Help text needs to be escaped
   Product: skrooge
   Version: Trunk from git
  Platform: Other
OS: All
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: jesusm.diazpe...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

SUMMARY

In the file skgbankmodeler/sources/org.kde.skrooge-source-exchangerates.desktop

the help text needs to be escaped for "Then, enter the -. Example: if you want BTC in USD, you must enter BTC-USD.".

At the moment the '' and '' cannot be
seen.

Same happens for other languages.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

--- Comment #4 from Jesus M Diaz  ---
Easier way to reproduce: from the dashboard widget, click on settings and then
'open report'.

The values don't match (incomes, the 'loan' transfer)

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

Jesus M Diaz  changed:

   What|Removed |Added

 Attachment #137629|0   |1
is obsolete||

--- Comment #3 from Jesus M Diaz  ---
Created attachment 137642
  --> https://bugs.kde.org/attachment.cgi?id=137642=edit
Sample Skrooge file, second attempt

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

--- Comment #2 from Jesus M Diaz  ---
That's weird. It is not protected and I have downloaded it and it opened fine,
so it's not corrupted apparently.
I uploaded it again, just in case.

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

[skrooge] [Bug 435762] Income widget don't match with Income report

[Jesus M Diaz]

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

Jesus M Diaz  changed:

   What|Removed |Added

 CC||jesusm.diazpe...@gmail.com

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

[skrooge] [Bug 435762] New: Income widget don't match with Income report

[Jesus M Diaz]

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

Bug ID: 435762
   Summary: Income widget don't match with
Income report
   Product: skrooge
   Version: Trunk from git
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: jesusm.diazpe...@gmail.com
CC: steph...@mankowski.fr
  Target Milestone: ---

Created attachment 137629
  --> https://bugs.kde.org/attachment.cgi?id=137629=edit
Sample Skrooge file

SUMMARY

Income widget don't match with Income report.

Payment of a loan as a split transaction: transfer from payment account to loan
account + interest payment as expense.

Dashboard widget tracks the whole transaction as expenditure, showing the two
sub-transactions

Report finds three transactions: the interest payment, the outcome transfer
from the payment account and the income transfer to the loan account.

STEPS TO REPRODUCE
1. Create a loan payment transaction merging two operations: transfer from
payment account to loan account and interest payment as expense.
2. Add Income widget to dashboard for relevant period
3. Open income report for relevant period

OBSERVED RESULT
Income widget don't match with Income report

EXPECTED RESULT
Income widget matching with Income report

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware 14.2 x86_64 (post 14.2 -current)
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: KDE Frameworks 5.81.0
Qt Version: Qt 5.15.2 (built against 5.15.2)

ADDITIONAL INFORMATION

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

[dolphin] [Bug 430142] Change color file being modified by a copy

[Jesus]

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

--- Comment #2 from Jesus  ---
When I dolphin copy large amounts of 4Gb files each, for example, I can
observe how the size of the current file, the one being copied, changes
in the destination directory. When a complete folder is copied, the
files are not copied in order but in the order in which dolphin
considers appropriate, which does not give me an idea of ​​where it is
going. I have to look at the permissions column to know where the new
file is while it is being copied and I get it by observing that the file
has the permissions "rw ---" while it is being copied and then "rw-r
- r - "when it has already been copied.
Therefore, I would like to see that the file being copied has a color
that highlights it in the row in the detailed view (the entire row
colored). It could also be done in another type of view.
It is not a characteristic that is urgent for me. It is only a
suggestion for improvement. This possible feature enhancement should not
slow down the dolphin. If it's going to slow it down, you better forget
my message.
I am Spanish. Sorry for my English (it's from Google translate).

Greetings

El 8/12/20 a las 15:56, Nate Graham escribió:
> https://bugs.kde.org/show_bug.cgi?id=430142
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
>  Status|REPORTED|NEEDSINFO
>Severity|task|wishlist
>  Resolution|--- |WAITINGFORINFO
>  CC||n...@kde.org
>
> --- Comment #1 from Nate Graham  ---
> Can you clarify what you mean by "is being modified"? Modified how? By which
> action? By another app? etc.
>

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

[dolphin] [Bug 430142] New: Change color file being modified by a copy

[Jesus]

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

Bug ID: 430142
   Summary: Change color file being modified by a copy
   Product: dolphin
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sug...@movistar.es
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
I would like dolphin to be able to highlight the file that is being modified
with a color change, for example with a copy in detailed view mode or in any
other view. And that that color could be changed.

I've been waiting for that feature for many years. I have not found any
software that does this. I think it would be a much appreciated feature.

Hello, I am new here. Be patient with me. I have not found where to put my
suggestions.

I am not reporting a bug but a new feature.

Thanks

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: Last versions or Never
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[krita] [Bug 348887] Algunas herramientas por momentos funcional mal o no funcionan.

[jesus]

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

jesus  changed:

   What|Removed |Added

 CC||jesusripc...@gmail.com

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

[kamoso] [Bug 402874] New: Kamoso crashed when starting

[Jesus Antonio Sanchez Antunez]

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

Bug ID: 402874
   Summary: Kamoso crashed when starting
   Product: kamoso
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: je...@jantonio.org
  Target Milestone: ---

Application: kamoso (3.2.3)

Qt Version: 5.12.0
Frameworks Version: 5.53.0
Operating System: Linux 4.20.0-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
I started Kamoso for the first time, but keeps crashing. (I did not have the
Pictures directory).

The crash can be reproduced every time.

-- Backtrace:
Application: Kamoso (kamoso), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f334b621cc0 (LWP 2132))]

Thread 24 (Thread 0x7f32eaffd700 (LWP 2155)):
[KCrash Handler]
#6  0x404ebef1 in  ()
#7  0x7f32ece55a33 in  ()
#8  0x7f32e02c1a70 in  ()
#9  0x7f32eaffc060 in  ()
#10 0x0001 in  ()
#11 0x7f333ad73366 in  () at /usr/lib/libnvidia-glcore.so.415.25
#12 0x7f333ad7df4a in  () at /usr/lib/libnvidia-glcore.so.415.25
#13 0x7f333aeead93 in  () at /usr/lib/libnvidia-glcore.so.415.25
#14 0x7f333aeb64f7 in  () at /usr/lib/libnvidia-glcore.so.415.25
#15 0x7f333aebfc03 in  () at /usr/lib/libnvidia-glcore.so.415.25
#16 0x7f333aec3718 in  () at /usr/lib/libnvidia-glcore.so.415.25
#17 0x7f333aedaa87 in  () at /usr/lib/libnvidia-glcore.so.415.25
#18 0x7f33276b80ce in VideoMaterial::bindTexture(int, unsigned char const*)
() at /usr/lib/gstreamer-1.0/libgstqt5videosink.so
#19 0x7f33276b81ca in VideoMaterial::bind() () at
/usr/lib/gstreamer-1.0/libgstqt5videosink.so
#20 0x7f33276b8869 in
VideoMaterialShader::updateState(QSGMaterialShader::RenderState const&,
QSGMaterial*, QSGMaterial*) () at /usr/lib/gstreamer-1.0/libgstqt5videosink.so
#21 0x7f335260dcd4 in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() at /usr/lib/libQt5Quick.so.5
#22 0x7f335260ee06 in QSGBatchRenderer::Renderer::renderBatches() () at
/usr/lib/libQt5Quick.so.5
#23 0x7f3352614653 in QSGBatchRenderer::Renderer::render() () at
/usr/lib/libQt5Quick.so.5
#24 0x7f3352604a3e in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/libQt5Quick.so.5
#25 0x7f3352604f0c in QSGRenderer::renderScene(unsigned int) () at
/usr/lib/libQt5Quick.so.5
#26 0x7f33526421a0 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at
/usr/lib/libQt5Quick.so.5
#27 0x7f33526a6085 in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /usr/lib/libQt5Quick.so.5
#28 0x7f335264d940 in  () at /usr/lib/libQt5Quick.so.5
#29 0x7f33526516f8 in  () at /usr/lib/libQt5Quick.so.5
#30 0x7f335070a9cc in  () at /usr/lib/libQt5Core.so.5
#31 0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0
#32 0x7f33503d8b23 in clone () at /usr/lib/libc.so.6

Thread 23 (Thread 0x7f32eb7fe700 (LWP 2154)):
#0  0x7f33503d34ed in syscall () at /usr/lib/libc.so.6
#1  0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7f33523216bf in  () at /usr/lib/libgstreamer-1.0.so.0
#3  0x7f335218f4a6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f335219867b in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f33503d8b23 in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f32ebfff700 (LWP 2153)):
#0  0x7f33503d34ed in syscall () at /usr/lib/libc.so.6
#1  0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7f3324b09579 in  () at /usr/lib/libgstapp-1.0.so.0
#3  0x7f334022f811 in  () at /usr/lib/libgstbase-1.0.so.0
#4  0x7f3340232870 in  () at /usr/lib/libgstbase-1.0.so.0
#5  0x7f33523214bb in  () at /usr/lib/libgstreamer-1.0.so.0
#6  0x7f335218f4a6 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7f335219867b in  () at /usr/lib/libglib-2.0.so.0
#8  0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f33503d8b23 in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f330cff9700 (LWP 2152)):
#0  0x7f33503d34ed in syscall () at /usr/lib/libc.so.6
#1  0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7f3326da9460 in  () at /usr/lib/gstreamer-1.0/libgstcoreelements.so
#3  0x7f33523214bb in  () at /usr/lib/libgstreamer-1.0.so.0
#4  0x7f335218f4a6 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f335219867b in  () at /usr/lib/libglib-2.0.so.0
#6  0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f33503d8b23 in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f330d7fa700 (LWP 2151)):
#0  0x7f33503d34ed in syscall () at 

[krita] [Bug 401157] não consegue abrir documentos e fecha instantaneamente

[Denis Willian Pereira de Jesus]

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

Denis Willian Pereira de Jesus  changed:

   What|Removed |Added

  Alias||nenhum, documento, mesmo,
   ||até, novos, criados, pelo,
   ||programa

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

[krita] [Bug 401157] não consegue abrir documentos e fecha instantaneamente

[Denis Willian Pereira de Jesus]

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

Denis Willian Pereira de Jesus  changed:

   What|Removed |Added

  Component|Tools/Transform |Usability

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

[krita] [Bug 401157] não consegue abrir documentos e fecha instantaneamente

[Denis Willian Pereira de Jesus]

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

Denis Willian Pereira de Jesus  changed:

   What|Removed |Added

 CC||dennis.w...@hotmail.com

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

[krita] [Bug 401157] New: não consegue abrir documentos e fecha instantaneamente

[Denis Willian Pereira de Jesus]

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

Bug ID: 401157
   Summary: não consegue abrir documentos e fecha instantaneamente
   Product: krita
   Version: 4.1.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: dennis.w...@hotmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kolourpaint] [Bug 401156] New: não consegue abrir documentos e fecha instantaneamente

[Denis Willian Pereira de Jesus]

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

Bug ID: 401156
   Summary: não consegue abrir documentos e fecha instantaneamente
   Product: kolourpaint
   Version: unspecified
  Platform: Windows CE
OS: Windows CE
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: dennis.w...@hotmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 400224] New: Plasma crashes after try to change the app launcher icon

[Francisco Jesus Oseguera Vega]

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

Bug ID: 400224
   Summary: Plasma crashes after try to change the app launcher
icon
   Product: plasmashell
   Version: 5.14.1
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: franc1sc...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.14.1)

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

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

Trying to change the app launcher icon (with adapta theme).

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f78b0e56700 (LWP 7710)):
#0  0x7f78e7226d94 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f78e71e135e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f78e71e154c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78edc9a53b in QEventDispatcherGlib::processEvents
(this=0x7f78ac000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f78edc3e7fa in QEventLoop::exec (this=this@entry=0x7f78b0e55d40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f78eda69bba in QThread::exec (this=this@entry=0x55795457c2f0) at
thread/qthread.cpp:525
#6  0x7f78f177a4f5 in QQmlThreadPrivate::run (this=0x55795457c2f0) at
qml/ftw/qqmlthread.cpp:148
#7  0x7f78eda74adb in QThreadPrivate::start (arg=0x55795457c2f0) at
thread/qthread_unix.cpp:367
#8  0x7f78ea59c6db in start_thread (arg=0x7f78b0e56700) at
pthread_create.c:463
#9  0x7f78ed36c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f78c0d32700 (LWP 1619)):
#0  0x7f78e7226d94 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f78e71e135e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f78e71e154c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78edc9a53b in QEventDispatcherGlib::processEvents
(this=0x7f78bc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f78edc3e7fa in QEventLoop::exec (this=this@entry=0x7f78c0d31cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f78eda69bba in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f78f1bf5826 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f78eda74adb in QThreadPrivate::start (arg=0x55795443c0b0) at
thread/qthread_unix.cpp:367
#8  0x7f78ea59c6db in start_thread (arg=0x7f78c0d32700) at
pthread_create.c:463
#9  0x7f78ed36c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f78d63c1700 (LWP 1515)):
#0  0x7f78ed35b0b4 in __GI___libc_read (fd=10, buf=0x7f78d63c0b30,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f78e7225a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f78e71e0f27 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78e71e13e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f78e71e154c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f78edc9a53b in QEventDispatcherGlib::processEvents
(this=0x7f78c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f78edc3e7fa in QEventLoop::exec (this=this@entry=0x7f78d63c0d40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#7  0x7f78eda69bba in QThread::exec (this=this@entry=0x5579543acee0) at
thread/qthread.cpp:525
#8  0x7f78f177a4f5 in QQmlThreadPrivate::run (this=0x5579543acee0) at
qml/ftw/qqmlthread.cpp:148
#9  0x7f78eda74adb in QThreadPrivate::start (arg=0x5579543acee0) at
thread/qthread_unix.cpp:367
#10 0x7f78ea59c6db in start_thread (arg=0x7f78d63c1700) at
pthread_create.c:463
#11 0x7f78ed36c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f78d7bfd700 (LWP 1495)):
#0  0x7f78ed35fbf9 in __GI___poll (fds=0x7f78d0004db0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f78e71e1439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f78e71e154c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f78edc9a53b in QEventDispatcherGlib::processEvents
(this=0x7f78db20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f78edc3e7fa in QEventLoop::exec 

[kmail2] [Bug 397088] New: kmail crashes

[Jesus Arocho]

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

Bug ID: 397088
   Summary: kmail crashes
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: yuqu...@verizon.net
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-29-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

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

- Unusual behavior I noticed: Frequent crashes when manipulating emails, delete
or move.  Sometimes system freezes.  Only happens with kmail.  High CPU usage.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb9c7154b80 (LWP 14071))]

Thread 29 (Thread 0x7fb867fff700 (LWP 14141)):
#0  0x7fb9b9b269f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55cbc5f9c418) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fb9b9b269f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55cbc5f9c3c8, cond=0x55cbc5f9c3f0) at pthread_cond_wait.c:502
#2  0x7fb9b9b269f3 in __pthread_cond_wait (cond=0x55cbc5f9c3f0,
mutex=0x55cbc5f9c3c8) at pthread_cond_wait.c:655
#3  0x7fb9ae9c7c95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fb9ae9c8177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fb9ae9c8f11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fb9ae9c55eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fb9b9b206db in start_thread (arg=0x7fb867fff700) at
pthread_create.c:463
#8  0x7fb9c423088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fb8ed428700 (LWP 14140)):
#0  0x7fb9b9b269f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fb9ab290fb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fb9b9b269f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fb9ab290f68, cond=0x7fb9ab290f90) at pthread_cond_wait.c:502
#2  0x7fb9b9b269f3 in __pthread_cond_wait (cond=0x7fb9ab290f90,
mutex=0x7fb9ab290f68) at pthread_cond_wait.c:655
#3  0x7fb9aaf9a5f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7fb9aaf9a639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7fb9b9b206db in start_thread (arg=0x7fb8ed428700) at
pthread_create.c:463
#6  0x7fb9c423088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fb8ef920700 (LWP 14131)):
#0  0x7fb9c4223bf9 in __GI___poll (fds=0x7fb8e8001cb0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fb9b7ecb439 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb9b7ecb54c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb9c4b7190b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb9c4b169ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb9c493522a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb9c493a16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb9b9b206db in start_thread (arg=0x7fb8ef920700) at
pthread_create.c:463
#8  0x7fb9c423088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7fb9257fa700 (LWP 14110)):
#0  0x7fb9c423f6ac in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7fb9c4241474 in ___fprintf_chk (fp=0x7fb9c44fc8b0
<_IO_stdfile_2_lock>, flag=1, format=0x7fb9a59cb6a8 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7fb9a59b39ad in event_logv_ () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7fb9a59b3b44 in event_warn () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#4  0x7fb9a59b546c in  () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#5  0x7fb9a59ab114 in event_base_loop () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#6  0x7fb9ae998ab9 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fb9ae994da8 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fb9ae9b177b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fb9ae9c94d6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7fb9ae9c55eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#11 0x7fb9b9b206db in start_thread (arg=0x7fb9257fa700) at
pthread_create.c:463
#12 0x7fb9c423088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 

[kwin] [Bug 395493] Random Kwin crashes

[Jesus]

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

--- Comment #7 from Jesus  ---
Sure! 

[Compositing]
AnimationSpeed=3
Backend=OpenGL
Enabled=true
GLCore=true
GLPreferBufferSwap=a
GLTextureFilter=2
HiddenPreviews=5
OpenGLIsUnsafe=false
OpenGLIsUnsafe0=false
OpenGLIsUnsafe1=false
WindowsBlockCompositing=true
XRenderSmoothScale=false

[Desktops]
Number=4
Rows=2

[Desktops-screen-1]
Number=1

[Effect-Cube]
BorderActivate=9
BorderActivateCylinder=9
BorderActivateSphere=9

[Effect-DesktopGrid]
BorderActivate=1

[Effect-PresentWindows]
BorderActivate=9
BorderActivateAll=7
BorderActivateClass=9

[Effect-ShowFps]
TextColor=227,65,255
TextFont=Input Serif,24,-1,5,50,0,0,0,0,0,Regular
TextPosition=2

[Effect-Wobbly]
Drag=92
MoveFactor=20
Stiffness=3
WobblynessLevel=3

[Effect-kwin4_effect_translucency]
Dialogs=93
Menus=96

[ElectricBorders]
Bottom=None
BottomLeft=None
BottomRight=None
Left=None
Right=None
Top=None
TopLeft=None
TopRight=None

[MouseBindings]
CommandActiveTitlebar1=Raise
CommandActiveTitlebar2=Start window tab drag
CommandActiveTitlebar3=Operations menu
CommandAll1=Move
CommandAll2=Toggle raise and lower
CommandAll3=Resize
CommandAllKey=Meta
CommandAllWheel=Shade/Unshade
CommandInactiveTitlebar1=Activate and raise
CommandInactiveTitlebar2=Start window tab drag
CommandInactiveTitlebar3=Operations menu
CommandTitlebarWheel=Raise/Lower
CommandWindow1=Activate, raise and pass click
CommandWindow2=Activate and pass click
CommandWindow3=Activate and pass click
CommandWindowWheel=Scroll

[Plugins]
cubeEnabled=true
cubeslideEnabled=false
desktopchangeosdEnabled=false
dimscreenEnabled=true
fallapartEnabled=true
glideEnabled=true
kwin4_effect_eyeonscreenEnabled=true
kwin4_effect_fadedesktopEnabled=false
kwin4_effect_scaleinEnabled=true
magiclampEnabled=true
minimizeanimationEnabled=false
mousemarkEnabled=true
sheetEnabled=true
slideEnabled=true
slidebackEnabled=true
snaphelperEnabled=true
thumbnailasideEnabled=true
touchpointsEnabled=true
windowgeometryEnabled=false
wobblywindowsEnabled=true

[Script-desktopchangeosd]
PopupHideDelay=1000
TextOnly=false

[TabBox]
BorderActivate=9
BorderAlternativeActivate=9
DesktopLayout=org.kde.breeze.desktop
DesktopListLayout=org.kde.breeze.desktop
LayoutName=org.kde.breeze.desktop

[Windows]
ActiveMouseScreen=true
AutoRaise=true
AutoRaiseInterval=1000
AutogroupInForeground=true
AutogroupSimilarWindows=false
BorderSnapZone=10
CenterSnapZone=0
ClickRaise=true
DelayFocusInterval=1000
ElectricBorderCooldown=350
ElectricBorderCornerRatio=0.25
ElectricBorderDelay=150
ElectricBorderMaximize=true
ElectricBorderTiling=true
ElectricBorders=0
FocusPolicy=FocusFollowsMouse
FocusStealingPreventionLevel=2
GeometryTip=false
HideUtilityWindowsForInactive=true
InactiveTabsSkipTaskbar=false
MaximizeButtonLeftClickCommand=Maximize
MaximizeButtonMiddleClickCommand=Maximize (vertical only)
MaximizeButtonRightClickCommand=Maximize (horizontal only)
NextFocusPrefersMouse=true
Placement=Smart
RollOverDesktops=true
SeparateScreenFocus=true
ShadeHover=false
ShadeHoverInterval=250
SnapOnlyWhenOverlapping=false
TitlebarDoubleClickCommand=Maximize
WindowSnapZone=10

[org.kde.kdecoration2]
BorderSize=Normal
ButtonsOnLeft=MHS
ButtonsOnRight=FIAX
CloseOnDoubleClickOnMenu=false
library=org.kde.breeze

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

[kwin] [Bug 395493] Random Kwin crashes

[Jesus]

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

--- Comment #5 from Jesus  ---
Maybe we should close this bug, since I don't know when it's gonna crash again
haha.

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

[kwin] [Bug 395493] Random Kwin crashes

[Jesus]

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

--- Comment #3 from Jesus  ---
I only submitted because the crash dialog said it could be useful. But I could
try compiling with debugging symbols if it's needed.

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

[kwin] [Bug 395493] New: Random Kwin crashes

[Jesus]

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

Bug ID: 395493
   Summary: Random Kwin crashes
   Product: kwin
   Version: 5.13.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jesusbalbas...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.13.0)

Qt Version: 5.11.0
Frameworks Version: 5.47.0
Operating System: Linux 4.14.49-1-lts x86_64
Distribution (Platform): Archlinux Packages

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

Kwin crashes when doing normal things like scrolling though worspaces or
switching activities.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7faed024b840 (LWP 1286))]

Thread 5 (Thread 0x7fae97779700 (LWP 1521)):
#0  0x7faec8c67ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7faecbf2abbc in  () at /usr/lib/libQt5Script.so.5
#2  0x7faecbf2abd9 in  () at /usr/lib/libQt5Script.so.5
#3  0x7faec8c62075 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7faecfc0b53f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7faeaddd3700 (LWP 1501)):
#0  0x7faecfc00fa6 in ppoll () at /usr/lib/libc.so.6
#1  0x7faecd006d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7faecd00820b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7faeccfb685c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7faeccdffac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7faec76aa559 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7faecce09b95 in  () at /usr/lib/libQt5Core.so.5
#7  0x7faec8c62075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7faecfc0b53f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7faeafdf5700 (LWP 1306)):
#0  0x7faecfc00fa6 in ppoll () at /usr/lib/libc.so.6
#1  0x7faecd006d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7faecd00820b in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7faeccfb685c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7faeccdffac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7faec659c976 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7faecce09b95 in  () at /usr/lib/libQt5Core.so.5
#7  0x7faec8c62075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7faecfc0b53f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7faeb6366700 (LWP 1292)):
#0  0x7faecfc00ea9 in poll () at /usr/lib/libc.so.6
#1  0x7faeceb24180 in  () at /usr/lib/libxcb.so.1
#2  0x7faeceb25e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7faeb7454f1a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7faecce09b95 in  () at /usr/lib/libQt5Core.so.5
#5  0x7faec8c62075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7faecfc0b53f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7faed024b840 (LWP 1286)):
[KCrash Handler]
#6  0x7faecfb4986b in raise () at /usr/lib/libc.so.6
#7  0x7faecfb3440e in abort () at /usr/lib/libc.so.6
#8  0x7faeccdc633c in  () at /usr/lib/libQt5Core.so.5
#9  0x7faecc79cd4a in KWin::WindowQuad::makeSubQuad(double, double, double,
double) const () at /usr/lib/libkwineffects.so.11
#10 0x7fae9fdeba6d in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#11 0x7fae9fdebbcc in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#12 0x7fae9fdf4d73 in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#13 0x7fae9fdf4eb9 in  () at
/usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#14 0x7faecf792aac in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#15 0x7faecc535426 in  () at /usr/lib/libkwin4_effect_builtins.so.1
#16 0x7faecf792a44 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#17 0x7faecc4a218a in  () at /usr/lib/libkwin4_effect_builtins.so.1
#18 0x7faecf792a44 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#19 0x7faecc79949d in KWin::Effect::drawWindow(KWin::EffectWindow*, int,
QRegion, KWin::WindowPaintData&) () at /usr/lib/libkwineffects.so.11
#20 0x7faecf792a44 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () at /usr/lib/libkwin.so.5
#21 0x7faecc79949d in 

[kaffeine] [Bug 394000] When starting Kaffeine with more than 2 parameters, only the last parameter is used.

[Jesus]

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

Jesus <jesusbalbas...@gmail.com> changed:

   What|Removed |Added

 CC||jesusbalbas...@gmail.com

--- Comment #2 from Jesus <jesusbalbas...@gmail.com> ---
*** Bug 394027 has been marked as a duplicate of this bug. ***

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

[kaffeine] [Bug 394027] Fullscreen and minimal flags don't work with lastchannel

[Jesus]

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

Jesus <jesusbalbas...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #3 from Jesus <jesusbalbas...@gmail.com> ---


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

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

[kaffeine] [Bug 394027] Fullscreen and minimal flags don't work with lastchannel

[Jesus]

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

--- Comment #2 from Jesus <jesusbalbas...@gmail.com> ---
Thanks, it is. 
That's so crazy, I first noticed this bug about a month ago but only just made
the report.

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

[kaffeine] [Bug 394027] New: Fullscreen and minimal flags don't work with lastchannel

[Jesus]

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

Bug ID: 394027
   Summary: Fullscreen and minimal flags don't work with
lastchannel
   Product: kaffeine
   Version: 2.0.15
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: jesusbalbas...@gmail.com
  Target Milestone: ---

Running kaffeine with the flag lastchannel prevents the fullscreen and minimal
flags to work.

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

[digikam] [Bug 381026] New: Plugin piwigo not sort albums

[jesus]

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

Bug ID: 381026
   Summary: Plugin piwigo not sort albums
   Product: digikam
   Version: 5.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: je...@mieresdelcamin.es
  Target Milestone: ---

Created attachment 106011
  --> https://bugs.kde.org/attachment.cgi?id=106011=edit
Piwigo window

With the piwigo plugin does not get the list of alphabetically ordered albums,
are obtained by date of pcreation. Is it possible to do it alphabetically in
some way?

Best regards.

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

[digikam] [Bug 380949] Bad quality image view

[jesus]

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

--- Comment #5 from je...@mieresdelcamin.es  ---
(In reply to caulier.gilles from comment #4)
> No, please show me the difference on your computer. We don't have the smae
> configuration and your one sound like older than mine. This can explain the
> difference.
> 
> Also, please test with digiKam 5.6.0 AppImage on your computer. There is
> more than 4 years of development between 4.12 and 5.6. This is just huge in
> open source world.
> 
> Thanks in advance
> 
> Gilles Caulier

Ok, with new version is good.

Thanks!!!

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

[digikam] [Bug 380949] Bad quality image view

[jesus]

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

je...@mieresdelcamin.es  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #3 from je...@mieresdelcamin.es  ---
(In reply to Christoph Feck from comment #2)
> Note the different file names at the window title. The bug reporter used the
> gwenview application to display both screen shots side by side.

Ok,in this link you can dowload the photo,

http://coyacios.es/piwigo/picture.php?/1771/category/339

try to see in digikam and gwenview

Best regards.

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

[digikam] [Bug 380949] New: Bad quality image view

[jesus]

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

Bug ID: 380949
   Summary: Bad quality image view
   Product: digikam
   Version: 4.12.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ImageEditor
  Assignee: digikam-de...@kde.org
  Reporter: je...@mieresdelcamin.es
  Target Milestone: ---

Created attachment 105969
  --> https://bugs.kde.org/attachment.cgi?id=105969=edit
the same image in digikam and gwenview

the image is bad quality

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

[digikam] [Bug 380949] Bad quality image view

[jesus]

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

je...@mieresdelcamin.es  changed:

   What|Removed |Added

Version|4.12.0  |unspecified
  Latest Commit||v.4.4.0

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