Содержание
- Arch Linux
- #1 2015-02-04 04:17:03
- [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #2 2015-02-04 07:48:40
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #3 2015-02-04 13:57:39
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #4 2015-02-04 14:04:17
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #5 2015-02-04 14:40:15
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #6 2015-02-04 15:14:55
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- #7 2015-02-05 03:03:04
- Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
- Debian User Forums
- Random logout in Buster/KDE
- Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Re: Random logout in Buster/KDE
- Намертво зависает(не могу например нум лок вырубить) линукс при работе в интернете.
- Ну хз
- Re: Ну хз
- Re: Нет
- Re: Хм
- Re: Хм
- Re: Хм
Arch Linux
You are not logged in.
#1 2015-02-04 04:17:03
[SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
I recently upgraded from KDE 4.12 to Plasma 5.2 following the instructions in this thread. The upgrade went smoothly and I was able to login and use the new Plasma 5 desktop successfully for a couple of days. However, today on boot and login (using sddm), the KDE loading screen is displayed and the progress bar gets to 100%, but the plasma desktop never loads.
It appears that plasma is running (in some capacity), because if I let it sit for awhile it will display the KDE lock screen and even let me «unlock» the session, which brings me back to the loading screen. If I create a new user from the command line, I am able to login successfully as this new user. I tried removing my
/.kde4 and some other config files from my existing profile with no improvement in behavior.
What else can I try to resolve this problem with Plasma 5?
Last edited by amartin (2015-02-06 02:38:12)
#2 2015-02-04 07:48:40
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
Try removing all plasma* files and dirs from .config and .cache
#3 2015-02-04 13:57:39
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
I gave that a try but no change in behavior. Any other ideas?
#4 2015-02-04 14:04:17
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
Have you selected «plasma» in the SDDM login screen?
#5 2015-02-04 14:40:15
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
Yes, I also tried invoking plasmashell manually from another TTY (via export DISPLAY=:0.0 && /usr/bin/plasmashell —shut-up) but no luck. Note that the new user I created can login to «plasma» from sddm without issue
#6 2015-02-04 15:14:55
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
Hi amartin,
Are you using any third-party plasma widget?
can you post the content of your
/.xsession-errors just after a reboot and (failed) login?
It may be useful to check also the journal for errors:
— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes
#7 2015-02-05 03:03:04
Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar
I am not using any third-party plasma widgets. Here’s the contents of
/etc/locale.conf: line 1: en_US.UTF-8: command not found
startkde: Starting up.
kbuildsycoca5 running.
Baloo File Indexing has been disabled
Already running
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running.
kbuildsycoca4(640) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(640) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(640) kdemain: Emitting notifyDatabaseChanged ()
requisition.width, requisition.height = self.__child.size_request ()
requisition.width, requisition.height = self.__child.size_request ()
gtk.main()
gtk.main()
kio_file(674) kdemain: Starting 674
kio_file(676) kdemain: Starting 676
kio_file(677) kdemain: Starting 677
kio_file(678) kdemain: Starting 678
dolphin(562) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Service started, version: 6.2.0
Service started, version: 6.2.0
Also, here’s the errors in «journalctl -b»:
Источник
Debian User Forums
Random logout in Buster/KDE
Random logout in Buster/KDE
#1 Post by NFT5 » 2019-08-05 10:52
I recently installed a clean Buster and chose the Plasma desktop.
I’ve been experiencing random logouts, usually when I click something with the mouse. That it’s logging out, not restarting, leads me to think that it’s display server related, but I’m not sure and can’t find any consistent errors that would point to a single problem.
Google returns a few instances of similar problems, usually on Mint (not that that’s relevant, I think) but no consistent answers.
So, I’m looking for some ideas on where to look to solve the problem.
These CPUs do run hot but I have a big cooler fitted and it usually sits around 59C. Weather is cool here and other sensor temperatures range 18-26C. System gets cleaned every few months. Pretty sure it isn’t a hardware problem anyway. No problem on this machine running Debian 8 or 9, MATE and XFCE respectively.
Re: Random logout in Buster/KDE
#2 Post by ruwolf » 2019-08-05 12:41
Re: Random logout in Buster/KDE
#3 Post by NFT5 » 2019-08-05 13:08
Re: Random logout in Buster/KDE
#4 Post by Head_on_a_Stick » 2019-08-05 14:53
Re: Random logout in Buster/KDE
#5 Post by NFT5 » 2019-08-05 21:10
Now wait for the next crash.
Re: Random logout in Buster/KDE
#6 Post by efrpcabo » 2019-08-30 08:33
NFT5 wrote: systemd-coredump installed.
Now wait for the next crash.
Re: Random logout in Buster/KDE
#7 Post by NFT5 » 2019-08-31 01:58
As per PM, no, I haven’t definitively found the cause.
I’ve installed the firmware packages and amd microcode (I have an AMD CPU). I’ve also (for what it was worth) changed where various USB plugs were plugged in on the back of the computer. This was something that was suggested in one of the searches I did, on the basis that some peripheral may have been causing some conflict with the controller that it was plugged in to. Seems a bit random, but i figured it can’t hurt.
Also installed the coredumpctl package. Not that this will fix the problem, but may help with diagnosis in the future. The reports mean absolutely nothing to me but I keep them each time the crash/logout happens in the hope that they may be useful to someone else, i.e. a dev.
in case it was hardware I increased the threshold temperatures in the BIOS. My CPU and system temperatures are typically quite low but the graphics chip seems to run much higher. Nothing in the reports to suggest that this is the problem but gave them all another 10C anyway. As above, it can’t hurt.
Again i can’t point to this as a definitive cause but I’ve changed the desktop theme as well. Back in the days of Jessie MATE some themes caused panel crashes and a change fixed that problem.
Since the installation is still new I’m still in the process of setting up, so lots of little tweaks here and there. Further, there have been a lot of updates for Buster in the past month and it’s entirely possible that one or some of those may have helped.
In combination, all, some or one of the above seem to have reduced the incidence of the logouts. Still happen occasionally, but for now I can live with that, even though I don’t think that i should have to. I’m not really happy that each new iteration of Debian seems to be less reliable and stable than its predecessor and takes ever increasing amounts of work to make work the way it should. I still have one notebook running Wheezy — it has been almost faultless since the original installation — just worked from day one.
Re: Random logout in Buster/KDE
#8 Post by efrpcabo » 2019-08-31 20:56
I understand your feelings.
I use Debian because I like a stable system.
Before Debian, I used Ubuntu and Xubuntu, but I moved to Debian because of constant issues.
I used Debian 7 and Debian 8 for the past 5 or 6 years.
I just switched to Debian 10 because Debian 8 as reached end of life, because for me it was working without issues for the last 2 years.
But, since I installed Buster I have had much more issues than I expected.
For example, I use the XFCE version and I noticed that only a few weeks ago Debian 8, 9 and 10 all used XFCE version 4.12.
I believe that shouldn’t happen because that 3 Debian versions share the «issues» that this version of XFCE has.
I think it would be nice to have even more stability in the stable version, even if that means sacrificing newer versions of programs, etc.
I really am grateful for Debian, please don’t get me wrong.
Источник
Намертво зависает(не могу например нум лок вырубить) линукс при работе в интернете.
Мой пекатор Acer Aspire TC-703 древний, как мир. Сабжи: коричная мята 19.1 и кубунта вроде 18.04. На винде кстати 2 года ничего ни разу не зависло. Скопировал сислог за 4 минуты, мб там кроется секрет.
Оформлять надо нормально, иначе это читать невозможно
Ну хз
Почему-то ни в спойлер, ни в список этот здоровенный лог не помещается.
тег code пробовал?
Не шарю, посвяти
Re: Ну хз
Используй тег [code][/code] и распиши нормально конфигурацию, сколько оперативной памяти, какой процессор, какой видео адаптер.
Что в логе xorg-server.
А так, если у тебя всего 2Гб оперативной памяти, то предполагаю, что у тебя просто заканчивается свободная оперативная память, а в linux при такой ситуации система начинает сильно тормозить и даже переставать откликаться.
Re: Нет
Это не ответ, открой ссылку :
Внимание: прочитайте описание разметки LORCODE
Она указана в форме посещения комментария на форум и прочти.
Если ты не можешь это сделать, то почему должны тебе помогать, если ты не в состоянии сделать усилия чтобы правильно оформить свой комментарий.?
Я думаю, что это очень логичный ответ, потому что на это у меня и были подозрения. Видимо придётся вернуть этот компик на винду.
Или перейти на Linux с Xfce или LXDE — они меньше жрут.
лорчую бродкомовский вайфай. мешанину из букв не читал.
придётся вернуть этот компик на винду.
Это правильное решение.
Ты еще не дорос для чего-то другого.
Это тролль или у него лапки?
Щвабодные видеодрова как обычно, небось.
Re: Хм
про LORCODE тебе уже проорали, а говорю открой для себя pastebin©
Mint он такой. бывает и на неделю уходит в себя от современного веба. попробуй debian и поменьше в него пихай — только самое необходимое 🙂
LOR опять не подводит нас. Шикарная аудитория)
Re: Хм
Не открывай 20 вкладок разом, 5-10 максимум самое то.
Видимо придётся вернуть этот компик на винду.
Посоны, надо уважить дядю. Или нас на понт берут?
я тебе так скажу пробуй 16.04 или 18.10
Re: Хм
проблема не с 2 гигами, а с выбором софта. я много лет жила на конфигурации 2 ядра x 2 гига и это была моя рабочая машина. и браузер работал нормально. у меня до сих пор этот ноут стоит и работает. я не знаю, что там нынче на мяте искаропки, но наверняка какая-нибудь жирнота. начать с того, что снести жирноту и вместо неё поставить хотя бы xfce. или lxde.
Через что в интернеты выходишь?
И не поспоришь, ведь выбор сайтов — это нынче тоже выбор софта.
обычные сайты (лор, юутубчик, любой девелопмент и т.д.) прекрасно работают. баннеры у меня режутся. не из соображений экономии процессора или трафика (хотя и это тоже имеет место при отрезании ненужного в современнном говновебе), а из соображений эстетики и нежелания засирать свой мозг.
вообще, не сталкивалась с тем, чтобы что-то не работало в вебе из нужного.
Ох уж эти балаболки.
Привет, Царь. Что не зарегаешься?
У тебя браузер сожрал всю память и протёк в своп.
а что мешает сидеть на ЛОРе? комп у меня всё равно включен 24/7. я могу прямо не вылезая с ЛОРа петь вокальные упражнения или программировать. или выгуливать хамелеона. пока я тут сижу, хамелеон по мне ползает.
До этих ваших школоцарей тут был мегабакс с такими выражениями. Ох уж эти ньюфаги.
мегабакс с такими выражениями. Ох уж эти ньюфаги.
Просто он был так уныл, что даже не запомнился.
У меня на работе как раз 2 гига 2 ядра, при этом KDE 5 и Debian 9. Казалось бы, злобная смесь, но все летает (и в интернете, Chromium и Firefox). Никакой «маргинализации» не применяю. Система 32 бит.
LXDE я ставил только когда было 768 Мб оперативной памяти и Pentium 3. Там результат по сравнению с KDE4 был заметен.
А у ТСа скорее всего с железом проблемы. Либо перегрев, либо кривые дрова.
ну, мне кроме браузера надо было ещё работать. писать софт, отлаживать, тестировать. а он сам по себе иногда был жручим. поэтому я ставила xfce, а потом перешла на wm. но в любом случае 2 ядра 2 гига — это вполне себе возможная комбинация для работы под линём. а кроме сжирания памяти, зависать в браузерах может только видео или какие-нибудь злобные плагины.
Один фрейм ютуба, даже тупо встроенный на какой-нибудь сайт, который ещё не запускался и не грузил видео — жрёт около 200 МБ рамы.
А ты уверена, что ты выгуливаешь хамелеона, а не хамелеон тебя?
Я, собсна, потому и спросил, через что ТС выходит в интернеты. Потому что у меня аналогичные проблемы из-за кривого драйвера на модем, который до сих пор полностью не починили: при активном исходящем трафике иногда крашится ядро. Нумлок обрабатывается прерыванием, поэтому должен реагировать мгновенно даже при зашкаливающем в десятки раз LA; если не работает, то и ядро, скорее всего, уже не работает.
На лор ходишь потому, что здесь нет гифок и это единственный сайт, который у тебя прогружается?
Как раз ЛОР на GPRS не грузится, соединения сразу дропаются.
ну, хамелеон — сверхсущество. он контролирует всех вокруг себя. я его летом брала с собой, когда ходила куда-нибудь. он сидел на шляпе. так при входе в любой магазин хамелеон захватывает контроль и все присутствующие переключаются на него. рептилоиды могут легко захватить мир.
Источник
Coriolis
Registered Member
- Posts
- 2
- Karma
- 1
Frequent plasmashell crashes with segmentation fault (11)
Sun Jul 26, 2015 9:11 pm
I’m using arch linux and plasma 5.3.2. The problem is, even on clear installation plasmashell keeps crashing frequently. I’m still able to do my things, as the shell automatically restarts. I had same problem on clean installation of kubuntu 15. The crash occurs mostly on browsing menu or adjusting widgets and interface layout. My specs are: pentium 2020m, nvidia gt 740m, 4 gb ram. Also, crash occurs almost always when shutting down or logging off. I’m also interested if this process creates a dump or a log file (or any other garbage after crash), and, if it does, where.
Lekensteyn
Registered Member
- Posts
- 5
- Karma
- 1
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sun Jul 26, 2015 9:52 pm
Can you look in your logs (journalctl)? I also see a crash in kactivitymanagerd on logout (which does not happen when I run
- Code: Select all
kactivitymanagerd stop
before logout)., but you claim that plasmashell is crashing. In your logs, look for «segfault» and (stacktrace) messages from drkonqi.
Have you enabled testing or other non-default repos?
Coriolis
Registered Member
- Posts
- 2
- Karma
- 1
Re: Frequent plasmashell crashes with segmentation fault (11
Mon Jul 27, 2015 12:19 am
I dont have testing enabled, the only non-default repo I have is multilib one, though I enabled it after crashes started to occur. There are logs from the second the crash happened, no segfault messages though:
Jul 27 02:46:38 tricopc kdeinit5[492]: Service «org.kde.StatusNotifierHost-585» unregistered
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Requested backend: «»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Lookup paths: («/usr/lib/qt/plugins», «/usr/lib/kf5»)
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Skipping «XRandR 1.1» backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Unloading «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr: Connected output 67 to CRTC 63
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Detected XRandR 1.4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Base: 89
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Error: 147
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Loading «XRandR» backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Failed to register as DBus service: another launcher already running?
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: «»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kwin_x11[568]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43503, resource id: 54525958, major code: 18 (ChangeProperty), minor code: 0
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Unregistering key «Alt+F1» for «plasmashell» : «activate widget 2»
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Registering key «Alt+F1» for «plasmashell» : «activate widget 2»
Jul 27 02:46:38 tricopc drkonqi[847]: Using /proc to determine executable path
Jul 27 02:46:38 tricopc drkonqi[847]: Executable is: «/usr/bin/plasmashell»
Jul 27 02:46:38 tricopc drkonqi[847]: Executable exists: true
Jul 27 02:46:38 tricopc drkonqi[847]: Unable to find an internal debugger that can work with the KCrash backend
Jul 27 02:46:38 tricopc drkonqi[847]: Enabling drkonqi crash catching
Jul 27 02:46:38 tricopc drkonqi[847]: Invalid pixmap specified.
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
— Logs begin at Sat 2015-07-25 23:08:47 MSK, end at Mon 2015-07-27 03:14:48 MSK. —
Jul 27 02:46:38 tricopc kdeinit5[492]: Service «org.kde.StatusNotifierHost-585» unregistered
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Requested backend: «»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Lookup paths: («/usr/lib/qt/plugins», «/usr/lib/kf5»)
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Skipping «XRandR 1.1» backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Unloading «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying «/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr: Connected output 67 to CRTC 63
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Detected XRandR 1.4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Base: 89
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Error: 147
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Loading «XRandR» backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Failed to register as DBus service: another launcher already running?
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: «»
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kwin_x11[568]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43503, resource id: 54525958, major code: 18 (ChangeProperty), minor code: 0
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» ) to KScreen::Output(Id: 67 , Name: «LVDS1» ) ( «LVDS1» )
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Unregistering key «Alt+F1» for «plasmashell» : «activate widget 2»
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Registering key «Alt+F1» for «plasmashell» : «activate widget 2»
Jul 27 02:46:38 tricopc drkonqi[847]: Using /proc to determine executable path
Jul 27 02:46:38 tricopc drkonqi[847]: Executable is: «/usr/bin/plasmashell»
Jul 27 02:46:38 tricopc drkonqi[847]: Executable exists: true
Jul 27 02:46:38 tricopc drkonqi[847]: Unable to find an internal debugger that can work with the KCrash backend
Jul 27 02:46:38 tricopc drkonqi[847]: Enabling drkonqi crash catching
Jul 27 02:46:38 tricopc drkonqi[847]: Invalid pixmap specified.
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
I also have this spam occupying majority of my log, what should I disable to stop these messages?
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: Output: 67
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: Property: Backlight
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: State (newValue, Deleted): 0
luebking
- Karma
- 0
Re: Frequent plasmashell crashes with segmentation fault (11
Mon Jul 27, 2015 6:40 am
Seems you’ve drkonqi installed, but it’s not showing up??
Enable core dumps:
https://blogs.kde.org/2009/03/27/settin … core-dumps
(if you generally know how anything about coredumps, «export KDE_DEBUG=1»)
> what should I disable to stop these messages?
Have
- Code: Select all
[Rules]
kscreen.xcb.helper=false
in ~/.config/QtProject/qtlogging.ini
Lekensteyn
Registered Member
- Posts
- 5
- Karma
- 1
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Mon Jul 27, 2015 9:49 am
Try installing gdb (drkonqi 5.3.2-2 added this required dependency) for sane traces. If coredumps are created, look at coredumpctl list.
alexbel
Registered Member
- Posts
- 4
- Karma
- 0
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 4:19 pm
luebking wrote:in ~/.config/QtProject/qtlogging.ini
qtlogging.ini doesn’t exist there.
If I created that file and put kscreen.xcb.helper=false, that would not have any effect.
I have ~/.config/QtProject.conf. I’ve tried to put the settings in it, but no result as well.
P.S.
I also have the same issue with segmentation fault (11) and the journalctl output looks very similar to the logs above.
- Code: Select all
$ kde-open -v
Qt: 4.8.7
KDE Development Platform: 4.14.10
KIO Client: 2.0$ uname -r
4.1.3-1-ARCH
Lekensteyn
Registered Member
- Posts
- 5
- Karma
- 1
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 4:37 pm
alexbel wrote:
luebking wrote:in ~/.config/QtProject/qtlogging.ini
qtlogging.ini doesn’t exist there.
If I created that file and put kscreen.xcb.helper=false, that would not have any effect.
I have ~/.config/QtProject.conf. I’ve tried to put the settings in it, but no result as well.
That folder and file does not exist by default. To reduce log spam in journal, I put this in ~/.config/plasma-workspace/env/disable-kde-spam.sh
- Code: Select all
# 2015-07-24 Attempt to force logging to ~/.xsession-errors
# https://stackoverflow.com/a/26325743
# http://lists.qt-project.org/pipermail/development/2014-July/017588.html
# http://www.kdab.com/wp-content/uploads/stories/slides/Day2/KaiKoehne_Qt%20Logging%20Framework%2016_9_0.pdf
# https://git.reviewboard.kde.org/r/121903/
# http://doc.qt.io/qt-5/qloggingcategory.html
export QT_LOGGING_TO_CONSOLE=1
alexbel wrote:P.S.
I also have the same issue with segmentation fault (11) and the journalctl output looks very similar to the logs above.
- Code: Select all
$ kde-open -v
Qt: 4.8.7
KDE Development Platform: 4.14.10
KIO Client: 2.0$ uname -r
4.1.3-1-ARCH
That is your library information for KDE 4.
BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?
alexbel
Registered Member
- Posts
- 4
- Karma
- 0
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 5:25 pm
Lekensteyn wrote:That is your library information for KDE 4.
oops.
- Code: Select all
Qt: 5.5.0
KDE Frameworks: 5.12.0
Lekensteyn wrote:BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?
Yes it does. Usually it happens few times a day. I didn’t notice any pattern for the events, except a crash on logout. It’s the most frequent one.
Also, if plasmashell has crashed then the old process would be hanging in memory. At the end of the day I can see 4-6 copies (dead/abandoned?) of plasmashell.
Lekensteyn
Registered Member
- Posts
- 5
- Karma
- 1
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 5:35 pm
Lekensteyn wrote:BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?
Yes it does. Usually it happens few times a day. I didn’t notice any pattern for the events, except a crash on logout. It’s the most frequent one.
Also, when plasmashell crashes the old process is still in memory. At the end of the day I can see 4-6 copies (dead/abandoned?) of plasmashell.[/quote]
Have you installed the gdb package? These processes are still in memory because drkonqi (crash reporter) tries to present you information about the crash (for debugging purposes). You can find those processes with ps uww -C drkonqi. To kill those plasmashell processes, try sending SIGTERM to drkonqi.
alexbel
Registered Member
- Posts
- 4
- Karma
- 0
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 7:39 pm
Lekensteyn wrote:Have you installed the gdb package? These processes are still in memory because drkonqi (crash reporter) tries to present you information about the crash (for debugging purposes). You can find those processes with ps uww -C drkonqi. To kill those plasmashell processes, try sending SIGTERM to drkonqi.
I did, but have no idea how to use it I’m a web developer. Anyway, I’m going to try to debug that.
Thanks for your help!!!
Lekensteyn
Registered Member
- Posts
- 5
- Karma
- 1
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Sat Aug 01, 2015 8:08 pm
By installing gdb, drkonqi will be able to generate backtraces. You do not need to run it yourself.
I managed to capture the backtrace for a such a crash (could be different from yours though) and reported it at
https://bugs.kde.org/show_bug.cgi?id=350866
alexbel
Registered Member
- Posts
- 4
- Karma
- 0
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Fri Aug 07, 2015 1:11 pm
davidmar
Registered Member
- Posts
- 9
- Karma
- 0
- OS
-
Re: Frequent plasmashell crashes with segmentation fault (11
Thu Aug 13, 2015 12:54 am
There is also a problem relating to xproto which causes a segfauly in kactivitymanager. It will often show up as something like:
- Code: Select all
kactivitymanage[720]: segfault at 7f2ac5430d10 ip 00007f2ac578b881 sp 00007fffb3881ce8 error 4 in libQt5Sql.so.5.5.0[7f2ac5735000+41000]
See
https://bugs.freedesktop.org/show_bug.cgi?id=91316
https://bbs.archlinux.org/viewtopic.php?id=199812
For a long time this was crashing my desktop and taking me back to sddm 2 or 3 times a day until I downgraded Xproto to 7.0.27 on Gentoo. with other distros they probably put it all in their xorg-server package and might apply a special patch for it as they did in Arch Linux.
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
© Copyright 2012 KDE Community Forum Team. All rights reserved.
KDE Community Forums has no liability for any content or post. All messages belong to and are the opinion of their respective authors.
KDE and K Desktop Environment are trademarks of KDE e.V. • For more details, contact the Forum Administrators.
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
still random freeze [solved]
hi again,
i do have 18.3 with kde running. still got some freezes. here is the output before the last freeze. graphicscard is a palit kalmx
i hinestly dont know, where to start…maybe the graphicscard ? i tried several drivers too. alas, no success
Code: Select all
:41 antichrist org.debian.apt[1234]: 14:30:41 AptDaemon.Worker [INFO]: Updating cache
Dez 31 14:30:43 antichrist AptDaemon.Worker[21479]: INFO: Finished transaction /org/debian/apt/transaction/f76dde546e754a6ea9178d011cbe8dd9
Dez 31 14:30:43 antichrist org.debian.apt[1234]: 14:30:43 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/f76dde546e754a6ea9178d0
Dez 31 14:31:10 antichrist sudo[21472]: pam_unix(sudo:session): session closed for user root
Dez 31 14:41:41 antichrist AptDaemon[21479]: INFO: Quitting due to inactivity
Dez 31 14:41:41 antichrist AptDaemon[21479]: INFO: Quitting was requested
Dez 31 14:41:41 antichrist org.debian.apt[1234]: 14:41:41 AptDaemon [INFO]: Quitting due to inactivity
Dez 31 14:41:41 antichrist org.debian.apt[1234]: 14:41:41 AptDaemon [INFO]: Quitting was requested
Dez 31 14:42:48 antichrist dhclient[3422]: DHCPREQUEST of 192.168.43.121 on wlp2s0 to 192.168.43.1 port 67 (xid=0x1979cc5d)
Dez 31 14:42:48 antichrist dhclient[3422]: DHCPACK of 192.168.43.121 from 192.168.43.1
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4773] address 192.168.43.121
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4773] plen 24 (255.255.255.0)
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4774] gateway 192.168.43.1
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4774] server identifier 192.168.43.1
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4774] lease time 3600
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4774] hostname 'antichrist'
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4775] nameserver '192.168.43.1'
Dez 31 14:42:48 antichrist NetworkManager[1238]: <info> [1514727768.4775] dhcp4 (wlp2s0): state changed bound -> bound
Dez 31 14:42:48 antichrist dbus[1234]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatch
Dez 31 14:42:48 antichrist systemd[1]: Starting Network Manager Script Dispatcher Service...
Dez 31 14:42:48 antichrist dhclient[3422]: bound to 192.168.43.121 -- renewal in 1285 seconds.
Dez 31 14:42:48 antichrist dbus[1234]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 31 14:42:48 antichrist systemd[1]: Started Network Manager Script Dispatcher Service.
Dez 31 14:42:48 antichrist nm-dispatcher[9205]: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dez 31 14:42:48 antichrist nm-dispatcher[9205]: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dez 31 15:04:13 antichrist dhclient[3422]: DHCPREQUEST of 192.168.43.121 on wlp2s0 to 192.168.43.1 port 67 (xid=0x1979cc5d)
Dez 31 15:04:13 antichrist dhclient[3422]: DHCPACK of 192.168.43.121 from 192.168.43.1
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2204] address 192.168.43.121
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2204] plen 24 (255.255.255.0)
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2205] gateway 192.168.43.1
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2205] server identifier 192.168.43.1
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2205] lease time 3600
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2205] hostname 'antichrist'
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2206] nameserver '192.168.43.1'
Dez 31 15:04:13 antichrist NetworkManager[1238]: <info> [1514729053.2206] dhcp4 (wlp2s0): state changed bound -> bound
Dez 31 15:04:13 antichrist dbus[1234]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatch
Dez 31 15:04:13 antichrist systemd[1]: Starting Network Manager Script Dispatcher Service...
Dez 31 15:04:13 antichrist dhclient[3422]: bound to 192.168.43.121 -- renewal in 1350 seconds.
Dez 31 15:04:13 antichrist dbus[1234]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dez 31 15:04:13 antichrist systemd[1]: Started Network Manager Script Dispatcher Service.
Dez 31 15:04:13 antichrist nm-dispatcher[12197]: req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
Dez 31 15:04:13 antichrist nm-dispatcher[12197]: req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:12:24 antichrist kernel: [UFW BLOCK] IN=wlp2s0 OUT= MAC=34:97:f6:68:e1:44:dc:ee:06:c1:e3:cc:08:00 SRC=82.6.31.58 DST=192.168.43.121 LEN=1500 TOS=
Dez 31 15:17:01 antichrist CRON[30778]: pam_unix(cron:session): session opened for user root by (uid=0)
Dez 31 15:17:01 antichrist CRON[30779]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dez 31 15:17:01 antichrist CRON[30778]: pam_unix(cron:session): session closed for user root
lines 1791-1823/1823 (END)
here is my hardware
Code: Select all
00:00.0 Host bridge: Intel Corporation Device 591f (rev 05)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 05)
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:17.0 SATA controller: Intel Corporation Device a282
00:1b.0 PCI bridge: Intel Corporation Device a2e7 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a290 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c5
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c82 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 0fb9 (rev a1)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe Wireless Network Adapter (rev 01)
04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
Code: Select all
Graphics: Card: NVIDIA Device 1c82
Display Server: X.Org 1.18.4 driver: nvidia Resolution: 1920x1200@59.95hz
GLX Renderer: GeForce GTX 1050 Ti/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.98
greets gunter
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Sun Dec 31, 2017 11:01 am
sorry, i forgot to mention,
i do have tested the usual suspects.
ram > passed
ssd > passed
the freeze is still randomly. and i dont know where to start. journalctl messages dont help me either. maybe other people can see anything ?
-
Laurent85
- Level 17
- Posts: 7015
- Joined: Tue May 26, 2015 10:11 am
Re: still random freeze
Post
by Laurent85 » Sun Dec 31, 2017 11:30 am
Run a Mint usb live session for some hours, use the desktop like you normally do. If the computer still freezes randomly chances you are facing an hardware failure.
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Sun Dec 31, 2017 11:39 am
thanks for the hint.
alas forgot. beforehand the desktop-system ran with win10 without errors. for some weeks. not a single freeze. the usual hickups with explorer, but not worth to mention.
so, under win10 the system ran fine.
then i saw that some people have had problems with nvidia drivers….so i stuck to win10. and for some daays now i run mint 18.3. already have had 2 freezes.
and in other distris too. so my primary suspect is the nvidia driver. i cant run the nouveau, because arguably the system didnt handle my resolution (1920×1200).
fazit:
win10 runs smooth, but is no option (over some weeks)
linux distris > all of them freezes randomly with the nvidia driver 384.98 (tried other versions too) no tearing or whatsoever. but the system freezes. sometimes after 3 days. sometimes ..i dont know. no heaatproblem, no hardwareissue…so, i have the nvidia-stuff left.
any ideas or similar experiences ?
thanks meanwhile for your time
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Sun Dec 31, 2017 12:37 pm
i have had the same thought.
so i have to buy an dvi (or an hdmi) cable, because my board has no displayport.
thanks meanwhile
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Wed Jan 03, 2018 6:53 pm
alas…i tried the intel gpu and the freeze continues. got back my nvidia card and here is the output from the last freeze.
right 5 minutes after the first start. …hmmm. any ideas ?
Code: Select all
root@antichrist:~/.cache$
zerst denkn,dann tippn-# journalctl -b -1 |grep -i error
Jan 03 23:05:18 antichrist kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: usb 2-5: device descriptor read/8, error -71
Jan 03 23:05:18 antichrist kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
Jan 03 23:05:21 antichrist gpu-manager[1133]: Error: can't open /lib/modules/4.10.0-42-generic/updates/dkms
Jan 03 23:05:21 antichrist gpu-manager[1133]: Error: can't open /lib/modules/4.10.0-42-generic/updates/dkms
Jan 03 23:05:21 antichrist gpu-manager[1133]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Jan 03 23:05:22 antichrist NetworkManager[1188]: <warn> [1515017122.4997] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.MovePidAbs failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.GetValue failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.SetValue failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:23 antichrist org.kde.KScreen[2878]: kscreen.xcb.helper: Event Error: 147
Jan 03 23:05:26 antichrist pulseaudio[3020]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
root@antichrist:~/.cache$
zerst denkn,dann tippn-# journalctl -b -1 |grep -i warning
Jan 03 23:05:20 antichrist ntfs-3g[884]: Warning : using problematic uid==0 and gid!=0
Jan 03 23:05:21 antichrist colord[2682]: (colord:2682): Cd-WARNING **: failed to get session [pid 1090]: No such device or address
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.MovePidAbs failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.GetValue failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:22 antichrist org.freedesktop.systemd1[2878]: ** (process:2914): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.SetValue failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.
Jan 03 23:05:23 antichrist org.freedesktop.Telepathy.AccountManager[2878]: (process:2945): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/ActiveConnection/0
Jan 03 23:05:23 antichrist org.freedesktop.Telepathy.AccountManager[2878]: (process:2945): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/ActiveConnection/0
Jan 03 23:05:23 antichrist org.freedesktop.Telepathy.AccountManager[2878]: (process:2945): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/ActiveConnection/0
Jan 03 23:05:23 antichrist org.freedesktop.Telepathy.AccountManager[2878]: (process:2945): libnm-glib-WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: No such interface 'org.freedesktop.DBus.Properties' on object at path /org/freedesktop/NetworkManager/ActiveConnection/0
Jan 03 23:05:27 antichrist dnsmasq[3276]: warning: no upstream servers configured
root@antichrist:~/.cache$
zerst denkn,dann tippn-#
greets günter
-
Laurent85
- Level 17
- Posts: 7015
- Joined: Tue May 26, 2015 10:11 am
Re: still random freeze
Post
by Laurent85 » Wed Jan 03, 2018 7:13 pm
Random freezes suggest an hardware failure. Memory, motherboard, PSU ?
Are you still able to run Windows with no freeze ?
-
ClixTrix
- Level 6
- Posts: 1069
- Joined: Wed Dec 09, 2015 11:40 am
- Location: Columbus, Ohio, USA
Re: still random freeze
Post
by ClixTrix » Wed Jan 03, 2018 7:19 pm
kscreen.xcb.helper: Event Error: 147
This thread has same KDE error from over a year ago.
viewtopic.php?t=234222
Linux Mint 19.2 x64 Cinnamon 4.15.0-118-generic
Gigabyte GA-AB350M-D3H (F20) / Ryzen 5 1600 / Micron Ballistix Sport DDR4 2400 2x8GB / Sapphire Radeon HD6450
NVMe-SSD: Samsung 960 EVO 250GB / SATA-SSD: Samsung 850 EVO 250GB + Toshiba OCZ VX500 512GB
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Wed Jan 03, 2018 9:39 pm
@lauren85
i checked beforehand memory and both harddisks. with memtest, and smart tools. and also under windows with crystaldisk
Are you still able to run Windows with no freeze ?
i dont know…struggle since 2 weeks with this annoying freezes. beforehand i installed win10 on the box and it ran without an single hiccup for at least 4 weeks.
nvidia and all pretty smooth.i have had the impression that the nvidia driver under linux was the culprit. not so sure now….
@ ClixTrix
i misse dthe post. thanks. but am i alone with this bug ? i have had the same experience with debian stable kde. i am stuck.
meanwhile i run the system in live modus with manjaro kde and see what happens. in manjaro you can beforehand activate the nvidia drivers. run smooth so far. if there is no error in the next days, i can definitely exclude an hardwareerror. we will see.
and win10 is no option…
its the first time that i struggle with such freezes…are there other people with similar experiences ?
thanks meanwhile…go to bed
greets gunter
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze
Post
by ghartl3 » Thu Jan 04, 2018 6:09 am
okay…switched to debian live with kde and let it run. manjaro struggled a little bit with my internet connection.
so i will see what happens with debian live and free graphics driver nouveau.
i forgot to mention that on my 9 year old laptop with intel graphics mint kde 18.3 runs fine. so the only major difference was the gpu. i honestly dont know if this is the major problem.
so, on the laptop with intel gpu all is fine
on desktop with nvidia card not.
now i let it run in debian live.
and yes i saw also the error 147….no clue if its relevant.
and now i wait for the next freeze..or not.
thanks meanwhile
-
BG405
- Level 8
- Posts: 2400
- Joined: Fri Mar 11, 2016 3:09 pm
- Location: England
Re: still random freeze
Post
by BG405 » Mon Jan 08, 2018 11:18 am
A visual check you can do is looking for capacitors with bulging tops, usually around the CPU and memory slots. These can cause all sorts of weird issues. If you have electronic test kit you could monitor the power supply voltages — a scope would be best as it’ll show noise or ripple on the supply rails — voltage checks can also be done in some BIOS & UEFI setup menus.
Dell Inspiron 1525 — LM17.3 CE 64——————-Lenovo T440 8GB — Manjaro KDE with Mint VMs
Toshiba NB250 — Manjaro KDE————————K7S5A AMD 1.2GHz — LM17.3 Xfce 32 & WinXP-Pro
Acer Aspire E11 ES1-111M — LM18.2 KDE 64 —-Two ROMS don’t make a WRITE …
-
tokland
Re: still random freeze
Post
by tokland » Mon Feb 05, 2018 10:59 am
Those are my devices in a MSI B350 / Ryzen 7 running on a Linux kernel 4.14.15-1-ARCH:
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
1f:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)
21:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
24:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe Wireless Network Adapter (rev 01)
25:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
25:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
Like you, I had random hangs (about once/twice a day). Just to test, I disabled the WiFi card (blacklisting the rtl8192ce module) and used a network cable instead. The result: No hangs since then, that was 3 weeks ago. Probably that’s related with the power management code in the driver, as disabling it (options rtl8192ce ips=0 fwlps=0) solves also the issue.
I see you too have a Realtek RTL8192CE, hope this helps.
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze [solved]
Post
by ghartl3 » Mon Jun 25, 2018 3:01 pm
i know…there went some time by…..and my linux box is now running for a few months.
the culprit was indeed the wlan-card with the realtek-chipset. thanks to @tokland for his hint.
maybe this info helps someone out there…
to make a long story short. the realtek-chipset is rather on the low end of quality. i bought a new wlan-card with an atheros-chipset and now the box is running fine without
any freezes.
very odd, that windows10 can handle the realtek card. any ideas, why windows can cope with the card and linux not ?
greets gunter
-
tokland
Re: still random freeze [solved]
Post
by tokland » Mon Jun 25, 2018 4:11 pm
Check the end of my post, I solved it by passing some options to the module load (in modprobe.d). To test:
# modprobe -r rtl8192ce
# modprobe rtl8192ce ips=0 swlps=0 fwlps=0 aspm=0 debug_level=5
-
tokland
Re: still random freeze [solved]
Post
by tokland » Mon Jun 25, 2018 4:36 pm
ghartl3 wrote: ↑
Mon Jun 25, 2018 4:27 pm
yes that works…but then do you still have the power savings capabilities on the card ?
Well, no, no power saving in the card now Personally I don’t mind, the computer is using the network almost non-stop.
You say the card works fine with Windows, so there is probably a bug in the Linux driver.
-
ghartl3
- Level 1
- Posts: 28
- Joined: Sun Sep 10, 2017 2:58 pm
Re: still random freeze [solved]
Post
by ghartl3 » Mon Jun 25, 2018 4:38 pm
You say the card works fine with Windows, so there is probably a bug in the Linux driver.
it seems so.
the atheros card is working fine also with power management
I’m having an issue that I can’t find an answer on. After I log into my computer it will hang for a couple of minutes before continuing. Yes, I’ve googled extensively, all of the links concerned bugs that either didn’t apply, or have been fixed, and I have tried multiple solutions including deleting .Xauthority and logging back in without rebooting.
Observations which may or may not be relevant:
-The problems seemed to start after I tried installing some wayland packages because I have multiple video cards and I wanted to see if I could put them to good use. I’ve since uninstalled all the wayland related packages I could without completely nuking the system.
— I have noticed that the audio clicks right after the hang ends, indicated that the audio driver has successfully loaded.
-The Mimetype error messages are related to my icon theme. I have tried changing the theme which made no difference.
— I had no luck finding useful information on kscreen event error 147.
— Other than this annoying 2 min hang after login, the system seems to be working perfectly.
This is my basic hardware information from Sandra when I had Windows installed:
Code: Select all
Chassis : Desktop
Mainboard : ASUS CROSSHAIR V FORMULA-Z
BIOS : AMI (OEM) 2201 03/23/2015
Total Memory : 31.78GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM
Processors
Processor : AMD FX(tm)-8350 Eight-Core Processor (4M 8T 4.64GHz, 2.2GHz IMC, 4x 2MB L2, 8MB L3)
Chipset
Memory Controller : AMD F15 (Orochi) CPU HT Hub 2x 1.1GHz (2.2GHz), 2x 16GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM 2GHz 128-bit
Memory Module(s)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Video System
Monitor/Panel : ACR XG270HU
(2560x1440, 27.0")
Monitor/Panel : ACR XG270HU
(1920x1080, 27.0")
Video Adapter : 2x Radeon RX 580 Series (36CU 2304SP SM5.1 1.34GHz, 16kB L2, 8GB DDR3 8GHz 256-bit, PCIe 3.00 x16)
Storage Devices
4 X 240GB SSD
Seagate ST8000VN0022-2EL112 (8TB, SATA2x1, 3.5", 7200rpm) : 7TB
ASUS BW-12B1ST a (SATA2x1, BD-RE, DVD+-RW, CD-RW) : N/A
Peripherals
Audio Device : ASUS Virtuoso 100 (Xonar Essence STX)
Keyboard: Logitech G510 Gaming Keyboard
Mouse: Logitech G502 Gaming Mouse
Input Device: Logitech G13 Gameboard
Network Services
Network Adapter : Intel(R) 82583V Gigabit Network Connection (Ethernet, 1Gbps)
This is my basic system information:
Code: Select all
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.19.0-1-amd64
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 31.2 GiB of RAM
Output of glxinfo | grep «version»
Code: Select all
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 4.5
Max compat profile version: 4.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.7
OpenGL core profile shading language version string: 4.50
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.7
OpenGL shading language version string: 4.40
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
This is the contents of my syslog which shows the hang. The syslog is always the same at the time of the hang:
Code: Select all
Dec 25 18:35:41 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 25 18:35:41 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 25 18:35:41 NAME systemd[1249]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 25 18:35:41 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.kglobalaccel' requested by ':1.1
25' (uid=1000 pid=4957 comm="kded5 [kdeinit5] ")
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.kglobalaccel'
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/16@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/22@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/24@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/32@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/48@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/64@2x/"
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.KScreen' requested by ':1.125' (
uid=1000 pid=4957 comm="kded5 [kdeinit5] ")
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.KScreen'
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Base: 89
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Error: 147
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: XRandR::setConfig
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Requested screen size is QSize(4480, 1440)
This dmesg output from the same time frame:
Code: Select all
[Dec25 18:35] usb 4-1: USB disconnect, device number 2
[ +3.116628] usb 4-1: new full-speed USB device number 4 using ohci-pci
[ +0.200766] usb 4-1: New USB device found, idVendor=046d, idProduct=c22d, bcdDevice=11.72
[ +0.000004] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0.000003] usb 4-1: Product: G510s Gaming Keyboard
[ +0.000003] usb 4-1: Manufacturer: Logitech
[ +0.006616] input: Logitech G510s Gaming Keyboard as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.0/0003:046D:C22D.000D/input/input25
[ +0.057059] hid-generic 0003:046D:C22D.000D: input,hidraw1: USB HID v1.11 Keyboard [Logitech G510s Gaming Keyboard] on usb-0000:00:12.0-1/input0
[ +0.003332] input: Logitech G510s Gaming Keyboard Consumer Control as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.1/0003:046D:C22D.000E/input/input26
[ +0.056571] hid-generic 0003:046D:C22D.000E: input,hiddev1,hidraw2: USB HID v1.11 Device [Logitech G510s Gaming Keyboard] on usb-0000:00:12.0-1/input1
[Dec25 18:38] input: G15 Extra Keys as /devices/virtual/input/input28
journalctl output from the same time frame:
Code: Select all
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Timers.
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Paths.
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Sockets.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-browser.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 25 18:35:41 NAME systemd[4795]: pulseaudio.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed Sound System.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-extra.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dec 25 18:35:41 NAME systemd[4795]: dirmngr.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG network certificate management daemon.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-ssh.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dec 25 18:35:41 NAME systemd[4795]: dbus.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed D-Bus User Message Bus Socket.
Dec 25 18:35:41 NAME systemd[4795]: Reached target Shutdown.
Dec 25 18:35:41 NAME systemd[4795]: systemd-exit.service: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Started Exit the Session.
Dec 25 18:35:41 NAME systemd[4795]: Reached target Exit the Session.
Dec 25 18:35:41 NAME systemd[1]: user@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 25 18:35:41 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 25 18:35:41 NAME systemd[1249]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 25 18:35:41 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.kglobalaccel' requested by ':1.1
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.kglobalaccel'
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme: "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.KScreen' requested by ':1.125' (
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.KScreen'
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Base: 89
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Error: 147
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: XRandR::setConfig
Mainboard : ASUS CROSSHAIR V FORMULA-Z
Total Memory : 31.78GB
Processor : AMD FX(tm)-8350
Video Adapter : 2x Radeon RX 580
Audio Device : ASUS Virtuoso 100 (Xonar Essence STX)
Network Adapter : Intel(R) 82583V Gigabit Network Connection (Ethernet, 1Gbps)
Every time I start KDE plasma with startx , latte-dock crashes. I’m sure it crashes on start-up since the crash time matches:
[puffer@puffer ~]$ sudo coredumpctl list
[sudo] senha para puffer:
TIME PID UID GID SIG COREFILE EXE >
Sun 2021-05-09 01:42:40 -04 11844 1000 1000 SIGSEGV present /usr/bin/systemsettings5 >
Sun 2021-05-09 09:00:39 -04 2088 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Sun 2021-05-09 13:55:11 -04 829 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Sun 2021-05-09 14:14:24 -04 8675 1000 1000 SIGSEGV present /user_data/SteamLibrary/steamapps/common/Proton 4.11/>
Mon 2021-05-10 04:00:31 -04 9276 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 04:19:01 -04 18177 1000 1000 SIGABRT present /usr/lib/drkonqi >
Mon 2021-05-10 04:19:01 -04 18172 1000 1000 SIGABRT present /usr/lib/kf5/klauncher >
Mon 2021-05-10 04:19:04 -04 8878 1000 1000 SIGSEGV truncated /usr/bin/kwin_x11 >
Mon 2021-05-10 04:20:21 -04 18446 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 04:37:47 -04 851 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 12:09:26 -04 842 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 12:25:48 -04 862 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 13:32:53 -04 837 1000 1000 SIGSEGV present /usr/bin/latte-dock >
Mon 2021-05-10 13:38:05 -04 838 1000 1000 SIGSEGV present /usr/bin/latte-dock >
lines 1-15/15 (END)
I tried cleaning the cache localized at ~/.cache/lattedock/qmlcache/, but had no lucky. I’m currently starting latte-dock through start up applications, on KDE Plasma configuration.
mai 10 13:36:54 puffer kernel: Bluetooth: hci0: Firmware revision 0.0 build 118 week 15 2021
mai 10 13:36:54 puffer systemd[1]: Starting Bluetooth service...
mai 10 13:36:54 puffer systemd-logind[430]: Watching system buttons on /dev/input/event7 (Gaming KB Gaming KB Keyboard)
mai 10 13:36:54 puffer systemd-logind[430]: Watching system buttons on /dev/input/event6 (Gaming KB Gaming KB System Control)
mai 10 13:36:54 puffer bluetoothd[509]: Bluetooth daemon 5.58
mai 10 13:36:54 puffer systemd[1]: Started Bluetooth service.
mai 10 13:36:54 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:54 puffer systemd[1]: Reached target Bluetooth.
mai 10 13:36:54 puffer bluetoothd[509]: Starting SDP server
mai 10 13:36:54 puffer kernel: Bluetooth: hci0: MSFT filter_enable is already on
mai 10 13:36:54 puffer bluetoothd[509]: Bluetooth management interface 1.19 initialized
mai 10 13:36:54 puffer kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
mai 10 13:36:54 puffer kernel: Bluetooth: BNEP filters: protocol multicast
mai 10 13:36:54 puffer kernel: Bluetooth: BNEP socket layer initialized
mai 10 13:36:54 puffer kernel: NET: Registered protocol family 38
mai 10 13:36:54 puffer systemd-udevd[319]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.4270] device (wlo1): set-hw-addr: set MAC address to FA:2A:1E:BA:44:88 (scanning)
mai 10 13:36:54 puffer dbus-daemon[428]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.3' (uid=0 pid=429 comm="/usr/bin/NetworkManager --no-daemon ")
mai 10 13:36:54 puffer systemd[1]: Starting WPA supplicant...
mai 10 13:36:54 puffer dbus-daemon[428]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
mai 10 13:36:54 puffer systemd[1]: Started WPA supplicant.
mai 10 13:36:54 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:54 puffer wpa_supplicant[537]: Successfully initialized wpa_supplicant
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain package
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain core
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain uncore
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain dram
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain psys
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7534] device (wlo1): supplicant interface state: internal-starting -> disconnected
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7534] Wi-Fi P2P device controlled by interface wlo1 created
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7536] manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7537] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
mai 10 13:36:54 puffer NetworkManager[429]: <warn> [1620668214.7540] sup-iface[a4c99c2cd346f8a9,0,wlo1]: call-p2p-cancel: failed with P2P cancel failed
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7541] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7545] device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
mai 10 13:36:54 puffer kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
mai 10 13:36:54 puffer kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
mai 10 13:36:54 puffer kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
mai 10 13:36:54 puffer kernel: ucsi_ccg: probe of 0-0008 failed with error -110
mai 10 13:36:55 puffer rngd[425]: [jitter]: Enabling JITTER rng support
mai 10 13:36:55 puffer rngd[425]: [jitter]: Initialized
mai 10 13:36:55 puffer rngd[425]: [pkcs11]: PKCS11 Engine /usr/lib64/opensc-pkcs11.so Error: No such file or directory
mai 10 13:36:55 puffer rngd[425]: [pkcs11]: Initialization Failed
mai 10 13:36:57 puffer audit[438]: USER_AUTH pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/login" hostname=puff>
mai 10 13:36:57 puffer kernel: kauditd_printk_skb: 32 callbacks suppressed
mai 10 13:36:57 puffer kernel: audit: type=1100 audit(1620668217.510:43): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe=">
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.8' (uid=0 pid=438 comm="/bin/login -p -- ")
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer login[438]: pam_systemd_home(login:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer audit[438]: USER_ACCT pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/login" hostname=puffer addr=? terminal=/dev/tt>
mai 10 13:36:57 puffer kernel: audit: type=1101 audit(1620668217.514:44): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/login" hostname=p>
mai 10 13:36:57 puffer audit[438]: CRED_ACQ pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/login" hostname=puffer addr=>
mai 10 13:36:57 puffer audit[438]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=5 a1=7ffd46bf57a0 a2=4 a3=3e8 items=0 ppid=1 pid=438 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fsgid=0 tty=tty1 ses=1 comm="logi>
mai 10 13:36:57 puffer audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D70002D2D00202020202020
mai 10 13:36:57 puffer login[438]: pam_unix(login:session): session opened for user puffer(uid=1000) by LOGIN(uid=0)
mai 10 13:36:57 puffer kernel: audit: type=1103 audit(1620668217.517:45): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bi>
mai 10 13:36:57 puffer kernel: audit: type=1006 audit(1620668217.517:46): pid=438 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
mai 10 13:36:57 puffer kernel: audit: type=1300 audit(1620668217.517:46): arch=c000003e syscall=1 success=yes exit=4 a0=5 a1=7ffd46bf57a0 a2=4 a3=3e8 items=0 ppid=1 pid=438 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fs>
mai 10 13:36:57 puffer kernel: audit: type=1327 audit(1620668217.517:46): proctitle=2F62696E2F6C6F67696E002D70002D2D00202020202020
mai 10 13:36:57 puffer systemd[1]: Created slice User Slice of UID 1000.
mai 10 13:36:57 puffer systemd[1]: Starting User Runtime Directory /run/user/1000...
mai 10 13:36:57 puffer systemd-logind[430]: New session 1 of user puffer.
mai 10 13:36:57 puffer systemd[1]: Finished User Runtime Directory /run/user/1000.
mai 10 13:36:57 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:57 puffer kernel: audit: type=1130 audit(1620668217.527:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:57 puffer systemd[1]: Starting User Manager for UID 1000...
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.10' (uid=0 pid=541 comm="(systemd) ")
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer systemd[541]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer audit[541]: USER_ACCT pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mai 10 13:36:57 puffer audit[541]: CRED_ACQ pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 10 13:36:57 puffer audit[541]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffc98f99eb0 a2=4 a3=3e8 items=0 ppid=1 pid=541 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="(syst>
mai 10 13:36:57 puffer audit: PROCTITLE proctitle="(systemd)"
mai 10 13:36:57 puffer systemd[541]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[puffer] ruser=[<unknown>] rhost=[<unknown>]
mai 10 13:36:57 puffer systemd[541]: pam_unix(systemd-user:session): session opened for user puffer(uid=1000) by (uid=0)
mai 10 13:36:57 puffer systemd[541]: pam_env(systemd-user:session): deprecated reading of user environment enabled
mai 10 13:36:57 puffer audit[541]: USER_START pid=541 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="puffer" exe="/usr/lib/>
mai 10 13:36:57 puffer kernel: audit: type=1101 audit(1620668217.534:48): pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/lib/systemd/systemd" >
mai 10 13:36:57 puffer kernel: audit: type=1103 audit(1620668217.534:49): pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 10 13:36:57 puffer kernel: audit: type=1006 audit(1620668217.534:50): pid=541 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1
mai 10 13:36:57 puffer audit: BPF prog-id=23 op=LOAD
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain uncore
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain dram
mai 10 13:36:54 puffer kernel: intel_rapl_common: Found RAPL domain psys
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7534] device (wlo1): supplicant interface state: internal-starting -> disconnected
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7534] Wi-Fi P2P device controlled by interface wlo1 created
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7536] manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7537] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
mai 10 13:36:54 puffer NetworkManager[429]: <warn> [1620668214.7540] sup-iface[a4c99c2cd346f8a9,0,wlo1]: call-p2p-cancel: failed with P2P cancel failed
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7541] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
mai 10 13:36:54 puffer NetworkManager[429]: <info> [1620668214.7545] device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
mai 10 13:36:54 puffer kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
mai 10 13:36:54 puffer kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
mai 10 13:36:54 puffer kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
mai 10 13:36:54 puffer kernel: ucsi_ccg: probe of 0-0008 failed with error -110
mai 10 13:36:55 puffer rngd[425]: [jitter]: Enabling JITTER rng support
mai 10 13:36:55 puffer rngd[425]: [jitter]: Initialized
mai 10 13:36:55 puffer rngd[425]: [pkcs11]: PKCS11 Engine /usr/lib64/opensc-pkcs11.so Error: No such file or directory
mai 10 13:36:55 puffer rngd[425]: [pkcs11]: Initialization Failed
mai 10 13:36:57 puffer audit[438]: USER_AUTH pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/login" hostname=puff>
mai 10 13:36:57 puffer kernel: kauditd_printk_skb: 32 callbacks suppressed
mai 10 13:36:57 puffer kernel: audit: type=1100 audit(1620668217.510:43): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe=">
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.8' (uid=0 pid=438 comm="/bin/login -p -- ")
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer login[438]: pam_systemd_home(login:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer audit[438]: USER_ACCT pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/login" hostname=puffer addr=? terminal=/dev/tt>
mai 10 13:36:57 puffer kernel: audit: type=1101 audit(1620668217.514:44): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/login" hostname=p>
mai 10 13:36:57 puffer audit[438]: CRED_ACQ pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/login" hostname=puffer addr=>
mai 10 13:36:57 puffer audit[438]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=5 a1=7ffd46bf57a0 a2=4 a3=3e8 items=0 ppid=1 pid=438 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fsgid=0 tty=tty1 ses=1 comm="logi>
mai 10 13:36:57 puffer audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D70002D2D00202020202020
mai 10 13:36:57 puffer login[438]: pam_unix(login:session): session opened for user puffer(uid=1000) by LOGIN(uid=0)
mai 10 13:36:57 puffer kernel: audit: type=1103 audit(1620668217.517:45): pid=438 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bi>
mai 10 13:36:57 puffer kernel: audit: type=1006 audit(1620668217.517:46): pid=438 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
mai 10 13:36:57 puffer kernel: audit: type=1300 audit(1620668217.517:46): arch=c000003e syscall=1 success=yes exit=4 a0=5 a1=7ffd46bf57a0 a2=4 a3=3e8 items=0 ppid=1 pid=438 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fs>
mai 10 13:36:57 puffer kernel: audit: type=1327 audit(1620668217.517:46): proctitle=2F62696E2F6C6F67696E002D70002D2D00202020202020
mai 10 13:36:57 puffer systemd[1]: Created slice User Slice of UID 1000.
mai 10 13:36:57 puffer systemd[1]: Starting User Runtime Directory /run/user/1000...
mai 10 13:36:57 puffer systemd-logind[430]: New session 1 of user puffer.
mai 10 13:36:57 puffer systemd[1]: Finished User Runtime Directory /run/user/1000.
mai 10 13:36:57 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:57 puffer kernel: audit: type=1130 audit(1620668217.527:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:57 puffer systemd[1]: Starting User Manager for UID 1000...
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.10' (uid=0 pid=541 comm="(systemd) ")
mai 10 13:36:57 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer systemd[541]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:36:57 puffer audit[541]: USER_ACCT pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
mai 10 13:36:57 puffer audit[541]: CRED_ACQ pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 10 13:36:57 puffer audit[541]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffc98f99eb0 a2=4 a3=3e8 items=0 ppid=1 pid=541 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="(syst>
mai 10 13:36:57 puffer audit: PROCTITLE proctitle="(systemd)"
mai 10 13:36:57 puffer systemd[541]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[puffer] ruser=[<unknown>] rhost=[<unknown>]
mai 10 13:36:57 puffer systemd[541]: pam_unix(systemd-user:session): session opened for user puffer(uid=1000) by (uid=0)
mai 10 13:36:57 puffer systemd[541]: pam_env(systemd-user:session): deprecated reading of user environment enabled
mai 10 13:36:57 puffer audit[541]: USER_START pid=541 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="puffer" exe="/usr/lib/>
mai 10 13:36:57 puffer kernel: audit: type=1101 audit(1620668217.534:48): pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/lib/systemd/systemd" >
mai 10 13:36:57 puffer kernel: audit: type=1103 audit(1620668217.534:49): pid=541 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="puffer" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
mai 10 13:36:57 puffer kernel: audit: type=1006 audit(1620668217.534:50): pid=541 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1
mai 10 13:36:57 puffer audit: BPF prog-id=23 op=LOAD
mai 10 13:36:57 puffer audit[541]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7fff12cc2060 a2=78 a3=7fff12cc2060 items=0 ppid=1 pid=541 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsg>
mai 10 13:36:57 puffer audit: PROCTITLE proctitle="(systemd)"
mai 10 13:36:57 puffer audit: BPF prog-id=23 op=UNLOAD
mai 10 13:36:57 puffer systemd-xdg-autostart-generator[547]: /home/puffer/.config/autostart/org.kde.latte-dock.desktop:102: Unknown key name 'InitialPreference' in section 'Desktop Entry', ignoring.
mai 10 13:36:57 puffer systemd[541]: Queued start job for default target Main User Target.
mai 10 13:36:57 puffer systemd[541]: Created slice User Application Slice.
mai 10 13:36:57 puffer systemd[541]: Reached target Paths.
mai 10 13:36:57 puffer systemd[541]: Reached target Timers.
mai 10 13:36:57 puffer systemd[541]: Starting D-Bus User Message Bus Socket.
mai 10 13:36:57 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:57 puffer systemd[541]: Listening on GnuPG network certificate management daemon.
mai 10 13:36:57 puffer systemd[541]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 10 13:36:57 puffer systemd[541]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
mai 10 13:36:57 puffer systemd[541]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
mai 10 13:36:57 puffer systemd[541]: Listening on GnuPG cryptographic agent and passphrase cache.
mai 10 13:36:57 puffer audit[438]: USER_START pid=438 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="puffer" exe="/usr/bin/login" hostna>
mai 10 13:36:57 puffer audit[438]: CRED_REFR pid=438 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/login" hostname=puffer addr=? terminal=/de>
mai 10 13:36:57 puffer login[438]: pam_env(login:session): deprecated reading of user environment enabled
mai 10 13:36:57 puffer systemd[541]: Listening on p11-kit server.
mai 10 13:36:57 puffer systemd[541]: Listening on Multimedia System.
mai 10 13:36:57 puffer login[438]: LOGIN ON tty1 BY puffer
mai 10 13:36:57 puffer systemd[541]: Listening on Sound System.
mai 10 13:36:57 puffer systemd[541]: Listening on D-Bus User Message Bus Socket.
mai 10 13:36:57 puffer systemd[541]: Reached target Sockets.
mai 10 13:36:57 puffer systemd[541]: Reached target Basic System.
mai 10 13:36:57 puffer systemd[541]: Reached target Main User Target.
mai 10 13:36:57 puffer systemd[541]: Startup finished in 107ms.
mai 10 13:36:57 puffer systemd[1]: Started User Manager for UID 1000.
mai 10 13:36:57 puffer systemd[1]: Started Session 1 of user puffer.
mai 10 13:36:59 puffer systemd[1]: systemd-rfkill.service: Deactivated successfully.
mai 10 13:36:59 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:36:59 puffer kernel: ACPI Warning: _SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210105/nsarguments-61)
mai 10 13:37:00 puffer systemd[541]: Started D-Bus User Message Bus.
mai 10 13:37:00 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating service name='org.kde.KSplash' requested by ':1.2' (uid=1000 pid=592 comm="startplasma-x11 ")
mai 10 13:37:00 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.KSplash'
mai 10 13:37:01 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1041] policy: auto-activating connection 'Pintinho Amarelinho' (4df9d410-4c48-4188-b716-1d2b7d7dc6d5)
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1045] device (wlo1): Activation: starting connection 'Pintinho Amarelinho' (4df9d410-4c48-4188-b716-1d2b7d7dc6d5)
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1045] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1048] manager: NetworkManager state is now CONNECTING
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1060] device (wlo1): set-hw-addr: reset MAC address to 5C:CD:5B:99:1C:27 (preserve)
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1067] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1070] device (wlo1): Activation: (wifi) access point 'Pintinho Amarelinho' has security, but secrets are required.
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1070] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1071] sup-iface[a4c99c2cd346f8a9,0,wlo1]: wps: type pbc start...
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1095] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1098] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1101] device (wlo1): Activation: (wifi) connection 'Pintinho Amarelinho' has security, and secrets exist. No new secrets needed.
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1101] Config: added 'ssid' value 'Pintinho Amarelinho'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1102] Config: added 'scan_ssid' value '1'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1102] Config: added 'bgscan' value 'simple:30:-70:86400'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1102] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1102] Config: added 'auth_alg' value 'OPEN'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1102] Config: added 'psk' value '<hidden>'
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1641] device (wlo1): supplicant interface state: disconnected -> scanning
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.1641] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[541]: Created slice User Background Tasks Slice.
mai 10 13:37:01 puffer systemd[541]: Starting KDE Global Shortcuts Server...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.kglobalaccel'
mai 10 13:37:01 puffer systemd[541]: Started KDE Global Shortcuts Server.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[1]: Starting Disk Manager...
mai 10 13:37:01 puffer udisksd[661]: udisks daemon version 2.9.2 starting
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.14' (uid=0 pid=661 comm="/usr/lib/udisks2/udisksd ")
mai 10 13:37:01 puffer systemd[1]: Starting Authorization Manager...
mai 10 13:37:01 puffer polkitd[665]: Started polkitd version 0.118
mai 10 13:37:01 puffer polkitd[665]: Loading rules from directory /etc/polkit-1/rules.d
mai 10 13:37:01 puffer polkitd[665]: Loading rules from directory /usr/share/polkit-1/rules.d
mai 10 13:37:01 puffer polkitd[665]: Finished loading, compiling and executing 4 rules
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
mai 10 13:37:01 puffer systemd[1]: Started Authorization Manager.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer polkitd[665]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.10' (uid=1000 pid=639 comm="/usr/bin/kwin_x11 ")
mai 10 13:37:01 puffer systemd[541]: Starting KActivityManager Activity manager Service...
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.UDisks2'
mai 10 13:37:01 puffer systemd[1]: Started Disk Manager.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer audit: BPF prog-id=24 op=LOAD
mai 10 13:37:01 puffer audit: BPF prog-id=25 op=LOAD
mai 10 13:37:01 puffer systemd[1]: Starting Daemon for power management...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.ActivityManager'
mai 10 13:37:01 puffer systemd[541]: Started KActivityManager Activity manager Service.
mai 10 13:37:01 puffer udisksd[661]: Acquired the name org.freedesktop.UDisks2 on the system message bus
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.UPower'
mai 10 13:37:01 puffer systemd[1]: Started Daemon for power management.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer systemd[541]: Starting Sound Service...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.16' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer systemd[541]: Starting User preferences database...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'ca.desrt.dconf'
mai 10 13:37:01 puffer systemd[541]: Started User preferences database.
mai 10 13:37:01 puffer systemd[541]: Started /usr/lib/DiscoverNotifier.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.25' (uid=1000 pid=789 comm="/usr/bin/pulseaudio --daemonize=no --log-targ>
mai 10 13:37:01 puffer systemd[1]: Starting RealtimeKit Scheduling Policy Service...
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
mai 10 13:37:01 puffer systemd[1]: Started RealtimeKit Scheduling Policy Service.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully called chroot.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully dropped privileges.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully limited resources.
mai 10 13:37:01 puffer rtkit-daemon[801]: Running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Canary thread running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Watchdog thread running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully made thread 789 of process 789 owned by '1000' high priority at nice level -11.
mai 10 13:37:01 puffer rtkit-daemon[801]: Supervising 1 threads of 1 processes of 1 users.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
mai 10 13:37:01 puffer polkitd[665]: Registered Authentication Agent for unix-session:1 (system bus name :1.29 [/usr/lib/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
mai 10 13:37:01 puffer systemd[541]: Started Latte - Área acoplável.
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.8558] agent-manager: agent[4277e0cb05fe94b6,:1.13/org.kde.plasma.networkmanagement/1000]: agent registered
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating service name='org.kde.KScreen' requested by ':1.15' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ")
mai 10 13:37:01 puffer systemd[541]: app-x2fusrx2flibx2fDiscoverNotifier-7076beed0a9a4b029d6d6a2b1f915677.scope: Deactivated successfully.
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.KScreen'
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Connected output 66 to CRTC 63
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Detected XRandR 1.6
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Event Base: 89
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Event Error: 147
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.kded.smart' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.kded.smart'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[541]: Starting Bluetooth OBEX service...
mai 10 13:37:01 puffer obexd[872]: OBEX daemon 5.58
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.bluez.obex'
mai 10 13:37:01 puffer systemd[541]: Started Bluetooth OBEX service.
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM TTY layer initialized
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM socket layer initialized
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM ver 1.11
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandR::setConfig
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Requested screen size is QSize(1920, 1080)
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Needed CRTCs: 1
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Actions to perform:
Primary Output: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Change Screen Size: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Disable outputs: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Change outputs: true
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: (66)
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Enable outputs: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: RRSetCrtcConfig (change output)
Output: 66 ( "eDP-1" )
CRTC: 63
Pos: QPoint(0,0)
Mode: 68 KScreen::Mode(Id: "68" , Size: QSize(1920, 1080) @ 144.014 )
Rotation: KScreen::Output::None
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Result: 0
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandROutput 66 update
m_connected: 0
m_crtc XRandRCrtc(0x5560e012d620)
CRTC: 63
MODE: 68
Connection: 0
Primary: true
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandR::setConfig done!
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 1 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Successfully made thread 892 of process 789 owned by '1000' RT at priority 5.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 2 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 2 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Successfully made thread 893 of process 789 owned by '1000' RT at priority 5.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer systemd[541]: Started Sound Service.
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: SME: Trying to authenticate with f4:8c:eb:b7:f1:f3 (SSID='Pintinho Amarelinho' freq=5765 MHz)
mai 10 13:37:03 puffer kernel: wlo1: authenticate with f4:8c:eb:b7:f1:f3
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.3699] device (wlo1): supplicant interface state: scanning -> authenticating
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.3700] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
mai 10 13:37:03 puffer kernel: wlo1: send auth to f4:8c:eb:b7:f1:f3 (try 1/3)
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: Trying to associate with f4:8c:eb:b7:f1:f3 (SSID='Pintinho Amarelinho' freq=5765 MHz)
mai 10 13:37:03 puffer kernel: wlo1: authenticated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5012] device (wlo1): supplicant interface state: authenticating -> associating
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
mai 10 13:37:03 puffer kernel: wlo1: associate with f4:8c:eb:b7:f1:f3 (try 1/3)
mai 10 13:37:03 puffer kernel: wlo1: RX AssocResp from f4:8c:eb:b7:f1:f3 (capab=0x31 status=0 aid=1)
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: Associated with f4:8c:eb:b7:f1:f3
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
mai 10 13:37:03 puffer kernel: wlo1: associated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5357] device (wlo1): supplicant interface state: associating -> associated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5358] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: WPA: Key negotiation completed with f4:8c:eb:b7:f1:f3 [PTK=CCMP GTK=TKIP]
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-CONNECTED - Connection to f4:8c:eb:b7:f1:f3 completed [id=0 id_str=]
mai 10 13:37:03 puffer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-25 noise=9999 txrate=234000
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (wlo1): supplicant interface state: associated -> completed
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Pintinho Amarelinho"
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (p2p-dev-wlo1): supplicant management interface state: associated -> completed
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7116] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7119] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7208] dhcp4 (wlo1): state changed unknown -> bound, address=192.168.0.198
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7222] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7238] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7240] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7244] manager: NetworkManager state is now CONNECTED_LOCAL
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7255] manager: NetworkManager state is now CONNECTED_SITE
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7256] policy: set 'Pintinho Amarelinho' (wlo1) as default for IPv4 routing and DNS
mai 10 13:37:03 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.3' (uid=0 pid=429 comm="/usr/bin/NetworkManager --no-daemon >
mai 10 13:37:03 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7287] device (wlo1): Activation: successful, device activated.
mai 10 13:37:03 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating service name='org.freedesktop.Notifications' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:03 puffer systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mai 10 13:37:03 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:03 puffer kernel: kauditd_printk_skb: 17 callbacks suppressed
mai 10 13:37:03 puffer kernel: audit: type=1131 audit(1620668223.784:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.2068] manager: NetworkManager state is now CONNECTED_GLOBAL
mai 10 13:37:04 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=429 comm="/usr/bin/NetworkManager -->
mai 10 13:37:04 puffer systemd[1]: Starting Network Manager Script Dispatcher Service...
mai 10 13:37:04 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mai 10 13:37:04 puffer systemd[1]: Started Network Manager Script Dispatcher Service.
mai 10 13:37:04 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:04 puffer kernel: audit: type=1130 audit(1620668224.207:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7813] dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds)
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7818] policy: set 'Pintinho Amarelinho' (wlo1) as default for IPv6 routing and DNS
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7902] dhcp6 (wlo1): state changed unknown -> bound
mai 10 13:37:10 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.krunner' unit='plasma-krunner.service' requested by ':1.40' (uid=1000 pid=953 comm="dbus-send --type=method_call --dest=or>
mai 10 13:37:10 puffer systemd[541]: Starting KRunner...
mai 10 13:37:10 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.krunner'
mai 10 13:37:10 puffer systemd[541]: Started KRunner.
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[541]: Created slice User Background Tasks Slice.
mai 10 13:37:01 puffer systemd[541]: Starting KDE Global Shortcuts Server...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.kglobalaccel'
mai 10 13:37:01 puffer systemd[541]: Started KDE Global Shortcuts Server.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[1]: Starting Disk Manager...
mai 10 13:37:01 puffer udisksd[661]: udisks daemon version 2.9.2 starting
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.14' (uid=0 pid=661 comm="/usr/lib/udisks2/udisksd ")
mai 10 13:37:01 puffer systemd[1]: Starting Authorization Manager...
mai 10 13:37:01 puffer polkitd[665]: Started polkitd version 0.118
mai 10 13:37:01 puffer polkitd[665]: Loading rules from directory /etc/polkit-1/rules.d
mai 10 13:37:01 puffer polkitd[665]: Loading rules from directory /usr/share/polkit-1/rules.d
mai 10 13:37:01 puffer polkitd[665]: Finished loading, compiling and executing 4 rules
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
mai 10 13:37:01 puffer systemd[1]: Started Authorization Manager.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer polkitd[665]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.10' (uid=1000 pid=639 comm="/usr/bin/kwin_x11 ")
mai 10 13:37:01 puffer systemd[541]: Starting KActivityManager Activity manager Service...
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.UDisks2'
mai 10 13:37:01 puffer systemd[1]: Started Disk Manager.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer audit: BPF prog-id=24 op=LOAD
mai 10 13:37:01 puffer audit: BPF prog-id=25 op=LOAD
mai 10 13:37:01 puffer systemd[1]: Starting Daemon for power management...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.ActivityManager'
mai 10 13:37:01 puffer systemd[541]: Started KActivityManager Activity manager Service.
mai 10 13:37:01 puffer udisksd[661]: Acquired the name org.freedesktop.UDisks2 on the system message bus
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.UPower'
mai 10 13:37:01 puffer systemd[1]: Started Daemon for power management.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer systemd[541]: Starting Sound Service...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.16' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer systemd[541]: Starting User preferences database...
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'ca.desrt.dconf'
mai 10 13:37:01 puffer systemd[541]: Started User preferences database.
mai 10 13:37:01 puffer systemd[541]: Started /usr/lib/DiscoverNotifier.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.25' (uid=1000 pid=789 comm="/usr/bin/pulseaudio --daemonize=no --log-targ>
mai 10 13:37:01 puffer systemd[1]: Starting RealtimeKit Scheduling Policy Service...
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
mai 10 13:37:01 puffer systemd[1]: Started RealtimeKit Scheduling Policy Service.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully called chroot.
mai 10 13:37:01 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully dropped privileges.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully limited resources.
mai 10 13:37:01 puffer rtkit-daemon[801]: Running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Canary thread running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Watchdog thread running.
mai 10 13:37:01 puffer rtkit-daemon[801]: Successfully made thread 789 of process 789 owned by '1000' high priority at nice level -11.
mai 10 13:37:01 puffer rtkit-daemon[801]: Supervising 1 threads of 1 processes of 1 users.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
mai 10 13:37:01 puffer polkitd[665]: Registered Authentication Agent for unix-session:1 (system bus name :1.29 [/usr/lib/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.22' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
mai 10 13:37:01 puffer systemd[541]: Started Latte - Área acoplável.
mai 10 13:37:01 puffer NetworkManager[429]: <info> [1620668221.8558] agent-manager: agent[4277e0cb05fe94b6,:1.13/org.kde.plasma.networkmanagement/1000]: agent registered
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating service name='org.kde.KScreen' requested by ':1.15' (uid=1000 pid=753 comm="/usr/lib/org_kde_powerdevil ")
mai 10 13:37:01 puffer systemd[541]: app-x2fusrx2flibx2fDiscoverNotifier-7076beed0a9a4b029d6d6a2b1f915677.scope: Deactivated successfully.
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.KScreen'
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Connected output 66 to CRTC 63
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Detected XRandR 1.6
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Event Base: 89
mai 10 13:37:01 puffer kscreen_backend_launcher[845]: kscreen.xcb.helper: Event Error: 147
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating service name='org.kde.kded.smart' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ") (using servicehelper)
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Successfully activated service 'org.kde.kded.smart'
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.13' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:01 puffer systemd[541]: Starting Bluetooth OBEX service...
mai 10 13:37:01 puffer obexd[872]: OBEX daemon 5.58
mai 10 13:37:01 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.bluez.obex'
mai 10 13:37:01 puffer systemd[541]: Started Bluetooth OBEX service.
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM TTY layer initialized
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM socket layer initialized
mai 10 13:37:02 puffer kernel: Bluetooth: RFCOMM ver 1.11
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandR::setConfig
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Requested screen size is QSize(1920, 1080)
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Needed CRTCs: 1
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Actions to perform:
Primary Output: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Change Screen Size: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Disable outputs: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Change outputs: true
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: (66)
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Enable outputs: false
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: RRSetCrtcConfig (change output)
Output: 66 ( "eDP-1" )
CRTC: 63
Pos: QPoint(0,0)
Mode: 68 KScreen::Mode(Id: "68" , Size: QSize(1920, 1080) @ 144.014 )
Rotation: KScreen::Output::None
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: Result: 0
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandROutput 66 update
m_connected: 0
m_crtc XRandRCrtc(0x5560e012d620)
CRTC: 63
MODE: 68
Connection: 0
Primary: true
mai 10 13:37:02 puffer kscreen_backend_launcher[845]: kscreen.xrandr: XRandR::setConfig done!
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 1 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Successfully made thread 892 of process 789 owned by '1000' RT at priority 5.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 2 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 2 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer rtkit-daemon[801]: Successfully made thread 893 of process 789 owned by '1000' RT at priority 5.
mai 10 13:37:02 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:02 puffer systemd[541]: Started Sound Service.
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: SME: Trying to authenticate with f4:8c:eb:b7:f1:f3 (SSID='Pintinho Amarelinho' freq=5765 MHz)
mai 10 13:37:03 puffer kernel: wlo1: authenticate with f4:8c:eb:b7:f1:f3
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.3699] device (wlo1): supplicant interface state: scanning -> authenticating
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.3700] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
mai 10 13:37:03 puffer kernel: wlo1: send auth to f4:8c:eb:b7:f1:f3 (try 1/3)
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: Trying to associate with f4:8c:eb:b7:f1:f3 (SSID='Pintinho Amarelinho' freq=5765 MHz)
mai 10 13:37:03 puffer kernel: wlo1: authenticated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5012] device (wlo1): supplicant interface state: authenticating -> associating
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
mai 10 13:37:03 puffer kernel: wlo1: associate with f4:8c:eb:b7:f1:f3 (try 1/3)
mai 10 13:37:03 puffer kernel: wlo1: RX AssocResp from f4:8c:eb:b7:f1:f3 (capab=0x31 status=0 aid=1)
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: Associated with f4:8c:eb:b7:f1:f3
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
mai 10 13:37:03 puffer kernel: wlo1: associated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5357] device (wlo1): supplicant interface state: associating -> associated
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.5358] device (p2p-dev-wlo1): supplicant management interface state: associating -> associated
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: WPA: Key negotiation completed with f4:8c:eb:b7:f1:f3 [PTK=CCMP GTK=TKIP]
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-CONNECTED - Connection to f4:8c:eb:b7:f1:f3 completed [id=0 id_str=]
mai 10 13:37:03 puffer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
mai 10 13:37:03 puffer wpa_supplicant[537]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-25 noise=9999 txrate=234000
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (wlo1): supplicant interface state: associated -> completed
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Pintinho Amarelinho"
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7115] device (p2p-dev-wlo1): supplicant management interface state: associated -> completed
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7116] device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7119] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7208] dhcp4 (wlo1): state changed unknown -> bound, address=192.168.0.198
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7222] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7238] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7240] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7244] manager: NetworkManager state is now CONNECTED_LOCAL
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7255] manager: NetworkManager state is now CONNECTED_SITE
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7256] policy: set 'Pintinho Amarelinho' (wlo1) as default for IPv4 routing and DNS
mai 10 13:37:03 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.3' (uid=0 pid=429 comm="/usr/bin/NetworkManager --no-daemon >
mai 10 13:37:03 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
mai 10 13:37:03 puffer NetworkManager[429]: <info> [1620668223.7287] device (wlo1): Activation: successful, device activated.
mai 10 13:37:03 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating service name='org.freedesktop.Notifications' requested by ':1.8' (uid=1000 pid=635 comm="/usr/bin/kded5 ")
mai 10 13:37:03 puffer systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mai 10 13:37:03 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:03 puffer kernel: kauditd_printk_skb: 17 callbacks suppressed
mai 10 13:37:03 puffer kernel: audit: type=1131 audit(1620668223.784:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.2068] manager: NetworkManager state is now CONNECTED_GLOBAL
mai 10 13:37:04 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=429 comm="/usr/bin/NetworkManager -->
mai 10 13:37:04 puffer systemd[1]: Starting Network Manager Script Dispatcher Service...
mai 10 13:37:04 puffer dbus-daemon[428]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mai 10 13:37:04 puffer systemd[1]: Started Network Manager Script Dispatcher Service.
mai 10 13:37:04 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:04 puffer kernel: audit: type=1130 audit(1620668224.207:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7813] dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds)
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7818] policy: set 'Pintinho Amarelinho' (wlo1) as default for IPv6 routing and DNS
mai 10 13:37:04 puffer NetworkManager[429]: <info> [1620668224.7902] dhcp6 (wlo1): state changed unknown -> bound
mai 10 13:37:10 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.krunner' unit='plasma-krunner.service' requested by ':1.40' (uid=1000 pid=953 comm="dbus-send --type=method_call --dest=or>
mai 10 13:37:10 puffer systemd[541]: Starting KRunner...
mai 10 13:37:10 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.krunner'
mai 10 13:37:10 puffer systemd[541]: Started KRunner.
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: não é pos>
mai 10 13:37:11 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.runners.baloo' unit='plasma-baloorunner.service' requested by ':1.41' (uid=1000 pid=954 comm="/usr/bin/krunner ")
mai 10 13:37:11 puffer krunner[954]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
mai 10 13:37:11 puffer systemd[541]: Starting KRunner provider for baloo file indexer...
mai 10 13:37:11 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.runners.baloo'
mai 10 13:37:11 puffer systemd[541]: Started KRunner provider for baloo file indexer.
mai 10 13:37:12 puffer systemd[541]: Started Firefox - Navegador Web.
mai 10 13:37:13 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.43' (uid=1000 pid=1011 comm="/usr/lib/firefox/firefox ")
mai 10 13:37:13 puffer systemd[541]: Starting Accessibility services bus...
mai 10 13:37:13 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.a11y.Bus'
mai 10 13:37:13 puffer systemd[541]: Started Accessibility services bus.
mai 10 13:37:13 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:13 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Successfully made thread 1150 of process 1011 owned by '1000' RT at priority 10.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:14 puffer systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mai 10 13:37:14 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:14 puffer kernel: audit: type=1131 audit(1620668234.794:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:15 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:15 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:16 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:16 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:24 puffer systemd[1]: systemd-hostnamed.service: Deactivated successfully.
mai 10 13:37:24 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:24 puffer kernel: audit: type=1131 audit(1620668244.330:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:24 puffer audit: BPF prog-id=22 op=UNLOAD
mai 10 13:37:24 puffer audit: BPF prog-id=21 op=UNLOAD
mai 10 13:37:24 puffer audit: BPF prog-id=20 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:68): prog-id=22 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:69): prog-id=21 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:70): prog-id=20 op=UNLOAD
mai 10 13:37:24 puffer krunner[1277]: (/usr/lib/firefox/firefox:1277): Gtk-WARNING **: 13:37:24.553: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:37:24 puffer krunner[1277]: (/usr/lib/firefox/firefox:1277): Gtk-WARNING **: 13:37:24.554: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:37:25 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:25 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:03 puffer plasma_waitforname[946]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mai 10 13:38:03 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
mai 10 13:38:04 puffer audit[838]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 pid=838 comm="latte-dock" exe="/usr/bin/latte-dock" sig=11 res=1
mai 10 13:38:04 puffer kernel: audit: type=1701 audit(1620668284.804:71): auid=1000 uid=1000 gid=1000 ses=1 pid=838 comm="latte-dock" exe="/usr/bin/latte-dock" sig=11 res=1
mai 10 13:38:04 puffer systemd[1]: Created slice system-systemdx2dcoredump.slice.
mai 10 13:38:04 puffer audit: BPF prog-id=26 op=LOAD
mai 10 13:38:04 puffer audit: BPF prog-id=27 op=LOAD
mai 10 13:38:04 puffer audit: BPF prog-id=28 op=LOAD
mai 10 13:38:04 puffer systemd[1]: Started Process Core Dump (PID 1474/UID 0).
mai 10 13:38:04 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:72): prog-id=26 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:73): prog-id=27 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:74): prog-id=28 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1130 audit(1620668284.824:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:38:05 puffer systemd-coredump[1475]: Process 838 (latte-dock) of user 1000 dumped core.
Stack trace of thread 838:
#0 0x00007f7655381ef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f76570b7189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
#2 0x00007f7655381f80 __restore_rt (libc.so.6 + 0x3cf80)
#3 0x000055ce88f60c24 n/a (latte-dock + 0x7bc24)
#4 0x000055ce88f8d665 n/a (latte-dock + 0xa8665)
#5 0x000055ce88f767d7 n/a (latte-dock + 0x917d7)
#6 0x000055ce88fbd4b6 n/a (latte-dock + 0xd84b6)
#7 0x000055ce88fbe77e n/a (latte-dock + 0xd977e)
#8 0x000055ce88fd8057 n/a (latte-dock + 0xf3057)
#9 0x000055ce88fcd121 n/a (latte-dock + 0xe8121)
#10 0x000055ce88f77055 n/a (latte-dock + 0x92055)
#11 0x000055ce89067181 n/a (latte-dock + 0x182181)
#12 0x00007f7655dae066 n/a (libQt5DBus.so.5 + 0x21066)
#13 0x00007f7655db165b n/a (libQt5DBus.so.5 + 0x2465b)
#14 0x00007f7655db1a8b n/a (libQt5DBus.so.5 + 0x24a8b)
#15 0x00007f7655db4478 n/a (libQt5DBus.so.5 + 0x27478)
#16 0x00007f7655b19322 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e3322)
#17 0x00007f7656836762 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a762)
#18 0x00007f7655aec81a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b681a)
#19 0x00007f7655aef313 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b9313)
#20 0x00007f7655b45ce4 n/a (libQt5Core.so.5 + 0x30fce4)
#21 0x00007f7653fa502c g_main_context_dispatch (libglib-2.0.so.0 + 0x5402c)
#22 0x00007f7653ff8b59 n/a (libglib-2.0.so.0 + 0xa7b59)
#23 0x00007f7653fa2781 g_main_context_iteration (libglib-2.0.so.0 + 0x51781)
#24 0x00007f7655b45321 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30f321)
#25 0x00007f7655aeb17c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b517c)
#26 0x00007f7655af3634 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bd634)
#27 0x000055ce88f2473b n/a (latte-dock + 0x3f73b)
#28 0x00007f765536cb25 __libc_start_main (libc.so.6 + 0x27b25)
#29 0x000055ce88f2503e _start (latte-dock + 0x4003e)
Stack trace of thread 881:
#0 0x00007f7653ff2ab4 g_mutex_unlock (libglib-2.0.so.0 + 0xa1ab4)
#1 0x00007f7653fa278d g_main_context_iteration (libglib-2.0.so.0 + 0x5178d)
#2 0x00007f7655b4533c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30f33c)
#3 0x00007f7655aeb17c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b517c)
#4 0x00007f7655902ea2 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccea2)
#5 0x00007f7655da4098 n/a (libQt5DBus.so.5 + 0x17098)
#6 0x00007f765590408f n/a (libQt5Core.so.5 + 0xce08f)
#7 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#8 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 877:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f764a16b0dc n/a (iris_dri.so + 0x1c70dc)
#3 0x00007f764a164ff8 n/a (iris_dri.so + 0x1c0ff8)
#4 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 879:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: não é pos>
mai 10 13:37:11 puffer krunner[954]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: não é pos>
mai 10 13:37:11 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.kde.runners.baloo' unit='plasma-baloorunner.service' requested by ':1.41' (uid=1000 pid=954 comm="/usr/bin/krunner ")
mai 10 13:37:11 puffer krunner[954]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
mai 10 13:37:11 puffer systemd[541]: Starting KRunner provider for baloo file indexer...
mai 10 13:37:11 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.kde.runners.baloo'
mai 10 13:37:11 puffer systemd[541]: Started KRunner provider for baloo file indexer.
mai 10 13:37:12 puffer systemd[541]: Started Firefox - Navegador Web.
mai 10 13:37:13 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.43' (uid=1000 pid=1011 comm="/usr/lib/firefox/firefox ")
mai 10 13:37:13 puffer systemd[541]: Starting Accessibility services bus...
mai 10 13:37:13 puffer dbus-daemon[595]: [session uid=1000 pid=595] Successfully activated service 'org.a11y.Bus'
mai 10 13:37:13 puffer systemd[541]: Started Accessibility services bus.
mai 10 13:37:13 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:13 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:37:14 puffer rtkit-daemon[801]: Successfully made thread 1150 of process 1011 owned by '1000' RT at priority 10.
mai 10 13:37:14 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:14 puffer systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mai 10 13:37:14 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:14 puffer kernel: audit: type=1131 audit(1620668234.794:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:37:15 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:15 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:16 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:16 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:24 puffer systemd[1]: systemd-hostnamed.service: Deactivated successfully.
mai 10 13:37:24 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:24 puffer kernel: audit: type=1131 audit(1620668244.330:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:37:24 puffer audit: BPF prog-id=22 op=UNLOAD
mai 10 13:37:24 puffer audit: BPF prog-id=21 op=UNLOAD
mai 10 13:37:24 puffer audit: BPF prog-id=20 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:68): prog-id=22 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:69): prog-id=21 op=UNLOAD
mai 10 13:37:24 puffer kernel: audit: type=1334 audit(1620668244.450:70): prog-id=20 op=UNLOAD
mai 10 13:37:24 puffer krunner[1277]: (/usr/lib/firefox/firefox:1277): Gtk-WARNING **: 13:37:24.553: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:37:24 puffer krunner[1277]: (/usr/lib/firefox/firefox:1277): Gtk-WARNING **: 13:37:24.554: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:37:25 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:37:25 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:03 puffer plasma_waitforname[946]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mai 10 13:38:03 puffer dbus-daemon[595]: [session uid=1000 pid=595] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
mai 10 13:38:04 puffer audit[838]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 pid=838 comm="latte-dock" exe="/usr/bin/latte-dock" sig=11 res=1
mai 10 13:38:04 puffer kernel: audit: type=1701 audit(1620668284.804:71): auid=1000 uid=1000 gid=1000 ses=1 pid=838 comm="latte-dock" exe="/usr/bin/latte-dock" sig=11 res=1
mai 10 13:38:04 puffer systemd[1]: Created slice system-systemdx2dcoredump.slice.
mai 10 13:38:04 puffer audit: BPF prog-id=26 op=LOAD
mai 10 13:38:04 puffer audit: BPF prog-id=27 op=LOAD
mai 10 13:38:04 puffer audit: BPF prog-id=28 op=LOAD
mai 10 13:38:04 puffer systemd[1]: Started Process Core Dump (PID 1474/UID 0).
mai 10 13:38:04 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:72): prog-id=26 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:73): prog-id=27 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:74): prog-id=28 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1130 audit(1620668284.824:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:38:04 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:72): prog-id=26 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:73): prog-id=27 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1334 audit(1620668284.824:74): prog-id=28 op=LOAD
mai 10 13:38:04 puffer kernel: audit: type=1130 audit(1620668284.824:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:38:05 puffer systemd-coredump[1475]: Process 838 (latte-dock) of user 1000 dumped core.
Stack trace of thread 838:
#0 0x00007f7655381ef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f76570b7189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
#2 0x00007f7655381f80 __restore_rt (libc.so.6 + 0x3cf80)
#3 0x000055ce88f60c24 n/a (latte-dock + 0x7bc24)
#4 0x000055ce88f8d665 n/a (latte-dock + 0xa8665)
#5 0x000055ce88f767d7 n/a (latte-dock + 0x917d7)
#6 0x000055ce88fbd4b6 n/a (latte-dock + 0xd84b6)
#7 0x000055ce88fbe77e n/a (latte-dock + 0xd977e)
#8 0x000055ce88fd8057 n/a (latte-dock + 0xf3057)
#9 0x000055ce88fcd121 n/a (latte-dock + 0xe8121)
#10 0x000055ce88f77055 n/a (latte-dock + 0x92055)
#11 0x000055ce89067181 n/a (latte-dock + 0x182181)
#12 0x00007f7655dae066 n/a (libQt5DBus.so.5 + 0x21066)
#13 0x00007f7655db165b n/a (libQt5DBus.so.5 + 0x2465b)
#14 0x00007f7655db1a8b n/a (libQt5DBus.so.5 + 0x24a8b)
#15 0x00007f7655db4478 n/a (libQt5DBus.so.5 + 0x27478)
#16 0x00007f7655b19322 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e3322)
#17 0x00007f7656836762 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a762)
#18 0x00007f7655aec81a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b681a)
#19 0x00007f7655aef313 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b9313)
#20 0x00007f7655b45ce4 n/a (libQt5Core.so.5 + 0x30fce4)
#21 0x00007f7653fa502c g_main_context_dispatch (libglib-2.0.so.0 + 0x5402c)
#22 0x00007f7653ff8b59 n/a (libglib-2.0.so.0 + 0xa7b59)
#23 0x00007f7653fa2781 g_main_context_iteration (libglib-2.0.so.0 + 0x51781)
#24 0x00007f7655b45321 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30f321)
#25 0x00007f7655aeb17c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b517c)
#26 0x00007f7655af3634 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bd634)
#27 0x000055ce88f2473b n/a (latte-dock + 0x3f73b)
#28 0x00007f765536cb25 __libc_start_main (libc.so.6 + 0x27b25)
#29 0x000055ce88f2503e _start (latte-dock + 0x4003e)
Stack trace of thread 881:
#0 0x00007f7653ff2ab4 g_mutex_unlock (libglib-2.0.so.0 + 0xa1ab4)
#1 0x00007f7653fa278d g_main_context_iteration (libglib-2.0.so.0 + 0x5178d)
#2 0x00007f7655b4533c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30f33c)
#3 0x00007f7655aeb17c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b517c)
#4 0x00007f7655902ea2 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccea2)
#5 0x00007f7655da4098 n/a (libQt5DBus.so.5 + 0x17098)
#6 0x00007f765590408f n/a (libQt5Core.so.5 + 0xce08f)
#7 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#8 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 877:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f764a16b0dc n/a (iris_dri.so + 0x1c70dc)
#3 0x00007f764a164ff8 n/a (iris_dri.so + 0x1c0ff8)
#4 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 879:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f764a16b0dc n/a (iris_dri.so + 0x1c70dc)
#3 0x00007f764a164ff8 n/a (iris_dri.so + 0x1c0ff8)
#4 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 849:
#0 0x00007f765543937f __poll (libc.so.6 + 0xf437f)
#1 0x00007f7657d3c63b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007f7657d3e37b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
#3 0x00007f765149d161 n/a (libQt5XcbQpa.so.5 + 0x5e161)
#4 0x00007f765590408f n/a (libQt5Core.so.5 + 0xce08f)
#5 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#6 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 876:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f764a16b0dc n/a (iris_dri.so + 0x1c70dc)
#3 0x00007f764a164ff8 n/a (iris_dri.so + 0x1c0ff8)
#4 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 878:
#0 0x00007f7654c9c9ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7654c96260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f764a16b0dc n/a (iris_dri.so + 0x1c70dc)
#3 0x00007f764a164ff8 n/a (iris_dri.so + 0x1c0ff8)
#4 0x00007f7654c90299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7655444053 __clone (libc.so.6 + 0xff053)
mai 10 13:38:05 puffer systemd[1]: systemd-coredump@0-1474-0.service: Deactivated successfully.
mai 10 13:38:05 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:38:05 puffer systemd[541]: app-org.kde.lattex2ddock-f56ebd56784345ae8c607a5684a4162e.scope: Deactivated successfully.
mai 10 13:38:05 puffer systemd[541]: app-org.kde.lattex2ddock-f56ebd56784345ae8c607a5684a4162e.scope: Consumed 3.475s CPU time.
mai 10 13:38:05 puffer kernel: audit: type=1131 audit(1620668285.024:76): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
mai 10 13:38:05 puffer audit: BPF prog-id=28 op=UNLOAD
mai 10 13:38:05 puffer audit: BPF prog-id=27 op=UNLOAD
mai 10 13:38:05 puffer audit: BPF prog-id=26 op=UNLOAD
mai 10 13:38:05 puffer kernel: audit: type=1334 audit(1620668285.150:77): prog-id=28 op=UNLOAD
mai 10 13:38:05 puffer kernel: audit: type=1334 audit(1620668285.150:78): prog-id=27 op=UNLOAD
mai 10 13:38:05 puffer kernel: audit: type=1334 audit(1620668285.150:79): prog-id=26 op=UNLOAD
mai 10 13:38:30 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:30 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:37 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:37 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:38:50 puffer systemd[541]: Started Konsole - Terminal.
mai 10 13:39:06 puffer systemd[541]: app-org.kde.konsole-3b0321ca7c5c41f99bd1149b248573db.scope: Deactivated successfully.
mai 10 13:39:51 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:39:51 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:12 puffer krunner[1011]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:40:15 puffer systemd[541]: app-firefox-c1f797807fb84e349d3b0cf7aa468969.scope: Deactivated successfully.
mai 10 13:40:15 puffer systemd[541]: app-firefox-c1f797807fb84e349d3b0cf7aa468969.scope: Consumed 46.733s CPU time.
mai 10 13:40:15 puffer systemd[541]: Started Latte - Área acoplável.
mai 10 13:40:17 puffer systemd[541]: Started Konsole - Terminal.
mai 10 13:40:37 puffer systemd[541]: Started Firefox - Navegador Web.
mai 10 13:40:37 puffer firefox[2141]: Failed to load module "appmenu-gtk-module"
mai 10 13:40:38 puffer MainThread[2249]: Failed to load module "appmenu-gtk-module"
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 3 threads of 1 processes of 1 users.
mai 10 13:40:38 puffer rtkit-daemon[801]: Successfully made thread 2272 of process 2141 owned by '1000' RT at priority 10.
mai 10 13:40:38 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:39 puffer MainThread[2334]: Failed to load module "appmenu-gtk-module"
mai 10 13:40:39 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:39 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:40 puffer MainThread[2398]: Failed to load module "appmenu-gtk-module"
mai 10 13:40:40 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:40 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:57 puffer MainThread[2486]: Failed to load module "appmenu-gtk-module"
mai 10 13:40:57 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:40:57 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:41:00 puffer krunner[2398]: (/usr/lib/firefox/firefox:2398): Gtk-WARNING **: 13:41:00.090: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:41:00 puffer krunner[2398]: (/usr/lib/firefox/firefox:2398): Gtk-WARNING **: 13:41:00.090: Failed to mkdir /home/puffer/.cache/gtk-3.0/compose
mai 10 13:42:18 puffer systemd[541]: Started Configurações do sistema - Configurações do sistema.
mai 10 13:42:18 puffer systemsettings5[2736]: Using fontconfig file: "/home/puffer/.fonts.conf"
mai 10 13:42:18 puffer systemsettings5[2736]: kf.coreaddons: Two plugins with the same interface( QObject ) were registered. Use keywords to identify the plugins.
mai 10 13:42:18 puffer systemsettings5[2736]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: >
mai 10 13:42:18 puffer systemsettings5[2736]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: >
mai 10 13:42:18 puffer systemsettings5[2736]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: >
mai 10 13:42:18 puffer systemsettings5[2736]: kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: >
mai 10 13:42:18 puffer systemsettings5[2736]: kf.coreaddons: Two plugins with the same interface( QObject ) were registered. Use keywords to identify the plugins.
mai 10 13:42:18 puffer systemsettings5[2736]: file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:158:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated>
mai 10 13:42:18 puffer systemsettings5[2736]: file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/SubCategoryPage.qml:148:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated>
mai 10 13:42:18 puffer systemsettings5[2736]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
mai 10 13:42:18 puffer systemsettings5[2736]: file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:109:27: QML IntroIcon (parent or ancestor of QQuickLayoutAttached): Binding loop detected for p>
mai 10 13:42:23 puffer systemsettings5[2736]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
mai 10 13:42:23 puffer systemsettings5[2736]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
mai 10 13:42:35 puffer systemsettings5[2736]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
mai 10 13:42:35 puffer systemsettings5[2736]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
mai 10 13:42:36 puffer systemsettings5[2736]: kf.kio.core: Url QUrl("file:///home/puffer/.config/autostart/org.kde.latte-dock.desktop") already represents a local file, cancelling job.
mai 10 13:42:36 puffer systemsettings5[2736]: kf.kio.widgets: Plugin "baloofilepropertiesplugin" is using the deprecated loading style. Please port it to JSON loading.
mai 10 13:43:29 puffer systemsettings5[2736]: QQuickVelocityCalculator: a call to stopMeasuring() must be preceded by a call to startMeasuring()
mai 10 13:43:30 puffer systemsettings5[2736]: kf.kio.core: Url QUrl("file:///home/puffer/.config/autostart/org.kde.latte-dock.desktop") already represents a local file, cancelling job.
mai 10 13:43:30 puffer systemsettings5[2736]: kf.kio.widgets: Plugin "baloofilepropertiesplugin" is using the deprecated loading style. Please port it to JSON loading.
mai 10 13:44:08 puffer systemsettings5[2736]: kf.kio.core: Url QUrl("file:///home/puffer/.config/autostart/org.kde.latte-dock.desktop") already represents a local file, cancelling job.
mai 10 13:44:08 puffer systemsettings5[2736]: kf.kio.widgets: Plugin "baloofilepropertiesplugin" is using the deprecated loading style. Please port it to JSON loading.
mai 10 13:44:34 puffer systemsettings5[2736]: Model size of -1 is less than 0
mai 10 13:47:39 puffer MainThread[3645]: Failed to load module "appmenu-gtk-module"
mai 10 13:47:39 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:47:39 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:48:27 puffer krunner[2141]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
mai 10 13:49:10 puffer systemd[541]: Started Konsole - Terminal.
mai 10 13:49:16 puffer audit[4082]: USER_AUTH pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:49:16 puffer kernel: audit: type=1100 audit(1620668956.794:80): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:49:16 puffer kernel: audit: type=1101 audit(1620668956.797:81): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/p>
mai 10 13:49:16 puffer kernel: audit: type=1110 audit(1620668956.797:82): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:49:16 puffer kernel: audit: type=1105 audit(1620668956.797:83): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev>
mai 10 13:49:16 puffer audit[4082]: USER_ACCT pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:49:16 puffer audit[4082]: CRED_REFR pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:49:16 puffer audit[4082]: USER_START pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:49:16 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.69' (uid=0 pid=4082 comm="sudo coredumpctl list ")
mai 10 13:49:16 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:49:16 puffer sudo[4082]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:49:16 puffer sudo[4082]: puffer : TTY=pts/2 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/coredumpctl list
mai 10 13:49:16 puffer sudo[4082]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 13:49:29 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:49:29 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:49:29 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:49:29 puffer rtkit-daemon[801]: Supervising 4 threads of 2 processes of 1 users.
mai 10 13:49:29 puffer rtkit-daemon[801]: Successfully made thread 4139 of process 2486 owned by '1000' RT at priority 10.
mai 10 13:49:29 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:50:27 puffer systemd[541]: Started Konsole - Terminal.
mai 10 13:50:40 puffer MainThread[4431]: Failed to load module "appmenu-gtk-module"
mai 10 13:50:40 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:50:40 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:51:19 puffer systemd[541]: app-org.kde.konsole-f4055484e79d46dc93a4cc5d750a3cb7.scope: Deactivated successfully.
mai 10 13:51:37 puffer sudo[4082]: pam_unix(sudo:session): session closed for user root
mai 10 13:51:37 puffer audit[4082]: USER_END pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:51:37 puffer audit[4082]: CRED_DISP pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
mai 10 13:51:37 puffer kernel: audit: type=1106 audit(1620669097.030:84): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:51:37 puffer kernel: audit: type=1104 audit(1620669097.030:85): pid=4082 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:51:37 puffer systemd[541]: app-org.kde.konsole-9a4c478e72844fc998e6fa8bbc034429.scope: Deactivated successfully.
mai 10 13:51:55 puffer audit[4743]: USER_AUTH pid=4743 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:51:55 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.75' (uid=0 pid=4743 comm="sudo journalclt ")
mai 10 13:51:55 puffer kernel: audit: type=1100 audit(1620669115.250:86): pid=4743 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:51:55 puffer systemd[1]: Starting Cleanup of Temporary Directories...
mai 10 13:51:55 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:51:55 puffer sudo[4743]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:51:55 puffer audit[4743]: USER_ACCT pid=4743 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:51:55 puffer kernel: audit: type=1101 audit(1620669115.254:87): pid=4743 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/p>
mai 10 13:51:55 puffer systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
mai 10 13:51:55 puffer systemd[1]: Finished Cleanup of Temporary Directories.
mai 10 13:51:55 puffer audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:51:55 puffer audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:51:55 puffer kernel: audit: type=1130 audit(1620669115.284:88): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:51:55 puffer kernel: audit: type=1131 audit(1620669115.284:89): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mai 10 13:52:05 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.76' (uid=0 pid=4793 comm="sudo journalctl ")
mai 10 13:52:05 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:52:05 puffer sudo[4793]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:52:05 puffer audit[4793]: USER_ACCT pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:05 puffer sudo[4793]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl
mai 10 13:52:05 puffer audit[4793]: CRED_REFR pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:05 puffer audit[4793]: USER_START pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:05 puffer sudo[4793]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 13:52:05 puffer kernel: audit: type=1101 audit(1620669125.254:90): pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/p>
mai 10 13:52:05 puffer kernel: audit: type=1110 audit(1620669125.254:91): pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
mai 10 13:52:05 puffer kernel: audit: type=1105 audit(1620669125.254:92): pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev>
mai 10 13:52:05 puffer sudo[4793]: pam_unix(sudo:session): session closed for user root
mai 10 13:52:05 puffer audit[4793]: USER_END pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:05 puffer audit[4793]: CRED_DISP pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:05 puffer kernel: audit: type=1106 audit(1620669125.487:93): pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:52:05 puffer kernel: audit: type=1104 audit(1620669125.487:94): pid=4793 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
mai 10 13:52:08 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.77' (uid=0 pid=4806 comm="sudo journalctl ")
mai 10 13:52:08 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:52:08 puffer sudo[4806]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:52:08 puffer audit[4806]: USER_ACCT pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:08 puffer audit[4806]: CRED_REFR pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:08 puffer audit[4806]: USER_START pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:08 puffer sudo[4806]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl
mai 10 13:52:08 puffer sudo[4806]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 13:52:08 puffer kernel: audit: type=1101 audit(1620669128.557:95): pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/p>
mai 10 13:52:08 puffer kernel: audit: type=1110 audit(1620669128.557:96): pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
mai 10 13:52:08 puffer kernel: audit: type=1105 audit(1620669128.557:97): pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev>
mai 10 13:52:08 puffer sudo[4806]: pam_unix(sudo:session): session closed for user root
mai 10 13:52:08 puffer audit[4806]: USER_END pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:08 puffer audit[4806]: CRED_DISP pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:52:08 puffer kernel: audit: type=1106 audit(1620669128.764:98): pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:52:08 puffer kernel: audit: type=1104 audit(1620669128.764:99): pid=4806 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? term>
mai 10 13:56:19 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.78' (uid=0 pid=5761 comm="sudo journalctl -b 1 ")
mai 10 13:56:19 puffer kernel: audit: type=1101 audit(1620669379.677:100): pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
mai 10 13:56:19 puffer kernel: audit: type=1110 audit(1620669379.677:101): pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:56:19 puffer kernel: audit: type=1105 audit(1620669379.677:102): pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:56:19 puffer audit[5761]: USER_ACCT pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:56:19 puffer audit[5761]: CRED_REFR pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:56:19 puffer audit[5761]: USER_START pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:56:19 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:56:19 puffer sudo[5761]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:56:19 puffer sudo[5761]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl -b 1
mai 10 13:56:19 puffer sudo[5761]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 13:56:50 puffer MainThread[5900]: Failed to load module "appmenu-gtk-module"
mai 10 13:56:50 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:56:50 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:57:34 puffer MainThread[6099]: Failed to load module "appmenu-gtk-module"
mai 10 13:57:34 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:57:34 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:58:55 puffer systemd[541]: Started Vim - Text Editor.
mai 10 13:58:57 puffer systemd[541]: Started Vim - Text Editor.
mai 10 13:59:03 puffer systemd[541]: app-vim-13dbcaf3501e4be3a6108e0c45a7d8d0.scope: Deactivated successfully.
mai 10 13:59:06 puffer systemd[541]: app-vim-9549af70ff1042e6b97aeccd5f20e5f6.scope: Deactivated successfully.
mai 10 13:59:07 puffer systemd[541]: Started Vim - Text Editor.
mai 10 13:59:08 puffer systemd[541]: Started Vim - Text Editor.
mai 10 13:59:13 puffer systemd[541]: app-vim-d550aa4449d7414f879ab37651bf93ad.scope: Deactivated successfully.
mai 10 13:59:14 puffer systemd[541]: app-vim-e930c45325564d85af7a9c77df7d8f17.scope: Deactivated successfully.
mai 10 13:59:18 puffer sudo[5761]: pam_unix(sudo:session): session closed for user root
mai 10 13:59:18 puffer audit[5761]: USER_END pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:18 puffer audit[5761]: CRED_DISP pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:18 puffer kernel: audit: type=1106 audit(1620669558.390:103): pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/d>
mai 10 13:59:18 puffer kernel: audit: type=1104 audit(1620669558.390:104): pid=5761 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:59:21 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.81' (uid=0 pid=6577 comm="sudo journalctl -b1 ")
mai 10 13:59:21 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:59:21 puffer sudo[6577]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 13:59:21 puffer audit[6577]: USER_ACCT pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:21 puffer audit[6577]: CRED_REFR pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:21 puffer audit[6577]: USER_START pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:21 puffer sudo[6577]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl -b1
mai 10 13:59:21 puffer sudo[6577]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 13:59:21 puffer kernel: audit: type=1101 audit(1620669561.307:105): pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
mai 10 13:59:21 puffer kernel: audit: type=1110 audit(1620669561.307:106): pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:59:21 puffer kernel: audit: type=1105 audit(1620669561.307:107): pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 13:59:28 puffer audit[6577]: USER_END pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:28 puffer audit[6577]: CRED_DISP pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 13:59:28 puffer sudo[6577]: pam_unix(sudo:session): session closed for user root
mai 10 13:59:28 puffer kernel: audit: type=1106 audit(1620669568.047:108): pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/d>
mai 10 13:59:28 puffer kernel: audit: type=1104 audit(1620669568.047:109): pid=6577 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 13:59:41 puffer MainThread[6672]: Failed to load module "appmenu-gtk-module"
mai 10 13:59:41 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 13:59:41 puffer rtkit-daemon[801]: Supervising 5 threads of 3 processes of 1 users.
mai 10 14:00:01 puffer CROND[6767]: (root) CMD (timeshift --check --scripted)
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT ((process:6767): GLib-GIO-CRITICAL **: 14:00:01.604: g_file_get_path: assertion 'G_IS_FILE (file)' failed)
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT ()
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT (** (process:6767): CRITICAL **: 14:00:01.605: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed)
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT ()
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT (** (process:6767): CRITICAL **: 14:00:01.605: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed)
mai 10 14:00:01 puffer CROND[6766]: (root) CMDOUT (Mounted '/dev/sda1' at '/run/timeshift/backup')
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Daily snapshots are enabled)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Last daily snapshot is 4 hours old)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Weekly snapshots are enabled)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Last weekly snapshot is 1 days old)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Monthly snapshot are enabled)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (Last monthly snapshot is 1 days old)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDOUT (------------------------------------------------------------------------------)
mai 10 14:00:02 puffer crontab[6805]: (root) LIST (root)
mai 10 14:00:02 puffer crontab[6806]: (root) LIST (root)
mai 10 14:00:02 puffer CROND[6766]: (root) CMDEND (timeshift --check --scripted)
mai 10 14:01:01 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.83' (uid=0 pid=7043 comm="sudo journalctl -b1 ")
mai 10 14:01:01 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:01:01 puffer sudo[7043]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:01:01 puffer audit[7043]: USER_ACCT pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:01 puffer sudo[7043]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl -b1
mai 10 14:01:01 puffer audit[7043]: CRED_REFR pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:01 puffer audit[7043]: USER_START pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:01 puffer sudo[7043]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 14:01:01 puffer kernel: audit: type=1101 audit(1620669661.190:110): pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
mai 10 14:01:01 puffer kernel: audit: type=1110 audit(1620669661.190:111): pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 14:01:01 puffer kernel: audit: type=1105 audit(1620669661.190:112): pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 14:01:01 puffer CROND[7047]: (root) CMD (run-parts /etc/cron.hourly)
mai 10 14:01:01 puffer CROND[7046]: (root) CMDEND (run-parts /etc/cron.hourly)
mai 10 14:01:03 puffer sudo[7043]: pam_unix(sudo:session): session closed for user root
mai 10 14:01:03 puffer audit[7043]: USER_END pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:03 puffer kernel: audit: type=1106 audit(1620669663.837:113): pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/d>
mai 10 14:01:03 puffer kernel: audit: type=1104 audit(1620669663.837:114): pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 14:01:03 puffer audit[7043]: CRED_DISP pid=7043 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.84' (uid=0 pid=7089 comm="sudo journalctl 1 -b ")
mai 10 14:01:11 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:01:11 puffer sudo[7089]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:01:11 puffer kernel: audit: type=1101 audit(1620669671.657:115): pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
mai 10 14:01:11 puffer kernel: audit: type=1110 audit(1620669671.657:116): pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 14:01:11 puffer kernel: audit: type=1105 audit(1620669671.657:117): pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 14:01:11 puffer audit[7089]: USER_ACCT pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer audit[7089]: CRED_REFR pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer audit[7089]: USER_START pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer sudo[7089]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl 1 -b
mai 10 14:01:11 puffer sudo[7089]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
mai 10 14:01:11 puffer sudo[7089]: pam_unix(sudo:session): session closed for user root
mai 10 14:01:11 puffer audit[7089]: USER_END pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer audit[7089]: CRED_DISP pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:01:11 puffer kernel: audit: type=1106 audit(1620669671.664:118): pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/d>
mai 10 14:01:11 puffer kernel: audit: type=1104 audit(1620669671.664:119): pid=7089 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 14:02:13 puffer dbus-daemon[428]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.85' (uid=0 pid=7358 comm="sudo journalctl -b ")
mai 10 14:02:13 puffer kernel: audit: type=1101 audit(1620669733.767:120): pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
mai 10 14:02:13 puffer kernel: audit: type=1110 audit(1620669733.767:121): pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? ter>
mai 10 14:02:13 puffer kernel: audit: type=1105 audit(1620669733.767:122): pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/de>
mai 10 14:02:13 puffer audit[7358]: USER_ACCT pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="puffer" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:02:13 puffer audit[7358]: CRED_REFR pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:02:13 puffer audit[7358]: USER_START pid=7358 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
mai 10 14:02:13 puffer dbus-daemon[428]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:02:13 puffer sudo[7358]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
mai 10 14:02:13 puffer sudo[7358]: puffer : TTY=pts/3 ; PWD=/home/puffer ; USER=root ; COMMAND=/usr/bin/journalctl -b
mai 10 14:02:13 puffer sudo[7358]: pam_unix(sudo:session): session opened for user root(uid=0) by puffer(uid=1000)
I’ve been looking around but still no clues. Read something about not using kwin, does anyone know something about it? Alternatives? Thanks in advance.
PS: I should also mention that once Plasma has initiated, I can safely execute latte.
I am running kali linux kde on a brand new computer. Have installed several times before on other computers without a problem. It seems like its an issue starting the display driver.
More specifically sometimes during the boot up it hangs with the following error messages.
pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
pci 0000:00:07.1: DPC: RP PIO log size 0 is invalid
pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
pci 0000:00:07.3: DPC: RP PIO log size 0 is invalid
After looking at the journalctl -xb command I found this information:
Jan 23 15:21:54 kali-framework systemd-xdg-autostart-generator[797]: Not generating service for XDG autostart app-xcapex2dsuperx2dkeyx2dbind@autostart.service, error parsing Exec= line: No such file or directory
and
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Connected output 67 to CRTC 63
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xcb.helper: Detected XRandR 1.6
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xcb.helper: Event Base: 89
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xcb.helper: Event Error: 147
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: XRandR::setConfig
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Requested screen size is QSize(2256, 1504)
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Needed CRTCs: 1
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Actions to perform:
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Primary Output: false
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Change Screen Size: false
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Disable outputs: false
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Change outputs: true
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: (67)
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Enable outputs: false
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: RRSetCrtcConfig (change output)
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Output: 67 ( «eDP-1» )
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: CRTC: 63
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Pos: QPoint(0,0)
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Mode: 73 KScreen::Mode(Id: «73» , Size: QSize(2256, 1504) @ 59.9985 )
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Rotation: KScreen::Output::None
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: Result: 0
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: XRandROutput 67 update
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: m_connected: 0
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: m_crtc XRandRCrtc(0x5582a6dca420)
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: CRTC: 63
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: MODE: 73
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Connection: 0
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: Primary: true
Jan 23 15:22:01 kali-framework org.kde.KScreen[1126]: kscreen.xrandr: XRandR::setConfig done!
I there are some other errors in it but they seem to be unrelated to the issue.
When I am running kde, but after getting stuck on the errors, I pressed ctrl-alt-f2 and then installed xinit. I then entered startx and got to the desktop login screen.
Here are some specs about the compu
OS: Kali GNU/Linux Rolling x86_64
Host: Laptop AB
Kernel: 5.15.0-kali2-amd64
Uptime: 31 mins
Packages: 2606 (dpkg)
Shell: zsh 5.8
Resolution: 2256×1504
DE: Plasma 5.23.4
WM: KWin
Theme: Kali-Dark [Plasma], Breeze [GTK2/3]
Icons: Flat-Remix-Blue-Dark [Plasma], Flat-Remix-Blue-Dark [GTK2/3]
Terminal: konsole
CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz
GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics]
Memory: 2012MiB / 31896MiB
Description
Bit Twister
2016-02-01 04:20:32 CET
Description of problem: journalctl snippet org.kde.KScreen[3842]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4 kscreen.xrandr: Connected output 83 to CRTC 79 kscreen.xcb.helper: Detected XRandR 1.4 kscreen.xcb.helper: Event Base: 89 kscreen.xcb.helper: Event Error: 147 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. journalctl | grep -i kscreen 2. 3. Reproducible: Steps to Reproduce:
Rémi Verschelde
2016-02-01 16:23:55 CET
Blocks:
(none) =>
17523
Samuel Verschelde
2016-02-02 14:20:34 CET
Assignee:
bugsquad =>
mageia
Comment 1
Nicolas Lécureuil
2016-05-05 11:22:25 CEST
Please report this bug upstream
Keywords:
(none) =>
UPSTREAM
Bit Twister
2016-07-06 19:48:07 CEST
URL:
(none) =>
https://bugs.kde.org/show_bug.cgi?id=365165
Summary:
mga6: kscreen.xcb.helper: Event Error: 147 =>
6_s1: kscreen.xcb.helper: Event Error: 145
Comment 2
Bit Twister
2016-07-07 01:06:36 CEST
[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145 What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #2 from Sebastian Kügler <sebas@kde.org> --- Do you experience any functional problem, or is this just about the noise in your journal? (In the latter case, you can disable the logging output in your ~/.config/QtProject/qtlogging.ini It seems that the wrong backend is picked, do you have the KSCREEN_BACKEND env var set? In any case, you're running an old version of Plasma, which we don't maintain anymore. I'd advise to upgrade to Plasma 5.7.
Comment 3
Bit Twister
2016-07-07 03:45:29 CEST
In reply to Sebastian Kügler from comment #4) > Could you be more precise? > Does it take 30 seconds to log in, Yes, running plymouth login screen. Timing starts after hitting enter after passwd. I get a quick x11 X cursor then the little circle indicating working, ~20 seconds latter KDE splash screen. > kinfocenter shows the current Plasma version. OK, ran it down, I needed the command line app for dumping that for my bug_report script. $ kf5-config --version Qt: 5.6.1 KDE Frameworks: 5.23.0 kf5-config: 1.0 > It seems that the wrong backend is picked by kscreen for whatever reason. > You could try exporting KSCREEN_BACKEND=xrandr to force the correct backend > (xrandr 1.1 is deprecated, your X actually provides xrandr 1.5, but the > xrandr 1.1 backends doesn't understand it. Wow, setting KSCREEN_BACKEND=xrandr jumped me right to the KDE splash screen. Good news, all my autostart scripts ran. Bad news, No plasma desktop, just a black screen, no taskbar, no desktop shortcuts, no Alt+Space bar,..... Just checked, and desktop and whatnot showed up while writing this message. Going to move https://bugs.mageia.org/show_bug.cgi?id=17658 from kscreen to xrandr. Thank you for your time and patience.
Source RPM:
libkscreen-5.5.4-1.mga6.src.rpm =>
xrandr-1.5.0-1.mga6.src.rpm
Comment 4
Rémi Verschelde
2016-07-07 10:03:45 CEST
(In reply to Bit Twister from comment #2) > [KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145 > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |UNMAINTAINED [...] > > In any case, you're running an old version of Plasma, which we don't maintain > anymore. I'd advise to upgrade to Plasma 5.7. Well, that's convenient... So basically as a stable distro we're on our own, since upstream considers Plasma 5.6.5 unmaintained two weeks after it's released...
Comment 5
Bit Twister
2016-07-07 14:51:37 CEST
(In reply to Rémi Verschelde from comment #4) > Well, that's convenient... So basically as a stable distro we're on our own, > since upstream considers Plasma 5.6.5 unmaintained two weeks after it's > released... It do make the developer's job much easier. :( (In reply to Sebastian Kügler from comment #6) > That's not the Plasma version, but the Frameworks version. As I said, please > run kinfocenter to find out. Can not find any plasma version information in kinfocenter. See kinfocenter screen shot attachment. Quick launch of kde splash screen in comment 5, was a leftover/not dead yet process from previous login. :( Guessing this will help $ plasmashell --version plasmashell 5.6.5 A little happy that QA seems to like the idea of using the newer KDE release. Still guessing xrandr will be scrape goat for slow kde login. Slow Plymouth login is not going to help general public acceptance either. I added splash back to kernel boot but plymouth login screen is still slow, bug 17530 and bug 17521
Comment 6
Nicolas Lécureuil
2016-07-17 00:37:45 CEST
is this bug still valid under Plasma 5.7.1 ?
Comment 7
Bit Twister
2016-07-17 02:22:29 CEST
(In reply to Nicolas Lécureuil from comment #6)
> is this bug still valid under Plasma 5.7.1 ?
Yes.
Samuel Verschelde
2016-08-25 16:22:48 CEST
Assignee:
mageia =>
kde
Comment 8
Nicolas Lécureuil
2017-01-24 09:48:21 CET
is it still valid with current cauldron ?
CC:
(none) =>
mageia
Comment 9
Bit Twister
2017-01-24 10:43:01 CET
(In reply to Nicolas Lécureuil from comment #8)
> is it still valid with current cauldron ?
My, my, aren't we in a bit of a hurry. :)
I've been working since 1am testing my bug reports.
Since you are in such a hurry, I'll close this because
journalctl | grep -i kscreen | grep Error
does not return Error 145
Status:
NEW =>
RESOLVED
Resolution:
(none) =>
FIXED
I’m having an issue that I can’t find an answer on. After I log into my computer it will hang for a couple of minutes before continuing. Yes, I’ve googled extensively, all of the links concerned bugs that either didn’t apply, or have been fixed, and I have tried multiple solutions including deleting .Xauthority and logging back in without rebooting.
Observations which may or may not be relevant:
-The problems seemed to start after I tried installing some wayland packages because I have multiple video cards and I wanted to see if I could put them to good use. I’ve since uninstalled all the wayland related packages I could without completely nuking the system.
— I have noticed that the audio clicks right after the hang ends, indicated that the audio driver has successfully loaded.
-The Mimetype error messages are related to my icon theme. I have tried changing the theme which made no difference.
— I had no luck finding useful information on kscreen event error 147.
— Other than this annoying 2 min hang after login, the system seems to be working perfectly.- I’m leaning towards this being an issue with multiple gpu’s.
This is my basic hardware information from Sandra when I had Windows installed:
Chassis : Desktop
Mainboard : ASUS CROSSHAIR V FORMULA-Z
BIOS : AMI (OEM) 2201 03/23/2015
Total Memory : 31.78GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM
Processors
Processor : AMD FX(tm)-8350 Eight-Core Processor (4M 8T 4.64GHz, 2.2GHz IMC, 4x 2MB L2, 8MB L3)
Chipset
Memory Controller : AMD F15 (Orochi) CPU HT Hub 2x 1.1GHz (2.2GHz), 2x 16GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM 2GHz 128-bit
Memory Module(s)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Video System
Monitor/Panel : ACR XG270HU
(2560x1440, 27.0")
Monitor/Panel : ACR XG270HU
(1920x1080, 27.0")
Video Adapter : 2x Radeon RX 580 Series (36CU 2304SP SM5.1 1.34GHz, 16kB L2, 8GB DDR3 8GHz 256-bit, PCIe 3.00 x16)
Storage Devices
4 X 240GB SSD
Seagate ST8000VN0022-2EL112 (8TB, SATA2x1, 3.5", 7200rpm) : 7TB
ASUS BW-12B1ST a (SATA2x1, BD-RE, DVD+-RW, CD-RW) : N/A
Peripherals
Audio Device : ASUS Virtuoso 100 (Xonar Essence STX)
Keyboard: Logitech G510 Gaming Keyboard
Mouse: Logitech G502 Gaming Mouse
Input Device: Logitech G13 Gameboard
Network Services
Network Adapter : Intel(R) 82583V Gigabit Network Connection (Ethernet, 1Gbps)
This is my basic system information:
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.19.0-1-amd64
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 31.2 GiB of RAM
Output of glxinfo | grep «version»
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 4.5
Max compat profile version: 4.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.7
OpenGL core profile shading language version string: 4.50
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.7
OpenGL shading language version string: 4.40
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
This is the contents of my syslog which shows the hang. The syslog is always the same at the time of the hang:
Dec 26 09:39:42 NAME systemd[1]: user@115.service: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 26 09:39:42 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 26 09:39:42 NAME systemd[1326]: run-user-115.mount: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 26 09:39:42 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 26 09:39:47 NAME systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 26 09:39:49 NAME systemd[1]: systemd-fsckd.service: Succeeded.
Dec 26 09:39:50 NAME systemd-timesyncd[703]: Synchronized to time server 62.112.194.89:123 (2.debian.pool.ntp.org).
Dec 26 09:39:50 NAME systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='org.kde.kglobalaccel' requested by ':1.1
0' (uid=1000 pid=1513 comm="/usr/bin/kaccess ")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='ca.desrt.dconf' requested by ':1.11' (ui
d=1000 pid=1523 comm="/usr/bin/gsettings set org.gnome.desktop.a11y.appl")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'ca.desrt.dconf'
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'org.kde.kglobalaccel'
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/16@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/22@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/24@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/32@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/48@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme: "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/64@2x/"
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='org.kde.KScreen' requested by ':1.9' (ui
d=1000 pid=1507 comm="kded5 [kdeinit5] ")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'org.kde.KScreen'
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Event Base: 89
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Event Error: 147
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: XRandR::setConfig
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Requested screen size is QSize(4480, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Needed CRTCs: 2
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Actions to perform:
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Primary Output: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Change Screen Size: true
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011Old: QSize(5120, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011Intermediate: QSize(5120, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011New: QSize(4480, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Disable outputs: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Change outputs: true
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011 (128, 129)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Enable outputs: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: RRSetCrtcConfig (change output)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Output: 128 ( "DisplayPort-0" )
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011CRTC: 122
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Pos: QPoint(0,0)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Mode: 135 KScreen::Mode(Id: "135" , Size: QSize(2560, 1440) @ 143.856
)
journalctl output from the same time frame:
Dec 26 09:39:18 NAME kernel: RAMDISK: [mem 0x37253000-0x37920fff]
Dec 26 09:39:18 NAME kernel: ACPI: Early table checksum verification disabled
Dec 26 09:39:18 NAME kernel: ACPI: RSDP 0x000000009A76D000 000024 (v02 ALASKA)
Dec 26 09:39:18 NAME kernel: ACPI: XSDT 0x000000009A76D078 000064 (v01 ALASKA A M I 01072009 AMI 00010013)
Dec 26 09:39:18 NAME kernel: ACPI: FACP 0x000000009A774290 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
Dec 26 09:39:18 NAME kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x000000
Dec 26 09:39:18 NAME kernel: ACPI: DSDT 0x000000009A76D170 007119 (v02 ALASKA A M I 00000000 INTL 20051117)
Dec 26 09:39:18 NAME kernel: ACPI: FACS 0x000000009B591F80 000040
Dec 26 09:39:18 NAME kernel: ACPI: APIC 0x000000009A7743A0 00009E (v03 ALASKA A M I 01072009 AMI 00010013)
Dec 26 09:39:18 NAME kernel: ACPI: FPDT 0x000000009A774440 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
Dec 26 09:39:18 NAME kernel: ACPI: MCFG 0x000000009A774488 00003C (v01 ALASKA A M I 01072009 MSFT 00010013)
Dec 26 09:39:18 NAME kernel: ACPI: HPET 0x000000009A7744C8 000038 (v01 ALASKA A M I 01072009 AMI 00000005)
Dec 26 09:39:18 NAME kernel: ACPI: SSDT 0x000000009A791630 000D3C (v01 AMD POWERNOW 00000001 AMD 00000001)
Dec 26 09:39:18 NAME kernel: ACPI: VFCT 0x000000009A774558 01D0A0 (v01 ALASKA A M I 00000001 AMD 31504F47)
...skipping...
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully called chroot.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully dropped privileges.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully limited resources.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Watchdog thread running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Canary thread running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully made thread 1577 of process 1577 (n/a) owned by '1000' high priority at nice le
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Supervising 1 threads of 1 processes of 1 users.
Dec 26 09:42:08 NAME kernel: fuse init (API version 7.27)
Dec 26 09:42:08 NAME systemd[1]: Mounting FUSE Control File System...
Dec 26 09:42:08 NAME systemd[1]: Mounted FUSE Control File System.