You are not logged in.

#1 2022-01-04 04:45:05

ningates
Member
Registered: 2021-12-31
Posts: 9

KDE spamming "Connection Ethernet activated" over and over

Hi,
just reinstalled arch for like the fifth time and running into a new issue here where upon connecting to my ethernet or even wifi, I get spammed continuously with "Connection [Wi-Fi/Ethernet) activated". Don't know what the heck to do. Thanks

Offline

#2 2022-01-04 08:29:39

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,296

Re: KDE spamming "Connection Ethernet activated" over and over

Post your system journal of an affected boot

sudo journalctl -b

https://wiki.archlinux.org/title/List_o … n_services

I assume you have multiple concurrent services running fighting for the device, what's your output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Offline

#3 2022-01-04 16:44:29

ningates
Member
Registered: 2021-12-31
Posts: 9

Re: KDE spamming "Connection Ethernet activated" over and over

V1del wrote:

Post your system journal of an affected boot

sudo journalctl -b

https://wiki.archlinux.org/title/List_o … n_services

I assume you have multiple concurrent services running fighting for the device, what's your output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Journalctl log: https://www.toptal.com/developers/haste … yak.apache

For the last line: https://i.imgur.com/uDbbeRQ.png

Thanks man

Offline

#4 2022-01-04 16:59:53

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,137

Re: KDE spamming "Connection Ethernet activated" over and over

No colliding services, but the journal is useless - don't copy out of the pager.

sudo journalctl -b | curl -F 'f:1=<-' ix.io

Offline

#5 2022-01-04 17:15:31

ningates
Member
Registered: 2021-12-31
Posts: 9

Re: KDE spamming "Connection Ethernet activated" over and over

seth wrote:

No colliding services, but the journal is useless - don't copy out of the pager.

sudo journalctl -b | curl -F 'f:1=<-' ix.io

Forgive me why is copying out of the terminal useless, at least in this case, but ix.io is not?

Offline

#6 2022-01-04 17:35:50

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: KDE spamming "Connection Ethernet activated" over and over

ningates wrote:

Please read CoC - Pasting pictures and code


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#7 2022-01-04 17:49:12

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,137

Re: KDE spamming "Connection Ethernet activated" over and over

Not the terminal, but the pager.
You copied a truncated version of the first page of the journal.

Feeding the journal into ix.io will actually provide all of it.
You can also redirect into a file and post that somewhere or take any approach that gets the full text (whan copying out of the pager will not)

Offline

#8 2022-01-04 18:18:47

ningates
Member
Registered: 2021-12-31
Posts: 9

Re: KDE spamming "Connection Ethernet activated" over and over

seth wrote:

Not the terminal, but the pager.
You copied a truncated version of the first page of the journal.

Feeding the journal into ix.io will actually provide all of it.
You can also redirect into a file and post that somewhere or take any approach that gets the full text (whan copying out of the pager will not)

So like, where the heck do I get the url to the ix.io. Thanks for hanging in there with me. Or give me a link to read at, just tryna escape the bloatwareof windows and the useless utilities from other distros. I've used ubuntu and fedora in the past so I'm facepalming trying to understand this stuff. There was one video I saw on youtube about ix.io but I wasn't following.. thanks again

Offline

#9 2022-01-04 18:22:12

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,137

Re: KDE spamming "Connection Ethernet activated" over and over

If you run the command I posted in #4 that will upload your journal to ix.io and print the url in return.

Offline

#10 2022-01-04 18:27:09

ningates
Member
Registered: 2021-12-31
Posts: 9

Re: KDE spamming "Connection Ethernet activated" over and over

seth wrote:

If you run the command I posted in #4 that will upload your journal to ix.io and print the url in return.

Strange because nothing is being returned upon entering the command. Have entered it in multiple times now.. lol fml

Last edited by ningates (2022-01-04 18:27:34)

Offline

#11 2022-01-04 18:31:41

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,137

Re: KDE spamming "Connection Ethernet activated" over and over

There's a quota - if the spam is really bad the output will be far too long to be accepted.
Redirect the journal into some file and upload that, you might have to use some google drive or wetransfer if it's really big.

Offline

#12 2022-01-04 19:29:13

ningates
Member
Registered: 2021-12-31
Posts: 9

Re: KDE spamming "Connection Ethernet activated" over and over

seth wrote:

There's a quota - if the spam is really bad the output will be far too long to be accepted.
Redirect the journal into some file and upload that, you might have to use some google drive or wetransfer if it's really big.

https://drive.google.com/file/d/1b3k4zd … sp=sharing

Offline

#13 2022-01-04 22:58:02

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,137

Re: KDE spamming "Connection Ethernet activated" over and over

It's 428MB - yeah, that's beyond any quota…
The reason is (probably the 4419 crashes of kded within 3h (so basically all the time and in a row)

They all kinda look like

                                             Stack trace of thread 1268:
                                             #0  0x00007f64d8b77d22 raise (libc.so.6 + 0x3cd22)
                                             #1  0x00007f64d9c121c4 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x51c4)
                                             #2  0x00007f64d8b77da0 __restore_rt (libc.so.6 + 0x3cda0)
                                             #3  0x00007f64c449fdc0 _ZNK7KScreen4Mode2idEv (libKF5Screen.so.7 + 0x33dc0)
                                             #4  0x00007f64c44fe61f n/a (kscreen.so + 0x2361f)
                                             #5  0x00007f64c4502e2e n/a (kscreen.so + 0x27e2e)
                                             #6  0x00007f64c44eab42 n/a (kscreen.so + 0xfb42)
                                             #7  0x00007f64c44ecf4c n/a (kscreen.so + 0x11f4c)
                                             #8  0x00007f64d91c7c03 n/a (libQt5Core.so.5 + 0x2aac03)
                                             #9  0x00007f64d91c7c03 n/a (libQt5Core.so.5 + 0x2aac03)
                                             #10 0x00007f64c450555f n/a (kscreen.so + 0x2a55f)
                                             #11 0x00007f64d91c7c03 n/a (libQt5Core.so.5 + 0x2aac03)
                                             #12 0x00007f64d95317a4 _ZN23QDBusPendingCallWatcher8finishedEPS_ (libQt5DBus.so.5 + 0x567a4)
                                             #13 0x00007f64d91bacf6 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x29dcf6)
                                             #14 0x00007f64d9e381a6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15f1a6)
                                             #15 0x00007f64d919708a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x27a08a)
                                             #16 0x00007f64d9197b89 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x27ab89)
                                             #17 0x00007f64d91de3b8 n/a (libQt5Core.so.5 + 0x2c13b8)
                                             #18 0x00007f64d7d0652c g_main_context_dispatch (libglib-2.0.so.0 + 0x5452c)
                                             #19 0x00007f64d7d5a7b9 n/a (libglib-2.0.so.0 + 0xa87b9)
                                             #20 0x00007f64d7d03c11 g_main_context_iteration (libglib-2.0.so.0 + 0x51c11)
                                             #21 0x00007f64d91e22ba _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2c52ba)
                                             #22 0x00007f64d918f36b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x27236b)
                                             #23 0x00007f64d919aab7 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x27dab7)
                                             #24 0x00005579d74c46fc n/a (kded5 + 0x66fc)
                                             #25 0x00007f64d8b62b25 __libc_start_main (libc.so.6 + 0x27b25)
                                             #26 0x00005579d74c4aee n/a (kded5 + 0x6aee)

So in the kscreen plugin.
=>

kcmshell5 kded

and there disable the kscreen plugin to stop this madness.

As for the cause:
What's the output of

xrandr -q

and your xorg log, https://wiki.archlinux.org/title/Xorg#General ?

Also to be sure: you didn't conduct some partial update, did you?

Offline

Board footer

Powered by FluxBB