upgrade-reports: After update/upgrade got some issues

[neo1]

Hi all,

Last update/ upgrade i've done got some applications with issues like not opening or showing its contends. Any idea?

Synaptic:

No protocol specified
** (synaptic:6299): WARNING **: Could not open X display

gnome sidebar toolbox for system is not openning after click on it:

Sin nombre.jpg

Other eg is Gimp with icos not showing:

Captura de pantalla de 2017-08-23 20-52-43.jpg

Either for launching through command line as root is not working, getting same results.

-- System Information:
Distributor ID: Kali
Description: Kali GNU/Linux Rolling
Release: kali-rolling
Codename: kali-rolling
Architecture: x86_64

Kernel: Linux 4.11.0-kali1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Kali installation (VM, HDD, USB): HDD
Basic output of commands (ifconfig, dmesg):

dmesg:

[ago24 17:54] microcode: microcode updated early to revision 0x1c, date = 2015-02-26
[  +0,000000] Linux version 4.11.0-kali1-amd64 ([email protected]) (gcc version 6.4.0 20170704 (Debian 6.4.0
[  +0,000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.11.0-kali1-amd64 root=UUID=c119cea6-ac5b-47bc-9632
[  +0,000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[  +0,000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[  +0,000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[  +0,000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[  +0,000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[  +0,000000] e820: BIOS-provided physical RAM map:
[  +0,000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[  +0,000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[  +0,000000] BIOS-e820: [mem 0x0000000000100000-0x00000000de20efff] usable
[  +0,000000] BIOS-e820: [mem 0x00000000de20f000-0x00000000de81ffff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000de820000-0x00000000de8a8fff] usable
[  +0,000000] BIOS-e820: [mem 0x00000000de8a9000-0x00000000de947fff] ACPI NVS
[  +0,000000] BIOS-e820: [mem 0x00000000de948000-0x00000000deed1fff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000deed2000-0x00000000deed2fff] usable
[  +0,000000] BIOS-e820: [mem 0x00000000deed3000-0x00000000def15fff] ACPI NVS
[  +0,000000] BIOS-e820: [mem 0x00000000def16000-0x00000000df5c4fff] usable
[  +0,000000] BIOS-e820: [mem 0x00000000df5c5000-0x00000000df7f1fff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000df7f2000-0x00000000df7fffff] usable
[  +0,000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[  +0,000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[  +0,000000] BIOS-e820: [mem 0x0000000100000000-0x000000031effffff] usable
[  +0,000000] NX (Execute Disable) protection: active
[  +0,000000] SMBIOS 2.7 present.
[  +0,000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-PS4, BIOS P1.10 05/13/2013
[  +0,000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[  +0,000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[  +0,000000] e820: last_pfn = 0x31f000 max_arch_pfn = 0x400000000
[  +0,000000] MTRR default type: uncachable
[  +0,000000] MTRR fixed ranges enabled:
[  +0,000000]   00000-9FFFF write-back
[  +0,000000]   A0000-BFFFF uncachable
[  +0,000000]   C0000-CFFFF write-protect
[  +0,000000]   D0000-E7FFF uncachable
[  +0,000000]   E8000-FFFFF write-protect
[  +0,000000] MTRR variable ranges enabled:
[  +0,000000]   0 base 000000000 mask E00000000 write-back
[  +0,000000]   1 base 200000000 mask F00000000 write-back
[  +0,000000]   2 base 300000000 mask FF0000000 write-back
[  +0,000000]   3 base 310000000 mask FF8000000 write-back
[  +0,000000]   4 base 318000000 mask FFC000000 write-back
[  +0,000000]   5 base 31C000000 mask FFE000000 write-back
[  +0,000000]   6 base 31E000000 mask FFF000000 write-back
[  +0,000000]   7 base 0E0000000 mask FE0000000 uncachable

Ifconfig:

        eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::be5f:f4ff:feb7:f2e9  prefixlen 64  scopeid 0x20<link>
        ether bc:5f:f4:b7:f2:e9  txqueuelen 1000  (Ethernet)
        RX packets 363764  bytes 455731161 (434.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 215830  bytes 25813211 (24.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4162  bytes 298696 (291.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4162  bytes 298696 (291.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Links to the same problem: https://bugs.launchpad.net/shutter
Solutions tried and their result: eg.: I tried to rm temp files from Shutter app in home .shutter it reloaded the app but no great deal.

[freedg]

I am having the same problems. After update/upgrade several apps are no longer working. Metasploit has been fixed, but faraday and burpsuite won't load.

[kypropex]

I noticed the same issue with eclipse SDK and VMware Workstation for linux, the applications work properly but it's very annoying. I assume it has something to do with GTK 2, when I try to run eclipse SDK with GTK3 it works fine

[kypropex]

I reported the issue on kali bug tracker and managed to get the solution for the issue. For those of you who struggle with this issue, this might help:

https://bugs.kali.org/view.php?id=4210