[elisa] [Bug 424517] New: Cannot play files from SMB Share

2020-07-21 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=424517

Bug ID: 424517
   Summary: Cannot play files from SMB Share
   Product: elisa
   Version: 19.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: o...@kapsi.fi
  Target Milestone: ---

SUMMARY
I'm trying to play Music from SMB share hosted on Synology NAS. 

STEPS TO REPRODUCE
1. Configure Elisa -> add path smb://username@server.local:445/music/ ->
Nothing happens 
2. From Dolphin open music file in Elisa -> File appears on Elisa playlist but
does not play.   

OBSERVED RESULT
Cannot playback Music from SMB share with Elisa

EXPECTED RESULT
Play music files from SMB share

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Pop!_OS 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Console error when trying to add folder with Configure Elisa:
"setting:kf5.kio.kdirmodel: The kioslave for "smb" violates the hierarchy
structure: I arrived at node "/music/" , but "/music" does not start with that
path."

Console error when trying to playback file by opening it from Dolphin:
[7f2490001b20] smb stream error: open failed for
'username:@server.local:445/music/Gamma Ray - Land of the Free II/01 - Into the
Storm.flac' (Operation not permitted)
[55b0e89ca660] main input error: Your input can't be opened
[55b0e89ca660] main input error: VLC is unable to open the MRL
'smb://username:@server.local:445/music/Gamma Ray - Land of the Free II/01 -
Into the Storm.flac'. Check the log for details.
qrc:/qml/ElisaMainWindow.qml:190:17: Unable to assign [undefined] to QString
qrc:/qml/HeaderBar.qml:94:9: QML Image: Failed to get image from provider:
image://icon/error
qrc:/qml/HeaderBar.qml:60:9: QML Image: Failed to get image from provider:
image://icon/error
[7f248c0070f0] main stream error: cannot resolve  port 554 : Name or
service not known
[7f248c0070f0] access_realrtsp stream error: cannot connect to :554
[7f248c0070f0] main stream error: Connection failed
[7f248c0070f0] main stream error: VLC could not connect to ":554".
[7f248c0070f0] nfs stream error: nfs_parse_url_incomplete failed: 'Invalid
URL specified'
[55b0e8dbe5c0] main input error: Your input can't be opened
[55b0e8dbe5c0] main input error: VLC is unable to open the MRL ''. Check
the log for details.
[7f24900528c0] main stream error: cannot resolve  port 554 : Name or
service not known
[7f24900528c0] access_realrtsp stream error: cannot connect to :554
[7f24900528c0] main stream error: Connection failed
[7f24900528c0] main stream error: VLC could not connect to ":554".
[7f24900528c0] nfs stream error: nfs_parse_url_incomplete failed: 'Invalid
URL specified'
[55b0e77edc80] main input error: Your input can't be opened
[55b0e77edc80] main input error: VLC is unable to open the MRL ''. Check
the log for details.

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

[neon] [Bug 476396] Discover: "The PackageKit daemon has crashed" when updating a Flatpak

2023-11-20 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=476396

Tomi  changed:

   What|Removed |Added

 CC||faufer...@gmail.com

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

[Discover] [Bug 476065] New: The PackageKit daemon has crashed

2023-10-24 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=476065

Bug ID: 476065
   Summary: The PackageKit daemon has crashed
Classification: Applications
   Product: Discover
   Version: 5.27.8
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: plasma-b...@kde.org
  Reporter: faufer...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***
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. 
2. 
3. 

OBSERVED RESULT
The PackageKit daemon has crashed

EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 494408] Monitor brightness

2024-10-10 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

--- Comment #1 from Tomi  ---
Managed to fix this issue by installing power-profiles-daemon from arch repo
since it was missing from original plasma install now i can change brightness
from taskbar. Still it might be better to let users decide between changing
monitor brightness from plasma itself or monitor osd. So adding option in
monitor configuration page would be ideal in my opinion

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

[plasmashell] [Bug 494408] New: Monitor brightness

2024-10-10 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

Bug ID: 494408
   Summary: Monitor brightness
Classification: Plasma
   Product: plasmashell
   Version: git-stable-Plasma/6.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brightness and Color
  Assignee: plasma-b...@kde.org
  Reporter: steampip...@protonmail.com
CC: natalie_clar...@yahoo.de
  Target Milestone: 1.0

SUMMARY
Monitor brightness keeps constantly resetting back to 100%

STEPS TO REPRODUCE
1. Turning monitor off and then on again
2. Just by launching some apps for example firefox
3. By having freesync enabled

OBSERVED RESULT
Brightness goes back to 100% with every monitor

EXPECTED RESULT
It should stay as that value i set it in OSD.

Linux/KDE Plasma: 
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3

ADDITIONAL INFORMATION
 Anyways i have sensitive eyes so white backgrounds at 100% brightness almost
get my eyes to watering. If this is some setting that can be changed then it
should be in display configuration so it can be easily found

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

[Powerdevil] [Bug 494408] Monitor brightness resets to 100% on every monitor wakeup

2024-10-11 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

--- Comment #3 from Tomi  ---
apparently i didnt have it installed i guess. When i installed arch i installed
plasma-meta package but it still was missing power-profiles-daemon. My kde
plasma basically let me know i was missing that package when i did some
digging. After i installed that package i can set my monitor brightness from
taskbar "brightness and color". I guess it defaulted to 100% when i was missing
that package so it got resolved that way

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

[plasmashell] [Bug 495134] New: Plasmashell crashes

2024-10-21 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495134

Bug ID: 495134
   Summary: Plasmashell crashes
Classification: Plasma
   Product: plasmashell
   Version: git-stable-Plasma/6.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: steampip...@protonmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 175075
  --> https://bugs.kde.org/attachment.cgi?id=175075&action=edit
After i eject bluray drive

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Plasmashell crashes everytime i eject bluray disc from bluray drive no need to
even mount bluray just put disk in and eject after it. This bug appeared after
update to 6.2.1

STEPS TO REPRODUCE
1. Eject bluray disk from drive
2. 
3. 

OBSERVED RESULT
Plasmashell, Dolphin and kde connect daemon crash

EXPECTED RESULT
No crashing

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Arch linux plasma meta package
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 495134] Plasmashell (and Dolphin) crash after ejecting a disc from an optical drive

2024-10-27 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495134

--- Comment #5 from Tomi  ---
(In reply to Luke Horwell from comment #4)
> According to a weekly blog update, this is fixed for KDE Frameworks 6.8:
> 
> > Fixed a case where Plasma and other KDE apps could crash when ejecting a CD 
> > (Nicolas Fella, Frameworks 6.8)
> > https://invent.kde.org/frameworks/solid/-/merge_requests/172
> > 
> > — 
> > https://pointieststick.com/2024/10/26/this-week-in-plasma-all-screens-all-the-time/

Thanks for letting me know. I just have to wait arch to roll Frameworks 6.8
then :) Current version i have according to kinfo is 6.7

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

[plasmashell] [Bug 495134] Plasmashell (and Dolphin) crash after ejecting a disc from an optical drive

2024-10-26 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495134

Tomi  changed:

   What|Removed |Added

 Status|CONFIRMED   |REPORTED
 Ever confirmed|1   |0

--- Comment #2 from Tomi  ---
Happens pretty much with every optical media for me cd, dvd, bluray

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

[plasmashell] [Bug 495109] Monitor brightness is reset to 100% after boot

2025-02-17 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495109

Tomi  changed:

   What|Removed |Added

   Platform|Fedora RPMs |Arch Linux
Version|6.2.4   |6.3.0

--- Comment #6 from Tomi  ---
Brightness is yet again broken after updating from 6.2.5 to plasma 6.3.0.
Monitor brightness resets back to 100% after turning off screen and then
turning it back on. Issue only affects primary screen thou for some reason.
Primary screen is connected through displayport and secondary screen is
connected with club 3D displayport to dvi-dl active adapter. It doesn't matter
if i set brightness through monitor settings or plasma control panel it always
resets back to 100% if i turn screen off and then on. Reboot doesn't reproduce
this issue.

Operating System: CachyOS Linux 
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT

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

[plasmashell] [Bug 495109] Monitor brightness is reset to 100% after boot

2025-02-17 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495109

Tomi  changed:

   What|Removed |Added

 CC||steampip...@protonmail.com

--- Comment #4 from Tomi  ---
Created attachment 178462
  --> https://bugs.kde.org/attachment.cgi?id=178462&action=edit
Brightness before turning off/on screen

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

[plasmashell] [Bug 495109] Monitor brightness is reset to 100% after boot

2025-02-17 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=495109

--- Comment #5 from Tomi  ---
Created attachment 178463
  --> https://bugs.kde.org/attachment.cgi?id=178463&action=edit
Brightness after turning screen on

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

[kwin] [Bug 494408] Monitor brightness resets to 100% on every monitor wakeup

2025-02-23 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

Tomi  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REPORTED
Version|6.2.0   |6.3.1
 Ever confirmed|1   |0

--- Comment #32 from Tomi  ---
I can confirm that ddcutil 2.2.0 fixed issue for me atleast. Brightness stays
at 35% where i have set it.

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

[kwin] [Bug 494408] Monitor brightness resets to 100% on every monitor wakeup

2025-02-23 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

--- Comment #34 from Tomi  ---
For me atleast both monitors are BenQ. 
Primary screen in Benq XL2540K and secondary screen is BenQ XL2411Z. 
Primary monitor is connected with displayport second screen is connected with
club3d displayport to active dvi-dual link adapter.
Primary monitor is running on 240 hz and freesync is enabled. 
Second monitor runs at 144 hz. 

Operating System: CachyOS Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9700X 8-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT

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

[kwin] [Bug 494408] Monitor brightness resets to 100% on every monitor wakeup

2025-02-25 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

--- Comment #39 from Tomi  ---
Try workaround i mentioned in https://bugs.kde.org/show_bug.cgi?id=494408#c26
it works unless you need to constantly switch brightness.

Sometimes bugs just get missed like this is probably setup sensitive stuff.
ddcutil 2.2.0 fixed issue for my setup but for example it doesn't work with
Gustavo's setup. I just have hunch this issue is monitor related like it
"forgets" monitor when you shut it down and when you turn it on again it
defaults to 100% brightness because it thinks its new monitor or something like
that.

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

[kwin] [Bug 494408] Monitor brightness resets to 100% on every monitor wakeup

2025-02-22 Thread Tomi
https://bugs.kde.org/show_bug.cgi?id=494408

Tomi  changed:

   What|Removed |Added

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

--- Comment #26 from Tomi  ---
Possible workaround for time being to get rid of issue is open /etc/environment
with your favorite text editor "sudo nano /etc/environment" and add
POWERDEVIL_NO_DDCUTIL=1 at the end of that file like this and then save and
exit and reboot. You cant control brightness from plasma after that but atleast
brightness stays at set percentage

#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
POWERDEVIL_NO_DDCUTIL=1

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

[kpat] [Bug 354065] kpat has a problem with redo and undo. Does not refresh the situation or does refresh with large delay.

2017-06-08 Thread Tomi Leppänen
https://bugs.kde.org/show_bug.cgi?id=354065

Tomi Leppänen  changed:

   What|Removed |Added

 CC||tomi.leppa...@telemail.fi

--- Comment #1 from Tomi Leppänen  ---
I can reproduce this. I think this is easiest to reproduce with Spider
solitaire. Do some moves then undo some and redo them. Should be clearly
visible. I can't take a screenshot since the problem disappears if I try to do
that.

My system:
Fedora 25, KPatience 3.6. I tried also git master, seems to work the same.

I already figured out that adding just a tiny bit of duration to the animation
(from 0 to 1) makes this work, but it won't look very nice when the card just
quickly flashes. There is probably a way to tell it to update that part of the
screen or the whole game, but I haven't yet figured that out. Or maybe the
animation code needs to be fixed.

If someone wants to try the workaround I mentioned, here is a quick patch:
diff --git a/dealer.cpp b/dealer.cpp
index dfee5e4..eb263c8 100644
--- a/dealer.cpp
+++ b/dealer.cpp
@@ -1219,7 +1219,7 @@ void DealerScene::undoOrRedo( bool undo )
 p->swapCards( i, index );
 }

-updatePileLayout( p, 0 );
+updatePileLayout( p, 1 );
 }

 emit updateMoves( moveCount() );

I didn't make a real patch since it I don't think this is proper way to fix
this, but it might provide some ideas to fix this properly.

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