[docs.kde.org] [Bug 467029] New: Web-Page part of Website is down! [ 404 Error ]

2023-03-07 Thread OpenOS-Founder
https://bugs.kde.org/show_bug.cgi?id=467029

Bug ID: 467029
   Summary: Web-Page part of Website is down! [ 404 Error ]
Classification: Websites
   Product: docs.kde.org
   Version: unspecified
  Platform: unspecified
OS: Unspecified
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: docs.kde.org
  Assignee: kde-doc-engl...@kde.org
  Reporter: admi.openos.n...@gmail.com
  Target Milestone: ---

Created attachment 157093
  --> https://bugs.kde.org/attachment.cgi?id=157093&action=edit
Screenshot of bug .

https://develop.kde.org/docs/extend/kcm/

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

[neon] [Bug 465450] New: Fresh Install From Same Day Download Of ISO from KDE Neon Downloads Page.

2023-02-07 Thread OpenOS-Founder
https://bugs.kde.org/show_bug.cgi?id=465450

Bug ID: 465450
   Summary: Fresh Install From Same Day Download Of ISO from KDE
Neon Downloads Page.
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: admi.openos.n...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 156051
  --> https://bugs.kde.org/attachment.cgi?id=156051&action=edit
Screenshot of bug .

I downloaded KDE Neon User Edition ISO.

https://files.kde.org/neon/images/user/20230206-1037/neon-user-20230206-1037.iso

Installed it from USB.

Using 3 partitions.

- /boot/efi/ = 750mb @ fat32

- /root/ = 125gb @ btrfs

- /home/ = 125gb @ btrfs

Internal Drive = SSD.

Device = https://www.dell.com/ae/business/p/inspiron-15-5567-laptop/pd


I used Google Lens to extract the text output shown in the screenshot
attachment.

0.136925] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
[0x7d00-0x7f7f), contact BIOS vendor for fixes
0.165313] x86/cpu: SGX disabled by BIOS.

0.478447] tpm.crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover t he
entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x2001 vs fe
d40080 f80 [ 0.478472] tpm.crb MSFT0101:00: [Firmware Bug]: ACPI region does
not cover t he entire command/response buffer. [mem 0xfed4-0xfed4087f flags
0x200] vs fe

d40080 f80 [ 2.286284] kfd kfd: amdgpu: TOPAZ not supported in kfd

[ 2.3727571 amdgpu :01:00.0: no suspend buffer for LTR: ASPH issues
possible after resume You are in emergency mode. After logging in, type
"Journalctl -xb" to view

system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"

to boot into default mode.

Press Enter for maintenance (or press Control-D to continue): [ 12.148414]
amdgpu :01:00.0: no suspend buffer for LTR: ASPH issues possible after
resume

Reloading system manager configuration

[195.539415] BTRFS error (device sda3): cannot disable free space tree [
195.541065] BTRFS error (device sda3): open.ctree failed [195.547366] BTRFS
error (device sda2): cannot disable free space tree

Starting default target You are in emergency mode. After logging in, type
"Journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl
default" or "exit" to boot into default mode. (or press Control-D to continue):

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

[neon] [Bug 465450] Fresh Install From Same Day Download Of ISO from KDE Neon Downloads Page.

2023-02-07 Thread OpenOS-Founder
https://bugs.kde.org/show_bug.cgi?id=465450

OpenOS-Founder  changed:

   What|Removed |Added

 CC||admi.openos.n...@gmail.com

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

[systemsettings] [Bug 480779] Can not add Google to Online Accounts anymore using a recent version of signon-ui

2025-01-19 Thread OpenOS-Founder
https://bugs.kde.org/show_bug.cgi?id=480779

OpenOS-Founder  changed:

   What|Removed |Added

 CC||admi.openos.n...@gmail.com
 Resolution|FIXED   |WAITINGFORINFO

--- Comment #58 from OpenOS-Founder  ---
(In reply to shatz.dan from comment #0)
> Created attachment 165499 [details]
> Google sign in browser window
> 
> SUMMARY
> 
> 
> STEPS TO REPRODUCE
> 1. System Settings -> Online Accounts -> Add -> Google
> 2. Enter email, press next.
> 
> OBSERVED RESULT
> Couldn’t sign you in - This browser or app may not be secure. See screenshot.
> Learn more leads here:
> https://support.google.com/accounts/answer/7675428?hl=en-US
> 
> 
> EXPECTED RESULT
> Password/2FA fields are shown.
> 
> SOFTWARE/OS VERSIONS
> Windows: 
> macOS: 
> Linux/KDE Plasma: 
> (available in About System)
> KDE Plasma Version: 
> KDE Frameworks Version: 
> Qt Version: 
> 
> ADDITIONAL INFORMATION

Happy New Years to all . . . 

A while ago I was doing some research on various KDE Frameworks in order to
build a KDE Variant of ChromiumOS featuring Plasma is the replacement for the
Ash/Aurora UI/UX Userspace elements.

I came across a ChromiumOS Derivatives called ThoriumOS, whose inner workings
of Google Drive Support on a ChromiumOS base image using this Git Issue . . . [
https://github.com/Alex313031/ThoriumOS/issues/18 ]

Could/Would it be possible to setup this Google Drive Configuration/Deployment
connect to "kaccounts-providers". Using a nested btrfs/zfs subvolumes for each
added Google account or if going more technical using a Incus/LXC/LXD +
Docker/Podman/Pods/Distrobox "Container" backend multiple instances of each per
added Google Account so it's secluded from the rest of the host/base system . .
. ?

I hope I have artikulated this well enough . . . ?(In reply to Nate Graham from
comment #2)
> Indeed, it looks like we're going to need to make some changes here.

Happy New Years to all . . . 

A while ago I was doing some research on various KDE Frameworks in order to
build a KDE Variant of ChromiumOS featuring Plasma is the replacement for the
Ash/Aurora UI/UX Userspace elements.

I came across a ChromiumOS Derivatives called ThoriumOS, whose inner workings
of Google Drive Support on a ChromiumOS base image using this Git Issue . . . [
https://github.com/Alex313031/ThoriumOS/issues/18 ]

Could/Would it be possible to setup this Google Drive Configuration/Deployment
connect to "kaccounts-providers". Using a nested btrfs/zfs subvolumes for each
added Google account or if going more technical using a Incus/LXC/LXD +
Docker/Podman/Pods/Distrobox "Container" backend multiple instances of each per
added Google Account so it's secluded from the rest of the host/base system . .
. ?

I hope I have artikulated this well enough . . . ?

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