Bug#888199: Fwd: Bug#888199: gnome-shell crashes at different circumstances (not usable anymore)

2018-01-28 Thread Thomas Renard
Oups, no Cc: to the bug list... Weitergeleitete Nachricht Betreff: Re: Bug#888199: gnome-shell crashes at different circumstances (not usable anymore) Datum: Sat, 27 Jan 2018 20:19:13 +0100 Von: Thomas Renard <cybae...@web.de> An: Simon McVittie <s...@debian.o

Bug#888199: To severity normal

2018-01-24 Thread Thomas Renard
Control: severity -1 normal more stable without notifications

Bug#888199: gnome-shell crashes at different circumstances (not usable anymore)

2018-01-23 Thread Thomas Renard
Package: gnome-shell Version: 3.26.2-4 Severity: grave Justification: renders package unusable Dear Maintainer, (it began with 3.26.2-3 with today's apt-upgrade before 3.26.2-4 but intel-microcode?? it crashes way more often) For me actual gnome shell crashes - seconds after establishing my

Bug#838047: Confirmed: breaks *all* tablets

2016-09-19 Thread Thomas Renard
Very grave: it breaks Lenovo Yoga Laptops because they have a buildin wacom display! Fortunately Wayland can be used as fallback...

Bug#814316: New Flash player is available -- fixes a security issue

2016-04-09 Thread Thomas Renard
... again: sudo update-flashplugin-nonfree --status 1 Flash Player version installed on this system : 11.2.202.577 Flash Player version available on upstream site: 11.2.202.616 flash-mozilla.so - auto mode link best version is

Bug#809526: network-manager-openvpn: Fail to set IPv4 route

2016-01-06 Thread Thomas Renard
Patch http://cgit.freedesktop.org/NetworkManager/NetworkManager/diff/?id=11aa07ed939193e85516c287a57dee1837242972=a232f885c233dbe4f2489c7a9691bd0b8c9816c5 from upstream bug report (fixed) https://bugzilla.gnome.org/show_bug.cgi?id=759892 works for me.

Bug#751952: linux-image-3.14-1-amd64: 3.14.7-1 crashes on startup on NUC DN2820

2014-06-18 Thread Thomas Renard
Package: src:linux Version: 3.14.4-1 Severity: critical Justification: breaks the whole system Dear Maintainer, after upgrading from 3.14.5-1 to 3.14.7-1 the system crashes directly after the message Uncompressing linux image... Booting into single user mode let the system hang on different

Bug#666468: xorg-server: major text display problems in several apps

2012-06-15 Thread Thomas Renard
With the following packages the bug disappears: ii xserver-xorg-video-nouveau 1:0.0.16+git20120529+ace77b6-1 ii linux-image-3.4-trunk-amd643.4.1-1~experimental.1 Unfortunately these packages are both experimental and I am not able to test the video driver with a stock 3.2 kernel right

Bug#523187: [Pkg-utopia-maintainers] Bug#523187: Same issue for me

2009-04-09 Thread Thomas Renard
Looks like a splashy related problem Thomas, do you also have splashy installed, ie. do you have a file /etc/lsb-base-logging.sh ? I have :-( So, then I tried your trick with renaming lsb-base-loging.sh and then the update works with no problem. Looks like uninstalling splashy for now...

Bug#425390: icedove: Cannot create a new setup on a blank account

2007-05-22 Thread Thomas Renard
Package: icedove Version: 2.0.0.0-3 Followup-For: Bug #425390 I am not able to create a new profile with a new user account with 2.0.0.0-3. The normal behavior on first startup of icedove would be: - (Dialog) ask for importing other setups - (Dialog, if no setup) create new profile dialog -

Bug#400720: mozilla-plugin-vlc: vlc plugin broken: (no video)

2006-12-12 Thread Thomas Renard
So you can check if it works with a build from nightlies.videolan.org or give us dome url which use to work and not longer does so i can check. I tried vlc/vlc-nox/mozilla-plugin-vlc _0.9.0-svn20061212-0-0 and it works for me. Regards, Thomas

Bug#363448: tightvncserver: Old paths in Xvnc again

2006-04-26 Thread Thomas Renard
Package: tightvncserver Version: 1.2.9-12 Followup-For: Bug #363448 I tried to startup Xvnc via gdm yesterday and it ended up with (/var/log/gdm/:10.log): -snip 27/04/06 10:57:01 Listening for VNC connections on TCP port 5910 Fatal server error: could not open default font 'fixed' -snip after