Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: KDE apps short freezes after file/directory content changes

  1. #11

    Default Re: KDE apps short freezes after file/directory content changes

    I used Wireshark to see what's going on.
    When the freezes happens, the network connection is flooded with DNS requests:

    Code:
    No.     Time           Source                Destination           Protocol Length Info
          1 0.000000000    192.168.1.2           192.168.1.1           DNS      73     Standard query 0x53ae A cetriolo.suse
    
    Frame 1: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0
    Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10)
    Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
    User Datagram Protocol, Src Port: 38071, Dst Port: 53
    Domain Name System (query)
    
    No.     Time           Source                Destination           Protocol Length Info
          2 0.000017735    192.168.1.2           192.168.1.1           DNS      73     Standard query 0xd632 AAAA cetriolo.suse
    
    Frame 2: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface 0
    Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10)
    Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
    User Datagram Protocol, Src Port: 38071, Dst Port: 53
    Domain Name System (query)
    
    No.     Time           Source                Destination           Protocol Length Info
          3 0.011026167    192.168.1.1           192.168.1.2           DNS      148    Standard query response 0x53ae No such name A cetriolo.suse SOA a.root-servers.net
    
    Frame 3: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
    Ethernet II, Src: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10), Dst: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1)
    Internet Protocol Version 4, Src: 192.168.1.1, Dst: 192.168.1.2
    User Datagram Protocol, Src Port: 53, Dst Port: 38071
    Domain Name System (response)
    
    No.     Time           Source                Destination           Protocol Length Info
          4 0.011628077    192.168.1.1           192.168.1.2           DNS      148    Standard query response 0xd632 No such name AAAA cetriolo.suse SOA a.root-servers.net
    
    Frame 4: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on interface 0
    Ethernet II, Src: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10), Dst: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1)
    Internet Protocol Version 4, Src: 192.168.1.1, Dst: 192.168.1.2
    User Datagram Protocol, Src Port: 53, Dst Port: 38071
    Domain Name System (response)
    
    No.     Time           Source                Destination           Protocol Length Info
          5 0.011700108    192.168.1.2           192.168.1.1           DNS      68     Standard query 0x8681 A cetriolo
    
    Frame 5: 68 bytes on wire (544 bits), 68 bytes captured (544 bits) on interface 0
    Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10)
    Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
    User Datagram Protocol, Src Port: 33958, Dst Port: 53
    Domain Name System (query)
    Btw, "cetriolo" is the name of the pc...

    When I start Yast2 and go to System -> Network Setting -> Hostname/DNS and check the option "Assign Hostname to Loopback IP",
    the freezes seem to disappear.

    Any ideas?

  2. #12
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,559

    Cool Re: KDE apps short freezes after file/directory content changes

    The normal assumption is that, assigning the Hostname to the loopback IP address (127.0.0.2) "is a useful option if you want to have the host name resolvable at all times, even without active network". See: <https://doc.opensuse.org/documentati....basicnet.yast>

    But, the help in YaST gives a little more information: "Be careful with this setting if your machine is offering Network Services".

    But, it seems that, the current KDE and/or Qt world has some issues if the Hostname is not assigned to the loopback IP address.

    Therefore, it seems that, it's advisable that, currently, machines with a KDE GUI should -- in all cases -- assign the Hostname to the loopback IP address.

  3. #13

    Default Re: KDE apps short freezes after file/directory content changes

    Quote Originally Posted by dcurtisfra View Post
    The normal assumption is that, assigning the Hostname to the loopback IP address (127.0.0.2) "is a useful option if you want to have the host name resolvable at all times, even without active network". See: <https://doc.opensuse.org/documentati....basicnet.yast>

    But, the help in YaST gives a little more information: "Be careful with this setting if your machine is offering Network Services".

    But, it seems that, the current KDE and/or Qt world has some issues if the Hostname is not assigned to the loopback IP address.

    Therefore, it seems that, it's advisable that, currently, machines with a KDE GUI should -- in all cases -- assign the Hostname to the loopback IP address.
    Can you point me to some sources regarding the issues with KDE/Qt in case hostname is not assigned to loopback IP address?

    This raises all kind of questions.

    Why I can not reproduce the problem at work where my pc is running the same distro and version and desktop?

    Why the problem doesn't seem to appear when I create a new user and use that to login?

    Some info that could or could not be related to this problem: I'm running a Samba server that shares some directories which contains multimedia files.
    That way my mediaplayer can directly access them via the network.
    I did that by using Dolphin and rightclicking on some directories and selecting the "Share" tab.

    Later, when I have time, I'll disable the Samba server and see what happens.

  4. #14
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,559

    Default Re: KDE apps short freezes after file/directory content changes

    Quote Originally Posted by Teuniz View Post
    Can you point me to some sources regarding the issues with KDE/Qt in case hostname is not assigned to loopback IP address?
    Way back in 2005, someone in Romania mentioned that:
    Is loopback interface correctly set up?
    A non-working loopback interface can mess up KDE.
    There's also this openSUSE Forums thread from 2012 which is dealing with Firefox taking a considerable amount of time to start under KDE: <https://forums.opensuse.org/showthre...-starts-slowly>
    • 'nrickert' mentioned "You need "localhost" there. You can put both names on the one line."

    You could contact 'nrickert' to ask if he has some real background as to why.
    Failing that, I can only suggest a support question to the Qt folks.

  5. #15

    Default Re: KDE apps short freezes after file/directory content changes

    I did some more tests and I'm now able to reproduce the problem on another Opensuse box with Leap 42.2 & KDE.

    In Yast2, enable/setup a Samba server. Startup -> During Boot. Shares -> Disable all available shares. Check Allow Users to Share Directories. Check Allow Guest Access.

    In Dolphin, select a couple of directories to share. Rightclick on it and select Properties -> Share. Check Share with Samba. Check Allow Guests.

    Reboot.

    Start Wireshark and filter on DNS packets only.

    Start a couple of KDE-libs dependant applications like Kate (preferably with th filesystem browser plugin activated), Okular, Dolphin, and perform some file manipulations (copy/edit/whatever).

    Look what happens in Wireshark.

    A temporary workaround is to open Yast2 -> System -> Network Settings -> Hostname/DNS and check Assign Hostname to Loopback IP.
    It will make the desktop usable again but still not snappy.
    For a snappy KDE experience, you can't share directories using the above setup.

    I'm going to try to report this bug but don't have high hope they wanna fix it.
    I have reported some KDE bugs in the past and they (Opensuse and/or KDE) never rolled out an official update for the present distribution the bug was reported for.
    But at least nobody can blame me for not reporting it.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •