[kontact] [Bug 479374] New: Unable to create account using initial account creator or add account
https://bugs.kde.org/show_bug.cgi?id=479374 Bug ID: 479374 Summary: Unable to create account using initial account creator or add account Classification: Applications Product: kontact Version: GIT (master) Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: davm...@davmor2.co.uk Target Milestone: --- Created attachment 164657 --> https://bugs.kde.org/attachment.cgi?id=164657=edit page I'm stuck on SUMMARY In Kontact 5.240.90 rc1 (24.01.90) I am unable to get past the attached screenshots page in the account creation STEPS TO REPRODUCE 1. On initial setup and on add account after 2. I am unable to get past this screen 3. Try an create an Imap/SMTP account OBSERVED RESULT I get to the create account page and it refuses to go any further leaving me without an account EXPECTED RESULT I expect the create account button to take me onto the next part of the setup normally encryption SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Unstable plasma 6 (available in About System) KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 --- Comment #40 from Dave Morley --- Confirmed. Running chrome://flags searching for wayland and enabling the 2 flags and restart chrome, means that the app opens correctly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461726] The application list in the Plasma Firewall "Add rule" dialog is broken, nothing is shown
https://bugs.kde.org/show_bug.cgi?id=461726 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 461747] Crash after setting an account
https://bugs.kde.org/show_bug.cgi?id=461747 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk --- Comment #3 from Dave Morley --- Created attachment 154055 --> https://bugs.kde.org/attachment.cgi?id=154055=edit Tokodon crash Confirmed I have the issue once the account is setup and the app has been closed once it will then not open again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 --- Comment #2 from Dave Morley --- Created attachment 152506 --> https://bugs.kde.org/attachment.cgi?id=152506=edit Clipboard contents -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 --- Comment #1 from Dave Morley --- Created attachment 152505 --> https://bugs.kde.org/attachment.cgi?id=152505=edit Panel options -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459834] New: Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON
https://bugs.kde.org/show_bug.cgi?id=459834 Bug ID: 459834 Summary: Since the last update with Floating Panel enabled on Wayland Session the widget windows nolonger line up with their ICON Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: davm...@davmor2.co.uk CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 152504 --> https://bugs.kde.org/attachment.cgi?id=152504=edit Application Launcher open SUMMARY Set up a session to be wayland, set the panel to be floating in either expanded mode (full screen app open) or floating mode the widgets nolonger map to the icon that opened them STEPS TO REPRODUCE 1. Boot in to the desktop 2. Open the application launcher OBSERVED RESULT Widget opens in the middle of the panel EXPECTED RESULT Widget opens above the icon on the left of the panel SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 10 Graphics Manufacturer: LENOVO Product Name: 81NC System Version: Lenovo IdeaPad S340-15API -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #9 from Dave Morley --- Hi Nate With the power options enabled for the screen brightness it still tries to dim but then comes back up to the correct brightness. There is a flash of the dimmed screen of about 1 second. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #8 from Dave Morley --- I'll give it a go when I am back home On 15 Jul 2022 22:22, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #7 from Nate Graham --- Thanks. Does the issue go away if you check the checkbox for "Screen brightness" on the "On AC Power" and "On Battery" tabs? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #6 from Dave Morley --- Created attachment 150631 --> https://bugs.kde.org/attachment.cgi?id=150631=edit With power plugged in -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #5 from Dave Morley --- Created attachment 150630 --> https://bugs.kde.org/attachment.cgi?id=150630=edit Battery settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #4 from Dave Morley --- Created attachment 150629 --> https://bugs.kde.org/attachment.cgi?id=150629=edit Power On Power Settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #3 from Dave Morley --- Sorry for the delay Attaching them now -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 --- Comment #1 from Dave Morley --- Relates to https://bugs.kde.org/show_bug.cgi?id=455960 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456215] New: When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot
https://bugs.kde.org/show_bug.cgi?id=456215 Bug ID: 456215 Summary: When booting on battery and plugging in power lead the brightness drops to minimum but only on the first time each boot Product: Powerdevil Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: davm...@davmor2.co.uk CC: m...@ratijas.tk Target Milestone: --- SUMMARY Brightness still dimming on initial power connection. However remains at the level set on subsequent lead plug ins. STEPS TO REPRODUCE 1. Power on the laptop on battery 2. Plug in the power lead 3. Unplug the power lead 4. Plug in the power lead OBSERVED RESULT >From a fresh boot the screen dims to minimum when plugged in On subsequent lead plug ins the screen doesn't dim EXPECTED RESULT I expect the screen to remain at the correct brightness SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.13.0-52-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 10 Graphics Manufacturer: LENOVO Product Name: 81NC System Version: Lenovo IdeaPad S340-15API ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 455960] When booting on battery and plugging in power lead the brightness changes to minimum
https://bugs.kde.org/show_bug.cgi?id=455960 Dave Morley changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Product|Powerdevil |frameworks-kwayland Status|NEEDSINFO |REPORTED Component|general |general --- Comment #2 from Dave Morley --- Confirmed this is resolved in 5.25.2 Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.13.0-52-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 10 Graphics Manufacturer: LENOVO Product Name: 81NC System Version: Lenovo IdeaPad S340-15API However small gotcha is that when you first plug the power it in drops to the low level brightness but once it is raised. It stays there I will do some further testing over the next couple of days and confirm if this is every first time the power is plugged in or just the first until the level is set. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 455960] New: When booting on battery and plugging in power lead the brightness changes to minimum
https://bugs.kde.org/show_bug.cgi?id=455960 Bug ID: 455960 Summary: When booting on battery and plugging in power lead the brightness changes to minimum Product: frameworks-kwayland Version: 5.95.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: client Assignee: mgraess...@kde.org Reporter: davm...@davmor2.co.uk CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY If I boot on my Lenovo Laptop on battery and then plug in the power the brightness drops to the minimum setting but only on wayland STEPS TO REPRODUCE 1. Install Neon User 2. Boot up on Battery 3. Plug in power OBSERVED RESULT Brightness drops but only when I boot on battery if I boot on Power it doesn't EXPECTED RESULT I expect the brightness to stay the same SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 10 Graphics Manufacturer: LENOVO Product Name: 81NC System Version: Lenovo IdeaPad S340-15API ADDITIONAL INFORMATION This may only affect my laptop type so I dropped the severity to minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439104] Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 --- Comment #5 from Dave Morley --- So I've now tried the Chrome install I had and Chromium Snap package and both behave the same for me. The versions I am now on are as follows: Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 9.7 GiB of RAM Graphics Processor: AMD RAVEN -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439104] Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 --- Comment #4 from Dave Morley --- Hi I have a feeling that chromium is working because it is either installed snap installed or flap pack installed so is locked down potentially. I'll have a play with this and confirm for you. This is definitely happening in the DEB chrome package though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439104] Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 --- Comment #1 from Dave Morley --- As an addendum youtube music in my case is still being opened in windowed mode just not associated with its launcher -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439104] New: Chrome apps are not opened in an isolated app window but in a chrome session instead
https://bugs.kde.org/show_bug.cgi?id=439104 Bug ID: 439104 Summary: Chrome apps are not opened in an isolated app window but in a chrome session instead Product: kwin Version: 5.22.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: davm...@davmor2.co.uk Target Milestone: --- Created attachment 139636 --> https://bugs.kde.org/attachment.cgi?id=139636=edit image of the issue note youtube music is open hence the + on the chrome window SUMMARY In XORG when you open a chrome app it opens in an isolated session. On Wayland in comparison it opens in chrome itself STEPS TO REPRODUCE 1. Install Chrome 2. Open (for me music.youtube.com) a web app/page 3. Click on the 3 dots, select more tools and then create shortcut 4. Name it and check the open as a window box 5. Pin the new shortcut to the task manager bar 6. Launch the app OBSERVED RESULT Opens in Chrome itself and not under it's app icon, click on the launcher will open another session rather than bringing the currently open app to the front. EXPECTED RESULT Under XORG it opens under the app icon and displays a speaker in Chrome. 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 438313] Wayland: Apps launcher is one launch late
https://bugs.kde.org/show_bug.cgi?id=438313 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434262] Klipper under wayland remain open with an invisible entry that can not be removed
https://bugs.kde.org/show_bug.cgi?id=434262 Dave Morley changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #9 from Dave Morley --- This issue seems to of been resolved by the latest set of updates. I can nolonger reproduce the issue please fell free to close this issue. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434262] Klipper under wayland remain open with an invisible entry that can not be removed
https://bugs.kde.org/show_bug.cgi?id=434262 --- Comment #3 from Dave Morley --- I'll try it again at the weekend with a different user and with the docker image, I'll read up on the other issue too. Bit pressed for time at the minute though. But thanks for the replies. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434262] New: Klipper under wayland remain open with an invisible entry that can not be removed
https://bugs.kde.org/show_bug.cgi?id=434262 Bug ID: 434262 Summary: Klipper under wayland remain open with an invisible entry that can not be removed Product: klipper Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: davm...@davmor2.co.uk Target Milestone: --- Created attachment 136573 --> https://bugs.kde.org/attachment.cgi?id=136573=edit screenshot of invisible entry in klipper SUMMARY On KDE Neon on a wayland session there is an invisible entry in klipper that keeps it open on the taskbar. Trying to delete this entry is impossible. STEPS TO REPRODUCE 1. run a wayland session on KDE Neon 2. look a the empty klipper 3. try to remove the invisible entry to clear it from taskbar OBSERVED RESULT you cant remove the entry, or clear the klipper from the task bar EXPECTED RESULT I expect to be able to clear the clipboard and have it hidden like I can in a normal X session SOFTWARE/OS VERSIONS Linux/KDE Plasma: kde neon 5.21 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384213] Kontact opens but Akregator shows no feeds.
https://bugs.kde.org/show_bug.cgi?id=384213 --- Comment #2 from Dave Morley --- Turns out it is a simple package upgrading issue looks like if you upgrade the package while akonadi is running it can completely bork it's ability to run. So now I take the time to stop services before an upgrade now to prevent this. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384213] Kontact opens but Akregator shows no feeds.
https://bugs.kde.org/show_bug.cgi?id=384213 Dave Morley changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region
https://bugs.kde.org/show_bug.cgi?id=413361 Dave Morley changed: What|Removed |Added CC||davm...@davmor2.co.uk Status|REOPENED|CONFIRMED --- Comment #7 from Dave Morley --- Hi guys I can confirm that with a laptop plugged into an additional Monitor I get the following on KDE NEON (Up-to-date) spectacle kf5.kconfig.core: "\"cropRegion\" - conversion of \"0,0,0,0\" to QRect failed" And the app closes no crash report However without the additional monitor in place I get the rectangular region but with the same error. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384213] Kontact opens but Akregator shows no feeds.
https://bugs.kde.org/show_bug.cgi?id=384213 Dave Morley <davm...@davmor2.co.uk> changed: What|Removed |Added CC||davm...@davmor2.co.uk -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 384213] New: Kontact opens but Akregator shows no feeds.
https://bugs.kde.org/show_bug.cgi?id=384213 Bug ID: 384213 Summary: Kontact opens but Akregator shows no feeds. Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kontact plugin Assignee: kdepim-b...@kde.org Reporter: davm...@davmor2.co.uk Target Milestone: --- Created attachment 107610 --> https://bugs.kde.org/attachment.cgi?id=107610=edit Screenshot showing lack of feeds DATE: 2017-08-31 OS: KDE Neon 5.10.5 PACKAGE: akregator 4:17.08.0-0neon+16.04+xenial+build24 amd64 STEPS: 1. Start the system 2. Open Kontact 3. Move to the Akregator page in Kontact 4. Close Kontact completely 5. Restart the system 6. Reopen Kontact EXPECTED: I expect Akregator to display the feed list and any new articles ACTUAL: Half the time it does the other half it doesn't see attached screenshot If there is any additional info please put in accurate steps and I can follow them and give you the info. Many thanks, keep up the good work. -- You are receiving this mail because: You are watching all bug changes.
