from:"Dennis"

[Discover] [Bug 487333] Discover doesnt update

2024-05-22 Thread Dennis

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

--- Comment #2 from Dennis  ---
Thank you very very much!


Στις 22/5/24 10:16, ο/η Harald Sitter έγραψε:
> https://bugs.kde.org/show_bug.cgi?id=487333
>
> Harald Sitter  changed:
>
> What|Removed |Added
> 
>   CC||sit...@kde.org
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #1 from Harald Sitter  ---
> what's the output of
>
> flatpak repair
> flatpak update
>

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

[kstars] [Bug 487342] New: Capture Module under file settings cannot change directory

2024-05-21 Thread Dennis

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

Bug ID: 487342
   Summary: Capture Module under file settings cannot change
directory
Classification: Applications
   Product: kstars
   Version: 3.7.0
  Platform: Other
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: dennisjcoll...@gmail.com
  Target Milestone: ---

***
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
***

SUMMARY
When selecting the folder button next to the Directory field under File
Settings in the Capture Module nothing happens. A spinning color wheel appears
indicating it is attempting the operation but it eventually just times out and
nothing happens. 

STEPS TO REPRODUCE
1. goto capture module
2. select folder icon to change directory under file settings
3. nothing happens

OBSERVED RESULT
Spinning colored wheel and eventually times out

EXPECTED RESULT
window appear to change directory where images will be saved to

SOFTWARE/OS VERSIONS
Windows: 
macOS: version 14.4.1 Sonoma
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.

[Discover] [Bug 487333] New: Discover doesnt update

2024-05-21 Thread Dennis

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

Bug ID: 487333
   Summary: Discover doesnt update
Classification: Applications
   Product: Discover
   Version: 5.27.11
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: dsou...@gmx.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 169685
  --> https://bugs.kde.org/attachment.cgi?id=169685=edit
Themessage received

***
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
***

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
I am receiving an error:
Aborted due to failure (While trying to apply extra data: apply_extra script
failed, exit status 256)
and discover is not updating applications (Kubuntu 24.04).

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

[kstars] [Bug 487322] New: Guide Module shows FOV as 35.2 x 12015.8 using simulator guide scope. Can't see stars to guide by.

2024-05-21 Thread Dennis

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

Bug ID: 487322
Summary: Guide Module shows FOV as 35.2 x 12015.8 using
simulator guide scope. Can't see stars to guide by.
Classification: Applications
Product: kstars
Version: 3.7.0
Platform: Other
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: dennisjcoll...@gmail.com
Target Milestone: ---

***
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
***

SUMMARY
Using simulators I apparently get a glitch with FOV in guide module. If I
select sample guide scope it reports fov of 35.2 x 12015.8.

Interestingly, for the primary train using Sample Primary 700@F/5.8 it shows
FOV is 24.1 x 17.9. However as an attempt to troubleshoot I also set the Sample
Primary scope for secondary train and it shows the same scope now with a field
of view of 15.1 x 5149.6.

STEPS TO REPRODUCE
1. using simulator choose use sample guide 300@F/6.0
2. In guide module select secondary train
3. Scope / Lens Info shows FOV 35.2 x 12015.8

OBSERVED RESULT
Can't see any stars to track

EXPECTED RESULT
Track multi stars

SOFTWARE/OS VERSIONS

macOS:

(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.

[plasma-browser-integration] [Bug 446119] plasma-browser-integration-host crashes after closing Firefox

2024-05-06 Thread Dennis

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

--- Comment #3 from Dennis  ---
Does not happen anymoren on:

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

External monitor connected through Dell TB16.

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

[plasma-browser-integration] [Bug 446119] plasma-browser-integration-host crashes after closing Firefox

2024-05-02 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

 CC||dennis@thegood.cloud

--- Comment #2 from Dennis  ---
I see the same issue. 

I updated the system today and I'm on:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

As there is no bug reporting address:
https://bugs.kde.org/show_bug.cgi?id=443053
I'm reporting this issue manually. I can't confirm it is actually firefox, but
it looks like it. I have firefox on autostart and I use the save session
feature from kde. Whic results in 2 firefox windows to be started after logging
in, one of them with empty tabs. If I close that one, 10 crash handlers start.

the crash report:
Application: Crash Handler (drkonqi), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  QScopedPointer >::get()
const (this=0x8, this=) at
./src/corelib/tools/qscopedpointer.h:110
#7  qGetPtrHelper > >(QScopedPointer >&) (ptr=..., ptr=) at
./src/corelib/global/qtclasshelpermacros.h:79
#8  QObject::d_func() (this=0x0) at ./src/corelib/kernel/qobject.h:107
#9  QObject::deleteLater() (this=0x0) at ./src/corelib/kernel/qobject.cpp:2456
#10 0x5c73322da648 in BacktraceGenerator::slotProcessExited(int,
QProcess::ExitStatus) (this=0x5c73339c74a0, exitCode=6,
exitStatus=QProcess::CrashExit) at ./src/backtracegenerator.cpp:136
#11 0x79433aa6355e in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff5118a250, r=0x5c73339c74a0, this=, this=, r=, a=) at
./src/corelib/kernel/qobjectdefs_impl.h:469
#12 doActivate(QObject*, int, void**) (sender=0x5c73339ef940,
signal_index=10, argv=0x7fff5118a250) at ./src/corelib/kernel/qobject.cpp:4078
#13 0x79433a8ed54c in QProcess::finished(int, QProcess::ExitStatus)
(this=, _t1=, _t2=) at
./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qprocess.cpp:346
#14 0x79433aa6383b in doActivate(QObject*, int, void**)
(sender=0x5c7333f1abe0, signal_index=3, argv=0x7fff5118a360) at
./src/corelib/kernel/qobject.cpp:4090
#15 0x79433aa0e653 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
(this=this@entry=0x5c7333f1abe0, _t1=..., _t2=, _t3=...) at
./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:195
#16 0x79433aa13096 in QSocketNotifier::event(QEvent*) (this=0x5c7333f1abe0,
e=) at ./src/corelib/kernel/qsocketnotifier.cpp:327
#17 0x79433be0992b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5c7333f1abe0, e=0x7fff5118a4a0) at
./src/widgets/kernel/qapplication.cpp:3287
#18 0x79433aaa1c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5c7333f1abe0, event=0x7fff5118a4a0) at
./src/corelib/kernel/qcoreapplication.cpp:1134
#19 0x79433a875454 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x5c73338b9db0) at
./src/corelib/kernel/qeventdispatcher_glib.cpp:75
#20 0x794339c34d3b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x794339c8a258 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x794339c323e3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x79433a876591 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5c7333839a30, flags=...) at
./src/corelib/kernel/qeventdispatcher_glib.cpp:396
#24 0x79433aaa3e3b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff5118a6d0, flags=..., flags@entry=...) at
./src/corelib/global/qflags.h:34
#25 0x79433aaa5a6c in QCoreApplication::exec() () at
./src/corelib/global/qflags.h:74
#26 0x79433b0e4330 in QGuiApplication::exec() () at
./src/gui/kernel/qguiapplication.cpp:1926
#27 0x79433be078d9 in QApplication::exec() () at
./src/widgets/kernel/qapplication.cpp:2555
#28 0x5c73322cbb92 in main(int, char**) (argc=,
argv=) at ./src/main.cpp:290
[Inferior 1 (process 6609) detached]

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken

2024-04-16 Thread Dennis

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

--- Comment #15 from Dennis  ---
ah yes, sorry. doing too much at the same time.

The issue is still there in notifications. 

im currently on:
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900 12-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NV174
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.15.0

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken

2024-04-10 Thread Dennis

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

--- Comment #12 from Dennis  ---
I can't reproduce in unstable, fixed upstream?

I tested breeze and Breeze dark. I am on:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380


I attached 2 screenshots from breeze and breeze dark.

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken

2024-04-10 Thread Dennis

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

--- Comment #11 from Dennis  ---
Created attachment 168341
  --> https://bugs.kde.org/attachment.cgi?id=168341=edit
breeze2

second breeze theme selected

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken

2024-04-10 Thread Dennis

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

--- Comment #10 from Dennis  ---
Created attachment 168340
  --> https://bugs.kde.org/attachment.cgi?id=168340=edit
breeze1

breeze theme selected

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

[krdc] [Bug 483638] TAB key not functional inside rdp windows client

2024-04-10 Thread Dennis van der Pool

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

--- Comment #4 from Dennis van der Pool  ---
This works fine: 
xfreerdp -grab-keyboard /u:"myusername" /v:someip /monitors:0,1 /f /floatbar
/multimon /gfx-h264:avc444 +gfx-progressive

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

[krdc] [Bug 483638] TAB key not functional inside rdp windows client

2024-04-10 Thread Dennis van der Pool

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

--- Comment #3 from Dennis van der Pool  ---
I've got the same issue.
OS: ArchLinux
KRDC fullscreen, configured application settings for krdc "Ignore global
shortcuts" Force Yes, but did not help either.
If I can help out in any way, let me know.

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

[krdc] [Bug 483638] TAB key not functional inside rdp windows client

2024-04-10 Thread Dennis van der Pool

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

Dennis van der Pool  changed:

   What|Removed |Added

 CC||dennis@demonautomatisering.
   ||nl

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

[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on

2024-04-08 Thread Dennis

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

--- Comment #117 from Dennis  ---
Does not seem to be happening anymore on:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900 12-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NV174
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.15.0

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing

2024-04-08 Thread Dennis

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

--- Comment #8 from Dennis  ---
Seems to be fixed in:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900 12-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NV174
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.15.0

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

[plasmashell] [Bug 477665] Cannot move icon in icons-only task manager if multiple instances of a program are running

2024-04-08 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

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

--- Comment #5 from Dennis  ---
It is not happening to me either in 

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900 12-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NV174
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.15.0

cl;osing the issue

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing

2024-04-08 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing

2024-04-08 Thread Dennis

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

--- Comment #7 from Dennis  ---
Seems to be fixed in:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900 12-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NV174
Manufacturer: Alienware
Product Name: Alienware Aurora Ryzen Edition R14
System Version: 2.15.0

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

[plasmashell] [Bug 483896] New: Addition to Software update: update software at restart or shutdown

2024-03-18 Thread Dennis

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

Bug ID: 483896
   Summary: Addition to Software update: update software at
restart or shutdown
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: dennis@thegood.cloud
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
I would like a feature request to add an update option to the shutdown/restart
button. So add an option to "update and shutdown" besides shutdown. 
***



ADDITIONAL INFORMATION
We have discussed the feature on discuss here:
https://discuss.kde.org/t/addition-to-software-update-update-software-at-restart-or-shutdown/11524/15

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

[neon] [Bug 478147] fwupd shows segmentation fault

2024-02-27 Thread Dennis

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

--- Comment #2 from Dennis  ---
Seems to be fixed in:

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

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

[plasmashell] [Bug 478875] SDDM and kscreenlocker does not accept enter key in X11

2024-02-06 Thread Dennis

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

--- Comment #42 from Dennis  ---
@Carlos De Maine, Thank you for helping me with virtualbox and kde unstable.

To confirm:
- I could reproduce this in Virtualbox with kde unstable, source:
neon-unstable-20231224-1120.iso
- After updating to today's packages (6th of feb) the bug still exists.

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

[kdeconnect] [Bug 480396] New: KDE Connect crashed when bluetooth headphones powered off and phone changed network

2024-01-27 Thread Dennis Schridde

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

Bug ID: 480396
   Summary: KDE Connect crashed when bluetooth headphones powered
off and phone changed network
Classification: Applications
   Product: kdeconnect
   Version: 23.08.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: dschridde+...@mailbox.org
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

Application: kdeconnectd (23.08.4)

Qt Version: 5.15.12
Frameworks Version: 5.113.0
Operating System: Linux 6.6.13-200.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 39 (KDE Plasma)
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I went away from the computer, which meant my bluetooth headphones would
eventually power off and my phone would be in a different network (no longer in
the same as the computer).

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7457ecfe17 in PulseAudioQt::CardPrivate::update(pa_card_info
const*) () from /lib64/libKF5PulseAudioQt.so.3
#5  0x7f74575d4d9f in context_get_card_info_callback () from
/lib64/libpulse.so.0
#6  0x7f7456fbf588 in run_action () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#7  0x7f7456fc3b1c in pa_pdispatch_run () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#8  0x7f74575c31ab in pstream_packet_callback () from /lib64/libpulse.so.0
#9  0x7f7456fc694f in do_read () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#10 0x7f7456fc83a7 in do_pstream_read_write () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#11 0x7f74781508a1 in dispatch_func () from
/lib64/libpulse-mainloop-glib.so.0
#12 0x7f7499f11e5c in g_main_context_dispatch_unlocked.lto_priv () from
/lib64/libglib-2.0.so.0
#13 0x7f7499f6cf18 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#14 0x7f7499f0fad3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#15 0x7f749b7073b9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#16 0x7f749b6b383b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#17 0x7f749b6bbacb in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#18 0x5611a131407d in main ()
[Inferior 1 (process 2899) detached]

The reporter indicates this bug may be a duplicate of or related to bug 475196,
bug 476154, bug 476500, bug 477104, bug 478794, bug 479535.

Reported using DrKonqi

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

[plasmashell] [Bug 479886] New: Save session (Session Restore) does not seem to work

2024-01-16 Thread Dennis

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

Bug ID: 479886
   Summary: Save session (Session Restore) does not seem to work
Classification: Plasma
   Product: plasmashell
   Version: 5.27.10
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: dennis@thegood.cloud
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
If I choose "save session" from the launcher and reboot I get an empty/normal
shell. Saving the session does not seem to work. 
***


STEPS TO REPRODUCE
1. Install KDE Neon (stable)
2. Set Desktop Session -> Session Restore --> When session was manually saved
3. Reboot
4. run a bunch of programs, like Firefox, Terminator, Brave, spotify, signal,
etc.
5. Login, start launcher, choose "save session"
6. Reboot
7. Login

OBSERVED RESULT
normal/empty shell. Only apps in startup list are started. 

EXPECTED RESULT
I would expect to have my previous session back

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27 
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113
Qt Version: 5.15.11

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

[kwin] [Bug 479614] Scroll direction inverted on Overview list of virtual desktop

2024-01-11 Thread Dennis Körner

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

Dennis Körner  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|INTENTIONAL |---

--- Comment #4 from Dennis Körner  ---
(In reply to Nate Graham from comment #3)
> > The horizontal list is scrolling in the same direction as on scrollable 
> > documents for me
> Then it's working as intended. :) 
> 
> > The bigger issue I notice is that the list of desktops isn't scrollable 
> > without first clicking on the + or a desktop thumbnail and changing 
> > desktops.
> Those would be separate issues; could you submit new separate bug reports
> for them? Thanks!

Added a report for that. See https://bugs.kde.org/show_bug.cgi?id=479657

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

[kwin] [Bug 479657] New: List of virtual desktops is not scrollable on Overview until a virtual desktop thumbnail is selected

2024-01-11 Thread Dennis Körner

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

Bug ID: 479657
   Summary: List of virtual desktops is not scrollable on Overview
until a virtual desktop thumbnail is selected
Classification: Plasma
   Product: kwin
   Version: 5.91.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: den...@bumblebeeman.dev
  Target Milestone: ---

SUMMARY
List of virtual desktops is not scrollable on Overview until a virtual desktop
thumbnail is selected by clicking on it.


STEPS TO REPRODUCE
1. Open overview
2. Add virtual desktops using the overview until "+" button moved out of screen
3. Close overview and reopen it again
4. Scroll through list of virtual desktops / their thumbnails

OBSERVED RESULT
List of virtual desktop thumbnails is only scrollable once a virtual is
selected my clicking on its thumbnail.

EXPECTED RESULT
List of virtual desktop thumbnails is scrollable once the mouse is hovering
over their thumbnails.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora Rawhide (reproducable on KDE Neon unstable as well)
with 6.7.0-68.fc40.x86_64
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Device: Framework 13 w/ AMD Ryzen 7 7840U 32GB RAM

ADDITIONAL INFORMATION

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

[kwin] [Bug 479614] Scroll direction inverted on Overview list of virtual desktop

2024-01-11 Thread Dennis Körner

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

--- Comment #2 from Dennis Körner  ---
(In reply to Doug from comment #1)
> The horizontal list is scrolling in the same direction as on scrollable
> documents for me, but it is very slow.  The bigger issue I notice is that
> the list of desktops isn't scrollable without first clicking on the + or a
> desktop thumbnail and changing desktops.
> 
> Of course, this is probably a bit of an edge case since it takes a lot of
> desktops to become an issue at all.

Weird! Are you using a trackpad or a mouse? Do you have natural scrolling
enabled or disabled? Natural scrolling is the only setting I played around with
on an otherwise vanilla system.

Yeah, if you reopen the overview you need to select a desktop thumbnail to be
able to scroll through the list. But I thought that it might be an UI/UX
decision to not scroll on mouse over.

Sure, it is a bit of an edge case, but there are definitely people out there
that are using a lot of virtual desktops. Some of them might be even former
users of other DEs that are familiar with a 1-d horizontal layout. ;-)

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

[kwin] [Bug 479614] New: Scroll direction inverted on Overview list of virtual desktop

2024-01-10 Thread Dennis Körner

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

Bug ID: 479614
   Summary: Scroll direction inverted on Overview list of virtual
desktop
Classification: Plasma
   Product: kwin
   Version: 5.91.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: den...@bumblebeeman.dev
  Target Milestone: ---

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

SUMMARY
When adding more virtual desktops than can be fitted within the overview, the
list of virtual desktops gets scrollable, but scroll direction is inverted and
scroll acceleration very slow.


STEPS TO REPRODUCE
0. Virtual desktop are configured to the default of 1 row. (1-dimensional
horizontal layout)
1. Open overview
2. Add virtual desktops using the overview until "+" button moved out of screen
3. Select a virtual desktop and scroll the list of workspaces sideways until
"+" button is moved back on screen.

OBSERVED RESULT
1. Scrolling direction is inverted than what is configured globals. For
example, if natural scrolling is enabled, you would need to scroll from left to
right.
2. Scrolling is VERY "slow" / unresponsive.

EXPECTED RESULT
- Scrolling should behave as configured (i.e. proper scroll direction and
acceleration).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora Rawhide (reproducable on KDE Neon unstable as well)
with 6.7.0-68.fc40.x86_64
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Device: Framework 13 w/ AMD Ryzen 7 7840U 32GB RAM

ADDITIONAL INFORMATION
- When using a 1-d vertical layout (by configuring 20 rows), virtual desktop
are placed vertically on the overview and their vertical list is NOT
scrollable.

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

[neon] [Bug 479607] plasmashell crash after login with closed lid

2024-01-10 Thread Dennis

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

--- Comment #3 from Dennis  ---
Created attachment 164789
  --> https://bugs.kde.org/attachment.cgi?id=164789=edit
crash happens when opening / closing the lid

It also happens if I close the lid and open it, reproducable every time.

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

[neon] [Bug 479607] plasmashell crash after login with closed lid

2024-01-10 Thread Dennis

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

--- Comment #2 from Dennis  ---
It does not happen on Ubuntu 23.10, I have attached the specs of the kubuntu
env I tested with.

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

[neon] [Bug 479607] plasmashell crash after login with closed lid

2024-01-10 Thread Dennis

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

--- Comment #1 from Dennis  ---
Created attachment 164787
  --> https://bugs.kde.org/attachment.cgi?id=164787=edit
Ubuntu 23.10 specs

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

[neon] [Bug 479607] plasmashell crash after login with closed lid

2024-01-10 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

   Keywords||qt6

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

[neon] [Bug 479607] New: plasmashell crash after login with closed lid

2024-01-10 Thread Dennis

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

Bug ID: 479607
   Summary: plasmashell crash after login with closed lid
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Unstable Edition
  Assignee: neon-b...@kde.org
  Reporter: dennis@thegood.cloud
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 164786
  --> https://bugs.kde.org/attachment.cgi?id=164786=edit
drkonqi plasmashell crash.md

SUMMARY
If I login with the lid closed of my laptop, plasmashell crashed. I have
connected a dock with an external monitor.


STEPS TO REPRODUCE
1. Laptop turned off, lid closed.
2. Connect to Dell TB16 Dock. 
3. Laptop turns itself on, I get a grub menu on the external monitor
4. system boots to Loginscreen
5. I login with my creds, screen turns black.
6. After I open the lid, the screen comes back with Drkonqi with a plasmashell
crash.

OBSERVED RESULT
black screen after login


EXPECTED RESULT
having a desktop session, without plasmashell crash.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

ADDITIONAL INFORMATION
- Drkonqi crash report attached
- updated neon unstable to today.
-

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

[drkonqi] [Bug 478883] drkonqi does not install debug packages on Neon unstable edition (plasma6_beta2)

2024-01-10 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

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

--- Comment #1 from Dennis  ---
This issue was raised because I had an issue with reporting through drkonqi
(bug report: https://bugs.kde.org/show_bug.cgi?id=478885).

As that bug has been resolved, I think this issue can be closed too, so I'm
closing.

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

[neon] [Bug 478885] drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91)

2024-01-10 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

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

--- Comment #2 from Dennis  ---
This is fixed in my edition, I had a plasmashell crash again and I could report
through Drkonqi again. 

I'm currently at:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

Updated to latest on 10 jan 2024. 

I'm closing this issue.

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

[neon] [Bug 478885] drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91)

2024-01-06 Thread Dennis

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

--- Comment #1 from Dennis  ---
Not sure if it is fixed, but I just reported a crashed Dolphin through Drkonqi
and that worked:
https://bugs.kde.org/show_bug.cgi?id=479485

If plasmashell crashes (any way to force/simulate that?) i'll test again with
drkonqi. 

My currect specs are:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

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

[dolphin] [Bug 479485] dolphin crashed

2024-01-06 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

   Keywords||qt6

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

[dolphin] [Bug 479485] New: dolphin crashed

2024-01-06 Thread Dennis

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

Bug ID: 479485
   Summary: dolphin crashed
Classification: Applications
   Product: dolphin
   Version: 24.01.85
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dennis@thegood.cloud
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (24.01.85)

Qt Version: 6.6.1
Frameworks Version: 5.248.0
Operating System: Linux 6.2.0-39-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 5.91.90 [CoredumpBackend]

-- Information about the crash:
I tried to go directory /home/dennis/Documents/talk2.tgc/07. Medewerkers
Drive/Dennis/Ubuntu Scripts/ and Dolphin crashed. It kept crashing if i
repeated the action. 8 hours later I started Nextcloud desktop client (which
syncs this dir) I could open this directory again.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
https://debuginfod.neon.kde.org/:
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 11353]
[New LWP 11290]
[New LWP 11293]
[New LWP 11292]
[New LWP 11288]
[New LWP 11289]
[New LWP 11308]
[New LWP 11307]
[New LWP 11295]
[New LWP 11296]
[New LWP 11328]
[New LWP 11309]
[New LWP 11325]
[New LWP 11298]
[New LWP 11327]
[New LWP 11310]
[New LWP 11329]
[New LWP 11291]
[New LWP 11330]
[New LWP 11294]
[New LWP 11323]
[New LWP 11297]
[New LWP 11354]
[New LWP 11324]
[New LWP 11361]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/dolphin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (no_tid=0, signo=11,
threadid=140379891385920) at ./nptl/pthread_kill.c:44
[Current thread is 1 (Thread 0x7facbd8f4640 (LWP 11353))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7facbd8f4640 (LWP 11353))]

Thread 25 (Thread 0x7facbc8f2640 (LWP 11361)):
#0  0x7fad24718ade in __ppoll (fds=0x7facbc8f1778, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#1  0x7fad2514e544 in ppoll (__ss=0x0, __timeout=0x0, __nfds=1,
__fds=0x7facbc8f1778) at /usr/include/x86_64-linux-gnu/bits/poll2.h:64
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7facbc8f1778) at
./src/corelib/kernel/qcore_unix.cpp:126
#3  qt_safe_poll (timeout_ts=, nfds=,
fds=) at ./src/corelib/kernel/qcore_unix.cpp:149
#4  qt_safe_poll (fds=fds@entry=0x7facbc8f1778, nfds=nfds@entry=1,
timeout_ts=) at ./src/corelib/kernel/qcore_unix.cpp:144
#5  0x7fad249732f7 in qt_poll_msecs (nfds=1, timeout=,
fds=0x7facbc8f1778) at
./obj-x86_64-linux-gnu/include/QtCore/6.6.1/QtCore/private/../../../../../../src/corelib/kernel/qcore_unix_p.h:404
#6  QNativeSocketEnginePrivate::nativeSelect (this=,
timeout=, checkRead=, checkWrite=,
selectForRead=0x7facbc8f185f, selectForWrite=0x7facbc8f185e) at
./src/network/socket/qnativesocketengine_unix.cpp:1379
#7  0x7fad249c7aa9 in QNativeSocketEngine::waitForReadOrWrite
(this=0x7faca0005fd0, readyToRead=0x7facbc8f185f, readyToWrite=,
checkRead=, checkWrite=, msecs=,
timedOut=0x0) at ./src/network/socket/qnativesocketengine.cpp:1084
#8  0x7fad249bfb93 in QAbstractSocket::waitForReadyRead
(this=0x7faca0002988, msecs=-1) at
./src/network/socket/qabstractsocket.cpp:2162
#9  0x7fad271d8be8 in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6
#10 0x7fad272c66df in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6
#11 0x7fad272a4d0b in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6
#12 0x7fad2515f6ed in operator() (__closure=) at
./src/corelib/thread/qthread_unix.cpp:324
#13 (anonymous
namespace)::terminate_on_exception >
(t=...) at ./src/corelib/thread/qthread_unix.cpp:260
#14 QThreadPrivate::start (arg=0x55b8d17378f0) at
./src/corelib/thread/qthread_unix.cpp:283
#15 0x7fad24694ac3 in start_thread (arg=) at
./nptl/pthread_create.c:442
#16 0x7fad24726660 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 24 (Thread 0x7facd4cf6640 (LWP 11324)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true,
abstime=0x7facd4cf5970, op=137, expected=0, futex_word=0x55b8d15a2f14) at
./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0,
abstime=0x7facd4cf5970, clockid=560, expected=0, futex_word=0x55b8d15a2f14) at
./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x55b8d15a2f14, expected=expected@entry=0,
clockid=clockid@entry=1, abstime=

[plasmashell] [Bug 478875] Cannot login by pressing enter/return

2024-01-05 Thread Dennis

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

--- Comment #18 from Dennis  ---
Ah yes, did read it but was not registered in my brain. My bad. I don't know
too much on all the details, I was just reading up what a compositor was,
weston vs kwin, etc. A bit new on this stuff all. I'm mainly here to report
bugs and test, for all the rest im a newb. 

But it was fixed! For reference, my /etc/sddm.conf.d/10-wayland.conf contains
now:

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts
--locale1

Is this just a side effect from running unstable or does there need to be
action for plasma6?

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

[plasmashell] [Bug 478875] Cannot login by pressing enter/return

2024-01-05 Thread Dennis

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

--- Comment #16 from Dennis  ---
(In reply to Russ Hay from comment #15)
> (In reply to Russ Hay from comment #14)
> > I also had this issue - but reconfigured sddm to use Wayland
> > (https://wiki.archlinux.org/title/SDDM#Running_under_Wayland) and the enter
> > key works with SDDM on Wayland.
> 
> I'm running Plasma 6 Beta 2 on KDE Neon (unstable)

I tried it, but does not seem to work for me. I entered:
[General]
DisplayServer=wayland

updated the system, rebooted but still no joy. 

/etc/sddm.conf is empty (0 bytes)
/etc/sddm.conf.d/kde_settings.conf has just basic settings:
[Autologin]
Relogin=false
Session=
User=

[General]
HaltCommand=
RebootCommand=

[Theme]
Current=breeze
CursorSize=
CursorTheme=breeze_cursors
Font=Noto Sans,10,-1,0,400,0,0,0,0,0,0,0,0,0,0,1

[Users]
MaximumUid=6
MinimumUid=1000

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

[kwin] [Bug 479391] "Remember" window rules don't consider multiple application windows

2024-01-04 Thread Dennis Marttinen

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

Dennis Marttinen  changed:

   What|Removed |Added

Summary|"Remember" window rules |"Remember" window rules
   |with multiple application   |don't consider multiple
   |windows |application windows

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

[kwin] [Bug 479391] New: "Remember" window rules with multiple application windows

2024-01-04 Thread Dennis Marttinen

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

Bug ID: 479391
   Summary: "Remember" window rules with multiple application
windows
Classification: Plasma
   Product: kwin
   Version: 5.27.9
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: rules
  Assignee: kwin-bugs-n...@kde.org
  Reporter: twe...@welho.tech
CC: isma...@gmail.com
  Target Milestone: ---

SUMMARY

In waiting for
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18
and/or
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264
to materialize and propagate through the ecosystem, I tried to set KWin Wayland
to remember window positions/sizes for specific applications, such as Firefox.
However, if the application has multiple windows (i.e., multiple browser
windows with different tabs each), the "Remember" option of the window rules
for Position (and probably Size, horizontal/vertical maximization etc.,
basically any property with the "Remember" option) works a bit
counter-intuitively. It does remember the position of *one* of the windows, and
sets the position of *all* windows upon re-launch to that remembered position.
In addition to the window class, I attempted substring matching based on the
window title etc., but still one rule seems to only remember one set of
properties. This is problematic since browser windows are dynamic, and I can't
create an individual rule for every single one. In general, for multi-window
applications, I would expect the "Remember" option to remember the positions of
all windows of the matched application individually. Something like this
already works when (un)plugging monitors.

STEPS TO REPRODUCE

1. Create window rule that matches Firefox windows by window class (and
optionally title)
2. Set property "Position" to "Remember"
3. Set "Ignore requested geometry" to "Force" and "Yes" (on Wayland this does
nothing except silence the warning AFAIU)
4. Open Firefox, open multiple windows and spread them around
5. Close Firefox
6. Re-open Firefox

OBSERVED RESULT

All Firefox windows are re-opened on top of each other at one of the previous
window positions.

EXPECTED RESULT

The Firefox windows open at their respective previous positions.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

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

[plasmashell] [Bug 478875] Cannot login by pressing enter/return

2024-01-04 Thread Dennis

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

--- Comment #13 from Dennis  ---
I tried to install a VM with Neon unstable to reproduce on a clean system, but
currently the Neon unstable iso's won't install a Virtualbox VM. 

it does not happen with kscreenlocker after I'm logged in, which would suggest
my system boots with an X11 and switches to wayland after logging in.

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

[neon] [Bug 478147] fwupd shows segmentation fault

2024-01-04 Thread Dennis

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

--- Comment #1 from Dennis  ---
sudo fwupdmgr get-updates

results currently in: 
Failed to connect to daemon: Error calling StartServiceByName for
org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd':
timed out (service_start_timeout=25000ms)

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

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

[neon] [Bug 479384] energy settings not honered?

2024-01-04 Thread Dennis

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

Dennis  changed:

   What|Removed |Added

   Keywords||qt6

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

[neon] [Bug 479384] New: energy settings not honered?

2024-01-04 Thread Dennis

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

Bug ID: 479384
   Summary: energy settings not honered?
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Unstable Edition
  Assignee: neon-b...@kde.org
  Reporter: dennis@thegood.cloud
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
***
I have a TB16 dock with an external monitor. I have my energy settings set to
do nothing when closing the lid while on AC power. I could close the lid and
keep on working. It looks like this behaviour does not work correctly anymore
***


STEPS TO REPRODUCE
1. have neon unstable updated, clean start OS with dock attached and lid open.
2.  connect TB16 dock to my XPS13 with external monitor
3. login to session
4. both displays are enabled (or just external monitor), close lid.
5. system goes to sleep mode (this used to be the previous setting.

OBSERVED RESULT
closing lid lets system sleep while energy settings are set to do nothing. 

EXPECTED RESULT
Closing the lid should not do anything as I have configured the energy settings
to do nothing. 

Software versions:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

ADDITIONAL INFORMATION
Interesting, this used to work. I don't know with what previous version, I
presume about a month ago or so. It also results in a crash of plasmashell. I
can't attach drkonqi reports due to bugs:
https://bugs.kde.org/show_bug.cgi?id=478885
https://bugs.kde.org/show_bug.cgi?id=478883

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

[plasmashell] [Bug 478875] Cannot login by pressing enter/return

2024-01-02 Thread Dennis

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

--- Comment #10 from Dennis  ---
I use wayland (In reply to fanzhuyifan from comment #9)
> (In reply to Dennis from comment #7)
> > confirmed on:
> > 
> > Operating System: KDE neon Unstable Edition
> > KDE Plasma Version: 5.91.90
> > KDE Frameworks Version: 5.248.0
> > Qt Version: 6.6.1
> > Kernel Version: 6.2.0-39-generic (64-bit)
> > Graphics Platform: Wayland
> > Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
> > Memory: 15,3 GiB of RAM
> > Graphics Processor: Mesa Intel® UHD Graphics 620
> > Manufacturer: Dell Inc.
> > Product Name: XPS 13 9380
> 
> Is your sddm using wayland or x11?

Wayland as far as I can see. I login with Wayland selected at least. I'm not
sure if the system boots up with x11/wayland before logging in. I looked at the
sddm config files, but no x11 is set. Let me know how I can check this further
if you need to know more.

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

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 991 matches

Mail list logo