midori do not show pages and ui correct

sithun · 11-17-2016, 12:38 AM

midori do not show pages and ui correct also proxy not work

terminal output:

Code:

bash-4.3# midori

** (midori4:6184): CRITICAL **: enchant_broker_dict_exists: assertion 'tag && strlen(tag)' failed

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:2:31: The style property GtkButton:default-border is deprecated and shouldn't be used anymore. It will be removed in a future version

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:3:39: The style property GtkButton:default-outside-border is deprecated and shouldn't be used anymore. It will be removed in a future version

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:4:29: The style property GtkButton:inner-border is deprecated and shouldn't be used anymore. It will be removed in a future version

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:5:33: The style property GtkWidget:focus-line-width is deprecated and shouldn't be used anymore. It will be removed in a future version

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:6:30: The style property GtkWidget:focus-padding is deprecated and shouldn't be used anymore. It will be removed in a future version

(midori4:6184): Gtk-WARNING **: Theme parsing error: gtk3.css:26:20: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(midori4:6184): Gtk-WARNING **: Error loading theme icon 'package' for stock: Icon 'package' not present in theme Adwaita

(midori4:6184): Gtk-WARNING **: Error loading theme icon 'package' for stock: Icon 'package' not present in theme Adwaita

(midori4:6184): Gtk-WARNING **: Error loading theme icon 'package' for stock: Icon 'package' not present in theme Adwaita
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

how to fix it?

ponce · 11-17-2016, 01:03 AM

about the ui try changing your icon theme, see for example if using the Tango icon theme in your desktop works (try also others).
same thing for your gtk+3 theme, try changing it: please post the output of this command

Code:

cat ~/.config/gtk-3.0/settings.ini

regarding the proxy seems to be a regression in webkit2gtk: to use a proxy you can still launch it from a terminal passing it the http_proxy variable, like (the proxy there is just for example)

Code:

http_proxy=http://187.44.1.54:8080 midori

sithun · 11-18-2016, 01:37 AM

Quote:

Originally Posted by ponce

about the ui try changing your icon theme, see for example if using the Tango icon theme in your desktop works (try also others).

how can i do this?

Quote:

Originally Posted by ponce

same thing for your gtk+3 theme, try changing it: please post the output of this command

Code:

cat ~/.config/gtk-3.0/settings.ini

Code:

bash-4.3# cat ~/.config/gtk-3.0/settings.ini
cat: /root/.config/gtk-3.0/settings.ini: No such file or directory
bash-4.3#

ponce · 11-18-2016, 02:16 AM

Quote:

Originally Posted by sithun

how can i do this?

which desktop are you using (xfce, kde, something else)?

can you please post the output of the following commands? all of them, please.

Code:

ls -1 /var/log/packages/{gcc,glib,gtk}*

Code:

cat /etc/slackware-version

Code:

ls -la /usr/lib*/libgtk-*

Code:

ls -la /usr/local/lib*/libgtk-*

Code:

echo $LD_LIBRARY_PATH

Code:

cat /etc/ld.so.conf

bassmadrigal · 11-18-2016, 07:04 AM

As an aside, can I ask why you're running midori as root? Ideally root should only be used when necessary for system administration tasks. Running it as your normal user is just asking for problems as now all your programs run with root access and any bugs/exploits/vulnerabilities also run with root access and could be a ticking timebomb. I would be especially leary of running a web browser as root, as the browser is a frequently targeted attack vector.

Then there's always the oops moments... if you're root and you have one typo in your rm command, or a badly coded shell script, you could easily remove some system files and prevent booting.

See the following sites for more info:
AskUbuntu: Why is it bad to login as root?
Superuser: Why is it bad to run as root?
How-To Geek: Why you shouldn't log into your Linux system as root
Serverfault: What's wrong with always being root?
CProgramming: Why is running programs as root so bad?

sithun · 11-18-2016, 01:57 PM

Quote:

Originally Posted by ponce

which desktop are you using (xfce, kde, something else)?

i use icewm

Quote:

Originally Posted by ponce

can you please post the output of the following commands? all of them, please.

Code:

ls -1 /var/log/packages/{gcc,glib,gtk}*

Code:

cat /etc/slackware-version

Code:

ls -la /usr/lib*/libgtk-*

Code:

ls -la /usr/local/lib*/libgtk-*

Code:

echo $LD_LIBRARY_PATH

Code:

cat /etc/ld.so.conf

Code:

bash-4.3# ls -1 /var/log/packages/{gcc,glib,gtk}*
/var/log/packages/gcc-5.3.0-x86_64-3
/var/log/packages/gcc-g++-5.3.0-x86_64-3
/var/log/packages/gcc-gfortran-5.3.0-x86_64-3
/var/log/packages/gcc-gnat-5.3.0-x86_64-3
/var/log/packages/gcc-go-5.3.0-x86_64-3
/var/log/packages/gcc-java-5.3.0-x86_64-3
/var/log/packages/gcc-objc-5.3.0-x86_64-3
/var/log/packages/gccmakedep-1.0.3-noarch-1
/var/log/packages/glib-1.2.10-x86_64-3
/var/log/packages/glib-2.50.1-x86_64-0
/var/log/packages/glib-networking-2.46.1-x86_64-1
/var/log/packages/glib2-2.46.2-x86_64-2
/var/log/packages/glibc-2.23-x86_64-1
/var/log/packages/glibc-i18n-2.23-x86_64-1
/var/log/packages/glibc-profile-2.23-x86_64-1
/var/log/packages/glibc-solibs-2.23-x86_64-1
/var/log/packages/glibc-zoneinfo-2016e-noarch-1
/var/log/packages/glibmm-2.46.4-x86_64-1
/var/log/packages/gtk+-1.2.10-x86_64-5
/var/log/packages/gtk+-3.22.1-x86_64-0
/var/log/packages/gtk+2-2.24.30-x86_64-1
/var/log/packages/gtk+3-3.18.9-x86_64-1
/var/log/packages/gtk-xfce-engine-2.10.1-x86_64-2
/var/log/packages/gtkmm2-2.24.4-x86_64-1
/var/log/packages/gtkmm3-3.18.1-x86_64-1
/var/log/packages/gtkspell-2.0.16-x86_64-3
bash-4.3# cat /etc/slackware-version                                           
Slackware 14.2
bash-4.3# ls -la /usr/lib*/libgtk-*
lrwxrwxrwx 1 root root       19 Oct 18 11:59 /usr/lib64/libgtk-1.2.so.0 -> libgtk-1.2.so.0.9.1
-rwxr-xr-x 1 root root  1501304 Jun  9  2009 /usr/lib64/libgtk-1.2.so.0.9.1
-rw-r--r-- 1 root root      927 Oct 23 18:37 /usr/lib64/libgtk-3.la
lrwxrwxrwx 1 root root       20 Oct 23 18:46 /usr/lib64/libgtk-3.so -> libgtk-3.so.0.2200.1
lrwxrwxrwx 1 root root       20 Oct 23 18:46 /usr/lib64/libgtk-3.so.0 -> libgtk-3.so.0.2200.1
-rwxr-xr-x 1 root root  7426904 Mar 10  2016 /usr/lib64/libgtk-3.so.0.1800.9
-rwxr-xr-x 1 root root 30790304 Oct 23 18:37 /usr/lib64/libgtk-3.so.0.2200.1
-rw-r--r-- 1 root root      965 Mar  7  2016 /usr/lib64/libgtk-x11-2.0.la
lrwxrwxrwx 1 root root       27 Oct 18 11:59 /usr/lib64/libgtk-x11-2.0.so -> libgtk-x11-2.0.so.0.2400.30
lrwxrwxrwx 1 root root       27 Oct 18 11:59 /usr/lib64/libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0.2400.30
-rwxr-xr-x 1 root root  4432088 Mar  7  2016 /usr/lib64/libgtk-x11-2.0.so.0.2400.30
bash-4.3# ls -la /usr/local/lib*/libgtk-*
ls: cannot access '/usr/local/lib*/libgtk-*': No such file or directory
bash-4.3# echo $LD_LIBRARY_PATH

bash-4.3# cat /etc/ld.so.conf
/lib64
/usr/lib64
/usr/local/lib64
/usr/x86_64-slackware-linux/lib64
/usr/lib64/seamonkey
bash-4.3#

ponce · 11-18-2016, 02:04 PM

you have installed conflicting version of gtk+3 and glib2, most probably borking your system: you can try removing the newer versions and reinstalling the original one that come with Slackware but there are no guarantee that this will fix your installation.

to change icon themes and the gtk one you can try installing lxappearance, but seeing the state of your system now I cannot guarantee it will work.

sithun · 11-18-2016, 02:08 PM

Quote:

Originally Posted by bassmadrigal

As an aside, can I ask why you're running midori as root? Ideally root should only be used when necessary for system administration tasks. Running it as your normal user is just asking for problems as now all your programs run with root access and any bugs/exploits/vulnerabilities also run with root access and could be a ticking timebomb. I would be especially leary of running a web browser as root, as the browser is a frequently targeted attack vector.

Then there's always the oops moments... if you're root and you have one typo in your rm command, or a badly coded shell script, you could easily remove some system files and prevent booting.

See the following sites for more info:
AskUbuntu: Why is it bad to login as root?
Superuser: Why is it bad to run as root?
How-To Geek: Why you shouldn't log into your Linux system as root
Serverfault: What's wrong with always being root?
CProgramming: Why is running programs as root so bad?

thanks, i did not know that using root is bad. it is looked stupid for me use not root account on system that used only by myself. when my system will broke once again in new one i will use ordinary account

bassmadrigal · 11-18-2016, 02:56 PM

Quote:

Originally Posted by sithun

thanks, i did not know that using root is bad. it is looked stupid for me use not root account on system that used only by myself. when my system will broke once again in new one i will use ordinary account

Don't worry. It's a common misconception in Linux. Overall, the goal is to run everything possible with the least amount of privileges, and then only escalate to root privileges as needed. I can't remember off the top of my head, but there's even some programs that, by default, refuse to start if you are the root user just because of the security implications.

Years ago, when I first started learning Linux in college, I had extensive experience with Windows 2000 and I was very familiar with the "Administrator" account and group. I wanted that same thing on my machine, but I knew I wasn't supposed to log in as "root", so I modified my user to have root privileges. Only later did I realize why they say to not log in as root... it's just to minimize the chance of something, whether that be a user's dumb moment, a developer's dumb moment, or a hacker's attempt to well... hack, breaking your computer.

All we can do is get the info out

sithun · 11-21-2016, 11:42 PM

Quote:

Originally Posted by ponce

you can try removing the newer versions and reinstalling the original one that come with Slackware

after i did it midori start to work correct but sakura broked with output:

Code:

bash-4.3# sakura
sakura: symbol lookup error: /usr/lib64/libvte-2.91.so.0: undefined symbol: gtk_widget_class_set_css_name

ponce · 11-21-2016, 11:45 PM

if you built stuff against the new gtk+3 (like vte3, in your case) you will have to rebuild it against the stock gtk+3.