Qt qpa xcb qxcbconnection xcb error 3 badwindow sequence

Comments

This simplifies the handling with a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:
The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0
where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.
See here: vgc/vgc#6

This simplifies the handling with a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:
The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0
where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.
See here: vgc/vgc#6

This simplifies the handling with a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:
The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0
where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.
See here: vgc/vgc#6

This simplifies the handling with a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:
The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0
where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.
See here: vgc/vgc#6

This simplifies the handling with a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:
The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0
where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.
See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

Where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
and the command line is invalid, rarely produces a warning message on stderr,
when closed. This is of the form:
    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

This simplifies the handling by a virtual keyboard, especially, with the
autoshow feature of the onboard keyboard.

Note:

The (ApplicationModal) MessageBox, that appears when pressing the run button
(or the ENTER key) and the command line is invalid, rarely produces a warning
message on stderr, when closed. This is of the form:

    qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 888,
    resource id: 16810974, major code: 40 (TranslateCoords), minor code: 0

where the numbers for sequence and resource id change and the rest repeats.

This a known bug in Qt, but does not crash the program. So it can be ignored.

See here: vgc/vgc#6

Arch Linux

You are not logged in.

#1 2021-12-29 12:13:44

Outlook login qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow)

Hi, I need to acces to outlook for work but during the login, the browser spam redirection and them it return error 500 with this error:

clientIPAddress 2a01:e0a:4a4:55e0:24a7:6784:7c27:1770
X-ClientId: CEA5EC1FBBB6461F82805F5FC99DA59F
X-Redir-Error ArLym14Bq7g_48PK2Qg|AsTJRt4By0Qt48PK2Qg|ArLym14BQifj4sPK2Qg|AsTJRt4BPefT4sPK2Qg|ArLym14BuZmN4sPK2Qg|AsTJRt4BdZZ94sPK2Qg|ArLym14BjPst4sPK2Qg|AsTJRt4Bcm0e4sPK2Qg|ArLym14BcCTW4cPK2Qg|AsTJRt4BSL3G4cPK2Qg|ArLym14BhFWD4cPK2Qg|AsTJRt4BkDx04cPK2Qg|ArLym14BvlY04cPK2Qg|AsTJRt4Bp-8k4cPK2Qg|ArLym14B4lfl4MPK2Qg|AsTJRt4BcTrY4MPK2Qg|ArLym14BIPmd4MPK2Qg|AsTJRt4B6hyO4MPK2Qg|ArLym14B_-hN4MPK2Qg|AsTJRt4BECc74MPK2Qg|ArLym14Bk57a38PK2Qg
X-FEServer LNXP265CA0065
Date:29/12/2021 12:08:13

In journalct I have the corresponding error:

déc. 29 13:09:23 arch-vince kwin_x11[455]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 42840, resource id: 10518546, major code: 3 (GetWindowAttribu>
déc. 29 13:09:23 arch-vince kwin_x11[455]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42841, resource id: 10518546, major code: 14 (GetGeometry),>
déc. 29 13:09:23 arch-vince kwin_x11[455]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 42844, resource id: 10518546, major code: 3 (GetWindowAttribu>
déc. 29 13:09:23 arch-vince kwin_x11[455]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 42845, resource id: 10518546, major code: 14 (GetGeometry),>

Distro: Arch Linux x86_64 on 5.15.11-arch2-1.
Desktop: Plasma 5.23.4

I have tried many browser with same result. I can login in office 365 but not in outlook.

I know that Microsoft is not very helpfull with linux but it seems it come from QT, that why I ask for some help here.

Last edited by Vincentimetr (2021-12-29 12:14:22)

#2 2022-01-02 15:20:39

Re: Outlook login qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow)

This error is normal when a window disappears and should have no relation to whatever browser problem you have. This sounds like a networking problem. do you have access to a different network where you can test this, e.g. phone hotspot? Is your local time set up correctly? On the off chance that this is something related are you in a Wayland session and have you tried normal xorg?

#3 2022-01-02 19:43:38

Re: Outlook login qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow)

Hi, thank you for your answer.

This issue raise on any networks.

I can access this using the same computer on same network (Windows OS).
According to you suppositions, it could be local time issue OR wayland session.

For localtime, it seems ok:

timedatectl
Local time: dim. 2022-01-02 20:42:37 CET
Universal time: dim. 2022-01-02 19:42:37 UTC
RTC time: dim. 2022-01-02 19:42:37
Time zone: Europe/Paris (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

I have try this:

sudo timedatectl set-local-rtc 1

But same result.

Last edited by Vincentimetr (2022-01-03 09:58:30)

Источник

«XCB error: 3» and no window at startup

Details

Description

My build of qtcreator does not come up. After a pause I get the following on my console:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 240, resource id: 37748750, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 241, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 242, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 243, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 245, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 246, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 247, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 248, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 252, resource id: 37748750, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 253, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 254, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 255, resource id: 37748750, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 258, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 259, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 260, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 261, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 262, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 266, resource id: 37748753, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 267, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 268, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 269, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 271, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 272, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 273, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 274, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 278, resource id: 37748753, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 279, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 280, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 281, resource id: 37748753, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 284, resource id: 37748753, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 285, resource id: 37748753, major code: 8 (MapWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 302, resource id: 37748750, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 303, resource id: 37748750, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 304, resource id: 37748750, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 305, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 306, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 307, resource id: 37748750, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 308, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 309, resource id: 37748750, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 310, resource id: 37748750, major code: 8 (MapWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 312, resource id: 37748750, major code: 18 (ChangeProperty), minor code: 0

Attachments

Issue Links

QTCREATORBUG-26036 QtC has crashed unexpectedly

• Closed
  The issue is considered finished, the resolution is correct. Issues which are closed can be reopened. «>Closed

Источник

KDE: Не запускаются программы по иконкам на рабочем столе

Доброго времени суток всем!

Возникла маленькая проблемка. Когда — не заметил, т.к. данной функциональностью почти не пользуюсь. В общем суть в том, что если рабочий стол в KDE чист (либо все приложения свёрнуты, либо не запущенно ни одного приложения), то двойной клик по иконке на рабочем столе не приводит к запуску программы — вообще ни какого эффекта. Если же есть хоть какое-то окно (не развёрнутое во весь стол), то по двойному клику по иконке нужное приложение запускается.

А как ты эту иконку сделал? Можешь открыть ее текстовым редактором и скинуть содержимое? Обычно это .desktop или ссылка на .desktop файл.

Все иконки одинаково реагируют

Какие-то иконки остались ещё с устанвоки системы (домашняя папка и корзина, которые dolphin открывают и вроде как ранее работали — но повторюсь, почти не пользуюсь таким способом запуска приложений, и не уверен, что кагда-либо вообще так запускал ранее). Остальные из меню достал.
Но не суть.
Проблема в том, что все иконки работают одинаково — если чисто, то не запускаются, если есть хоть какое окно (абсолютно любое) — то все норм.

Прям бред какой-то.

Дополнение

В общем творятся какие-то странности.
Если рабочий стол чистый, то двойной клик по любой иконке на рабочем столе не даёт ни какого эффекта.
Если же на рабочем столе отображается хоть что-нибудь (кроме контекстного меню), например, меню запуска приложений (на панели), или меню запуска (по Alt+F2), или настройка панели, или отображение скрытых значков/уведомлений на панели, или настройка сети/заряда батареи/громкости (иконки на панели), то в этом случае двойной клик по тем же самым иконкам приводит к запуску нужного приложения.

плазма она коварна

На Manjaro нормально всё запускается, версии ПО как у тебя.

Очередное дополнение

Кнопка в правом верхнем углу рабочего стола (которая в настройках называется ‘Кнопка инструментов Plasma’) отрабатывает только один раз. После перезапуска plasmashell:

опять отрабатывает только один раз.

Может кто подскажет где логи посмотреть или как настроить плазму логировать события?

journalctl -b /usr/bin/plasmashell

Ситуация один в один, та же проблема!

Там хоть какое-то действие выполняется — открывается редактор.
В рассматриваемом случае, нет ни какой реакции вообще.

Криминала не обнаружено

Пробовал, ничего в логах необычного не зафиксировано.

в домашнем каталоге юзера в.xsession-errors тоже ничего?

Ошибки есть

Вот эти записи появляются когда Dolphin открывается по двойному клику по иконке на рабочем столе (т.е. были выполнены условия для этого):

А если настроить запуск/открытие на одиночный клик?

Одиночный работает правильно

Если настроить на одиночный клик, то всё работает.
Но я привык к двойному. Да ладно, проблема есть, но не критичная, т.к. в основном пользуюсь другими способами запуска приложений (рабочий стол почти всегда полнсотью закрыт окнами).

Значит, надо писать багрепорт

Завтра попробую завести, если ещё не завели.
Да и для ‘кнопки инструментов Plasma’ проблема однократного запуска присутствует.

Покажите .desktop файл (любой)? интересуют права/владелец на него?

Если остались ещё сомнения

Раз так хочется взглянуть на содержимое файлов, то вот самый мелкий (в остальных полно записей, связанных с i18n, но двойной клик по любому файлу работает одинаково):

Владелец — пользователь ‘********’, права для пользователя — ‘rwx’ (надеюсь понятно, что под ****** прячется реальное имя)
Если Вас пугает содержимое, то спешу успокоить. Этот *.desktop файл рабочий — нужную программу запускает, но с оговорками. Самый простой способ — ткнуть по нему мышкой (выделить) и нажать Enter. Либо настроить окружение на запуск программ одним кликом.
Если же очень сильно хочется запустить именно двойным кликом мышки, то без выполнения условий, описанных в начале темы, этого сделать не получиться.

И дело тут не в содержимом или правах файла, а в поведении либо плазмоида Desktop (или как он там правильно называется), либо plasmashell.

Всё равно задам вопрос: ты проверял на более простых примерах? Хотя бы бы на запуске konsole?

Источник

Arch Linux

You are not logged in.

#1 2020-02-19 08:22:50

KDE problems

Since I installed Arch KDE on the new PC, I have continuous warnings in the journal and, when I make intensive use of graphics, even crashes.
The warnings (very many) concern kde, for example:

Others concern QT:

I also insert a line from Xorg.0.log that is about sddm:

Other types of error concern colord:

I tried formatting and reinstalling (following the wiki scrupulously) but I get exactly the same results. In the meantime I also changed my video card from AMD RX 5700 XT to Nvidia 1660. But the problems continue.

I also tried to delete all plasma* entries from

/.config, but I always get the same errors.

I also leave the sequence of the journal in which, working with a video editing program, I got a crash:

What I’m asking is how to investigate KDE to get to the bottom of the problems. I can’t find anything on Google or the forum. The only idea that came to me is the fact that I don’t install «Plasma» or «Plasma-meta», but «Plasma-desktop». Is it possible that in this minimal installation something necessary is missing?

My PC: Asus X570; Ryzen 3700x; Nvidia 1660.
A complete journal is at:

#2 2020-02-19 09:09:55

Re: KDE problems

You can ignore most of these. The crash has no relevance to KDE, but reads like CPU microcode bugs. Read and apply early microcode loading: https://wiki.archlinux.org/index.php/Microcode at the very least, maybe even try updating your BIOS/UEFI.

I don’t really know the deal with the invalid metadata, but I have that as well and it doesn’t seem to cause any harm, the XCB errors are normal and are a side effect of async communication between xorg and the application (if you close a window, xorg might unregister/kill it before the Qt application gets that information, and when it tries to access something that it tought was still available it will log out that warning, it’s harmless)

#3 2020-02-19 09:43:23

Re: KDE problems

The ryzen 3700x is new and still not very well supported. So there are frequent releases of microcode; I do all the updates. The Asus TUF x570 Bios is updated, even if the last release is in November (and for a new chipset it seems strange not to make frequent updates).
The fact that I don’t have all these warnings on my old laptop confirms that it depends on too new hardware.
Thanks for the clarifications and reassurances, the messages about sddm remain; do you think they are ignorable? The line taken from Xorg.0.log I don’t understand it at all (the file obviously exists: User and Groupd owner = sddm), the rest of the log doesn’t report the slightest error.

Last edited by apaz (2020-02-19 09:45:24)

#4 2020-02-19 09:53:13

Re: KDE problems

Yes if your vendor is that slow with UEFI updates you definitely should set up early microcode loading, those are likely updated more frequently (from what I’ve seen late loading is quite unreliable and not guaranteed to be properly applied, explicitly setting up early loading should be preferred).

Источник

Hi,

I’m running KDE Plasma on Arch, and when i attempt to start GUI of a few GTK programs ( Gufw, timeshift etc) I get no result.

When I run journalctl -f, and attempt again I get the follwing log output

LT430 kwin_x11[1093]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 25191, resource id: 39845942, major code: 18 (ChangeProperty), minor code: 0 Jan 23 14:37:53 LT430 systemd-coredump[4907]: Process 4896 (python3) of user 0 dumped core.

                                          Stack trace of thread 4896:
                                          #0  0x00007f32fd65cf29 n/a (libgtk-3.so.0)
                                          #1  0x00007f32fd4eb5f9 n/a (libgtk-3.so.0)
                                          #2  0x00007f32fd501895 n/a (libgtk-3.so.0)
                                          #3  0x00007f32fd4ec9ad n/a (libgtk-3.so.0)
                                          #4  0x00007f32fd5017d0 n/a (libgtk-3.so.0)
                                          #5  0x00007f32fd501826 n/a (libgtk-3.so.0)
                                          #6  0x00007f32fd4ed344 n/a (libgtk-3.so.0)
                                          #7  0x00007f3304a57c98 g_type_create_instance (libgobject-2.0.so.0)
                                          #8  0x00007f3304a37729 n/a (libgobject-2.0.so.0)
                                          #9  0x00007f3304a38f6d g_object_new_with_properties (libgobject-2.0.so.0)
                                          #10 0x00007f3304a39a22 g_object_new (libgobject-2.0.so.0)
                                          #11 0x00007f32fd509fbb n/a (libgtk-3.so.0)
                                          #12 0x00007f32fd6f521a n/a (libgtk-3.so.0)
                                          #13 0x00007f3304a57c98 g_type_create_instance (libgobject-2.0.so.0)
                                          #14 0x00007f3304a37729 n/a (libgobject-2.0.so.0)
                                          #15 0x00007f3304a3925d g_object_newv (libgobject-2.0.so.0)
                                          #16 0x00007f32fd490735 n/a (libgtk-3.so.0)
                                          #17 0x00007f32fd491dc6 n/a (libgtk-3.so.0)
                                          #18 0x00007f32fd493842 n/a (libgtk-3.so.0)
                                          #19 0x00007f330475b512 n/a (libglib-2.0.so.0)
                                          #20 0x00007f330475c418 g_markup_parse_context_parse (libglib-2.0.so.0)
                                          #21 0x00007f32fd493d22 n/a (libgtk-3.so.0)
                                          #22 0x00007f32fd48d6ce gtk_builder_add_from_file (libgtk-3.so.0)
                                          #23 0x00007f330450a1c8 ffi_call_unix64 (libffi.so.6)
                                          #24 0x00007f3304509c2a ffi_call (libffi.so.6)
                                          #25 0x00007f3304ed6b34 n/a (_gi.cpython-36m-x86_64-linux-gnu.so)
                                          #26 0x00007f3304ed87b8 n/a (_gi.cpython-36m-x86_64-linux-gnu.so)
                                          #27 0x00007f3304ecc54a n/a (_gi.cpython-36m-x86_64-linux-gnu.so)
                                          #28 0x00007f330761ad85 _PyObject_FastCallDict (libpython3.6m.so.1.0)
                                          #29 0x00007f330766be1e n/a (libpython3.6m.so.1.0)
                                          #30 0x00007f33075fc92a _PyEval_EvalFrameDefault (libpython3.6m.so.1.0)
                                          #31 0x00007f330766b33b _PyFunction_FastCallDict (libpython3.6m.so.1.0)
                                          #32 0x00007f330761af5f _PyObject_FastCallDict (libpython3.6m.so.1.0)
                                          #33 0x00007f330761bd13 _PyObject_Call_Prepend (libpython3.6m.so.1.0)
                                          #34 0x00007f330761bdfb PyObject_Call (libpython3.6m.so.1.0)

google is giving me too many results, and maybe i dont understand them .. but the few people reported fixing the issue:

a. download and run a new python version

b. change the themes back to default

c. set the environment variable QT_DEVICE_PIXEL_RATIO=1

nothing seems to work, hoping someone can point me in the right direction.