Package: mate-dialogs
Version: 1.8.0+dfsg1-2
Severity: important
Dear Maintainer,
Upgrading from MATE 1.6 to 1.8, mate-dialogs package fails to tell that it
replaces/provides zenity and so does not install any alternative using
/usr/bin/matedialog.
I manually added this alternative group/entry o
There is a partial workaround for the case of a noexec /tmp or /var/tmp
that I found in the mkinitramfs manpage and used to circumvent this
problem: using/adding TMPDIR in /etc/initramfs-tools/initramfs.conf and
make it point to an "exec" dir.
Unfortunately, this tip is not repeated where it belo
Hi Henrique,
I found where does the problem come from. My /tmp is mounted with
"noexec" option since ages. If I remount it with "exec" before running
"update-initramfs -u", there is no error and then the next reboot is
ok. I had a similar problem a few weeks ago with the new flashplayer
updater sc
Meanwhile I tried something else: I kept the "intel-microde" and
"iucode-tool" packages installed but used the previous microcode-free
kernel instead of the one generated after installing the above
packages. However, I added "microcode" to "/etc/modules" in order to
force module loading. When I boo
Hi Henrique,
2012/9/29 Henrique de Moraes Holschuh :
> On Fri, 28 Sep 2012, Lionel Gamay wrote:
>> I followed you advice but I still get a similar error message, without
>> any reference to udev:
>>
>> "Loading, please wait...
>> /init: eval: line 1: arra
Hi Henrique,
I followed you advice but I still get a similar error message, without
any reference to udev:
"Loading, please wait...
/init: eval: line 1: array_intel_microcode=: not found
/init: eval: line 1: array_intel_microcode=: not found
PANIC: Circular dependancy. Exiting."
Then I am droppe
Hi Henrique,
It is quite weird to get this error on two different machines using
different architectures and even while trying two different kernels on
these two machines. Then four different configurations lead to this
message. BTW, you are right: it is "array..." and not "Array..." in
the error
Sorry, typo error: it occurs when installing 1.20120606.6 coming from
0.20120606-1.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: intel-microcode
Version: 0.20120606-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I tried to upgrade from 1.20120606.1 on my i386 netbook and my current x64
machine, with either 3.2 or 3.5-trunk kernels on each PC. On reboot I always
get the following error m
Should "--disable-x509" be run only with the version 0.9.2 from
experimental ? I didn't think so.
However, this option works and does solve the problem. Then deleting
~/.gnupg is not necessary.
Regards,
Lionel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subjec
Trying to run "gpa --disable-x509" issues an error in either 0.7.x or
0.9.0 versions:
v 0.7.x: gpa: unrecognized option '--disable-x509'
v 0.9.0: option parsing failed: Option inconnue --disable-x509
Either version was purged and reinstalled multiple times.
Regards,
Lionel
--
To UNSUBSCRIBE
The problem was not solved with this experimental version :(
However the hack given above does work: I removed "com-certs.pem",
made a backup of my keys,
deleted my ~/.gnupg, reimported the keys and everything works again
with the current 0.9.0-2.
I then tested with the version from experimental
I had this error displayed in three existing profiles on this machine,
even with no gpg key stored in one of these profiles. So I created a
fresh new profile as you suggested. The result are:
- there is not any problem with any of the reimported keys in the new profile
- in the new profile, there
Package: gpa
Version: 0.9.0-2
Followup-For: Bug #634930
Dear Maintainer,
I was hoping to really have this bug solved but I upgraded from a working
0.7.0-1.1 old version this 0.9.0-2 and still get the "General Assuan Error"
that was first described here.
Of course, as usual, reverting once again
Package: seahorse-daemon
Version: 3.2.2-1
Severity: normal
Dear Maintainer,
the seahorse-daemon.desktop shortcut is missing in /usr/share/gnome/autostart
and hence must be built manually in order to launch the daemon during a gnome-
session start.
thanks
-- System Information:
Debian Release:
15 matches
Mail list logo
