[ktorrent] [Bug 493771] New: ktorrent does not play sound on event

2024-09-28 Thread Antonin
https://bugs.kde.org/show_bug.cgi?id=493771

Bug ID: 493771
   Summary: ktorrent does not play sound on event
Classification: Applications
   Product: ktorrent
   Version: 24.08.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: antonin.vec...@gmail.com
  Target Milestone: ---

SUMMARY

When I assign sound to any event (for example "Torrent has finished
downloading") the sound is not played.

STEPS TO REPRODUCE
1. Settings
2. Configure Notifications
3. for event "Torrent has finished downloading" set any sound

OBSERVED RESULT
no sound

EXPECTED RESULT
the sound is played

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.11-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4250U CPU @ 1.30GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5000

ADDITIONAL INFORMATION
Tested on Fedora Kionite 40 and also in virtual pc with Fedora KDE Live 40.
KTorrent was installed as flatpak.

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

[ktorrent] [Bug 493771] ktorrent does not play sound on event

2025-01-24 Thread Antonin
https://bugs.kde.org/show_bug.cgi?id=493771

--- Comment #1 from Antonin  ---
After several updates it works now.

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

[ktorrent] [Bug 493771] ktorrent does not play sound on event

2025-01-24 Thread Antonin
https://bugs.kde.org/show_bug.cgi?id=493771

Antonin  changed:

   What|Removed |Added

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

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

[kdeconnect] [Bug 418074] KDE Connect crashed sometimes when sharing files from Android

2023-10-16 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=418074

Antonin Roussel  changed:

   What|Removed |Added

 CC||antonin.rous...@laposte.net

--- Comment #3 from Antonin Roussel  ---
Hi, same bug for me. 

It looks to happen only when a multiple files selection from the Android device
is shared. Single file transfer looks fine.
If transfer happens to hang, Dolphin may hang too.

Problem, once the multiple files transfer failed, Dolphin is badly responding.
For instance impossible to rename a file through context menu.
This Dolphin bogus behaviour lasts for hours, maybe for ever ?

WORKAROUND
1- Kill kdeconnect daemon : kdeconnectd
For instance :
- from terminal, top, k
- from desktop Alt+F2, killall kdeconnectd
2- launch KDE Connect from desktop
3- everything is fine again

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Mageia Linux 8
package kdeconnect-kde-20.12.0-1.mga8.x86_64
KDE Plasma Version: 5.17.5-2
KDE Frameworks 5.76.0
Qt 5.15.2 (construit sur 5.15.2)
Le système de fenêtres xcb

Interacting with /e/OS 1.15-s-20230913330639-stable-FP4 (Android 12)

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

[gwenview] [Bug 432094] New: XMP and IPTC metadata loss when rotating image jpg

2021-01-25 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=432094

Bug ID: 432094
   Summary: XMP and IPTC metadata loss when rotating image jpg
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Mageia RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: antonin.rous...@laposte.net
  Target Milestone: ---

Created attachment 135164
  --> https://bugs.kde.org/attachment.cgi?id=135164&action=edit
Comparing exiftool -g file.jpg outputs

SUMMARY
using jbrout and exiftool to tag (and read)
XMP and IPTC metadata loss when rotating image jpg
I will now be aware

STEPS TO REPRODUCE
1. tag
2. read
2. rotate
3. read

OBSERVED RESULT
IPTC and XMP metadata are gone

EXPECTED RESULT
height, width, size and a little bit more expected to change

SOFTWARE/OS VERSIONS
Gwenview: gwenview-19.04.0-2.mga7.x86_64
Linux/KDE Plasma: Mageia 7 - 5.10.8-desktop-2.mga7
KDE Plasma Version: kdeplasma-addons-5.15.4-1.mga7.x86_64
KDE Frameworks 5.57.0
Qt 5.12.6 (construit sur 5.12.2)
Le système de fenêtres xcb

ADDITIONAL INFORMATION

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

[gwenview] [Bug 432094] XMP and IPTC metadata loss when rotating image jpg

2021-01-25 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=432094

--- Comment #1 from Antonin Roussel  ---
close to bug 278661

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

[krdc] [Bug 359992] Krdc crashed on quit - LXDE desktop

2018-11-02 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=359992

Antonin Roussel  changed:

   What|Removed |Added

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

--- Comment #2 from Antonin Roussel  ---
>From x2goclient 4.0.1.3 mga5 connected to x2goserver 4.0.1.20 mga6
both in kde/plasma or (task-)lxde-3-18.mga6 session.
Launched krdc 17.12.2 and without testing any remote desktop connection, left
krdc app.

Did not get any crash. This very simple test gives a clean result.

NB : The remote connection I was used to test, is not possible anymore from my
linux (I don't know why. I suspect the server outdated certificate to be
silently rejected by krdc. That's another subject)

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

[KScreen] [Bug 414256] New: rotating screen breaks session kscreen

2019-11-18 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=414256

Bug ID: 414256
   Summary: rotating screen breaks session kscreen
   Product: KScreen
   Version: 5.15.4
  Platform: Mageia RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: kcm
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: antonin.rous...@laposte.net
  Target Milestone: ---

Created attachment 123980
  --> https://bugs.kde.org/attachment.cgi?id=123980&action=edit
systemsettings - display rotate bug log

SUMMARY
changing screen orientation (90° counter clockwise) with system settings makes
screen display picture freezing. 

STEPS TO REPRODUCE
1. system settings > Display
2. change screen orientation (90° counter clockwise)
3. Apply

OBSERVED RESULT
Rotated display moves a bit like an opening session, and freezes

Workaround : After freeze, kill session, edit
.local/share/kscreen/30177a7ea70499dc2f3b80c7f48491e4 and set rotation value
back to 1
NB : there was no problem with mga6

EXPECTED RESULT
session still on screen, windows moving to adapt to new screen orientation

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ? mga7
KDE Plasma Version: 5.15.4
KDE Frameworks 5.57.0
Qt 5.12.2 (construit sur 5.12.2)
Le système de fenêtres xcb

ADDITIONAL INFORMATION
https://bugs.mageia.org/show_bug.cgi?id=25702
(wondering if this link could have replaced a full bug report)

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

[KScreen] [Bug 414256] rotating screen breaks session kscreen

2019-11-21 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=414256

--- Comment #2 from Antonin Roussel  ---
I cannot right now, I'm stuck in finishing booting mageia development version.

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

[plasmashell] [Bug 387548] plasma crashes when hovering jumpily in app menu

2017-12-31 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=387548

--- Comment #3 from Antonin Roussel  ---
Created attachment 109607
  --> https://bugs.kde.org/attachment.cgi?id=109607&action=edit
gdb backtrace

I did attach gdb to plasmashell process from my user terminal, I got many many
errors like in the ten first lines, then I needed to continue the interrupted
process [(gdb) c]
I made a jump in the menu, and then I got the line :
Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
following lines may give you clues. Let me know if it's not sufficient.
At the end plasmashell has restarted itself, after a black desktop (with
applications still running over)

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

[plasmashell] [Bug 387548] plasma crashes when hovering jumpily in app menu

2018-01-31 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=387548

--- Comment #6 from Antonin Roussel  ---
Created attachment 110274
  --> https://bugs.kde.org/attachment.cgi?id=110274&action=edit
plasmashell gdb backtrace (c > "bug" > bt)

hope this backtrace is good enough

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

[plasmashell] [Bug 387548] New: plasma crashes when hovering jumpily in app menu

2017-12-03 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=387548

Bug ID: 387548
   Summary: plasma crashes when hovering jumpily in app menu
   Product: plasmashell
   Version: 5.8.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: antonin.rous...@laposte.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Description of problem:
When exploring app menu with the mouse, I manage to make plasma crash (black
desktop/screen, except for already running applications)

How reproducible: 
Every time !

Steps to Reproduce:
1. App menu > Tools > Emulators > Virtual box (or wine sub menu)
2. mouse jump on App menu > Recent apps   OR App menu > Internet  OR ... 
3. after a sub second, plasma crashes before restarting itself
https://bugs.mageia.org/show_bug.cgi?id=22117

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

[plasmashell] [Bug 387548] plasma crashes when hovering jumpily in app menu

2017-12-03 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=387548

--- Comment #1 from Antonin Roussel  ---
Application: plasmashell (5.8.7)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.56-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

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

[plasmashell] [Bug 377951] New: Crash desktop, black, after changes in clock config

2017-03-22 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=377951

Bug ID: 377951
   Summary: Crash desktop, black, after changes in clock config
   Product: plasmashell
   Version: 5.8.6
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antonin.rous...@laposte.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.16-desktop-2.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
 from default :
- I added week numbers, 
- make some try to display date and seconds, apply then revert,
- added fr-fr holidays, applied, browse de calendar, but no holidays appear.
Leave the config, ask to save changes, ok. Crash.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7fdca52e7700 (LWP 685)):
#0  0x7fdd7730b000 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#1  0x7fdd7730b983 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#8  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fdcacd3a700 (LWP 592)):
#0  0x7fdd7a3a4f9d in poll () from /lib64/libc.so.6
#1  0x7fdd7730ba54 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7d324915 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#9  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fdccd810700 (LWP 32638)):
#0  0x7fdd7730b3ee in g_main_context_check () from /lib64/libglib-2.0.so.0
#1  0x7fdd7730b9f8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7dcaa8e2 in QQuickPixmapReader::run() () from
/lib64/libQt5Quick.so.5
#7  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#9  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fdd57bdf700 (LWP 32621)):
#0  0x7fdd79ba6c4f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fdd7f712234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7fdd7f712279 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#4  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fdd61da1700 (LWP 32598)):
#0  0x7fdd77350604 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7fdd7730bb66 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fdd7d324915 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#6  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#8  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fdd633ea700 (LWP 32595)):
#0  0x000

[plasmashell] [Bug 377951] Crash desktop, black, after changes in clock config

2017-03-22 Thread Antonin Roussel
https://bugs.kde.org/show_bug.cgi?id=377951

--- Comment #1 from Antonin Roussel  ---
Looks close to Bug 377936, but backtraces beginings are different (I don't know
what makes backtraces similar enough)

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

[krdc] [Bug 359992] New: Krdc crashed on quit - LXDE desktop

2016-03-02 Thread Antonin Roussel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359992

Bug ID: 359992
   Summary: Krdc crashed on quit - LXDE desktop
   Product: krdc
   Version: unspecified
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: uwol...@kde.org
  Reporter: antonin.rous...@laposte.net

Application: krdc (4.14.3)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 4.1.15-desktop-2.mga5 i686
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:
I was leaving the app.
I was running it through x2go remote LXDE session.

-- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[KCrash Handler]
#6  0x in ImportYUVAFromRGBA.constprop.5 () at /lib/libwebp.so.5
#7  0x in Import () at /lib/libwebp.so.5
#8  0x in WebPPictureImportRGB () at /lib/libwebp.so.5
#9  0x in Encode () at /lib/libwebp.so.5
#10 0x in WebPHandler::write(QImage const&) () at
/usr/lib/kde4/plugins/imageformats/kimg_webp.so
#11 0x in QImageWriter::write(QImage const&) () at /lib/libQtGui.so.4
#12 0x in QImageData::doImageIO(QImage const*, QImageWriter*, int)
const () at /lib/libQtGui.so.4
#13 0x in QImage::save(QIODevice*, char const*, int) const () at
/lib/libQtGui.so.4
#14 0x in QInternalMimeData::renderDataHelper(QString const&, QMimeData
const*) () at /lib/libQtGui.so.4
#15 0x in QX11Data::xdndMimeDataForAtom(unsigned long, QMimeData*,
QByteArray*, unsigned long*, int*) () at /lib/libQtGui.so.4
#16 0x in QClipboard::event(QEvent*) () at /lib/libQtGui.so.4
#17 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#18 0x in QApplication::notify(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#19 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at
/lib/libQtCore.so.4
#20 0x in QApplication::x11ProcessEvent(_XEvent*) () at
/lib/libQtGui.so.4
#21 0x in QX11Data::clipboardWaitForEvent(unsigned long, int, _XEvent*,
int, bool) () at /lib/libQtGui.so.4
#22 0x in QClipboard::event(QEvent*) () at /lib/libQtGui.so.4
#23 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#24 0x in QApplication::notify(QObject*, QEvent*) () at
/lib/libQtGui.so.4
#25 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at
/lib/libQtCore.so.4
#26 0x in QApplication::~QApplication() () at /lib/libQtGui.so.4
#27 0x in KApplication::~KApplication() () at /lib/libkdeui.so.5
#28 0x08058e76 in main ()

Reported using DrKonqi

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