reneas's questions

Problema semelhante ao aqui, mas não exatamente o mesmo e também não no Ubuntu 23.04, mas no 24.04 LTS.

Quando tento executá wine-lo resulta nesta mensagem:

it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32:i386"

Ao tentar executá sudo apt-get install wine32:i386-lo resulta em:

sudo apt-get install wine32:i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libgd3:i386 : Depends: libheif1:i386 (>= 1.17.6-1ubuntu4~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Ao tentar instalar libheif1:i386resulta em:

sudo apt-get install libheif1:i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libheif1:i386 : Depends: libdav1d5:i386 (>= 0.1.0) but it is not installable
Depends: libde265-0:i386 (>= 1.0.7) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

sudo apt updatefornece esta saída:

OK:1 https://dl.winehq.org/wine-builds/ubuntu noble InRelease
OK:2 https://ubuntu.mirror.wearetriple.com/archive noble InRelease
OK:3 http://packages.easyroam.de/repos/easyroam-desktop stable InRelease
OK:4 http://ftp.klid.dk/ftp/ubuntu noble InRelease
OK:5 http://ubuntu.mirror.tudos.de/ubuntu noble InRelease
OK:6 https://mirror.united-gameserver.de/ubuntu noble InRelease
OK:7 http://security.ubuntu.com/ubuntu noble-security InRelease
Holen:8 https://typora.io/linux ./ InRelease [793 B]
OK:10 http://de.archive.ubuntu.com/ubuntu noble InRelease
Holen:11 http://de.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
OK:12 http://ftp.tudelft.nl/archive.ubuntu.com noble InRelease
OK:13 http://repository.spotify.com stable InRelease
OK:14 https://brave-browser-apt-release.s3.brave.com stable InRelease
OK:16 http://nl3.archive.ubuntu.com/ubuntu noble InRelease
OK:17 https://nl.mirrors.clouvider.net/ubuntu noble InRelease
OK:18 https://mirror.nl.mirhosting.net/ubuntu noble InRelease
Holen:19 https://esm.ubuntu.com/apps/ubuntu jammy-apps-security InRelease [7.553 B]
Holen:20 https://esm.ubuntu.com/apps/ubuntu jammy-apps-updates InRelease [7.456 B]
Holen:15 http://mirrors.edge.kernel.org/ubuntu noble InRelease [256 kB]
OK:21 https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu jammy InRelease
OK:22 https://ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu noble InRelease
Holen:23 https://esm.ubuntu.com/infra/ubuntu jammy-infra-security InRelease [7.450 B]
OK:9 https://mirrors.edge.kernel.org/ubuntu noble InRelease
OK:24 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Holen:25 https://esm.ubuntu.com/infra/ubuntu jammy-infra-updates InRelease [7.449 B]
OK:26 https://ppa.launchpadcontent.net/phoerious/keepassxc/ubuntu mantic InRelease
Es wurden 413 kB in 3 s geholt (136 kB/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.

E o conteúdo de /etc/apt/sources.list.d/winehq-noble.sourcesé:

Types: deb
URIs: https://dl.winehq.org/wine-builds/ubuntu
Suites: noble
Components: main
Architectures: amd64 i386
Signed-By: /etc/apt/keyrings/winehq-archive.key

A questão agora seria: preciso mesmo deste wine32:i386pacote ou posso ignorá-lo? E se eu precisar, como posso conseguir?

Eu queria usar o sensor de impressão digital com essa configuração, mas não consigo fazê-lo funcionar. Quando executo fprintd-enrollrecebo a seguinte mensagem:
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

Meu modelo exato de laptop é este

lsusbsaída:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 056a:51f6 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 004: ID 06cb:00be Synaptics, Inc.
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 002: ID 04f2:b681 Chicony Electronics Co., Ltd ThinkPad T490 Webcam
Bus 001 Device 006: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspcisaída:

00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:13.0 Serial controller: Intel Corporation Comet Lake Integrated Sensor Solution
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (10) I219-V
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)

Alguma idéia de como fazer isso funcionar? Parece que o dispositivo está

Bus 001 Device 004: ID 06cb:00be Synaptics, Inc.

Depois de resolver o primeiro problema com meu prompt personalizado, ainda tenho outro.

Quando eu percorro meus últimos comandos usados ​​por meio das teclas de seta para cima e para baixo, às vezes alguns caracteres de um comando anterior permanecem visíveis, embora não estejam acessíveis nem estejam realmente na linha de comando. Eles são apenas um bug visual muito chato e confuso.

Se parece com isso:

Aqui subi um pouco no histórico de comandos e depois voltei ao prompt atual (vazio) e digitei echo. o pip i(vindo de um pip installcomando anterior) não está acessível com meu cursor. É visível lá, mas na verdade não existe.

Meu .bashrctem este código para personalizar o prompt:

set_PS1()
{
    local Reset="\\[$(tput sgr0 )\\]"
    local Bold="\\[$(tput bold )\\]"
    local Red="\\[$(tput setaf 1 )\\]"
    local Green="\\[$(tput setaf 2 )\\]"
    local Yellow="\\[$(tput setaf 3 )\\]"
    local Blue="\\[$(tput setaf 4 )\\]"
    local MagentaBG="\\[$(tput setab 5 )\\]"
    local Cyan="\\[$(tput setaf 6 )\\]"

    local Whoami='\u'
    local Where='\w'
    local Hostname='\h'
    local Time='\D{%H:%M:%S}'
    local Exit_Code="$?"

    exit_code_prompt() {
        local Exit_Code="$?"
        local Red="$(tput setaf 1 )"
        local Green="$(tput setaf 2 )"
        if (($Exit_Code == 0 )); then
            printf '%s\xE2\x9C\x93 \xE2\x86\x92 ' "$Green" # Green checkmark symbol
        else
            printf '%s\xE2\x9C\x98 %s \xE2\x86\x92 ' "$Red" "$Exit_Code" # Red cross mark symbol and exit code
        fi
    }

    local Line_1="$Bold$Yellow$Time $Cyan$Whoami$Blue@$Cyan$Hostname$Reset$Bold":" $Blue$Where$Reset"
    local Line_2="$Bold\$(exit_code_prompt)$Reset$Bold \$: $Reset"
    #local Line_2="$Bold \$: $Reset"

    PS1="$Line_1\n$Line_2"

    unset -f set_PS1
}

set_PS1

Já reduzi o problema à exit_code_promptfunção, pois o problema não aparece se eu removê-lo do$Line_2

EDIT: Quando coloco as definições de cores dentro da função entre colchetes, como na parte externa, assim:

exit_code_prompt() {
        local Exit_Code="$?"
        local Red="\\[$(tput setaf 1 )\\]"
        local Green="\\[$(tput setaf 2 )\\]"
        if (($Exit_Code == 0 )); then
            printf '%s\xE2\x9C\x93 \xE2\x86\x92 ' "$Green" # Green checkmark symbol
        else
            printf '%s\xE2\x9C\x98 %s \xE2\x86\x92 ' "$Red" "$Exit_Code" # Red cross mark symbol and exit code
        fi
    }

Eu obtenho este resultado:

O mesmo resultado se eu colocar apenas barras invertidas. \
Além disso, o problema inicial ainda está lá!

Já mudei meu formato de saída do bash para algo assim:

com o qual estou muito feliz. Consegui isso adicionando este código ao .bashrc:

set_PS1()
{
    local RESET=$(tput sgr0 )
    local BOLD=$(tput bold )
    local RED=$(tput setaf 1 )
    local GREEN=$(tput setaf 2 )
    local YELLOW=$(tput setaf 3 )
    local BLUE=$(tput setaf 4 )
    local CYAN=$(tput setaf 6 )

    local WHOAMI='\u'
    local WHERE='\w'
    local HOSTNAME='\h'
    local TIME='\D{%H:%M:%S}'


     exit_code_prompt() {
        local EXIT_CODE=$?
        local RED=$(tput setaf 1 )
        local GREEN=$(tput setaf 2 )
        if [ $EXIT_CODE -ne 0 ]; then
            echo -e "$RED$BOLD\xE2\x9C\x98 $EXIT_CODE \xE2\x86\x92"  # Red cross mark symbol
        else
            echo -e "$GREEN$BOLD\xE2\x9C\x93 \xE2\x86\x92"  # Green checkmark symbol
        fi
    }

    local LINE_1="$BOLD$YELLOW$TIME $CYAN$WHOAMI$BLUE@$CYAN$HOSTNAME$RESET$BOLD":" $BLUE$WHERE$RESET"
    local LINE_2="$BOLD\$(exit_code_prompt) "$RESET$BOLD' \$: '$RESET


    PS1="$LINE_1\n$LINE_2"

    unset -f set_PS1
}

set_PS1

Meu problema era que se eu tivesse um comando com mais de uma linha, ele não fazia uma quebra de linha, mas sobrescrevia o conteúdo da mesma linha (apenas na representação visual ofc):

Agora, quando eu excluo o comando completo, ele também exclui uma parte do prompt do bash:

Isso poderia ser resolvido adicionando \[e \]:

    local LINE_1="\[$BOLD$YELLOW$TIME $CYAN$WHOAMI$BLUE@$CYAN$HOSTNAME$RESET$BOLD":" $BLUE$WHERE$RESET\]"
    local LINE_2="\[$BOLD\$(exit_code_prompt) "$RESET$BOLD' \$: \]'$RESET

Outro problema persiste. Quando percorro os últimos comandos usados, ele exclui o sinal de prompt $:

como faço para resolver esse problema?

Já pensei em usar zshmas não queria perder bashfuncionalidades como atalhos de teclado com os quais já me acostumei...

ATUALIZAÇÃO: abaixo está meu código atualizado, que ainda não funciona:

set_PS1()
{
    local Reset="\\[$(tput sgr0 )\\]"
    local Bold="\\[$(tput bold )\\]"
    local Red="\\[$(tput setaf 1 )\\]"
    local Green="\\[$(tput setaf 2 )\\]"
    local Yellow="\\[$(tput setaf 3 )\\]"
    local Blue="\\[$(tput setaf 4 )\\]"
    local MagentaBG="\\[$(tput setab 5 )\\]"
    local Cyan="\\[$(tput setaf 6 )\\]"

    local Whoami='\u'
    local Where='\w'
    local Hostname='\h'
    local Time='\D{%H:%M:%S}'
    local Exit_Code="$?"

    exit_code_prompt() {
        local Exit_Code="$?"
        local Red="$(tput setaf 1 )"
        local Green="$(tput setaf 2 )"
        if [ $Exit_Code -ne 0 ]; then
            printf "$Red\xE2\x9C\x98 $Exit_Code \xE2\x86\x92 " # Red cross mark symbol
        else
            printf "$Green\xE2\x9C\x93 \xE2\x86\x92 " # Green checkmark symbol
        fi
    }

    local Line_1="$Bold$Yellow$Time $Cyan$Whoami$Blue@$Cyan$Hostname$Reset$Bold":" $Blue$Where$Reset"
    local Line_2="$Bold\$(exit_code_prompt)$Reset$Bold \$: $Reset"

    PS1="$Line_1\n$Line_2"

    unset -f set_PS1
}

set_PS1

Terei o mesmo problema de antes. O texto com mais de uma linha aparecerá no início da mesma linha e será substituído. Percorrer os comandos resulta na exclusão de uma parte do prompt ou em um bug visual que mostra parte de um comando anterior que não está acessível.

ATUALIZAÇÃO 2 : O problema definitivamente está na exit_code_promptfunção. quando eu o excluo de $Line_2tudo, funciona conforme o esperado.

Não consigo definir programas diferentes para abrir os tipos de arquivos mencionados no Kubuntu 22.04. Quero abrir *.ziparquivos com arke *.3mfarquivos com Ultimaker Cura.

Quando tento alterar o programa padrão via right click -> properties -> "open with" -> change, ele altera a associação para ambos os tipos de arquivos. Na verdade, as propriedades também são exibidas Type: zip-archivepara os arquivos. Estou usando o Cura como um programa e normalmente posso adicioná-lo como um programa padrão para arquivos através do menu de contexto.*.3mf
AppImageAppImageLauncher

Mesmo depois de editar ~/.config/mimeapps.liste adicionar a linha

application/3mf=appimagekit_968bf060d41f38a8b5f435483426a7e5-com.ultimaker.cura.desktop;

não vai funcionar, embora esse seja o caminho correto para associar o Cura.

Por que meu sistema operacional está pensando que *.3mfarquivos são *.ziparquivos e como posso mudar isso?

O comando grep 3mf -r ~/.local/share/mime /usr/share/mimefornece:

/usr/share/mime/types:model/3mf

mas apenas porque eu editei manualmente. Mesmo assim o problema persiste.

Acabei de instalar o Kubuntu no meu laptop e tudo funcionou perfeitamente. Então plasma-discoverparou de funcionar de repente. Quando tento iniciá-lo, a janela aparece por um segundo ou mais como um pequeno retângulo no canto superior esquerdo e desaparece imediatamente depois. Iniciá-lo na linha de comando dá o mesmo resultado com a seguinte mensagem:

$ plasma-discover
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
QObject::startTimer: Timers cannot have negative intervals
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
adding empty sources model QStandardItemModel(0x55feeb4688e0)
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:75:5: QML Binding: Binding loop detected for property "value"
QQuickItem::stackBefore: Cannot stack QQuickRectangle(0x55feeb88dda0, parent=0x55feeaea8fe0, geometry=0,0 0x0) before QQuickPopupItem(0x55feeb04c110), which must be a sibling
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:333:17: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

Segmentation fault (core dumped)

Executar o comando rootinicia o aplicativo corretamente com a seguinte mensagem:

sudo plasma-discover
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
adding empty sources model QStandardItemModel(0x561aaf758820)
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:75:5: QML Binding: Binding loop detected for property "value"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:273:18: QML QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.

Fiz algumas pesquisas e talvez tenha algo a ver com alguns atalhos de teclado, mas não tenho ideia de como consertar isso... Minha plasma-discoverversão é 5.24.7e estou executando o Kubuntu 22.04 no 6.5.0-15-generic x86_64kernel

A execução gdb plasma-discoverresulta em:

$ gdb plasma-discover
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from plasma-discover...
(No debugging symbols found in plasma-discover)
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
Starting program: /usr/bin/plasma-discover 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff0147640 (LWP 9869)]
[New Thread 0x7fffef0d6640 (LWP 9870)]
[New Thread 0x7fffedb22640 (LWP 9871)]
[New Thread 0x7fffed321640 (LWP 9872)]
[New Thread 0x7fffecb20640 (LWP 9873)]
[New Thread 0x7fffe5fff640 (LWP 9874)]
[New Thread 0x7fffe57fe640 (LWP 9875)]
[New Thread 0x7fffe4ffd640 (LWP 9876)]
[New Thread 0x7fffd8fff640 (LWP 9877)]
[New Thread 0x7fffbbfff640 (LWP 9878)]
[New Thread 0x7fffbb7fe640 (LWP 9879)]
[Thread 0x7fffbb7fe640 (LWP 9879) exited]
[Thread 0x7fffbbfff640 (LWP 9878) exited]
[New Thread 0x7fffbbfff640 (LWP 9880)]
[New Thread 0x7fffbb7fe640 (LWP 9881)]
[New Thread 0x7fffbaffd640 (LWP 9882)]
[Thread 0x7fffbaffd640 (LWP 9882) exited]
[Thread 0x7fffbb7fe640 (LWP 9881) exited]
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
QObject::startTimer: Timers cannot have negative intervals
[New Thread 0x7fffbb7fe640 (LWP 9883)]
[New Thread 0x7fffbaffd640 (LWP 9884)]
[New Thread 0x7fffb99e6640 (LWP 9885)]
[New Thread 0x7fffb91e5640 (LWP 9886)]
kf.config.core: "\"geometry\" - conversion of \"776,258,0,65507\" to QRect failed"
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
[New Thread 0x7fffa3fff640 (LWP 9887)]
[New Thread 0x7fffa37fe640 (LWP 9888)]
[New Thread 0x7fffa2ffd640 (LWP 9889)]
[New Thread 0x7fffa27fc640 (LWP 9890)]
[New Thread 0x7fffa1ffb640 (LWP 9891)]
adding empty sources model QStandardItemModel(0x555555eec230)
[New Thread 0x7fffa17fa640 (LWP 9892)]
[New Thread 0x7fff8bfff640 (LWP 9893)]
[Detaching after fork from child process 9894]
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:75:5: QML Binding: Binding loop detected for property "value"
[New Thread 0x7fff8b7fe640 (LWP 9896)]
[New Thread 0x7fff8affd640 (LWP 9897)]
[New Thread 0x7fff8a7fc640 (LWP 9898)]
QQuickItem::stackBefore: Cannot stack QQuickRectangle(0x555556312ba0, parent=0x55555592d020, geometry=0,0 0x0) before QQuickPopupItem(0x555555acfa70), which must be a sibling
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:333:17: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.


Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault.
0x00007ffff6ace859 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
(gdb) c
Continuing.
[Thread 0x7fffb91e5640 (LWP 9886) exited]
[Thread 0x7fffa3fff640 (LWP 9887) exited]
[Thread 0x7fffa17fa640 (LWP 9892) exited]
[Thread 0x7fffa27fc640 (LWP 9890) exited]
[Thread 0x7fffbb7fe640 (LWP 9883) exited]
[Thread 0x7fffbaffd640 (LWP 9884) exited]
[Thread 0x7fffb99e6640 (LWP 9885) exited]

Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault.
0x00007ffff6ace859 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
(gdb) bt
#0  0x00007ffff6ace859 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#1  0x00007ffff6aeaa4e in QQmlPropertyCapture::captureProperty(QObject*, int, int, bool) ()
   from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#2  0x00007ffff69a78cd in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*) ()
   from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#3  0x00007fffd82c119b in ?? ()
#4  0x0000000000000000 in ?? ()