On 21/05/2016 22:31, Reiner Herrmann wrote:
> Hi Guy,
>
> Did you already have the possibility to check if firejail works again
> without the workaround?
>
> Kind regards,
> Reiner
>
Hi Reiner,
Apologies for my tardy response!
Yes - it worked without requiring to apply the workaround, once t
On 04/05/2016 18:28, Reiner Herrmann wrote:
>> https://github.com/netblue30/firejail/issues/494
> I also assume that you ran into this libselinux1 regression.
> Can you please recheck with libselinux1 2.5-1 (when it lands in testing)
> and tell me if it solved your problem?
>
> Kind regards,
>
https://github.com/netblue30/firejail/issues/494
"A recent libselinux1 update (2.5-1) introduces a bug where it attempts
to re-mount /proc directory."
This issue is closed on the Github site so hopefully will shortly filter
down into testing.
--
Guy
signature.asc
Description: OpenPGP digital
Subject: firejail no longer allows some programs to run
Package: firejail
Version: 0.9.38-1
Severity: important
Dear Maintainer,
Firejail no longer allows certain programs to run in the sandbox e.g.
iceweasel (and other programs based on firefox e.g. tor browser,
icedove), and java programs. It s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Hans, that someone was me :-)
Same issue with PXE booting for the AMD64 architecture.
A few more details for noobs:
Assuming you have a running install of Jessie for the architecture you
wish to boot up via TFTP, check the version:
$ dpkg -l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gnunet
Version: 0.10.1-2.1
Severity: important
Dear Maintainer,
Line 26 in /var/lib/dpkg/info/gnunet.postinst fails and leaves the
package unconfigured by dpkg, on armhf.
eval $(grep GNUNET_HOME /etc/gnunet.conf | tr -d [:blank:])
It appear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: udftools
Version: 1.0.0b3-14.3
Severity: wishlist
Dear Maintainer,
Given that most current popular OSs now support reading from / writing
to UDF formatted storage, UDF makes a useful OS agnostic, standardised
filesystem for use in heterogeno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sven,
This problem appears to been fixed in the latest kernel image to hit
testing:
ii linux-image-3.9-1-amd643.9.8-1
amd64Linux 3.9 for 64-bit PCs
I hope I'm not speaking too soon! Fingers crossed!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have raised this issue as a bug on freedesktop.org
The bug number is 63048
https://bugs.freedesktop.org/show_bug.cgi?id=63048
Cheers!
- --
Guy
On 19/03/13 19:39, Sven Joachim wrote:
> On 2013-03-18 22:44 +0100, Guy Heatley wrote:
>
>&
9:39, Sven Joachim wrote:
> On 2013-03-18 22:44 +0100, Guy Heatley wrote:
>
>> Sven - I can confirm that your downgrading suggestion fixes this
>> problem.
>>
>> On 18/03/13 17:03, Sven Joachim wrote:
>>> Kernel folks, this appears to be a regression resulti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven - I can confirm that your downgrading suggestion fixes this problem.
On 18/03/13 17:03, Sven Joachim wrote:
> Kernel folks, this appears to be a regression resulting from the
> DRM 3.4 backport.
>
> On 2013-03-18 02:05 +0100, Guy H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: eclipse
Version: 3.7.2-1
Severity: normal
- --- Please enter the report below this line. ---
The software I locally installed when using the previous version of
Eclipse seems to still be recognised by Eclipse - listed in the
"Installed Softw
IMP pretty much unusable for me!
Thanks for any help.
- --
Guy Heatley
- --- System information. ---
Architecture: amd64
Kernel: Linux 2.6.39-2-amd64
Debian Release: wheezy/sid
500 testing security.debian.org
500 testing ftp.uk.debian.org
- --- Package informati
IMP pretty much unusable for me!
Thanks for any help.
- --
Guy Heatley
- --- System information. ---
Architecture: amd64
Kernel: Linux 2.6.39-2-amd64
Debian Release: wheezy/sid
500 testing security.debian.org
500 testing ftp.uk.debian.org
- --- Package informati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just as a little bit of extra info:-
I think there is a problem with the reading of the EDID on the 2nd
graphics card output with the nouveau driver on this nVidia card.
I tried a much more modern monitor in the 2nd output and there was still
no read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/05/11 07:06, Sven Joachim wrote:
>> I had to add a modeline as the EEID is not detected properly on the 2nd
>> monitor (DVI-I-1)
>
> I think this is the reason for the flickering. Do you also see it if
> you connect only the DVI monitor?
>
Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-nouveau
Version: 1:0.0.16+git20110411+8378443-1+b1
Severity: normal
- --- Please enter the report below this line. ---
I use this nVidia graphics card (from "lspci -vnn"):
02:00.0 VGA compatible controller [0300]: nVidia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It was as simple as that!
Sound is now working on the Roland device using default drivers.
BUT ...
I had another go at compiling the source setting the env variable for root:
# export CC=/usr/bin/gcc-4.3 (Which exists!)
I ran
# m-a clean alsa-sourc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2010 18:06, Elimar Riesebieter wrote:
> You don't need the 1.0.23 drivers really. If you're using a Debian
> Kernel > 2.6.30 you should be fine.
Hi Elimar,
Yes - the only reason I embarked on this journey was because I thought
compiling the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Elimar,
I think the module assistant ought to check the versions of GCC that the
live kernel was built with, and compare it with the version available to
compile with on the running system, then give a warning if they differ.
Maybe I should raise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's your problem, right there!
r2d2:~# cat /proc/version
Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk)
(gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010
r2d2:~# gcc --version
gcc (Debian 4.4.4-6) 4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Elimar,
Heres what dmesg reports as I disconnect, then reconnect the Roland device.
All I can think is that the version of the compiler might be different
on my system, to that which compiled the kernel. I using an "off the
shelf" Debian AMD64 kern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Elimar,
There are problems with the insertion of the snd-usb-audio module.
I tried disconnecting and re-connecting my Roland device.
Dmesg correctly identified the device but then reported problems with
the snd-usb-audio module, as the module was
lsactl restore' failed with error message
'alsactl: load_state:1610: No soundcards found...'...done.
Hmm ... so far not fine! Rebooting doesn't get me off the hook either!
Thanks,
- --
Guy
On 07/07/10 23:11, Elimar Riesebieter wrote:
> * Guy Heatley [100707 22:46 +0100]:
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: alsa-source
Version: 1.0.23+dfsg-1
Severity: normal
- --- Please enter the report below this line. ---
After compiling alsa-source, installing modules and doing "alsa reload",
dmesg gives the following:
[30243.544731] snd_usb_lib: disagrees
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still a little confused about what to do here to get my usb UA-25EX
to appear!
(I reported a similar bug which has been merged with this one: Bug#587585)
I created a file /etc/modprobe.d/local.conf as described, and reloaded
the alsa modules, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The alsa unofficial wiki page on the device that is not being detected
http://alsa.opensrc.org/index.php/Edirol_UA-25EX
Also, I notice that all the current bug reports against the alsa-source
packages "Found in version alsa-driver/1.0.23+dfsg-1" (bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: alsa-source
Version: 1.0.23+dfsg-1
Severity: normal
- --- Please enter the report below this line. ---
After building the alsa source package using the module assistant, and
installing the resulting alsa drivers, my Roland UA-25EX external u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milan,
I can confirm that this fixed the problem!
It must have been that the partition in question was created with an old
version of cryptsetup.
Thanks to all involved in the bug fixing!
- --
Guy
On 16/06/10 12:19, Milan Broz wrote:
>
> If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/06/2010 12:19, Milan Broz wrote:
> On 06/16/2010 12:57 PM, Guy Heatley wrote:
>> On 16/06/2010 11:39, Milan Broz wrote:
>> I'm not sure this is true - this device had not been opened by
>> cryptsetup at this point:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/06/2010 11:39, Milan Broz wrote:
>
> Nope. You are mixing up two UUIDs:
>
> luksUUID is the UUID from LUKS header of underlying device (/dev/sdc1),
>
> ID_FS_UUID is UUID of fs on top of it (here labeled "/", it is device
> /dev/mapper/sdc1_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 23:01, Marco d'Itri wrote:
> And did udev create links to sdc1 in /dev/disk/ this time?
No :-(
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAY
ID_FS_SEC_TYPE=ext2
ID_FS_TYPE=ext3
r2d2:/home/guy# cryptsetup luksUUID /dev/sdc1
bf6cfa88-8f0c-4e07-ae24-84b25e7e7960
Hmmm... contradictory
On 15/06/10 13:20, Marco d'Itri wrote:
> On Jun 15, Guy Heatley wrote:
>
>>> Please report the output of: blkid -o udev /dev/sda6 .
>> Er
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 12:11, Marco d'Itri wrote:
> On Jun 15, Guy Heatley wrote:
>
>> If I run "cryptsetup luksUUID /dev/sdb1" I get the UUID of this partition.
>>
>> If I run "udevadm info --name=/dev/sdb1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 12:11, Marco d'Itri wrote:
> On Jun 15, Guy Heatley wrote:
>
>> If I run "cryptsetup luksUUID /dev/sdb1" I get the UUID of this partition.
>>
>> If I run "udevadm info --name=/dev/sdb1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: udev
Version: 157-1
Severity: normal
- --- Please enter the report below this line. ---
I have a harddrive with an encrypted luks partition. It usually appears
as /dev/sdb1 on my system.
I want to move to a persistent naming convention and
27;'open computing,''
the free exchange of digital information that has defined the
personal computer industry, is ending.'
New York Times, July 25, 2002
On 29/06/07, Guy Heatley <[EMAIL PROTECTED]> wrote:
Cool!
I'm at work right now, using the laptop in question,
Subject: xserver-xorg-video-i810: LCD won't turn off when docked on Dell laptop
Package: xserver-xorg-video-i810
Version: 2:2.0.0-1
Severity: normal
*** Please type your report below this line ***
I use a docking station for my laptop: a Dell Latitude D610.
Since a apt-get upgrade of the X serve
3.5.so
[EMAIL PROTECTED]:~$ ls -l /lib/tls/ld-2.3.5.so
-rwxr-xr-x 1 root root 96356 2005-11-13 01:23 /lib/tls/ld-2.3.5.so
--
Guy Heatley
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh lin
39 matches
Mail list logo
