Package: usrmerge
Version: 31
Severity: normal
During an "apt full-upgrade", the usrmerge package was installed for the first
time on my system. During package setup, it immediately fails with the
following message:
> Setting up usrmerge (31) ...
>
> FATAL ERROR:
> Both
to
uninstall xfce / thunar.
Any help appreciated :-)
cheers,
On Sun, 14 Jan 2018 12:15:48 +0100 Matthieu Imbert
<matthieu.imb...@inria.fr> wrote:
Here's a more detailed fix:
--
Matthieu
Here's a more detailed fix:
deleting ~/.config was not a very appealing fix for me since I don't
want to lost everything :-)
When double clicking a file in nautilus, it ends up calling "gio open".
stracing gio:
$ strace -f gio open 2>&1 | grep '\.config'
it shows that at some point an
On 10/10/2017 11:20 AM, Phil Wyett wrote:
On Tue, 2017-10-10 at 09:42 +0200, Matthieu Imbert wrote:
I confirm, same behavior for me since the upgrade nautilus:amd64
3.22.3-1 -> 3.25.92-1:
- not opening files when double clicking or when right clicking and
choosing the first entry &q
I confirm, same behavior for me since the upgrade nautilus:amd64
3.22.3-1 -> 3.25.92-1:
- not opening files when double clicking or when right clicking and
choosing the first entry "open with " (xxx being the default
application)
- workaround possible by right clicking, selecting "open with
This is probably because you hardcoded Gnome in Keyring configuration file,
however that backend was removed in Keyring 8.x (moved to keyrings.alt package).
The recommeneded alternative is to install python-secretstorage and let Keyring
use the default secretstorage-based backend instead (which
Package: python-keyring
Version: 8.5.1-1
Severity: serious
Hi,
python-keyring is broken, at least on my system
$ python
>>> import keyring
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/keyring/__init__.py", line 6, in
from .core import
.
Note also that I used to look at verbose logs in the same manner before
the upgrade to version 3.8.3-1, and I never had this issue.
--
Matthieu Imbert matthieu.imb...@ens-lyon.fr
http://graal.ens-lyon.fr/~mimbert/
INRIA research engineer / SED / GRAAL and RESO teams
http://www.inria.fr http
Package: gnome-terminal
Version: 3.8.3-1
Severity: normal
Normally gnome-terminal remembers the state of the Show Menubar option,
between invocations.
When run as root with gksu, it does not. Thus even if the user disables the
menubar, when he quits and relaunch gksu gnome-terminal the menubar
Package: gnome-terminal
Version: 3.8.3-1
Severity: normal
Since the upgrade to this version I noticed in certain situations
that the auto-srolling hangs.
This occured with a gnome-terminal configured with a huge
scrolling buffer (5 lines), a few tabs opened, and a program
generating a lot
Package: gnome
Version: 1:3.8+2
Severity: normal
Since the upgrade to gnome 3.8, the gnome panels do not adapt anymore to
screen resolution change.
It occurs when I unplug my laptop from its docking station and open its
integrated screen: the resolution changes from the resolution of my
same issue for me: gksu gnome-terminal only works once
If you try
# unset DBUS_SESSION_BUS_ADDRESS
# gksu gnome-terminal
does it run correctly?
no, it doesn't:
$ unset DBUS_SESSION_BUS_ADDRESS
$ gksu gnome-terminal
glibtop: Non-standard uts for running kernel:
release 3.9-1-amd64=3.9.0
Hi,
I have this problem with eclipse 3.5.2-11 and eclipse-cdt 6.0.2-1
cheers,
Matthieu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Same for me with 4 jabber accounts.
One thing worth noting: if i disable each account and then re-enable it,
then it connects correctly to each. If then i quit pidgin and start it
again, then again it does not connect and shows Waiting for network
connection.
cheers,
Matthieu
--
To
On 08/25/2010 05:18 AM, Andreas Beckmann wrote:
nvidia-graphics-drivers 195.36.31-2 entered unstable yesterday, kernel
2.6.32-5-* is available, too. Please test if the problem still exists
with
the new versions.
Andreas
Hi Andreas,
The issue is fixed with these versions of nvidia driver and
- On one of my systems, i was unable to reproduce the bug with
python-defaults 2.6.5-5 and python-sqlalchemy 0.6.2-1
- On another one of my systems, i had the bug with python-defaults
2.6.5-5 and python-sqlalchemy 0.6.2-1. Upgrading to python-defaults
2.6.5-10 fixed the exception
Hi,
I strongly agree with this wish, bm.el is a very convenient package.
Cheers,
Matthieu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I also had this bug but installing a package triggering install-info had the
side effect to restore the infodir and solve the problem.
At least, this is what i understand from the output of apt (especially the
line: install-info(ccmode): no file /usr/share/info/dir, retrieving backup file
Package: nvidia-kernel-source
Version: 185.18.14-2
Severity: normal
after upgrading nvidia-kernel-source (and nvidia-glx) from 180.29-1 to
185-18-14-2 (and upgrading at the same time from kernel 2.6.26-2 to
2.6.30-1), i get the following behaviour:
My (dell) laptop is plugged in a docking
Hi,
While it is fixed with emacs22, the bug is still there with emacs21.
regards,
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8,
Package: speedbar
Version: 1:1.0pre3-7
Severity: grave
File: /usr/share/emacs/site-lisp/speedbar/sb-info.el
since upgrading to emacs22, it is no longer possible to access the
info mode in emacs. When trying to execute the info command in
emacs, i get the following error message: Recursive
Package: xorg
Version: 1:7.2-3
Severity: normal
Having apt configured for 'testing', i upgraded today to the latest
xorg. After this upgrade, xorg was unable to start with the nvidia
driver.
Going to /usr/lib/xorg/modules/drivers and issuing: 'gcc gcc -shared
nvidia_drv.o -o nvidia_drv.so'
Package: mozilla
Version: 2:1.7.8-1sarge7.1
Since upgrading my system to this security update, the Opening file
dialog does not close anymore when a file has finished downloading and
is viewed in an external application. This seems to happen only when the
file is in the cache.
Example of
23 matches
Mail list logo
