date:20240326

[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin

2024-03-26 Thread libjared

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

libjared  changed:

   What|Removed |Added

 CC||ja...@perrycode.com

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

[konqueror] [Bug 484509] Not open direrctory -crash

2024-03-26 Thread lipun

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

--- Comment #2 from lipun  ---
Good afternoon. Many thanks for the feedback.I open Konqueror, click on the
home folder and it doesn't go into it. It's like the panel doesn't open.
[image: image.png]
In principle, to any folder, local or network

вт, 26 мар. 2024 г. в 21:40, Stefano Crocco :

> https://bugs.kde.org/show_bug.cgi?id=484509
>
> Stefano Crocco  changed:
>
>What|Removed |Added
>
> 
>  CC||stefano.cro...@alice.it
>
> --- Comment #1 from Stefano Crocco  ---
> I don't think I can reproduce your issue. Could you please be more
> detailed in
> your description? How do you "open Home"? Do you enter the path in the
> address
> bar (and, if so, do you write ~ or the full path)? Do you click on the
> "home
> folder" link in the starting page?
>
> Could you please include a backtrace of your crash (see
>
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
> )?
> Unless I can reproduce the bug, there's nothing I can do without a
> backtrace.
>
> Thanks
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kate] [Bug 484573] New: Some bold mono fonts are actually "bolder" than normal fonts on Wayland.

2024-03-26 Thread Mosklia

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

Bug ID: 484573
Summary: Some bold mono fonts are actually "bolder" than normal
fonts on Wayland.
Classification: Applications
Product: kate
Version: 24.02.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: sparky_14...@outlook.com
Target Milestone: ---

Created attachment 167832
--> https://bugs.kde.org/attachment.cgi?id=167832=edit
Screenshot when using WenQuanYi Micro Hei Mono font

***
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
Some bold mono fonts are actually "bolder" than normal fonts.
Though reported in Plasma 6, this can be observed on Plasma 5 if you use
Wayland. Cannot be observed on X11.
Konsole does also have this problem.

STEPS TO REPRODUCE
1. Open Kate
2. Select some bold mono fonts as editor font (Not all, the fonts I know can
reproduce are WenQuanYi Micro Hei Mono and WenQuanYi Zen Hei Mono.)
3. You may see that words highlighted as bold are "bolder", or wider than the
others.

OBSERVED RESULT
words highlighted as bold are "bolder", or wider than the others.

EXPECTED RESULT
All words should be of the same width.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Archlinux 6.8.1-arch1-1 (64 bit)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
DroidSansMono Nerd Fonts seem to have problems too. When using DroidSansMono
Nerd Font and DroidSansMono Nerd Font Mono, the highlighted words have no
visual difference than the others. When using DroidSansMono Nerd Fond Proto the
highlighted words are wider. Other mono fonts seems to be correct.

When "Show mono fonts only" is on, WenQuanYi fonts are not shown. But
DroidSansMono Nerd Fonts are shown.

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

[kst] [Bug 484572] New: Build fails with LTO

2024-03-26 Thread Eli Schwartz

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

Bug ID: 484572
   Summary: Build fails with LTO
Classification: Applications
   Product: kst
   Version: 2.0.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: packaging
  Assignee: k...@kde.org
  Reporter: eschwart...@gmail.com
  Target Milestone: ---

Created attachment 167831
  --> https://bugs.kde.org/attachment.cgi?id=167831=edit
Full build log

I tried to build with the following *FLAGS to optimize the build: `-flto=4
-Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing`

Note the -Werror=* flags are used to help detect cases where the compiler tries
to optimize by assuming UB cannot exist in the source code -- if it does exist,
ordinarily the code would be miscompiled, and this says to make the
miscompilation a fatal error.

I got this error:
```
[1138/1138] : && /usr/bin/x86_64-pc-linux-gnu-g++ -march=native
-fstack-protector-all -O2 -pipe -fdiagnostics-color=always
-frecord-gcc-switches -flto=4 -Werror=odr -Werror=lto-type-mismatch
-Werror=strict-aliasing  -Wformat -Werror=format-security -Wall -Wl,-O1
-Wl,--as-needed -flto=4 -Werror=odr -Werror=lto-type-mismatch
-Werror=strict-aliasing -Wl,--defsym=__gentoo_check_ldflags__=0-rdynamic
src/kst/CMakeFiles/kst2.dir/main.cpp.o
src/kst/CMakeFiles/kst2.dir/qrc_icons.cpp.o -o build/bin/kst2 
-Wl,-rpath,/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8_build/build/lib64:
 src/libkstapp/libkst2app.a  build/lib64/libkst2widgets.so.2.0.8 
build/lib64/libkst2math.so.2.0.8  build/lib64/libkst2core.so.2.0.8 
/usr/lib64/libQt5Xml.so.5.15.12  /usr/lib64/libQt5Network.so.5.15.12 
/usr/lib64/libQt5PrintSupport.so.5.15.12  /usr/lib64/libQt5Widgets.so.5.15.12 
/usr/lib64/libQt5Gui.so.5.15.12  /usr/lib64/libQt5Core.so.5.15.12 && :
FAILED: build/bin/kst2 
: && /usr/bin/x86_64-pc-linux-gnu-g++ -march=native -fstack-protector-all -O2
-pipe -fdiagnostics-color=always -frecord-gcc-switches -flto=4 -Werror=odr
-Werror=lto-type-mismatch -Werror=strict-aliasing  -Wformat
-Werror=format-security -Wall -Wl,-O1 -Wl,--as-needed -flto=4 -Werror=odr
-Werror=lto-type-mismatch -Werror=strict-aliasing
-Wl,--defsym=__gentoo_check_ldflags__=0-rdynamic
src/kst/CMakeFiles/kst2.dir/main.cpp.o
src/kst/CMakeFiles/kst2.dir/qrc_icons.cpp.o -o build/bin/kst2 
-Wl,-rpath,/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8_build/build/lib64:
 src/libkstapp/libkst2app.a  build/lib64/libkst2widgets.so.2.0.8 
build/lib64/libkst2math.so.2.0.8  build/lib64/libkst2core.so.2.0.8 
/usr/lib64/libQt5Xml.so.5.15.12  /usr/lib64/libQt5Network.so.5.15.12 
/usr/lib64/libQt5PrintSupport.so.5.15.12  /usr/lib64/libQt5Widgets.so.5.15.12 
/usr/lib64/libQt5Gui.so.5.15.12  /usr/lib64/libQt5Core.so.5.15.12 && :
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.h:53:7:
error: type ‘struct MainWindow’ violates the C++ One Definition Rule
[-Werror=odr]
   53 | class MainWindow : public QMainWindow
  |   ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.h:53:7:
note: a different type is defined in another translation unit
   53 | class MainWindow : public QMainWindow
  |   ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.h:258:14:
note: the first difference of corresponding definitions is field
‘_createSvgAct’
  258 | QAction *_createSvgAct;
  |  ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.h:260:14:
note: a field with different name is defined in another translation unit
  260 | QAction *_createSharedAxisBoxAct;
  |  ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.h:64:10:
error: type of ‘initFromCommandLine’ does not match original declaration
[-Werror=lto-type-mismatch]
   64 | bool initFromCommandLine();
  |  ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.cpp:431:6:
note: ‘initFromCommandLine’ was previously declared here
  431 | bool MainWindow::initFromCommandLine() {
  |  ^
/var/tmp/portage/sci-visualization/kst-2.0.8-r2/work/Kst-2.0.8/src/libkstapp/mainwindow.cpp:431:6:
note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
lto1: some warnings being treated as errors
lto-wrapper: fatal error: /usr/bin/x86_64-pc-linux-gnu-g++ returned 1 exit
status
compilation terminated.
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld:
error: lto-wrapper failed
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
```

Originally reported downstream: https://bugs.gentoo.org/863296

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

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2024-03-26 Thread Nate Graham

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

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED
   Assignee|ainnatul5...@gmail.com  |plasma-b...@kde.org

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

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2024-03-26 Thread Nate Graham

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

Nate Graham  changed:

   What|Removed |Added

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

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

[neon] [Bug 484571] New: deb ... Unpacking qml-module-org-kde-qqc2desktopstyle (5.115.0+p22.04+vunstable+git20240326.0748-0) over (5.115.0+p22.04+vunstable+git20240315.0359-0) ... dpkg: error processi

2024-03-26 Thread Jay Augen

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

Bug ID: 484571
   Summary: deb ... Unpacking qml-module-org-kde-qqc2desktopstyle
(5.115.0+p22.04+vunstable+git20240326.0748-0) over
(5.115.0+p22.04+vunstable+git20240315.0359-0) ...
dpkg: error processing archive
/var/cache/apt/archives/qml-module-org-kde-qqc2desktop
style_5.115.0+p
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: jay.au...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

deb ...
Unpacking qml-module-org-kde-qqc2desktopstyle
(5.115.0+p22.04+vunstable+git20240326.0748-0) over
(5.115.0+p22.04+vunstable+git20240315.0359-0) ...
dpkg: error processing archive
/var/cache/apt/archives/qml-module-org-kde-qqc2desktopstyle_5.115.0+p22.04+vunstable+git20240326.0748-0_amd64.deb
(--unpack):
 trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/qqc2desktopstyle_qt.qm',
which is also in package kf6-qqc2-desktop-style
6.0.0+p22.04+vunstable+git20240325.0210-0
Errors were encountered while processing:

/var/cache/apt/archives/qml-module-org-kde-qqc2desktopstyle_5.115.0+p22.04+vunstable+git20240326.0748-0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)***
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

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

[frameworks-bluez-qt] [Bug 480653] Updating to support LE Audio and Auracast

2024-03-26 Thread John Schulz

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

--- Comment #1 from John Schulz  ---
Hello,

Quick update; I've got a pair of LE Audio earbuds to see how KDE currently
handles it. Overall, it's pretty easy thanks to the great work of BlueZ and
PipeWire under the hood. Playback was hit or miss but Nix only has BlueZ 5.72
and it seems that most of the present issue are fixed in 5.73. That being said,
there is still ways that we can enhance the experience. First being the
discovery of BLEA devices. I think a check mark button should be added into the
discover menus in BlueDevil. This would add PACS to the discovery filter which
ensures only BLEA devices show up. This will be crucial since many devices will
have both LE and Classic audio for the next few years and they don't always
distinguish in their names. Currently, I know that I am connecting via LE Audio
because I set BlueZ to only LE Bluetooth. This is not ideal for legacy devices
wand should be avoided. I have other ideas for improvements but let's start
with this one. If you have any objections or concerns, please raise them. 

Thanks!

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

[systemsettings] [Bug 484570] Chromium cannot open network settings in Plasma 6

2024-03-26 Thread Mosklia

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

--- Comment #1 from Mosklia  ---
Chromium version: 123.0.6312.58 Arch Linux （64 bit）

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

[systemsettings] [Bug 484570] New: Chromium cannot open network settings in Plasma 6

2024-03-26 Thread Mosklia

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

Bug ID: 484570
   Summary: Chromium cannot open network settings in Plasma 6
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcmshell
  Assignee: plasma-b...@kde.org
  Reporter: sparky_14...@outlook.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

Chromium cannot open network settings in Plasma 6, which can be opened in
Plasma 5

STEPS TO REPRODUCE
1. Open Chromium, entering its settings
2. Click System -> Open your computer proxy settings（“打开您计算机的代理设置”）
3. You may see a window saying "无法从 /usr/bin/proxy 加载插件：Failed to extract
plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin
(metadata not found)"

OBSERVED RESULT

A window titled "kcmshell6" saying "无法从 /usr/bin/proxy 加载插件：Failed to extract
plugin meta data from '/usr/bin/proxy': '/usr/bin/proxy' is not a Qt plugin
(metadata not found)"

EXPECTED RESULT

System proxy settings is opened as is worked in Plasma 5.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
ArchLinux 6.8.1-arch1-1 (64 bit)
KDE Plasma Version:  6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
See https://bbs.archlinux.org/viewtopic.php?id=293966

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

[plasma4] [Bug 241562] Plasma crash on different situations (Kubuntu, DBusMenuImporter) [KJob::isAutoDelete, Plasma::ServiceJob::setResult, StatusNotifierItemJob::contextMenuReady, ..., DBusMenuImport

2024-03-26 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |VHI

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

[kwin] [Bug 483309] Resizing window that opens maximized glitches

2024-03-26 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #5 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/5528

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

1 2 3 4 5 >

1 - 100 of 416 matches

Mail list logo