Bug 414328 - After making a wifi connection the windows system is unstable, new programs cannot be started
Summary: After making a wifi connection the windows system is unstable, new programs c...
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-networkmanager-qt
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.64.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-20 12:05 UTC by R.V.
Modified: 2022-10-28 05:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R.V. 2019-11-20 12:05:17 UTC
SUMMARY
When the system makes a wifi connection no new programs can bestarted until a complete restart of the windows system "/etc/init.d/xdm restart"


STEPS TO REPRODUCE
1. reboot with a perfect running system
2. make a wifi connection
3. try to start an application. Even try to star an application from a console both user and root will result in error

OBSERVED RESULT
A NORMAL START OF DOLPHIN BY A USER

robert@localhost ~ $ dolphin
kf5.kio.core: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf\nError loading services.\n"
kf5.kio.core: We got some errors while running 'net usershare info'
kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n"

STARTING DOLPHIN AFTER MAKING A WIFI CONNECTION

robert@localhost ~ $ dolphin
Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland-org.kde.kwin.qpa, minimal, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted
robert@localhost ~ $ 

RESTART XDM AND START DOLPHIN

robert@localhost ~ $ dolphin
kf5.kio.core: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf\nError loading services.\n"
kf5.kio.core: We got some errors while running 'net usershare info'
kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n"

Now for porthole started by root

A NORMAL START BY ROOT

Porthole: python version =  2.7.16 (default, Oct 24 2019, 16:23:30) 
[GCC 8.3.0]
importing installed modules
starting main()
CONFIG: id initialized to  289096
CONFIGURATION: id initialized to  289485
PREFERENCES: id initialized to  355732
initializing utils.__init__.py
DEBUG: id initialized to  375089
UTILS: mydebug.id =  375089
PREFERENCES: imported debug.id =  375089
BACKENDS: id initialized to  580003
PORTAGELIB: id initialized to  580725
STERMINAL: id initialized to  601637
VERSION_SORT: id initialized to  672212
PROPERTIES: id initialized to  673492
METADATA: id initialized to  673815
PORTAGELIB: imported portage-2.2 modules
PORTAGELIB: portage version = 2.3.76
BACKENDS: portage_lib import complete : <module 'porthole.backends.portagelib' from '/usr/lib64/python2.7/site-packages/porthole/backends/portagelib.pyc'>
MAINWINDOW: id initialized to  691704
DATABASE: id initialized to  908683
PACKAGE: id initialized to  909144
DBREADER: import id initialized to  909494
UTILITIES: id initialized to  931579
USERCONFIGS: id initialized to  939884
DBREADER: DatabaseReader.id initialized to  949587
PLUGIN: id initialized to  159979
ADVEMERGE: id initialized to  269392
PORTHOLE: i18n_DIR = /usr/share/locale/

STARTING BY ROOT AFTER MAKING A WIFI CONNECTION

localhost /home/robert # porthole
Porthole: python version =  2.7.16 (default, Oct 24 2019, 16:23:30) 
[GCC 8.3.0]
importing installed modules
No protocol specified
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
starting main()
CONFIG: id initialized to  490159
CONFIGURATION: id initialized to  490287
PREFERENCES: id initialized to  493003
initializing utils.__init__.py
DEBUG: id initialized to  493426
UTILS: mydebug.id =  493426
PREFERENCES: imported debug.id =  493426
BACKENDS: id initialized to  513449
PORTAGELIB: id initialized to  513806
STERMINAL: id initialized to  514707
VERSION_SORT: id initialized to  515738
PROPERTIES: id initialized to  516834
METADATA: id initialized to  516950
PORTAGELIB: imported portage-2.2 modules
PORTAGELIB: portage version = 2.3.76
BACKENDS: portage_lib import complete : <module 'porthole.backends.portagelib' from '/usr/lib64/python2.7/site-packages/porthole/backends/portagelib.pyc'>
MAINWINDOW: id initialized to  83144
DATABASE: id initialized to  93687
PACKAGE: id initialized to  93903
DBREADER: import id initialized to  94035
UTILITIES: id initialized to  94510
USERCONFIGS: id initialized to  94748
DBREADER: DatabaseReader.id initialized to  95495
PLUGIN: id initialized to  113634
ADVEMERGE: id initialized to  116907
PORTHOLE: i18n_DIR = /usr/share/locale/
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: invalid (NULL) pointer instance
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: GtkWarning: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: g_object_get: assertion 'G_IS_OBJECT (object)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: value "TRUE" of type 'gboolean' is invalid or out of range for property 'visible' of type 'gboolean'
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: GtkWarning: IA__gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: GtkWarning: IA__gdk_pango_context_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_context_set_font_description: assertion 'context != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_context_set_base_dir: assertion 'context != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_context_set_language: assertion 'context != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_layout_new: assertion 'context != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_layout_set_attributes: assertion 'layout != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_layout_set_text: assertion 'layout != NULL' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: PangoWarning: pango_layout_get_unknown_glyphs_count: assertion 'PANGO_IS_LAYOUT (layout)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  config.Prefs.APP)
/usr/lib64/python2.7/site-packages/porthole/mainwindow.py:122: GtkWarning: IA__gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed
  config.Prefs.APP)
Segmentation fault
localhost /home/robert # 


RESTART XDM

localhost /home/robert # porthole
Porthole: python version =  2.7.16 (default, Oct 24 2019, 16:23:30) 
[GCC 8.3.0]
importing installed modules
starting main()
CONFIG: id initialized to  581817
CONFIGURATION: id initialized to  581952
PREFERENCES: id initialized to  584678
initializing utils.__init__.py
DEBUG: id initialized to  585105
UTILS: mydebug.id =  585105
PREFERENCES: imported debug.id =  585105
BACKENDS: id initialized to  604764
PORTAGELIB: id initialized to  605061
STERMINAL: id initialized to  605812
VERSION_SORT: id initialized to  606783
PROPERTIES: id initialized to  607873
METADATA: id initialized to  607982
PORTAGELIB: imported portage-2.2 modules
PORTAGELIB: portage version = 2.3.76
BACKENDS: portage_lib import complete : <module 'porthole.backends.portagelib' from '/usr/lib64/python2.7/site-packages/porthole/backends/portagelib.pyc'>
MAINWINDOW: id initialized to  173114
DATABASE: id initialized to  183656
PACKAGE: id initialized to  183882
DBREADER: import id initialized to  184005
UTILITIES: id initialized to  184456
USERCONFIGS: id initialized to  184671
DBREADER: DatabaseReader.id initialized to  185418
PLUGIN: id initialized to  203481
ADVEMERGE: id initialized to  206683
PORTHOLE: i18n_DIR = /usr/share/locale/

EXPECTED RESULT

I expected the windows system to remain stable

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
kernel 4.14.143-gentoo 64 bit


ADDITIONAL INFORMATION

This is not the only system that I have running right now. Its a new install the other one, a laptop, runs without any problems
Comment 1 R.V. 2019-11-21 17:24:51 UTC
After restarting xdm the system remains stable
Comment 2 Justin Zobel 2022-09-28 00:43:04 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-13 04:55:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-10-28 05:02:45 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!