Bug 391157 - virt-manager won't start after su
Summary: virt-manager won't start after su
Status: RESOLVED DUPLICATE of bug 398932
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Xen (show other bugs)
Version: Beta 3
Hardware: x86-64 openSUSE 11.0
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: James Fehlig
QA Contact: Jason Douglas
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-16 06:31 UTC by Anders Johansson
Modified: 2009-05-29 16:16 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Johansson 2008-05-16 06:31:22 UTC 
11.0 beta 3 with kde4 as desktop

virt-manager doesn't show an warning if you try to start it as non-root, I think it used to say something like "must be run as root", but now it just crashes with an obscure error message about not being able to open /tmp/livirt_sock

If you su to root with "su", virt-manager just crashes. You have to use "su -" to reset the environment. There is something in the user environment that is kept by su without the - that causes it to fail. This also causes it to fail when started from YaST, unless you start yast2 from the command line after "su -"
Comment 1 Anders Johansson 2008-05-16 06:34:00 UTC 
Clarification: when started from yast (without "su -"), virt-manager never comes up at all.

When virt-manager is started from the command line (without "su -"), it starts but comes up as "disconnected", and when you try to connect it crashes with a SIGFPE

If it's started after "su -" everything works
Comment 2 Anders Johansson 2008-05-16 06:38:15 UTC 
btw, this is a fresh install with a newly created user, so there are no kept settings from 10.3 and no customisations from me
Comment 3 Anders Johansson 2008-05-16 06:40:34 UTC 
The same thing happens from xfce, so I don't think it's kde4 specific
Comment 4 Anders Johansson 2008-05-16 06:50:09 UTC 
It's in libvirtd

#0  0x00007fe9a91cf5ac in xenDaemonNodeGetInfo (conn=<value optimized out>,
    info=0x7fffbd9bfcb0) at xend_internal.c:1917
1917            info->sockets = nr_cpus / (info->nodes * info->cores * info->threads);

info->threads here is 0, so it's a division by zero

I don't understand why it doesn't happen after "su -" though
Comment 6 James Fehlig 2009-05-29 16:16:18 UTC 
This bug appears to be a duplicate of bug#398932.  It was fixed long ago.

*** This bug has been marked as a duplicate of bug 398932 ***