Re: oh no something is definitly wrong adieu debian.
On 8/30/13, Phi Debian <phi.debian@gmail.com> wrote:
> On Fri, Aug 30, 2013 at 8:34 AM, Zenaan Harkness <zen@freedbms.net> wrote:
>> If you have any cycles, I, and I am sure others, will be pleased to
>> assist with a little debugging, like using "strace" tool for example.
>>
>> You see, in your case, the bug seems very reproducible - every time
>> you can repeat it from what I understand. So if you have even a few
>> cycles, and you can keep a wheezy partition installed for a little
>> tests here and there, this might be very good for wheezy. and gnome I
>> guess..
>
> Ok I'll do that I will re-install wheezy on a spare part (or in this
> case probaly a tiny server I have)
>
> But frankly I don't even know what process to monitor
What is the program or package you install for vnc, and what do you
click on or run to run it?
STEP 1: find out how to run your vncserver desktop session:
Then we figure out how to run your vnc server session command from a shell. Eg:
vncserver :55 -geometry 1024x768 -localhost -depth 24
For the vncserver to work properly, ie to create a normal desktop
session, you might need to edit ~/.vnc/xstartup to have something like
the following 2 lines:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
alternatively, something like the following in ~/.vnc/xstartup
xsetroot -solid -gray
vncconfig -iconic &
xterm &
x-window-manager &
alternatively:
gnome-session
or (not sure if the following works sorry):
ck-launch-session gnome-session
STEP 1a:
Test running your vncserver from a shell, and connecting to it to
check, until you get it looking right, like your normal (gnome)
desktop.
If ~/.vnc/xstartup just starts a xterm, then try running gnome-session
(or ck-launch-session gnome-session) from the xterm inside vnc
desktop.
STEP 2: run your vncserver:
Then, for example, run the vncserver using strace, from a terminal of
course. Eg kill any test vncserver you have running on the server, and
now run a vncserver using strace logging (all one line):
strace -fo phi.log vncserver :55 -geometry 1024x768 -localhost -depth 24
STEP 3: produce the bug:
vncclient/rdp into your server vnc desktop session and kill it.
After that, you should have a file phi.log, which has lots of file
opens etc, and should show at the end, an idea of what happened just
before the crash.
I don't know who this could be sent to. If there is a bugs.debian.org
bug for your bug, then perhaps attach your strace log file to that bug
report, so that a developer could look at it. That's what I would do.
Reply to: