[gentoo-user] elogviewer and something odd with equery

[gentoo-user] elogviewer and something odd with equery

[Dale]

Hi folks,

I have had elogv and elogviewer installed for a while.  I only use it on 
occasion but when I tried to use it the other day I get this little 
error message:

root@smoker / # elogviewer
No protocol specified
/usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: 
could not open display
   warnings.warn(str(e), _gtk.Warning)
/usr/bin/elogviewer:109: Warning: invalid (NULL) pointer instance
   gtk.Window.__init__ (self, gtk.WINDOW_TOPLEVEL)
/usr/bin/elogviewer:109: Warning: g_signal_connect_data: assertion 
`G_TYPE_CHECK_INSTANCE (instance)' failed
   gtk.Window.__init__ (self, gtk.WINDOW_TOPLEVEL)
/usr/bin/elogviewer:546: Warning: invalid (NULL) pointer instance
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: Warning: g_signal_connect_data: assertion 
`G_TYPE_CHECK_INSTANCE (instance)' failed
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: Warning: g_object_get: assertion `G_IS_OBJECT 
(object)' failed
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: Warning: value "TRUE" of type `gboolean' is 
invalid or out of range for property `visible' of type `gboolean'
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: GtkWarning: gdk_screen_get_display: assertion 
`GDK_IS_SCREEN (screen)' failed
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:546: Warning: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
   menubar = ui.get_widget('/Menubar')
/usr/bin/elogviewer:117: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   gtk.ScrolledWindow.__init__(self)
/usr/bin/elogviewer:203: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   'Category', gtk.CellRendererText(), text=CATEGORY))
/usr/bin/elogviewer:203: Warning: g_object_get: assertion `G_IS_OBJECT 
(object)' failed
   'Category', gtk.CellRendererText(), text=CATEGORY))
/usr/bin/elogviewer:205: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   'Package', gtk.CellRendererText(), text=PACKAGE))
/usr/bin/elogviewer:205: Warning: g_object_get: assertion `G_IS_OBJECT 
(object)' failed
   'Package', gtk.CellRendererText(), text=PACKAGE))
/usr/bin/elogviewer:207: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   'Time', gtk.CellRendererText(), text=TIMESORT))
/usr/bin/elogviewer:207: Warning: g_object_get: assertion `G_IS_OBJECT 
(object)' failed
   'Time', gtk.CellRendererText(), text=TIMESORT))
/usr/bin/elogviewer:571: GtkWarning: gdk_pango_context_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: PangoWarning: 
pango_context_set_font_description: assertion `context != NULL' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: PangoWarning: pango_context_set_base_dir: 
assertion `context != NULL' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: PangoWarning: pango_context_set_language: 
assertion `context != NULL' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: Warning: g_object_unref: assertion `G_IS_OBJECT 
(object)' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: GtkWarning: gtk_settings_get_for_screen: 
assertion `GDK_IS_SCREEN (screen)' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: GtkWarning: gdk_screen_get_display: assertion 
`GDK_IS_SCREEN (screen)' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: GtkWarning: gdk_keymap_get_for_display: 
assertion `GDK_IS_DISPLAY (display)' failed
   elogview_box.add(elogview)
/usr/bin/elogviewer:571: Warning: g_object_get: assertion `G_IS_OBJECT 
(object)' failed
   elogview_box.add(elogview)
Segmentation fault
root@smoker / #

I re-emerged python, everything gtk and elogviewer itself but still get 
this error.  I thought I would remove it and then install it again to 
get a fresh start.  Well before I remove anything I always check to see 
what is installed first and I get this from equery:

root@smoker / # equery list -p elog*
  * Searching for elog* ...
[IP-] [  ] app-portage/elogv-0.7.4:0
[IP-] [  ] app-portage/elogv-0.7.4:0
[-P-] [ ~] app-portage/elogv-0.7.4-r1:0
[IP-] [  ] app-portage/elogviewer-0.5.2-r2:0
[IP-] [  ] app-portage/elogviewer-0.5.2-r2:0
root@smoker / #

According to that, I have two copies of the same version installed.  
Huh?  Then I notice the same for elogv.  Double huh?  Well, I emerge -C 
the thing then run the equery command again.  They are both gone so I 
think this is a improvement at least.  I then install elogviewer again.  
It shows two copies installed again just like above.

So, it appears elogviewer has some issues but equery seems to have a 
weird streak as well.  I'm not sure which to tackle first.  By the way, 
elogv works fine.  The logs show up but I prefer elogviewer when i am 
logged into KDE.  I'm a bit of a GUI guy.

My question is, what the heck is going on with equery and why did 
elogviewer stop working?   I know equery gets a little weird sometimes 
so maybe it is a 24 hour bug.  lol

Thoughts?  Ideas?  Can of Raid?

Dale

:-)  :-)

[gentoo-user] Re: elogviewer and something odd with equery

[walt]

On 04/25/2010 09:25 PM, Dale wrote:
> Hi folks,
>
> I have had elogv and elogviewer installed for a while. I only use it on occasion but when I tried to use it the other day I get this little error message:
>
> root@smoker / # elogviewer
> No protocol specified
> /usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display

Do you have the DISPLAY variable set properly in root's environment?

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

walt wrote:
> On 04/25/2010 09:25 PM, Dale wrote:
>> Hi folks,
>>
>> I have had elogv and elogviewer installed for a while. I only use it 
>> on occasion but when I tried to use it the other day I get this 
>> little error message:
>>
>> root@smoker / # elogviewer
>> No protocol specified
>> /usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: 
>> GtkWarning: could not open display
>
> Do you have the DISPLAY variable set properly in root's environment?
>
>
>

Apparently something got changed with a update.  I tried to run hp-setup 
a bit ago and it failed too.  It gave this error:

No protocol specified
hp-setup: cannot connect to X server :0.0

I'm running this in a Konsole, part of KDE, so just where would I set 
this up?  I don't usually have to mess with it and it "just works".  I'm 
on KDE 4.4.2.  Maybe this is a "feature" of KDE4 until it gets 
"fixed".   ;-)

Thanks.

Dale

:-)  :-)

[gentoo-user] Re: elogviewer and something odd with equery

[walt]

On 04/26/2010 10:59 AM, Dale wrote:
> walt wrote:
>> On 04/25/2010 09:25 PM, Dale wrote:
>>> Hi folks,
>>>
>>> I have had elogv and elogviewer installed for a while. I only use it on occasion but when I tried to use it the other day I get this little error message:
>>>
>>> root@smoker / # elogviewer
>>> No protocol specified
>>> /usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
>>
>> Do you have the DISPLAY variable set properly in root's environment?
>>
>>
>>
>
> Apparently something got changed with a update. I tried to run hp-setup a bit ago and it failed too. It gave this error:
>
> No protocol specified
> hp-setup: cannot connect to X server :0.0

Wait, this is more complicated than I thought.  The error above clearly mentions
display :0.0, which should be correct unless you're running multiple X sessions.
When I 'unset DISPLAY' I get 'DISPLAY is not set'.

Do you have any files like /root/.xauthXXXXXX?

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

walt wrote:
> On 04/26/2010 10:59 AM, Dale wrote:
>> walt wrote:
>>> On 04/25/2010 09:25 PM, Dale wrote:
>>>> Hi folks,
>>>>
>>>> I have had elogv and elogviewer installed for a while. I only use 
>>>> it on occasion but when I tried to use it the other day I get this 
>>>> little error message:
>>>>
>>>> root@smoker / # elogviewer
>>>> No protocol specified
>>>> /usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: 
>>>> GtkWarning: could not open display
>>>
>>> Do you have the DISPLAY variable set properly in root's environment?
>>>
>>>
>>>
>>
>> Apparently something got changed with a update. I tried to run 
>> hp-setup a bit ago and it failed too. It gave this error:
>>
>> No protocol specified
>> hp-setup: cannot connect to X server :0.0
>
> Wait, this is more complicated than I thought.  The error above 
> clearly mentions
> display :0.0, which should be correct unless you're running multiple X 
> sessions.
> When I 'unset DISPLAY' I get 'DISPLAY is not set'.
>
> Do you have any files like /root/.xauthXXXXXX?
>
>

I think I can safely say yes to that question.  I do have a couple.  ;-)

root@smoker ~ # ls /root/.xauth*
-rw------- 1 root root 51 Dec 14 14:10 /root/.xauth48naIs
-rw------- 1 root root 51 Dec 14 17:31 /root/.xauth9yEErh
-rw------- 1 root root 51 Oct  2  2009 /root/.xauthAfQHY0
-rw------- 1 root root 51 Oct  6  2009 /root/.xauthEltCUe
-rw------- 1 root root 51 Apr 26 14:06 /root/.xauthFBdWPY
-rw------- 1 root root 51 Oct  6  2009 /root/.xauthJJISAe
-rw------- 1 root root 51 Oct  3  2009 /root/.xauthMjZyQi
-rw------- 1 root root 51 Sep 29  2009 /root/.xauthOApO1i
-rw------- 1 root root 51 Sep 25  2009 /root/.xauthSshOXz
-rw------- 1 root root 51 Sep 28  2009 /root/.xauthbFAjxt
-rw------- 1 root root 51 Oct  4  2009 /root/.xauthdKOWE3
-rw------- 1 root root 51 Oct  9  2009 /root/.xauthfCNLCo
-rw------- 1 root root 51 Oct 15  2009 /root/.xauthhhDOTW
-rw------- 1 root root 51 Oct 15  2009 /root/.xauthjRxXE8
-rw------- 1 root root 51 Dec 13 13:09 /root/.xauthm5cv93
-rw------- 1 root root 51 Sep 23  2009 /root/.xauthnARKQ1
-rw------- 1 root root 51 Oct  2  2009 /root/.xauthnaLVUB
root@smoker ~ #


Do I need to log out of KDE, delete those then login again?  What 
generates those and is something wrong that makes it create those?

Thanks.

Dale

:-)  :-)

[gentoo-user] Re: elogviewer and something odd with equery

[walt]

On 04/26/2010 01:53 PM, Dale wrote:
> walt wrote:

>> Do you have any files like /root/.xauthXXXXXX?
>>
>>
>
> I think I can safely say yes to that question. I do have a couple. ;-)
>
> root@smoker ~ # ls /root/.xauth*
> -rw------- 1 root root 51 Dec 14 14:10 /root/.xauth48naIs
> -rw------- 1 root root 51 Dec 14 17:31 /root/.xauth9yEErh
> -rw------- 1 root root 51 Oct 2 2009 /root/.xauthAfQHY0
> -rw------- 1 root root 51 Oct 6 2009 /root/.xauthEltCUe
> -rw------- 1 root root 51 Apr 26 14:06 /root/.xauthFBdWPY
> -rw------- 1 root root 51 Oct 6 2009 /root/.xauthJJISAe
> -rw------- 1 root root 51 Oct 3 2009 /root/.xauthMjZyQi
> -rw------- 1 root root 51 Sep 29 2009 /root/.xauthOApO1i
> -rw------- 1 root root 51 Sep 25 2009 /root/.xauthSshOXz
> -rw------- 1 root root 51 Sep 28 2009 /root/.xauthbFAjxt
> -rw------- 1 root root 51 Oct 4 2009 /root/.xauthdKOWE3
> -rw------- 1 root root 51 Oct 9 2009 /root/.xauthfCNLCo
> -rw------- 1 root root 51 Oct 15 2009 /root/.xauthhhDOTW
> -rw------- 1 root root 51 Oct 15 2009 /root/.xauthjRxXE8
> -rw------- 1 root root 51 Dec 13 13:09 /root/.xauthm5cv93
> -rw------- 1 root root 51 Sep 23 2009 /root/.xauthnARKQ1
> -rw------- 1 root root 51 Oct 2 2009 /root/.xauthnaLVUB
> root@smoker ~ #
>
>
> Do I need to log out of KDE, delete those then login again? What generates those and is something wrong that makes it create those?

I deleted all of them and generated a new one just by doing su from an xterm.
Does that work for you?

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

walt wrote:
> On 04/26/2010 01:53 PM, Dale wrote:
>> walt wrote:
>
>>> Do you have any files like /root/.xauthXXXXXX?
>>>
>>>
>>
>> I think I can safely say yes to that question. I do have a couple. ;-)
>>
>> root@smoker ~ # ls /root/.xauth*
>> -rw------- 1 root root 51 Dec 14 14:10 /root/.xauth48naIs
>> -rw------- 1 root root 51 Dec 14 17:31 /root/.xauth9yEErh
>> -rw------- 1 root root 51 Oct 2 2009 /root/.xauthAfQHY0
>> -rw------- 1 root root 51 Oct 6 2009 /root/.xauthEltCUe
>> -rw------- 1 root root 51 Apr 26 14:06 /root/.xauthFBdWPY
>> -rw------- 1 root root 51 Oct 6 2009 /root/.xauthJJISAe
>> -rw------- 1 root root 51 Oct 3 2009 /root/.xauthMjZyQi
>> -rw------- 1 root root 51 Sep 29 2009 /root/.xauthOApO1i
>> -rw------- 1 root root 51 Sep 25 2009 /root/.xauthSshOXz
>> -rw------- 1 root root 51 Sep 28 2009 /root/.xauthbFAjxt
>> -rw------- 1 root root 51 Oct 4 2009 /root/.xauthdKOWE3
>> -rw------- 1 root root 51 Oct 9 2009 /root/.xauthfCNLCo
>> -rw------- 1 root root 51 Oct 15 2009 /root/.xauthhhDOTW
>> -rw------- 1 root root 51 Oct 15 2009 /root/.xauthjRxXE8
>> -rw------- 1 root root 51 Dec 13 13:09 /root/.xauthm5cv93
>> -rw------- 1 root root 51 Sep 23 2009 /root/.xauthnARKQ1
>> -rw------- 1 root root 51 Oct 2 2009 /root/.xauthnaLVUB
>> root@smoker ~ #
>>
>>
>> Do I need to log out of KDE, delete those then login again? What 
>> generates those and is something wrong that makes it create those?
>
> I deleted all of them and generated a new one just by doing su from an 
> xterm.
> Does that work for you?
>

Well, I deleted them all, logged out of KDE and back in.  I still get 
the same thing as before with hp-setup.

Again, I am using Konsole for this.  This may be a KDE thing.  I know it 
worked fine in KDE3 but then again, a LOT of things worked fine in KDE3.

Dale

:-)  :-)

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Alex Schuster]

Dale writes:

> Again, I am using Konsole for this.  This may be a KDE thing.  I know
> it worked fine in KDE3 but then again, a LOT of things worked fine in
> KDE3.

It's probably not a KDE thing. I'm also using konsole in KDE4, and after 
becoming root (via su or su -) I have no Problems starting X applications.

I'm no expert at X authorization stuff. But I know that in the past I also 
had trouble when becoming root. Why it works for me and not for you - I 
don't know.

Workarounds you might try:
- Emerge sux, and use sux instead of su. Worked for me in the past.
- ssh -Y root@localhost

	Wonko

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

Alex Schuster wrote:
> Dale writes:
>
>    
>> Again, I am using Konsole for this.  This may be a KDE thing.  I know
>> it worked fine in KDE3 but then again, a LOT of things worked fine in
>> KDE3.
>>      
> It's probably not a KDE thing. I'm also using konsole in KDE4, and after
> becoming root (via su or su -) I have no Problems starting X applications.
>
> I'm no expert at X authorization stuff. But I know that in the past I also
> had trouble when becoming root. Why it works for me and not for you - I
> don't know.
>
> Workarounds you might try:
> - Emerge sux, and use sux instead of su. Worked for me in the past.
> - ssh -Y root@localhost
>
> 	Wonko
>
>
>    

I don't use su.  When I open the Konsole, it asks for a password.  It 
just uses the konsole command but it is told to run as root.  This is 
pretty much how it did in KDE3 tho.  When I open it, it pops up a window 
and asks for the root password.  Then it opens Konsole.  This is done 
from the little K menu thingy.

That make sense?

Dale

:-)  :-)

[gentoo-user] Re: elogviewer and something odd with equery

[walt]

On 04/26/2010 03:11 PM, Dale wrote:
> Alex Schuster wrote:
>> Dale writes:
>>
>>> Again, I am using Konsole for this. This may be a KDE thing. I know
>>> it worked fine in KDE3 but then again, a LOT of things worked fine in
>>> KDE3.
>> It's probably not a KDE thing. I'm also using konsole in KDE4, and after
>> becoming root (via su or su -) I have no Problems starting X applications.
>>
>> I'm no expert at X authorization stuff. But I know that in the past I also
>> had trouble when becoming root. Why it works for me and not for you - I
>> don't know.
>>
>> Workarounds you might try:
>> - Emerge sux, and use sux instead of su. Worked for me in the past.
>> - ssh -Y root@localhost
>>
>> Wonko
>>
>>
>
> I don't use su. When I open the Konsole, it asks for a password.

Does that mean you are not using the standard konsole, rather a special
icon intended to open a root terminal?  Must be, otherwise it wouldn't
ask for the root password.

Try opening a standard user konsole and just use su instead.  (Or even,
heaven forbid, an xterm instead of konsole.)  That should detect a KDE
problem if it exists.

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

walt wrote:
> On 04/26/2010 03:11 PM, Dale wrote:
>> Alex Schuster wrote:
>>> Dale writes:
>>>
>>>> Again, I am using Konsole for this. This may be a KDE thing. I know
>>>> it worked fine in KDE3 but then again, a LOT of things worked fine in
>>>> KDE3.
>>> It's probably not a KDE thing. I'm also using konsole in KDE4, and 
>>> after
>>> becoming root (via su or su -) I have no Problems starting X 
>>> applications.
>>>
>>> I'm no expert at X authorization stuff. But I know that in the past 
>>> I also
>>> had trouble when becoming root. Why it works for me and not for you - I
>>> don't know.
>>>
>>> Workarounds you might try:
>>> - Emerge sux, and use sux instead of su. Worked for me in the past.
>>> - ssh -Y root@localhost
>>>
>>> Wonko
>>>
>>>
>>
>> I don't use su. When I open the Konsole, it asks for a password.
>
> Does that mean you are not using the standard konsole, rather a special
> icon intended to open a root terminal?  Must be, otherwise it wouldn't
> ask for the root password.
>
> Try opening a standard user konsole and just use su instead.  (Or even,
> heaven forbid, an xterm instead of konsole.)  That should detect a KDE
> problem if it exists.
>

The way I did was this.  The entry you have but I edited it to run as 
root when it is clicked on.  I have a couple things that are set that 
way.  Kbackup is set that way.  It can't access some files I want to 
backup if it is set to run as a user.  You can edit this by clicking the 
advanced tab in the menu editor.  I also have konqueror set as my file 
manager and it is set to run as root.  It is running on another desktop 
right now.  It works fine.  I can run Kbackup, as root, and it connects 
just fine.  I just tried it to make sure.  Since I can go to my /root 
directory, I know it is running as root.

Weird things always happen to me.  Why can't something weird like 
winning the lottery happen to me?  lol

Dale

:-)  :-)

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

Dale wrote:
> walt wrote:
>> On 04/26/2010 03:11 PM, Dale wrote:
>>> Alex Schuster wrote:
>>>> Dale writes:
>>>>
>>>>> Again, I am using Konsole for this. This may be a KDE thing. I know
>>>>> it worked fine in KDE3 but then again, a LOT of things worked fine in
>>>>> KDE3.
>>>> It's probably not a KDE thing. I'm also using konsole in KDE4, and 
>>>> after
>>>> becoming root (via su or su -) I have no Problems starting X 
>>>> applications.
>>>>
>>>> I'm no expert at X authorization stuff. But I know that in the past 
>>>> I also
>>>> had trouble when becoming root. Why it works for me and not for you 
>>>> - I
>>>> don't know.
>>>>
>>>> Workarounds you might try:
>>>> - Emerge sux, and use sux instead of su. Worked for me in the past.
>>>> - ssh -Y root@localhost
>>>>
>>>> Wonko
>>>>
>>>>
>>>
>>> I don't use su. When I open the Konsole, it asks for a password.
>>
>> Does that mean you are not using the standard konsole, rather a special
>> icon intended to open a root terminal?  Must be, otherwise it wouldn't
>> ask for the root password.
>>
>> Try opening a standard user konsole and just use su instead.  (Or even,
>> heaven forbid, an xterm instead of konsole.)  That should detect a KDE
>> problem if it exists.
>>
>
> The way I did was this.  The entry you have but I edited it to run as 
> root when it is clicked on.  I have a couple things that are set that 
> way.  Kbackup is set that way.  It can't access some files I want to 
> backup if it is set to run as a user.  You can edit this by clicking 
> the advanced tab in the menu editor.  I also have konqueror set as my 
> file manager and it is set to run as root.  It is running on another 
> desktop right now.  It works fine.  I can run Kbackup, as root, and it 
> connects just fine.  I just tried it to make sure.  Since I can go to 
> my /root directory, I know it is running as root.
>
> Weird things always happen to me.  Why can't something weird like 
> winning the lottery happen to me?  lol
>
> Dale
>
> :-)  :-)
>

OK.  I finally fixed this so that it works.  Naturally it was simple but 
I wanted to share.  ;-)   Edit the menu item for konsole and on the line 
where it says command, enter this:  "konsole --profile root"  Remove the 
quotes of course.  That is part one.  Part two, open a console and 
create a new profile named root.  If you name it something else, edit 
the line above to match.  Then in the General tab in the box command, 
type in "/bin/su -".  Remove the quotes of course.  Save everything.

Then when you click on it in the future, it will open as a user BUT it 
asks for the root password.  Then you can run programs and it find the 
GUI.  This has worked with kwrite and elogviewer so far.

Yea, this was driving me nuts.  I knew this could work but had to figure 
out how to make it work.  The command to run was my light bulb moment.

Dale

:-)  :-)

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

On Mon, 26 Apr 2010 16:46:57 -0500, Dale wrote:

> Well, I deleted them all, logged out of KDE and back in.  I still get 
> the same thing as before with hp-setup.
> 
> Again, I am using Konsole for this.  This may be a KDE thing.  I know
> it worked fine in KDE3 but then again, a LOT of things worked fine in
> KDE3.

Are you using su, sudo or sux?


-- 
Neil Bothwick

I'm writing a book. I've got the page numbers done.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

Neil Bothwick wrote:
> On Mon, 26 Apr 2010 16:46:57 -0500, Dale wrote:
>
>    
>> Well, I deleted them all, logged out of KDE and back in.  I still get
>> the same thing as before with hp-setup.
>>
>> Again, I am using Konsole for this.  This may be a KDE thing.  I know
>> it worked fine in KDE3 but then again, a LOT of things worked fine in
>> KDE3.
>>      
> Are you using su, sudo or sux?
>
>    

I am using none of the above.  I say "I" because the menu system for KDE 
may be using one of those.  The KDE menu thingy has a entry that says 
Konsole.  I edited the settings for it to run as root.  When I click on 
the entry for it to run, a window pops up and asks for the root 
password.  When I enter it, konsole opens as root.

Now that I think about it, it used to open a Konsole window,ask for the 
password and go to a root prompt.  That was in KDE3.  No pop up window 
in KDE3.  KDE4 has a little pop up window THEN the Konsole opens up as root.

That is different so maybe I need to set something different for it to 
start up and be able to connect to the GUI.  I unmerged KDE3 so I can't 
go look and see how it was set up.

Dale

:-)  :-)

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Alan McKinnon]

On Monday 26 April 2010 19:59:26 Dale wrote:
> walt wrote:
> > On 04/25/2010 09:25 PM, Dale wrote:
> >> Hi folks,
> >> 
> >> I have had elogv and elogviewer installed for a while. I only use it
> >> on occasion but when I tried to use it the other day I get this
> >> little error message:
> >> 
> >> root@smoker / # elogviewer
> >> No protocol specified
> >> /usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57:
> >> GtkWarning: could not open display
> > 
> > Do you have the DISPLAY variable set properly in root's environment?
> 
> Apparently something got changed with a update.  I tried to run hp-setup
> a bit ago and it failed too.  It gave this error:
> 
> No protocol specified
> hp-setup: cannot connect to X server :0.0
> 
> I'm running this in a Konsole, part of KDE, so just where would I set
> this up?  I don't usually have to mess with it and it "just works".  I'm
> on KDE 4.4.2.  Maybe this is a "feature" of KDE4 until it gets
> "fixed".   ;-)

The X server is running at Dale and you are trying to connect to it as root.

It (correctly) disapproves of this and is telling you so, while still 
remaining polite.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Peter Humphrey]

On Monday 26 April 2010 18:59:26 Dale wrote:

> Apparently something got changed with a update.  I tried to run
> hp-setup a bit ago and it failed too.  It gave this error:
> 
> No protocol specified
> hp-setup: cannot connect to X server :0.0
> 
> I'm running this in a Konsole, part of KDE, so just where would I set
> this up?  I don't usually have to mess with it and it "just works". 
> I'm on KDE 4.4.2.  Maybe this is a "feature" of KDE4 until it gets
> "fixed".   ;-)

I run hp-setup at a virtual console, no X running. Have you tried that?

-- 
Rgds
Peter.

Re: [gentoo-user] Re: elogviewer and something odd with equery

[Dale]

Peter Humphrey wrote:
> On Monday 26 April 2010 18:59:26 Dale wrote:
>
>    
>> Apparently something got changed with a update.  I tried to run
>> hp-setup a bit ago and it failed too.  It gave this error:
>>
>> No protocol specified
>> hp-setup: cannot connect to X server :0.0
>>
>> I'm running this in a Konsole, part of KDE, so just where would I set
>> this up?  I don't usually have to mess with it and it "just works".
>> I'm on KDE 4.4.2.  Maybe this is a "feature" of KDE4 until it gets
>> "fixed".   ;-)
>>      
> I run hp-setup at a virtual console, no X running. Have you tried that?
>
>    

I haven't but I guess I could.  Things is, there is more than just 
hp-setup that needs to be run from time to time.

I did open a Konsole as user then su to root.  That worked fine.  I 
could run elogviewer too.  Now to just figure out a way to get the other 
to work the way it used to.

I hope I don't have to install KDE3 and figure out how it was set up to 
work.

Dale

:-)  :-)