su-to-root -X -c bleachbit: Could not open X display

Bug #1100219 reported by marcobra (Marco Braida)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

bleachbit:
  Installato: 0.9.3-1
  Candidato: 0.9.3-1
  Tabella versione:
 *** 0.9.3-1 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

Running as non root bleachbit works fine bu if i run from menu item and also in terminal with:

su-to-root -X -c bleachbit

i get
(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_long_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_long_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_long_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_long_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_string_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_prepend_search_path: assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_prepend_search_path: assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_icon_theme_prepend_search_path: assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_string_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_string_property: assertion `GTK_SETTINGS (settings)' failed

(gksu:15117): Gtk-CRITICAL **: IA__gtk_settings_set_string_property: assertion `GTK_SETTINGS (settings)' failed
Could not open X display

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: bleachbit 0.9.3-1
Uname: Linux 3.7.1-030701-generic i686
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
Date: Wed Jan 16 10:24:01 2013
MarkForUpload: True
PackageArchitecture: all
SourcePackage: bleachbit
UpgradeStatus: Upgraded to quantal on 2012-07-02 (197 days ago)

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :
Revision history for this message
Andrew Ziem (ahziem1) wrote :

I cannot reproduce on Ubuntu 12.10 with BleachBit 0.9.3 installed from the Ubuntu repository.

Are you using KDE, GNOME, Ubuntu Unity, or something else?

Do you have a file ~/.gtkrc-2.0 ? What is in it?

From https://bbs.archlinux.org/viewtopic.php?pid=999078#p999078

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

I made login on "Ubuntu classic (no effects)"
---------------------------------------------------------------
The .gtkrc-2.0 content: cat .gtkrc-2.0

include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"

gtk-theme-name="oxygen-gtk"

---------------------------------------------------------------
also the .gtkrc-2.0-kde4 content

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"

include "/usr/share/themes/Radiance/gtk-2.0/gtkrc"

style "user-font"
{
 font_name="Ubuntu"
}
widget_class "*" style "user-font"

gtk-theme-name="Radiance"
gtk-font-name="Ubuntu 9"

---------------------------------------------------------------

echo $DISPLAY
:0.0

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

With this command

gksudo -k bleachbit

bleachbit is work as root

tags: added: su-to-root
Revision history for this message
Andrew Ziem (ahziem1) wrote :

I think this problem is in GTK or su-to-root

affects: bleachbit (Ubuntu) → gksu (Ubuntu)
Revision history for this message
jay (jay-mcml) wrote :

Just installed Kubuntu 12.10 AMD64 desktop

get same problem trying to run bleacbit as root
gksudo -k bleachbit did not work - did get error message:
Error copying '/tmp/kde-jay/xauth-1000-_0' to '/tmp/libgksu-db2kSu': No such file or directory

but, in /tmp is:
drwx------ 2 jay jay 4096 Mar 12 18:45 libgksu-db2kSu
in there is
-rw------- 1 jay jay 0 Mar 12 18:45 .Xauthority

note: zero-length.
and /tmp/kde-jay is empty.

nothing interestin in /var/log/Xorg.0.log
no errors in /var/log/auth.log

weird message in syslog
Mar 12 18:53:45 pc-14-large dbus[780]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Mar 12 18:53:45 pc-14-large org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 12 18:53:45 pc-14-large dbus[780]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Mar 12 18:55:00 pc-14-large dbus[780]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Mar 12 18:55:00 pc-14-large org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 12 18:55:00 pc-14-large dbus[780]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'

hope this helps.
Jay

Revision history for this message
Vladimir Chapaikin (chapaikinva) wrote :

On KDE (KUbuntu) I solved this problem via adding the following files to bleachbit's white list:

/tmp/kde-chapaikinva/xauth-1000-_0
/home/chapaikinva/.kde/tmp-AP35-2008/xauth-1000-_0

where:

"chapaikinva" - is my username in ubuntu,
"1000" - is code for my ubuntu user's account,
"AP35-2008" - is my computer's name.

Revision history for this message
Andrew Ziem (ahziem1) wrote :

I think this is a duplicate of bug 1377719. There is more info there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.