>I somehow resist the possibility of making my system unstable again,
>since everything else works fine with Testing and upgrading to 2.18.3
>didn't help. Additionally, I noticed no hint showing that this
>problem was solved with never versions.

Some search work at http://bugzilla.gnome.org shows no similar report, and as it is unreproducible anywhere, there's no reason for the upstream or Debian maintainer to address such bug, which doesn't prevent the possibility for the bug's silent disappearance either. Moreover, there's no difficulty to downgrade back to 2.14.5 if something still goes wrong. Finally, as the only one encountering this bug, only you can tell whether 2.18.5 is ok. So why not give it a shot? :)

P.S.: No offense, but I really doubt such a problem is necessary to be set as grave severity.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to