Bug 487886 - Network disconnection Ethernet
Summary: Network disconnection Ethernet
Status: REPORTED
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-01 14:11 UTC by Dav84
Modified: 2024-06-13 01:11 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
KCrash Handler (4.66 KB, text/vnd.kde.kcrash-report)
2024-06-13 01:11 UTC, Dav84
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dav84 2024-06-01 14:11:59 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 6.0.4
(available in About System)
KDE Plasma Version: 6.0
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

More or less 4 days ago it started sending a message disconnecting the cable or Ethernet network for no reason that I can understand and it tells me that the connection is limited and puts the yellow triangle on the network icon on the taskbar what I do is simply turn off the connection and then reconnect and the triangle is eliminated and it does not seem constant. It can happen to me once or twice a day and it seems that the connection speed is not affected but if I am in Spotify, for example, obviously cuts off my playback, it doesn't seem like a local network problem or a problem with the PC's network card, that's thanks.
Comment 1 Dav84 2024-06-02 19:16:06 UTC
To the above I add that it is difficult to recognize a Wi-Fi network and when I manage to connect to the home Wi-Fi network it seems to be connecting and disconnecting from the Wi-Fi and I highlight that in my case in Wi-Fi I use it via USB that is not integrated into the board although it is not It is my priority connection because I prefer cable, these frequent disconnections should not happen, it reminds me of when I used Windows 8 for a while and that damn problem of constant Wi-Fi disconnection.
Comment 2 Dav84 2024-06-02 22:33:52 UTC
It will have something to do with Power Management, although I am not using a laptop, it is a desktop PC but...in the last few hours, the annoying network disconnection and limited connection message has become more frequent.
Comment 3 Carlos De Maine 2024-06-03 01:40:33 UTC
more tan likely a wifi driver.  do you see anything in the journal??
Comment 4 Dav84 2024-06-03 16:25:42 UTC
(In reply to Carlos De Maine from comment #3)
> more tan likely a wifi driver.  do you see anything in the journal??

Yes, they always say that it is a driver and it may be that it is, but the problem is that the wired connection is affecting me. Honestly, the Wi-Fi works for me since it is a desktop PC, but since it is disconnecting from the wired network, it bothers me. Now I have been using KDE for more than three years and a few months since this latest version and I had never had network connection problems either on my old laptop or on this new PC and these started almost a week ago with some update something was loaded and now this happens, I don't know if it happens to anyone else, I've seen several forums with the same problem.
Comment 5 Dav84 2024-06-09 21:13:01 UTC
I still have network disconnection problems and you are giving the problem to someone with the same story, which is the wifi or network driver. It's been almost 15 days with this problem. Before these 15 days, I never had network problems in KDE neon. Even when I restart the PC when loading it disconnects itself from the network, it is a new PC with modern components, I know that it is not the strong point of Linux to work well on new computers which seems very bad to me and that is why it cannot take off in Mass so many failures on new PCs is not good for the aspirations of the Linux desktop, it is unfortunate but I will have to change to Linux Mint because I do not see a solution and as an end user there is no reason to rack my brain looking for or compiling drivers and even more so when You are not that expert in Linux.
Comment 6 Dav84 2024-06-12 19:41:31 UTC
I just turned on the PC and this happened, I know that maybe the report is not here or someone is going to get upset but I thought it was important to report it.


Application: Sistema de gestión de energía de KDE (org_kde_powerdevil), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=132477106899584) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=132477106899584) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=132477106899584, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x0000787cc1a42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x0000787cc1a287f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x0000787cc1a2871b in __assert_fail_base (fmt=0x787cc1bdd130 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x787cabfe5530 "finish_time > tsrec->finish_time", file=0x787cabfe3995 "last_io_event.c", line=119, function=<optimized out>) at ./assert/assert.c:92
#10 0x0000787cc1a39e96 in __GI___assert_fail (assertion=0x787cabfe5530 "finish_time > tsrec->finish_time", file=0x787cabfe3995 "last_io_event.c", line=119, function=0x787cabfe6e90 "record_io_finish") at ./assert/assert.c:101
#11 0x0000787cabfc2a94 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#12 0x0000787cabfbaf0d in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#13 0x0000787cabfaa19b in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#14 0x0000787cabfaa5fd in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#15 0x0000787cabfaaac1 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#16 0x0000787cabfadd76 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#17 0x0000787cabfafb04 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#18 0x0000787cabfb00c0 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#19 0x0000787cabfb11d2 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#20 0x0000787cabfb18da in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#21 0x0000787cabfb1ac5 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#22 0x0000787cabfb1df8 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#23 0x0000787cabfb2185 in ?? () from /lib/x86_64-linux-gnu/libddcutil.so.4
#24 0x0000787cabfa36c3 in ddca_get_display_refs () from /lib/x86_64-linux-gnu/libddcutil.so.4
#25 0x0000787cb808e895 in PowerDevilUPowerBackend::initWithBrightness(bool) () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/powerdevil/powerdevilupowerbackend.so
#26 0x0000787cc266355e in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#27 0x0000787cb808a903 in PowerDevilUPowerBackend::brightnessSupportQueried(bool) () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/powerdevil/powerdevilupowerbackend.so
#28 0x0000787cc266355e in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#29 0x0000787cc33cda80 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF6CoreAddons.so.6
#30 0x0000787cc33d185b in ?? () from /lib/x86_64-linux-gnu/libKF6CoreAddons.so.6
#31 0x0000787cc266355e in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#32 0x0000787cb81524d6 in ?? () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kauth/helper/kauth_helper_plugin.so
#33 0x0000787cb815325a in ?? () from /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kauth/helper/kauth_helper_plugin.so
#34 0x0000787cc326856f in ?? () from /lib/x86_64-linux-gnu/libQt6DBus.so.6
#35 0x0000787cc25fa272 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#36 0x0000787cc26a1c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#37 0x0000787cc26a23e0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#38 0x0000787cc2478277 in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#39 0x0000787cc091bd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#40 0x0000787cc09712b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#41 0x0000787cc09193e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#42 0x0000787cc2476570 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#43 0x0000787cc26a3e3b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#44 0x0000787cc26a5a6c in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#45 0x00005c460d80be48 in ?? ()
#46 0x0000787cc1a29d90 in __libc_start_call_main (main=main@entry=0x5c460d80b720, argc=argc@entry=1, argv=argv@entry=0x7ffeb8e9c6a8) at ../sysdeps/nptl/libc_start_call_main.h:58
#47 0x0000787cc1a29e40 in __libc_start_main_impl (main=0x5c460d80b720, argc=1, argv=0x7ffeb8e9c6a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeb8e9c698) at ../csu/libc-start.c:392
#48 0x00005c460d80cab5 in ?? ()
[Inferior 1 (process 1053) detached]
Comment 7 Dav84 2024-06-13 01:11:08 UTC
Created attachment 170445 [details]
KCrash Handler