Mailinglist Archive: opensuse-bugs (7806 mails)

< Previous Next >
[Bug 239608] CD for Monitor Information not readable when configuring monitor with Yast2
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 23 Feb 2007 07:43:05 -0700 (MST)
  • Message-id: <20070223144305.129C425C887@xxxxxxxxxxxxxxxxxxxxxx>

rm@xxxxxxxxxx changed:

What |Removed |Added
Info Provider|rm@xxxxxxxxxx |

------- Comment #12 from rm@xxxxxxxxxx 2007-02-23 07:43 MST -------
did some more tests (including the debugging). The first result is that getINF
behaves erratically, not really predictable.
If you repeat the following steps several times you sometimes get an error
message and sometimes not.
Step 1: Open DVD device tray and insert CD without closing the tray.
Step 2: Start getINF -> tray is drawn inwards by DVD device - KDE demon
detects device - KDE window opens that offers to show CD contents with
konqueror - answer positively
(In the background getINF may produce an error message or sometimes not)
Step 3: Close konquerer window (which displays the CD contents correctly)
Step 4: umount /dev/hda
Step 5: open DVD device tray again and start the whole process again.

Sometimes getINF produces an error message at Step 2, sometimes not. I tested
this with 2 different DVD drives (/dev/hda - an LG drive; /dev/hdb - a Pioneer
drive). Please see the files "erratic_behaviour_getINF_hdx.txt" for this
erratic behaviour.
I repeated the tests with SUE 10.1 - this erratic behaviour does not appear

When you run getINF with the debugger you get two different situations which
correspond to the described scenarios with and without error message. See the
"getINF_error_case_debug.txt" for a situation wih error message. The file
"getINF_no_error_msg_debug.txt" contains the debug results for a situation in
which getINF just stops without error message.

I thin that the erratic behaviour is strange already. Nevertheless I hope that
the results in "getINF_error_case_debug.txt" help to analyze the bug.

Kind regards

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >