Bug#742282: Re: btrfs-tools: receive fails if btrfs is mounted with a non-root default subvolume
On 25/04/16 21:53, Nicholas D Steeves wrote: Followup-For: Bug #742282 Hi Giorgos, Does your script trigger this behaviour with btrfs-tools-3.17-1.1? If it doesn't, great! If it does, please read on. Hi Nicholas! The behaviour has changed. I don't get anymore the "ERROR: open def/subvROsnap1 failed. No such file or directory" but the following: It seems that you have changed your default subvolume or you specify other subvolume to mount btrfs, try to remount this btrfs filesystem with fs tree, and run btrfs receive again! #1: There are known issues with btrfs send|receive when operating on volumes mounted with the default subvolume (subvolid=5); This is what happens with a simple mkfs.btrfs /dev/sdX && mount /dev/sdX /mnt/1. The following instructions exists primarily to gather the negative results necessary to confirm this. If it works, you will have succeeded in providing data that disproves commonly held btrfs lore. #2 and #3 are also possible causes. #2: If you still get "no such file or directory," it may be that that you've encountered one of the "timing issues" in btrfs. There are fewer and fewer of these with every release, but I still keep a couple of "work around the timing issues" lines in my backup scripts. For the record, my scripts don't use btrfs send|receive, and I had timing issues which hung subvolume management until the system was rebooted. I've also read about some nasty interactions between the loop subsystem and btrfs...it might be worth increasing the sleep times even more, in case transactions are stalling somewhere in the loop. It would be appreciated if you could find a small usb flash drive to test this, to eliminate the loop subsystem as a contributing factor. #3: I've read that another data needs to be committed to the disk before a snapshot actually exists. This would also explain why you received a "no such file or directory" error. Arguably, this is part of the #2 group of issues, but I've broken it out into it's own point because #2 is a huge and complicated category of issues. #3 can be eliminated simply by making sure that the data is physically on the disk (eg: sync the FS to get it into a consistent state, then sync to disk). Could you please try replacing the btrfs sub section and the btrfs send section with the following: btrfs sub create mnt/1/subv sleep 3 date > mnt/1/subv/fileA btrfs fi sync /mnt/1 sleep 3 sync sleep 3 btrfs sub snap -r mnt/1/subv mnt/1/subvROsnap1 date > mnt/1/subv/fileB btrfs fi sync /mnt/1 sleep 3 sync sleep 3 btrfs sub snap -r mnt/1/subv mnt/1/subvROsnap2 btrfs send mnt/1/subvROsnap1 | btrfs receive mnt/2 btrfs fi sync /mnt/1 sleep 3 sync sleep 3 btrfs send -p mnt/1/subvROsnap1 mnt/1/subvROsnap2 | btrfs receive mnt/2 ## This worked without any problems :-) (note that I fixed the typo '/mnt' which should be 'mnt') and also, if you have the time, please test this one too: btrfs sub create mnt/1/subv sleep 3 date > mnt/1/subv/fileA btrfs sub sync /mnt/1/subv sleep 3 sync sleep 3 btrfs sub snap -r mnt/1/subv mnt/1/subvROsnap1 date > mnt/1/subv/fileB btrfs sub sync /mnt/1 sleep 3 sync sleep 3 btrfs sub snap -r mnt/1/subv mnt/1/subvROsnap2 btrfs send mnt/1/subvROsnap1 | btrfs receive mnt/2 btrfs sub sync /mnt/1 sleep 3 sync sleep 3 btrfs send -p mnt/1/subvROsnap1 mnt/1/subvROsnap2 | btrfs receive mnt/2 Kind regards, Nicholas This also worked without any problems! (fixed same typo as before) Cheers, Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#820822: vlc consumes all RAM within seconds and system swaps and freezes
On 12/04/16 22:59, Sebastian Ramacher wrote: Control: tags -1 + moreinfo On 2016-04-12 22:36:30, Giorgos Pallas wrote: Package: src:vlc Version: 2.2.2-5+b2 Severity: important Dear Maintainer, Whatever video I will try to play, vlc consumes within seconds all 4GB of RAM and makes the system swap and eventually freeze, requiring a reboot. This started after upgrading to debian testing (vlc 2.2.2-5), and continues even after I upgraded vlc to unstable (vlc 2.2.2-5+b2). Below is vlc -vvv log: $ vlc -vvv dvgrab-078.dv Does it happen only with this file or any file? As I wrote above, it happens with all video files of various types and codecs. [7feca0001268] vdpau_display vout display debug: using back-end OpenGL/VAAPI/libswscale backend for VDPAU [7feca0001268] vdpau_display vout display debug: using RGBA format 2 [7feca0001268] vdpau_display vout display debug: using X11 window 0x0481 ... [7feca4000958] core video output warning: picture is too late to be displayed (missing 79 ms) [7feca4000958] core video output warning: picture is too late to be displayed (missing 39 ms) [7feca4000958] core video output warning: picture is too late to be displayed (missing 95 ms) [7feca4000958] core video output warning: picture is too late to be displayed (missing 56 ms) This reminds me of libvdpau-va-gl1 bugs. Is it any better if you remove libvdpau-va-gl1? Regards You got it! After removing that package, vlc would not freeze anymore. Regards, Giorgos Pallas smime.p7s Description: S/MIME Cryptographic Signature
Bug#812981: [Pkg-privacy-maintainers] Bug#812981: torbrowser-launcher: torbrowser cannot start possibly due to apparmor issue
On 28/01/16 13:46, Holger Levsen wrote: Hi, On Donnerstag, 28. Januar 2016, Γιώργος Πάλλας wrote: So, indeed, I disabled apparmor (aa-disable /etc/apparmor.d/*torbrowser*) and it worked. cool, thanks for confirming! But I see that #793142 has not been updated since July when it was filed. How could I help for solving this? by enabling apparmor again and fixing the broken rules which are located in /etc/apparmor/torbrowser* on your system. But I don't know how to fix the apparmor rules... In our private discussion you suggested that I build the package from sid, but I don't understand what has this to do with fixing the apparmor rules. well, in sid the apparmor rules are currently broken too: there, installation works, but upgrade not. This is fixed in git though and I'm pondering a new upload. Will there be a fix for the jessie package? G. cheers, Holger smime.p7s Description: S/MIME Cryptographic Signature
Bug#812981: [Pkg-privacy-maintainers] Bug#812981: torbrowser-launcher: torbrowser cannot start possibly due to apparmor issue
On 28/01/16 12:47, Holger Levsen wrote: forcemerge 793142 812981 user pkg-apparmor-t...@lists.alioth.debian.org usertags 793142 + buggy-profile tags 793142 + help thanks Hi Giorgos, On Donnerstag, 28. Januar 2016, Giorgos Pallas wrote: Package: torbrowser-launcher Version: 0.1.9-1+deb8u2 that's not the latest version but rather the latest version in stable… (refering to our previous private discussion…) Yes, because I meant the latest and fully updated version from whatever Debian suite I am using, which is Debian GNU/Linux 8.3 (jessie). and indeed a known bug, see: #793142 torbrowser-launcher: Broken AppArmor profile on Jessie So, indeed, I disabled apparmor (aa-disable /etc/apparmor.d/*torbrowser*) and it worked. But I see that #793142 has not been updated since July when it was filed. How could I help for solving this? In our private discussion you suggested that I build the package from sid, but I don't understand what has this to do with fixing the apparmor rules. G. Help to fix this would be much welcome. cheers, Holger smime.p7s Description: S/MIME Cryptographic Signature
Bug#768857: torbrowser-launcher (0.1.6-1): processes do not terminate on exit and tor browser cannot be reopened
On 25/01/16 20:27, Holger Levsen wrote: control: tags -1 + unreproducible Hi Giorgos, do you still see this bug with recent versions of torbrowser(-launcher)? I've not seen in it in a very long time and am tempted to close this bug report - what do you think? cheers, Holger Hi! Let me use it for a couple of days and I will get back to you. Thanks! Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#767117: ufw: default settings after install block all connectivity
On 20/02/15 23:31, Jamie Strandboge wrote: Thanks for the bug report. What is the output of: # /usr/share/ufw/check-requirements Hello, I send you the required output. In case you missed it, the problem was due to something that was solved after rebooting, as I mentioned on Tue, 28 Oct 2014 17:06:35 +0200. Thanks, Giorgos Has python: pass (binary: python2.7, version: 2.7.8, py2) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass state (NEW): pass state (RELATED): pass state (ESTABLISHED): pass state (INVALID): pass state (new, recent set): pass state (new, recent update): pass state (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): pass icmp (source-quench): pass icmp (time-exceeded): pass icmp (parameter-problem): pass icmp (echo-request): pass == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass state (NEW): pass state (RELATED): pass state (ESTABLISHED): pass state (INVALID): pass state (new, recent set): pass state (new, recent update): pass state (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass icmpv6 (destination-unreachable): pass icmpv6 (packet-too-big): pass icmpv6 (time-exceeded): pass icmpv6 (parameter-problem): pass icmpv6 (echo-request): pass icmpv6 with hl (neighbor-solicitation): pass icmpv6 with hl (neighbor-advertisement): pass icmpv6 with hl (router-solicitation): pass icmpv6 with hl (router-advertisement): pass ipv6 rt: pass All tests passed smime.p7s Description: S/MIME Cryptographic Signature
Bug#773609: virtualbox: freezes and reads disk forever with fresh install of a debian jessie VM
On 20/12/14 21:14, Ritesh Raj Sarraf wrote: On 12/21/2014 12:23 AM, Giorgos Pallas wrote: This is an issue on both 4.3.18 (current testing vb version) and 4.3.20 to which I upgraded. There is a problem with installing debian on a new VM. I downloaded jessie's small installer (debian-jessie-DI-b2-i386-netinst.iso) and installed debian. The install completed (I did a minimum install: just standard utilities and openssh-server selected at tasksel). The VM rebooted after completing the install and then without any command the VM froze and the disk reads without stopping. I let it over 20 minutes and it was still reading. During that time the VM console was frozen as well as the Virtualbox manager. I killed both and then tried to start the VM again: Both are frozen, showing the dialog box saying: starting virtual machine, and the disk reads without stop. I tried the whole procedure over 3 times: Everytime the same. I even tried to snapshot the machine during the new install. I took during the install several snapshots without problem, but after the dialog of setting up partitions etc I pressed the snap button and the VM as well as the VB manager froze, and the disk started reading without stopping. I don't think its a disk fault (I/O errors etc) because kernel would show something and in addition I tried reading the VM file (vdi) and it is read without problem. How much memory have you allocated to the Guest VM ? -- Ritesh Raj Sarraf |http://people.debian.org/~rrs Debian - The Universal Operating System It was 512 MB. I have previously run many times installed debian VMs with that much memory. Of course something may have changed lately, although I have checked of course with atop that the disk was not busy with swap I/O. G. smime.p7s Description: S/MIME Cryptographic Signature
Bug#768858: [Pkg-anonymity-tools] Bug#768858: torbrowser-launcher: html5 audio does not work
On 10/11/14 23:19, intrigeri wrote: Control: retitle -1 Please add (possibly opt-in) audio support to AppArmor profiles Control: severity -1 wishlist Control: tag -1 + upstream Γιώργος Πάλλας wrote (10 Nov 2014 20:54:41 GMT) : I also state that rebooting my system with apparmor = 0, the audio plays OK. So the problem is in the apparmor rules that were installed with torbrowser-launcher. Ah, OK, thanks for reporting back. That's on purpose, since it's not been evaluated yet how dangerous enabling audio support could be (both for security and for anonymity), and the relevant bits haven't been developed in the profile yet. You might give it a try to edit /etc/apparmor.d/torbrowser.Browser.firefox - look for sound hardware. Not sure it will be enough without also allowing the browser to run PulseAudio, though (and I guess it will need its own one, since it runs with a custom $HOME). Cheers! Cool, I followed your hint and I just uncommented the following line in the apparmor profile you mentioned. #include abstractions/audio Then a systemctl restart apparmor and htm5 audio fully working! Now about the bug, I don't know how it should be handled... Thanks again, Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#504917: network-manager-openvpn: cannot connect using method X509 certificates
Please close this bug. I opened it 7 years ago and since then it is resolved. smime.p7s Description: S/MIME Cryptographic Signature
Bug#768858: [Pkg-anonymity-tools] Bug#768858: torbrowser-launcher: html5 audio does not work
On 10/11/14 10:07, intrigeri wrote:
Control: tag -1 + moreinfo
Hi,
Giorgos Pallas wrote (09 Nov 2014 17:36:05 GMT) :
HTML5 audio does not work. Neither youtube, neither other sites for testing
html5 audio functionality. Video plays OK.
Do you have AppArmor enabled?
I also state that rebooting my system with apparmor = 0, the audio plays
OK. So the problem is in the apparmor rules that were installed with
torbrowser-launcher.
These are the logs appearing while the browser tries to play some html5
audio (with no success):
Nov 10 22:43:17 mordor kernel: [ 2342.267981] audit: type=1400
audit(1415652197.927:22): apparmor=DENIED operation=open
profile=/usr/bin/torbrowser-launcher
name=/home/gpall/.kde/share/config/gtkrc-2.0 pid=6004
comm=torbrowser-laun requested_mask=r denied_mask=r fsuid=1000
ouid=1000
Nov 10 22:43:33 mordor kernel: [ 2358.026992] audit: type=1400
audit(1415652213.687:23): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/etc/pulse/client.conf pid=6077 comm=4D6564696120417564696F
requested_mask=r denied_mask=r fsuid=1000 ouid=0
Nov 10 22:43:33 mordor kernel: [ 2358.029689] audit: type=1400
audit(1415652213.691:24): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/dev/shm/ pid=6077 comm=4D6564696120417564696F requested_mask=r
denied_mask=r fsuid=1000 ouid=0
Nov 10 22:43:33 mordor kernel: [ 2358.030107] audit: type=1400
audit(1415652213.691:25): apparmor=DENIED operation=mknod
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/dev/shm/pulse-shm-3574326807 pid=6077
comm=4D6564696120417564696F requested_mask=c denied_mask=c
fsuid=1000 ouid=1000
Nov 10 22:43:33 mordor kernel: [ 2358.030240] audit: type=1400
audit(1415652213.691:26): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/dev/shm/ pid=6077 comm=4D6564696120417564696F requested_mask=r
denied_mask=r fsuid=1000 ouid=0
Nov 10 22:43:33 mordor kernel: [ 2358.030683] audit: type=1400
audit(1415652213.691:27): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/run/user/1000/pulse/ pid=6077 comm=4D6564696120417564696F
requested_mask=r denied_mask=r fsuid=1000 ouid=1000
Nov 10 22:43:33 mordor kernel: [ 2358.030710] audit: type=1400
audit(1415652213.691:28): apparmor=DENIED operation=rmdir
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/run/user/1000/pulse/ pid=6077 comm=4D6564696120417564696F
requested_mask=d denied_mask=d fsuid=1000 ouid=1000
Nov 10 22:43:33 mordor kernel: [ 2358.039930] audit: type=1400
audit(1415652213.699:29): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/proc/6080/fd/ pid=6080 comm=4D6564696120417564696F
requested_mask=r denied_mask=r fsuid=1000 ouid=1000
Nov 10 22:43:33 mordor kernel: [ 2358.058800] audit: type=1400
audit(1415652213.719:30): apparmor=DENIED operation=exec
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/usr/bin/pulseaudio pid=6080 comm=4D6564696120417564696F
requested_mask=x denied_mask=x fsuid=1000 ouid=0
Nov 10 22:43:33 mordor kernel: [ 2358.069116] audit: type=1400
audit(1415652213.731:31): apparmor=DENIED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/usr/share/alsa/alsa.conf pid=6077 comm=4D6564696120417564696F
requested_mask=r denied_mask=r fsuid=1000 ouid=0
I then set torbrowser.Browser.firefox to complain mode and the audio
played fine, leaving those logs:
Nov 10 22:51:03 mordor kernel: [ 2807.451657] audit: type=1400
audit(1415652663.111:59): apparmor=DENIED operation=open
profile=/usr/bin/torbrowser-launcher
name=/home/gpall/.kde/share/config/gtkrc-2.0 pid=6389
comm=torbrowser-laun requested_mask=r denied_mask=r fsuid=1000
ouid=1000
Nov 10 22:51:15 mordor kernel: [ 2820.228224] audit: type=1400
audit(1415652675.891:60): apparmor=ALLOWED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/etc/pulse/client.conf pid=6462 comm=4D6564696120417564696F
requested_mask=r denied_mask=r fsuid=1000 ouid=0
Nov 10 22:51:15 mordor kernel: [ 2820.229899] audit: type=1400
audit(1415652675.891:61): apparmor=ALLOWED operation=open
profile=/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/firefox
name=/dev/shm/ pid=6462 comm=4D6564696120417564696F requested_mask=r
denied_mask=r fsuid=1000 ouid=0
Nov 10 22:51:15 mordor kernel: [ 2820.230106] audit: type=1400
audit(1415652675.891:62): apparmor=ALLOWED operation=open
Bug#767117: Acknowledgement (ufw: default settings after install block all connectivity)
I'm sorry about this bug report. Solved by rebooting. On 28/10/14 16:57, ow...@bugs.debian.org (Debian Bug Tracking System) wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Jamie Strandboge ja...@ubuntu.com If you wish to submit further information on this problem, please send it to 767...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. smime.p7s Description: S/MIME Cryptographic Signature
Bug#762067: wireshark crashes immediately
On 18/09/14 23:48, Bálint Réczey wrote: Hi, Control: reassign -1 libgdk-pixbuf2.0-0 2.30.8-1 Control: tags -1 moreinfo unreproducible Control: affects -1 wireshark 2014-09-18 7:25 GMT+02:00 Giorgos Pallas gp...@auth.gr: Package: wireshark Version: 1.12.0+git+4fab41a1-1+b1 Severity: important Dear Maintainer, When I start wireshark it gives the following messages and crashes: (wireshark:3095): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported ** ERROR:/build/wireshark-VQ_DcW/wireshark-1.12.0+git+4fab41a1/ui/gtk/stock_icons.c:401:stock_icons_init: assertion failed: (pixbuf) Aborted It does not seem to be a wireshark-specific problem. Please attach the output of /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders . I assume the XPM loader will be missing, but I could not reproduce the same problem with the same version on my system. Cheers, Balint Hello, I'm sending you the requested output: aris ~ $ /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders # GdkPixbuf Image Loader Modules file # Automatically generated file, do not edit # Created by gdk-pixbuf-query-loaders from gdk-pixbuf-2.30.8 # # LoaderDir = /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders # /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/io-wmf.so wmf 0 gdk-pixbuf Windows Metafile image/x-wmf wmf apm \327\315\306\232 100 \001 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so svg 6 gdk-pixbuf Scalable Vector Graphics LGPL image/svg+xml image/svg image/svg-xml image/vnd.adobe.svg+xml text/xml-svg image/svg+xml-compressed svg svgz svg.gz svg * 100 !DOCTYPE svg * 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-ras.so ras 4 gdk-pixbuf The Sun raster image format LGPL image/x-cmu-raster image/x-sun-raster ras Y\246j\225 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-tga.so tga 4 gdk-pixbuf The Targa image format LGPL image/x-tga tga targa \001\001 x 100 \001\t x 100 \002 xz 99 \003 xz 100 \n xz 100 \v xz 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so xpm 4 gdk-pixbuf The XPM image format LGPL image/x-xpixmap xpm /* XPM */ 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-ico.so ico 5 gdk-pixbuf The ICO image format LGPL image/x-icon image/x-ico image/x-win-bitmap ico cur \001zz znz 100 \002zz znz 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-bmp.so bmp 5 gdk-pixbuf The BMP image format LGPL image/bmp image/x-bmp image/x-MS-bmp bmp BM 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so jpeg 5 gdk-pixbuf The JPEG image format LGPL image/jpeg jpeg jpe jpg \377\330 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so gif 4 gdk-pixbuf The GIF image format LGPL image/gif gif GIF8 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-ani.so ani 4 gdk-pixbuf The ANI image format LGPL application/x-navi-animation ani RIFFACON 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-wbmp.so wbmp 4 gdk-pixbuf The WBMP image format LGPL image/vnd.wap.wbmp wbmp zz 1 ` z 1 @ z 1 z 1 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-pnm.so pnm 4 gdk-pixbuf The PNM/PBM/PGM/PPM image format family LGPL image/x-portable-anymap image/x-portable-bitmap image/x-portable-graymap image/x-portable-pixmap pnm pbm pgm ppm P1 100 P2 100 P3 100 P4 100 P5 100 P6 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-icns.so icns 4 gdk-pixbuf The ICNS image format GPL image/x-icns icns icns 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-pcx.so pcx 4 gdk-pixbuf The PCX image format LGPL image/x-pcx pcx \n \001 100 \n\002\001 100 \n\003\001 100 \n\004\001 100 \n\005\001 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-tiff.so tiff 5 gdk-pixbuf The TIFF image format LGPL image/tiff tiff tif MM * z 100 II* z 100 II* \020 CR\002 z zzz z 0 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jasper.so jpeg2000 4 gdk-pixbuf The JPEG 2000 image format LGPL image/jp2 image/jpeg2000 image/jpx jp2 jpc jpx j2k jpf jP 100 \377O\377Q 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-qtif.so qtif 4 gdk-pixbuf The QTIF image format LGPL image/x-quicktime image/qtif qtif qif abcdidsc 100 abcdidat 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so png 5 gdk-pixbuf The PNG image format LGPL image/png png \211PNG\r\n\032\n 100 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xbm.so xbm 4 gdk-pixbuf The XBM image format LGPL
Bug#762067: wireshark crashes immediately
On 19/09/14 15:49, Bálint Réczey wrote: From https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294 : ... This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... With a aptitude reinstall libgdk-pixbuf2.0-0 the problem was solved! Many thanks! Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#743264: it worked after saving the file elsewhere
After three failed attempts, where I must note that each time it hanged after having written in outDEL different volume of data, this time I retried it by saving the outDEL file on a different filesystem. And it worked. smime.p7s Description: S/MIME Cryptographic Signature
Bug#736227: linux-headers-3.12-1-amd64: general protection fault when using aptitude
In case this may help: Today the hard disk has reported unreadable sectors, so the issue reported could be related to some kind of emerging disk failure. Giorgos On 23/01/2014 07:47 πμ, Ben Hutchings wrote: I'm sending this on to the btrfs developers to see if they can help. On Tue, 2014-01-21 at 11:00 +0200, Giorgos Pallas wrote: [...] I just installed 3.12-amd64 stock kernel. It booted OK, I opened a konsole and just tried to installed the kernel headers. Just as aptitude tried to start downloading packages, I got: E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. and btrfs has crashed as seen in dmesg. It should be noted that I use btrfs without problems with 3.7-trunk-amd64 for almost a year. [...] The full message can be seen at http://bugs.debian.org/736227; here is the crash log: [ 322.368186] general protection fault: [#1] SMP [ 322.368233] Modules linked in: cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative xt_multiport uinput ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse ip6table_filter ip6table_mangle ip6_tables xt_tcpudp iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ip_tables x_tables ext4 crc16 mbcache jbd2 loop firewire_sbp2 uvcvideo arc4 videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media b43 joydev bcma snd_hda_codec_hdmi mac80211 cfg80211 snd_hda_codec_idt ir_lirc_codec rfkill snd_hda_intel snd_hda_codec rng_core iTCO_wdt snd_hwdep snd_pcm r852 lirc_dev iTCO_vendor_support ir_mce_kbd_decoder snd_page_alloc snd_seq ir_sony_decoder ir_sanyo_decoder dell_wmi ir_jvc_decoder sm_common nand ir_nec_decoder ir_rc6_decoder ir_rc5_decoder nand_ecc rc_rc6_mce nand_ids mtd lpc_ich i2c_i801 dell_laptop coretemp acpi_cpufreq snd_seq_device ! r592 snd_timer mfd_core sparse_keymap dcdbas psmouse snd ite_cir rc_core memstick soundcore processor pcspkr wmi serio_raw battery ac evdev btrfs xor raid6_pq crc32c libcrc32c sha256_generic cbc dm_crypt dm_mod sg sd_mod crct10dif_generic sr_mod crc_t10dif cdrom crct10dif_common firewire_ohci sdhci_pci sdhci firewire_core crc_itu_t thermal ahci libahci tg3 libata ssb mmc_core pcmcia i915 ptp pps_core libphy pcmcia_core video scsi_mod ehci_pci uhci_hcd ehci_hcd button i2c_algo_bit drm_kms_helper drm i2c_core thermal_sys usbcore usb_common [ 322.369458] CPU: 0 PID: 4353 Comm: http Not tainted 3.12-1-amd64 #1 Debian 3.12.6-2 [ 322.369493] Hardware name: Dell Inc. Studio 1737/0P792H, BIOS A09 04/14/2011 [ 322.369534] task: 880036e80840 ti: 88009bf7e000 task.ti: 88009bf7e000 [ 322.369569] RIP: 0010:[812713e2] [812713e2] memcpy+0x12/0x110 [ 322.369615] RSP: 0018:88009bf7f968 EFLAGS: 00010202 [ 322.369646] RAX: 88008e2eaf39 RBX: 0001 RCX: 0001 [ 322.369679] RDX: 0001 RSI: db738800 RDI: 88008e2eaf39 [ 322.369711] RBP: 880131ca9770 R08: 1000 R09: 88009bf7f978 [ 322.369744] R10: R11: R12: 6db6db6db6db6db7 [ 322.369776] R13: 1600 R14: 88008e2eaf3a R15: 0001 [ 322.369810] FS: 7f00804a4720() GS:88013fc0() knlGS: [ 322.369855] CS: 0010 DS: ES: CR0: 80050033 [ 322.369881] CR2: ff600400 CR3: 9d52b000 CR4: 07f0 [ 322.369914] Stack: [ 322.369928] a034a568 8801378a [ 322.369980] 88013b3a9250 88008e2ea000 8800aa637d50 8800925c3260 [ 322.370032] a032f510 1000 880131ca96a0 ea0001f1a330 [ 322.370085] Call Trace: [ 322.370119] [a034a568] ? read_extent_buffer+0xc8/0x120 [btrfs] [ 322.370164] [a032f510] ? btrfs_get_extent+0x910/0x990 [btrfs] [ 322.370214] [a03469b8] ? __do_readpage+0x398/0x780 [btrfs] [ 322.370256] [a032ec00] ? btrfs_real_readdir+0x550/0x550 [btrfs] [ 322.370307] [a0347142] ? __extent_readpages.constprop.43+0x2d2/0x2f0 [btrfs] [ 322.370355] [a032ec00] ? btrfs_real_readdir+0x550/0x550 [btrfs] [ 322.370406] [a0348de2] ? extent_readpages+0x182/0x190 [btrfs] [ 322.370457] [a032ec00] ? btrfs_real_readdir+0x550/0x550 [btrfs] [ 322.370499] [8115ba6b] ? kmem_getpages+0x15b/0x1a0 [ 322.370527] [811554ad] ? alloc_pages_current+0x9d/0x160 [ 322.370565] [8111dbc3] ? __do_page_cache_readahead+0x193/0x240 [ 322.370598] [8111e07a] ? ondemand_readahead+0x14a/0x280 [ 322.370636] [81113986] ? generic_file_aio_read+0x4a6/0x6f0 [ 322.370668] [81172a07] ? do_sync_read+0x57/0x90 [ 322.370701] [81172f94] ? vfs_read+0x94/0x160 [ 322.370726] [81173a83] ? SyS_read+0x43/0xa0 [ 322.370759] [81499b39] ?
Bug#680514: bugs have not been solved
These two bugs, 703276 and 680514 have still not been solved in wheezy and they are a great problem for a stable debian release... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680514: bugs have not been solved
On 07/05/2013 11:24 μμ, Julien Cristau wrote: On Tue, May 7, 2013 at 13:10:29 +0300, Γιώργος Πάλλας wrote: These two bugs, 703276 and 680514 have still not been solved in wheezy and they are a great problem for a stable debian release... Send patches? Cheers, Julien Can't code, but I'm doing my share helping debian with other ways. Anyway, I did not demand anything, but it strikes me odd that such problem which makes a desktop system pretty useless was not solved before releasing wheezy. George smime.p7s Description: S/MIME Cryptographic Signature
Bug#674258: btrfs bug?
Package: linux-image-3.2.0-2-amd64 Hello! I'm sending this bug report using a simple email because the reportbug tool always fails due to timeouts when used on the kernel (probably because there are many bugs). I'm using a fully updated squeeze with 3.2.0-2-amd64. I guess the whole thing happened due to a (temporary?) fail of the disk, but anyway btrfs dumped some things which you may find interesting. In your disposal for any additional data. Giorgos Pallas btrfsBug.txt.bz2 Description: Binary data
Bug#663067: meta-error
My email is gp...@ccf.auth.gr and not gp...@aris.ccf2.auth.gr that is shown due to a badly configured reportbug.conf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577054: acpi: After upgrade, computer does not turn off
On 02/10/2011 08:15 πμ, Jonathan Nieder wrote: Hi! Giorgos Pallas wrote: After the upgrade that happened around 2010-03-04 or 2010-03-22, the computer does not turn off after shutdown procedure. The disk spins down, the kernel says 'Power down' and I must push the box's turn off button for it to shutdown. Sorry for the long silence. The symptoms sound like ACPI support is being disabled for some reason indeed. Happy to provide more info as requested... Please attach: - dmesg output immediately after booting - output from /usr/share/bug/linux-image-$(uname -r)/script 31 which provides basic information about your hardware and how the kernel sees it. Any other observations since then would be helpful, too (whether newer kernels behave differently, other weird symptoms, which kernel used to work --- you can get the history of installed kernels from /var/log/dpkg.log* --- and so on). Thanks for reporting it, and sorry we missed this before. Hi! This goes so much time in the past that I don't remember anything about the case. Since then I followed the regular squeeze upgrades and the problem vanished at some point. So there is none of the data you requested available! Giorgos Pallas smime.p7s Description: S/MIME Cryptographic Signature
Bug#619170: /sbin/btrfs: crash after usb disconnect
On 30/03/2011 04:55 μμ, Cyril Brulebois wrote: reassign 619170 src:linux-2.6 2.6.32-31 thanks Hi, (just a random passer-by…) Giorgos Pallas gp...@ccf.auth.gr (21/03/2011): Package: btrfs-tools Version: 0.19+20100601-3 Severity: normal File: /sbin/btrfs I run btrfs on a USB disk and after an accidental disconnect of the USB cable, I got this: [109158.260743] usb 2-3: USB disconnect, address 3 [110181.902026] lost page write due to I/O error on dm-5 [110181.902092] lost page write due to I/O error on dm-5 [110181.905171] lost page write due to I/O error on dm-5 [110181.905182] btrfs: 1 errors while writing supers [110181.905228] [ cut here ] [110181.905231] kernel BUG at /build/buildd-linux-2.6_2.6.32-31-amd64-vrfdM4/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/btrfs/disk-io.c:2300! ^^ Looks like a kernel bug [:)], reassigning to the kernel package. You may want to run the linux-2.6 bug script and attach its output to this bug report: /usr/share/bug/linux-$yourpackage/script 3/tmp/kernel-bug.txt What do you mean linux-$yourpackage? smime.p7s Description: S/MIME Cryptographic Signature
Bug#567996: same thing here
I had it once, disappeared after some upgrade, and now have it again after some upgrade about 2 or 3 weeks ago. Running a fully upgraded squeeze system (2.6.32-5-amd64). In your disposal for any extra info needed... [ 54.858614] usb 2-4: new high speed USB device using ehci_hcd and address 4 [ 54.994460] usb 2-4: New USB device found, idVendor=1307, idProduct=0165 [ 54.994465] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.994468] usb 2-4: Product: USB Mass Storage Device [ 54.994471] usb 2-4: Manufacturer: USBest Technology [ 54.994473] usb 2-4: SerialNumber: 000383 [ 54.994610] usb 2-4: configuration #1 chosen from 1 choice [ 55.225262] Initializing USB Mass Storage driver... [ 55.225413] scsi6 : SCSI emulation for USB Mass Storage devices [ 55.225572] usbcore: registered new interface driver usb-storage [ 55.225576] USB Mass Storage support registered. [ 55.228926] usb-storage: device found at 4 [ 55.228930] usb-storage: waiting for device to settle before scanning [ 60.224267] usb-storage: device scan complete [ 60.225136] scsi 6:0:0:0: Direct-Access Ut165USB2FlashStorage 0.00 PQ: 0 ANSI: 2 [ 60.226811] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 60.227705] sd 6:0:0:0: [sdb] 7897088 512-byte logical blocks: (4.04 GB/3.76 GiB) [ 60.228453] sd 6:0:0:0: [sdb] Write Protect is off [ 60.228457] sd 6:0:0:0: [sdb] Mode Sense: 00 00 00 00 [ 60.228460] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 60.235210] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 60.235218] sdb: [ 60.510225] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 60.510231] sd 6:0:0:0: [sdb] Attached SCSI removable disk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524441: suspend to RAM stopped working with linux-image-2.6.26-2-686
On 07/10/2010 10:29 PM, Moritz Muehlenhoff wrote: tags 524441 moreinfo thanks On Sat, Feb 20, 2010 at 10:22:48AM +0100, Moritz Muehlenhoff wrote: On Fri, Apr 17, 2009 at 10:18:22AM +0300, Giorgos D. Pallas wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: normal After upgrading my debian testing from linux-image-2.6.26-1-686 to linux-image-2.6.26-2-686, suspend to RAM stopped working. It blacks the screen, it does not turn off, and is completely frozen. It needs hard restart... Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Did you test a more recent kernel? Cheers, Moritz Since I'm following debian testing's updates, I'm currently running 2.6.32-5-amd64 where suspend works fine. Greetings, Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#586286: [pkg-cryptsetup-devel] Bug#586286: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433
On 07/09/2010 03:26 PM, Jonas Meurer wrote: Hey again, On 09/07/2010 Milan Broz wrote: On 07/09/2010 09:41 AM, Γιώργος Πάλλας wrote: # WARNING: other process locked internal device temporary-cryptsetup-18450, retrying remove. # WARNING: Process PID 18473 (hald-probe-volu) [PPID 1711 (hald-runner)] spying on internal device /dev/dm-4. Ha! So finally the debug code found something locking the device! :-) HAL _must_ _not_ open temporary-cryptsetup device. It can scan final device but not the temporary one. (udev/udisks have this solved, I thought hal uses the same...) Maybe it is not the real problem but please fix hal too here. I discussed that with the hal maintainer. Hal already has a workaround to ignore temporary-cryptsetup-* devices (in hald/linux/osspec.c). The problem here seems to be that hal probes /dev/dm-4, and not the temporary-cryptsetup device. and the workaround doesn't ignore that one. so, Giorgos, please temporarily disable hal (/etc/init.d/hal stop), and see whether the issue disappears. In that case, hal is the problem for sure. But then still the problem is, how should hal distinguish temporary cryptsetup devices reliably, when '/dev/dm-X' is used? Milan, is there any better/cheaper solution than a lookup for symlinks in /dev/mapper/*? greetings, jonas Hi Jonas. Indeed, with hal stopped, the issue disappears: mordor:/home/gpall# cryptsetup --debug luksOpen /dev/sdb2 dataspace_crypt # cryptsetup 1.1.2 processing cryptsetup --debug luksOpen /dev/sdb2 dataspace_crypt # Locking memory. # Allocating crypt device /dev/sdb2 context. # Trying to open and read device /dev/sdb2. # Initialising device-mapper backend, UDEV is enabled. # Detected dm-crypt target of version 1.7.0. # Timeout set to 0 miliseconds. # Password retry count set to 3. # Iteration time set to 1000 miliseconds. # Password verification disabled. # Trying to load LUKS1 crypt type from device /dev/sdb2. # Initializing crypto backend (using secure memory). # Reading LUKS header of size 1024 from device /dev/sdb2 # Activating volume dataspace_crypt [keyslot -1] using [none] passphrase. # dm status dataspace_crypt OF [16384] Enter passphrase for /dev/sdb2: # Trying to open key slot 0 [1]. # Trying to open key slot 1 [3]. # Reading key slot 1 area. # DM-UUID is CRYPT-TEMP-temporary-cryptsetup-3744 # Udev cookie 0xd4d1bcb (semid 1081344) created # Udev cookie 0xd4d1bcb (semid 1081344) incremented # Udev cookie 0xd4d1bcb (semid 1081344) incremented # Udev cookie 0xd4d1bcb (semid 1081344) assigned to dm_task type 0 with flags 0xe # dm create temporary-cryptsetup-3744 CRYPT-TEMP-temporary-cryptsetup-3744 OF [16384] # temporary-cryptsetup-3744: Stacking NODE_ADD (254,4) 0:6 0660 # dm reload temporary-cryptsetup-3744 OF [16384] # dm resume temporary-cryptsetup-3744 OF [16384] # temporary-cryptsetup-3744: Stacking NODE_READ_AHEAD 256 (flags=1) # Udev cookie 0xd4d1bcb (semid 1081344) decremented # Udev cookie 0xd4d1bcb (semid 1081344): Waiting for zero # Udev cookie 0xd4d1bcb (semid 1081344) destroyed # temporary-cryptsetup-3744: read ahead is 256 # temporary-cryptsetup-3744: Setting read ahead to 256 # Udev cookie 0xd4d61a6 (semid 1114112) created # Udev cookie 0xd4d61a6 (semid 1114112) incremented # Udev cookie 0xd4d61a6 (semid 1114112) incremented # Udev cookie 0xd4d61a6 (semid 1114112) assigned to dm_task type 2 with flags 0x0 # dm remove temporary-cryptsetup-3744 OF [16384] # temporary-cryptsetup-3744: Stacking NODE_DEL (replaces other stacked ops) # Udev cookie 0xd4d61a6 (semid 1114112) decremented # Udev cookie 0xd4d61a6 (semid 1114112): Waiting for zero # Udev cookie 0xd4d61a6 (semid 1114112) destroyed Key slot 1 unlocked. # Calculated device size is 167973584 sectors (RW), offset 2056. # DM-UUID is CRYPT-LUKS1-b63c55b1055d47fb850bb733993f555b-dataspace_crypt # Udev cookie 0xd4dca41 (semid 1146880) created # Udev cookie 0xd4dca41 (semid 1146880) incremented # Udev cookie 0xd4dca41 (semid 1146880) incremented # Udev cookie 0xd4dca41 (semid 1146880) assigned to dm_task type 0 with flags 0x0 # dm create dataspace_crypt CRYPT-LUKS1-b63c55b1055d47fb850bb733993f555b-dataspace_crypt OF [16384] # dataspace_crypt: Stacking NODE_ADD (254,4) 0:6 0660 # dm reload dataspace_crypt OF [16384] # dm resume dataspace_crypt OF [16384] # dataspace_crypt: Stacking NODE_READ_AHEAD 256 (flags=1) # Udev cookie 0xd4dca41 (semid 1146880) decremented # Udev cookie 0xd4dca41 (semid 1146880): Waiting for zero # Udev cookie 0xd4dca41 (semid 1146880) destroyed # dataspace_crypt: read ahead is 256 # dataspace_crypt: Setting read ahead to 256 # Releasing crypt device /dev/sdb2 context. # Releasing device-mapper backend. # Unlocking memory. Command successful. mordor:/home/gpall# -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586286: [pkg-cryptsetup-devel] Bug#586286: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433
On 07/08/2010 12:23 PM, Jonas Meurer wrote: Hey Giorgos, On 18/06/2010 Giorgos Pallas wrote: I am experiencing a reproducable behaviour everytime I unlock a LUKS partition (unrelated with booting). So: aris:/home/encmp/gpall# cryptsetup luksOpen /dev/sdb4 dataspace_crypt Enter passphrase for /dev/sdb4: device-mapper: remove ioctl failed: Device or resource busy At the same time something like: Jun 18 09:35:40 aris kernel: [ 4210.586137] device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433 appears at the kernel messages. can you provide the output of 'cryptsetup --debug luksOpen ...'? Thanks for the good job with cryptsetup!!! would you mind giving preliminary 2:1.1.3-1 packages a try to see whether that changes anything? you can find the packages at http://people.debian.org/~mejo/cryptsetup/ greetings, jonas Hello Jonas, I'm sending you the output requested: mordor:~/proj/cryptsetup-bug# cryptsetup --version cryptsetup 1.1.2 mordor:~/proj/cryptsetup-bug# cryptsetup --debug luksOpen /dev/sdb2 dataspace_crypt # cryptsetup 1.1.2 processing cryptsetup --debug luksOpen /dev/sdb2 dataspace_crypt # Locking memory. # Allocating crypt device /dev/sdb2 context. # Trying to open and read device /dev/sdb2. # Initialising device-mapper backend, UDEV is enabled. # Detected dm-crypt target of version 1.7.0. # Timeout set to 0 miliseconds. # Password retry count set to 3. # Iteration time set to 1000 miliseconds. # Password verification disabled. # Trying to load LUKS1 crypt type from device /dev/sdb2. # Initializing crypto backend (using secure memory). # Reading LUKS header of size 1024 from device /dev/sdb2 # Activating volume dataspace_crypt [keyslot -1] using [none] passphrase. # dm status dataspace_crypt OF [16384] Enter passphrase for /dev/sdb2: # Trying to open key slot 0 [1]. # Trying to open key slot 1 [3]. # Reading key slot 1 area. # DM-UUID is CRYPT-TEMP-temporary-cryptsetup-18450 # Udev cookie 0xd4dfa3d (semid 917505) created # Udev cookie 0xd4dfa3d (semid 917505) incremented # Udev cookie 0xd4dfa3d (semid 917505) incremented # Udev cookie 0xd4dfa3d (semid 917505) assigned to dm_task type 0 with flags 0xe # dm create temporary-cryptsetup-18450 CRYPT-TEMP-temporary-cryptsetup-18450 OF [16384] # temporary-cryptsetup-18450: Stacking NODE_ADD (254,4) 0:6 0660 # dm reload temporary-cryptsetup-18450 OF [16384] # dm resume temporary-cryptsetup-18450 OF [16384] # temporary-cryptsetup-18450: Stacking NODE_READ_AHEAD 256 (flags=1) # Udev cookie 0xd4dfa3d (semid 917505) decremented # Udev cookie 0xd4dfa3d (semid 917505): Waiting for zero # Udev cookie 0xd4dfa3d (semid 917505) destroyed # temporary-cryptsetup-18450: read ahead is 256 # temporary-cryptsetup-18450: Setting read ahead to 256 # Udev cookie 0xd4d3f6c (semid 950273) created # Udev cookie 0xd4d3f6c (semid 950273) incremented # Udev cookie 0xd4d3f6c (semid 950273) incremented # Udev cookie 0xd4d3f6c (semid 950273) assigned to dm_task type 2 with flags 0x0 # dm remove temporary-cryptsetup-18450 OF [16384] device-mapper: remove ioctl failed: Device or resource busy # Udev cookie 0xd4d3f6c (semid 950273) decremented # Udev cookie 0xd4d3f6c (semid 950273) decremented # Udev cookie 0xd4d3f6c (semid 950273): Waiting for zero # Udev cookie 0xd4d3f6c (semid 950273) destroyed # WARNING: other process locked internal device temporary-cryptsetup-18450, retrying remove. # WARNING: Process PID 18473 (hald-probe-volu) [PPID 1711 (hald-runner)] spying on internal device /dev/dm-4. # dm reload temporary-cryptsetup-18450 NF [16384] # Udev cookie 0xd4d58f7 (semid 983041) created # Udev cookie 0xd4d58f7 (semid 983041) incremented # Udev cookie 0xd4d58f7 (semid 983041) incremented # Udev cookie 0xd4d58f7 (semid 983041) assigned to dm_task type 5 with flags 0x0 # dm resume temporary-cryptsetup-18450 OF [16384] # Udev cookie 0xd4d58f7 (semid 983041) decremented # Udev cookie 0xd4d58f7 (semid 983041): Waiting for zero # Udev cookie 0xd4d58f7 (semid 983041) destroyed # Udev cookie 0xd4d1219 (semid 1015809) created # Udev cookie 0xd4d1219 (semid 1015809) incremented # Udev cookie 0xd4d1219 (semid 1015809) incremented # Udev cookie 0xd4d1219 (semid 1015809) assigned to dm_task type 2 with flags 0x0 # dm remove temporary-cryptsetup-18450 OF [16384] # temporary-cryptsetup-18450: Stacking NODE_DEL (replaces other stacked ops) # Udev cookie 0xd4d1219 (semid 1015809) decremented # Udev cookie 0xd4d1219 (semid 1015809): Waiting for zero # Udev cookie 0xd4d1219 (semid 1015809) destroyed Key slot 1 unlocked. # Calculated device size is 167973584 sectors (RW), offset 2056. # DM-UUID is CRYPT-LUKS1-b63c55b1055d47fb850bb733993f555b-dataspace_crypt # Udev cookie 0xd4d401a (semid 1048577) created # Udev cookie 0xd4d401a (semid 1048577) incremented # Udev cookie 0xd4d401a (semid 1048577) incremented # Udev cookie 0xd4d401a (semid 1048577) assigned to dm_task type 0 with flags 0x0 # dm create
Bug#586286: [pkg-cryptsetup-devel] Bug#586286: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433
On 07/09/2010 10:59 AM, Milan Broz wrote: On 07/09/2010 09:41 AM, Γιώργος Πάλλας wrote: # WARNING: other process locked internal device temporary-cryptsetup-18450, retrying remove. # WARNING: Process PID 18473 (hald-probe-volu) [PPID 1711 (hald-runner)] spying on internal device /dev/dm-4. Ha! So finally the debug code found something locking the device! :-) HAL _must_ _not_ open temporary-cryptsetup device. It can scan final device but not the temporary one. (udev/udisks have this solved, I thought hal uses the same...) Maybe it is not the real problem but please fix hal too here. Milan So, should I file this bug to hal package? I'm running version 0.5.14-2 (latest in debian testing) Or will you reassign this bug? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586286: about the strace
It is not on a separate email as I wrote but it is attached on the initial bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528366: a last question
Fixing this implies that somehow we are now able to automatically mount a LUKS volume during system boot, by specifying the keyfile inside /etc/fstab? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582639: kernel's problem?
Marco, as I understand this is not a udev's bug. Could you please reassign the bug to the kernel? smime.p7s Description: S/MIME Cryptographic Signature
Bug#582329: udev: strange warnings after upgrade to 154.1
I also use LVM2 over LUKS, and after the upgrade of udev, I keep getting those same messages seen on the JPG, on every boot. I also don't have this 55-dm-rules.conf file. The contents of /etc/udev are: mordor:/etc/udev# ls -laR .: total 36 drwxr-xr-x 4 root root 4096 May 20 18:31 . drwxr-xr-x 120 root root 12288 May 21 12:04 .. drwxr-xr-x 2 root root 4096 Apr 16 2009 .dev -rw-r--r-- 1 root root92 Dec 28 2008 hdparm.rules -rw-r--r-- 1 root root 397 Apr 16 2009 links.conf drwxr-xr-x 2 root root 4096 May 21 00:32 rules.d -rw-r--r-- 1 root root 269 Apr 19 2009 udev.conf ./.dev: total 8 drwxr-xr-x 2 root root 4096 Apr 16 2009 . drwxr-xr-x 4 root root 4096 May 20 18:31 .. ./rules.d: total 28 drwxr-xr-x 2 root root 4096 May 21 00:32 . drwxr-xr-x 4 root root 4096 May 20 18:31 .. -rw-r--r-- 1 root root 208 May 21 00:32 10-vboxdrv.rules -rw-r--r-- 1 root root 1872 May 10 18:38 70-persistent-cd.rules -rw-r--r-- 1 root root 885 Jan 3 13:11 70-persistent-net.rules lrwxrwxrwx 1 root root 15 Jul 4 2009 z60_hdparm.rules - ../hdparm.rules -rw-r--r-- 1 root root 7117 Apr 12 2009 z60_xserver-xorg-input-wacom.rules mordor:/etc/udev# -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563313: that's not fair!
Ben Hutchings wrote: On Tue, May 04, 2010 at 02:23:20PM +0300, Γιώργος Πάλλας wrote: I regularly follow testing's upgrades. So I was with 2.6.30, the sensors were working fine. I got 2.6.32-3 sensors broken. And I must wait until 2.6.32-12 (!) to get it working again? Why doesn't a patch slip into 2.6.32-3 ?? Am I missing something? Yes, you are confused about the current version. First, package names do not contain the package version. For example, there were several versions of linux-image-2.6.32-3-686, none of which was version 2.6.32-3. The number 3 here is an ABI version which is used to associate the kernel with additional kernel modules. Whenever the ABI changes the additional modules must be rebuilt. Not every package version requires a new ABI version. Second, the latest kernel versions appear in unstable, not testing. As of today, version 2.6.32-12 is available in unstable. Ben. Oh, OK, sorry for the misunderstanding! I tried 2.6.32-5 and it works fine! smime.p7s Description: S/MIME Cryptographic Signature
Bug#563313: that's not fair!
I regularly follow testing's upgrades. So I was with 2.6.30, the sensors were working fine. I got 2.6.32-3 sensors broken. And I must wait until 2.6.32-12 (!) to get it working again? Why doesn't a patch slip into 2.6.32-3 ?? Am I missing something? With real respect to your job, Giorgos Pallas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563247: audacious: crashes with Floating point exception
John Lindgren wrote: Please test version 2.3, and provide a debugger backtrace if the problem still exists. Peace, John Lindgren Hi John! I am not very familiar with the debian bug tracking system, but I am running debian squeeze, fully updated, where the installed audacious version is Version: 2.1-1+b1 So, I can't test version 2.3, except if I miss something... smime.p7s Description: S/MIME Cryptographic Signature
Bug#577054: [Pkg-acpi-devel] Bug#577054: acpi: After upgrade, computer does not turn off
Michael Meskes wrote: After the upgrade that happened around 2010-03-04 or 2010-03-22, the Upgrade of what? acpi hasnb't been updated between June 2009 and March 28 this year. computer does not turn off after shutdown procedure. The disk spins down, the kernel says 'Power down' and I must push the box's turn off button for it to shutdown. This surely is not acpi's fault: mich...@feivel:~$ dpkg --print-avail acpi ... Description: displays information on ACPI devices ... acpi *only* display some information, but has nothing to do with the kernel which I suppose is at fault here. And yes, I know the naming leads to confusion. Michael Yes, I was confused. Actually acpid was upgraded around those dates, but if you think that this must be kernel bug and not an acpid problem, tell me to file the bug against the kernel. Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#563313: linux-image-2.6.32-3-amd64: no CPU temp reading after suspend using debian stock kernel
Package: linux-2.6 Version: 2.6.32-9 Severity: normal So, I have also noticed after upgrading to linux-image-2.6.32-3-amd64 (from 2.6.30), that after a suspend/unsuspend, the temperatures in /proc/acpi/thermal_zone/TZ0* are all zero. As a result, the fan never starts, and some minutes later I get a nice thermal shutdown to protect the innocent CPU. As this completely ruins the concept of suspend, please fix it! :-) -- Package-specific info: ** Version: Linux version 2.6.32-3-amd64 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Feb 24 18:07:42 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-3-amd64 root=/dev/mapper/luksVG-rootFS ro quiet video=i915:modeset=1 ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [2.972451] usb 6-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [2.972453] usb 6-2: Product: USB-compliant keyboard [2.972547] usb 6-2: configuration #1 chosen from 1 choice [2.990723] input: USB-compliant keyboard as /devices/pci:00/:00:1d.0/usb6/6-2/6-2:1.0/input/input8 [2.990788] generic-usb 0003:062A:0201.0002: input,hidraw1: USB HID v1.10 Keyboard [USB-compliant keyboard] on usb-:00:1d.0-2/input0 [3.018854] input: USB-compliant keyboard as /devices/pci:00/:00:1d.0/usb6/6-2/6-2:1.1/input/input9 [3.019025] generic-usb 0003:062A:0201.0003: input,hiddev0,hidraw2: USB HID v1.10 Mouse [USB-compliant keyboard] on usb-:00:1d.0-2/input1 [ 11.509175] Intel AES-NI instructions are not detected. [ 14.509289] PM: Starting manual resume from disk [ 14.509292] PM: Resume from partition 254:2 [ 14.509294] PM: Checking hibernation image. [ 14.509539] PM: Error -22 checking image file [ 14.509541] PM: Resume from disk failed. [ 14.514340] PM: Marking nosave pages: 0009c000 - 0010 [ 14.514346] PM: Marking nosave pages: bd4a1000 - bd4a7000 [ 14.514349] PM: Marking nosave pages: bd5c2000 - bd60f000 [ 14.514353] PM: Marking nosave pages: bd709000 - bd90f000 [ 14.514369] PM: Marking nosave pages: bd918000 - bd91f000 [ 14.514371] PM: Marking nosave pages: bd963000 - bd99f000 [ 14.514375] PM: Marking nosave pages: bd9e4000 - bd9ff000 [ 14.514377] PM: Marking nosave pages: bda0 - 0001 [ 14.515852] PM: Basic memory bitmaps created [ 14.536042] PM: Basic memory bitmaps freed [ 14.604919] EXT4-fs (dm-1): mounted filesystem with ordered data mode [ 15.965852] udev: starting version 151 [ 16.323061] lib80211: common routines for IEEE802.11 drivers [ 16.323064] lib80211_crypt: registered algorithm 'NULL' [ 16.326513] ACPI: Battery Slot [BAT0] (battery present) [ 16.340428] ACPI: SSDT bd91ac20 00265 (v01 PmRef Cpu0Ist 3000 INTL 20050624) [ 16.340919] ACPI: SSDT bd918620 00575 (v01 PmRef Cpu0Cst 3001 INTL 20050624) [ 16.341116] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [ 16.344334] Monitor-Mwait will be used to enter C-1 state [ 16.344360] Monitor-Mwait will be used to enter C-2 state [ 16.344379] Monitor-Mwait will be used to enter C-3 state [ 16.344384] Marking TSC unstable due to TSC halts in idle [ 16.344490] processor LNXCPU:00: registered as cooling_device0 [ 16.348336] ACPI: SSDT bd919ca0 001CF (v01 PmRefApIst 3000 INTL 20050624) [ 16.348726] ACPI: SSDT bd919f20 0008D (v01 PmRefApCst 3000 INTL 20050624) [ 16.349305] Switching to clocksource hpet [ 16.354696] processor LNXCPU:01: registered as cooling_device1 [ 16.429298] ACPI: AC Adapter [ADP1] (on-line) [ 16.429430] ACPI: WMI: Mapper loaded [ 16.460252] i801_smbus :00:1f.3: PCI INT C - GSI 19 (level, low) - IRQ 19 [ 16.460258] ACPI: I/O resource :00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f] [ 16.460321] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 16.483230] input: PC Speaker as /devices/platform/pcspkr/input/input10 [ 16.529941] Linux video capture interface: v2.00 [ 16.573501] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_2M (0c45:63fb) [ 16.578175] input: Laptop_Integrated_Webcam_2M as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input11 [ 16.578238] usbcore: registered new interface driver uvcvideo [ 16.578241] USB Video Class driver (v0.1.0) [ 16.812144] wl: module license 'MIXED/Proprietary' taints kernel. [ 16.812148] Disabling lock debugging due to kernel taint [ 16.815673] wl :04:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 16.815687] wl :04:00.0: setting latency timer to 64 [ 16.855454] lib80211_crypt: registered algorithm 'TKIP' [ 16.855818] eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36 [ 16.861204] udev: renamed network
Bug#567435: linux-image-2.6.32-3-686: address space collision with 2.6.32-3-686 stock
maximilian attems wrote: On Thu, Apr 08, 2010 at 03:00:07PM +0300, Giorgos Pallas wrote: Package: linux-2.6 Version: 2.6.32-9 Severity: normal At every boot I get this message: pci :02:06.0: BAR 6: address space collision on of device [0xfe6c-0xfe6d] this pci messages got reworked for .34 It must be pretty harmless, since I have no problem with my machine, but I thought to report it... In your disposal for more info. a bit late in the game now to change that for lenny as most of these warnings are most likely harmless. so will close away unless someone wants to backport pci stuff, but we seem to have more worthwile bugs to work on. OK, considering all those, it's ok for me to close... smime.p7s Description: S/MIME Cryptographic Signature
Bug#572222: sshfs: handle IPv6 host addresses
Miklos Szeredi wrote: On Tue, 02 Mar 2010, Giorgos Pallas wrote: I guess that sshfs could also handle a command of the form: sshfs 2001:648:2800:13:21fa:d05f:fea4:b155:/media/ /media/myserver or something like that in order for the colons not to get confused... See also: http://old.nabble.com/sshfs-and-IPv6-numerical-addresses-td19586406.html So, does the following work? sshfs [2001:648:2800:13:21fa:d05f:fea4:b155]:/media/ /media/myserver Thanks, Miklos Err, yes... Shame on me for not trying it before filling the bug. It is not documented in the man page though... Anyway the bug can be closed, and shame on me again... smime.p7s Description: S/MIME Cryptographic Signature
Bug#565987: iceweasel: secure connection failed message, from https page - works with firefox same version
Mike Hommey wrote: On Wed, Jan 20, 2010 at 02:46:54PM +0200, Giorgos Pallas wrote: Package: iceweasel Version: 3.5.6-1 Severity: important I have tried running iceweasel in safe mode, on a new user (rm -rf ..mozilla), and still, I can reproduce the following behaviour: I go to https://myserver.mydomain.com - it works ok. When I go to https://myserver.mydomain.com/userspace (where I should be authenticated with my personal certificate) I get the message: Secure Connection Failed An error occurred during a connection to myserver.mydomain.com. * The page you are trying to view can not be shown because the * authenticity of the received data could not be verified. * Please contact the web site owners to inform them of this problem. * Alternatively, use the command found in the help menu to report this * broken site. I downloaded from mozilla.com the firefox 3.5.6 binary and run it - it works OK. First, the difference in behaviour betweeen firefox 3.5.6 and iceweasel 3.5.6 is a bit strange. I keep my debian testing system regularly updated, and this must have happened about a month ago - maybe sooner. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561918#74 or http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561918#79 Mike Thank you very much! NSS_SSL_ENABLE_RENEGOTIATION=1 iceweasel worked as a temporary solution. I searched for bugs containing 'certificate' in the subject before I submitted the bug with reportbug, but I did not find #561918. Thanks again! Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#528366: /sbin/mount.crypt: mount.crypt does not send keyfile option to cryptsetup
So, the final answer is that you cannot automatically mount via fstab a LUKS volume? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545713: gnome-subtitles crashes
Package: gnome-subtitles
Version: 0.9.1-1
Severity: grave
Justification: renders package unusable
Invoking gnome-subtitles from the console gives:
Got 5 languages.
Unhandled Exception:
GnomeSubtitles.Ui.VideoPreview.Exceptions.PlayerCouldNotInitiateEngineException:
An application exception has occurred.
at GnomeSubtitles.Ui.VideoPreview.Player.InitializePlaybin () [0x0]
at GnomeSubtitles.Ui.VideoPreview.Player..ctor (Gtk.AspectFrame aspectFrame)
[0x0]
at GnomeSubtitles.Ui.VideoPreview.Video.InitializePlayer () [0x0]
at GnomeSubtitles.Ui.VideoPreview.Video..ctor () [0x0]
at GnomeSubtitles.Ui.MainUi..ctor (GnomeSubtitles.Core.EventHandlers
handlers, Glade.XML glade) [0x0]
at GnomeSubtitles.Core.Base.Init (GnomeSubtitles.Execution.ExecutionContext
newExecutionContext) [0x0]
at GnomeSubtitles.Core.Base.Run (GnomeSubtitles.Execution.ExecutionContext
executionContext) [0x0]
at GnomeSubtitles.Execution.Executable.Main (System.String[] args) [0x0]
The install procedure was as follows:
mordor:/home/gpall# aptitude install gnome-subtitles
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
cli-common{a} gnome-subtitles libgconf2.0-cil{a} libglade2.0-cil{a}
libglib2.0-cil{a} libgtk2.0-cil{a} libgtkspell0{a} libmono-cairo2.0-cil{a}
libmono-corlib2.0-cil{a}
libmono-i18n-west2.0-cil{a} libmono-i18n2.0-cil{a} libmono-posix2.0-cil{a}
libmono-security2.0-cil{a} libmono-system2.0-cil{a} mono-2.0-gac{a} mono-gac{a}
mono-runtime{a}
The following packages are RECOMMENDED but will NOT be installed:
binfmt-support
0 packages upgraded, 17 newly installed, 0 to remove and 0 not upgraded.
Need to get 6363kB of archives. After unpacking 20.8MB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Get:1 http://postmortem.csd.auth.gr testing/main cli-common 0.7 [183kB]
Get:2 http://postmortem.csd.auth.gr testing/main libmono-corlib2.0-cil
2.4.2.3+dfsg-1 [903kB]
Get:3 http://postmortem.csd.auth.gr testing/main libmono-system2.0-cil
2.4.2.3+dfsg-1 [1517kB]
Get:4 http://postmortem.csd.auth.gr testing/main libmono-security2.0-cil
2.4.2.3+dfsg-1 [138kB]
Get:5 http://postmortem.csd.auth.gr testing/main mono-2.0-gac 2.4.2.3+dfsg-1
[35.1kB]
Get:6 http://postmortem.csd.auth.gr testing/main mono-gac 2.4.2.3+dfsg-1
[27.1kB]
Get:7 http://postmortem.csd.auth.gr testing/main mono-runtime 2.4.2.3+dfsg-1
[1266kB]
Get:8 http://postmortem.csd.auth.gr testing/main libglib2.0-cil 2.12.9-1
[183kB]
Get:9 http://postmortem.csd.auth.gr testing/main libgconf2.0-cil 2.24.1-4
[135kB]
Get:10 http://postmortem.csd.auth.gr testing/main libmono-cairo2.0-cil
2.4.2.3+dfsg-1 [43.5kB]
Get:11 http://postmortem.csd.auth.gr testing/main libgtk2.0-cil 2.12.9-1
[906kB]
Get:12 http://postmortem.csd.auth.gr testing/main libglade2.0-cil 2.12.9-1
[157kB]
Get:13 http://postmortem.csd.auth.gr testing/main
Bug#240989: procps: watch does not show UTF-8 encoded command line
Package: procps Version: 1:3.2.8-1 Severity: normal I execute: watch 'ls -la Πάλλας*' And watch shows at the header: Every 2.0s: ls -la M-NM- M-NM-,M-NM-;M-NM-;M-NM-1M-O~B* Fri Jul 3 12:57:16 2009 Could this be fixed? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii libc6 2.9-12 GNU C Library: Shared libraries ii libncurses5 5.7+20090523-1 shared libraries for terminal hand ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip Versions of packages procps recommends: ii psmisc22.7-1 utilities that use the proc file s procps suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533309: openoffice: Version: OO 3.0.1 OOO300m15 (Build 9379) - PDFs created have, wrong definition for the black color
Package: openoffice.org-writer Version: 1:3.0.1-9 Severity: important File: openoffice I went to a store to print a pdf that I created using OO-writer, and they told me that the black color is not black. It is: 75% Cyan, 68% Magenta, 67% Yellow and 90% Black. This creates obvious problems with digital printing since they empty all their color toners and creates very saturated paper. The problem was confirmed by a friend of mine who works as a designer. For your convenience I include two sample pdf files, one ok (2) and one problematic (1). This was created with OpenOffice 3.0.1 on debian testing: 1) http://postmortem.csd.auth.gr/~gpall/versteckt/openOffice.pdf This was created by PDFCreator (free Windows app) 2) http://postmortem.csd.auth.gr/~gpall/versteckt/pdfcreator.pdf My friend told me to write that the problem can be seen by examining the 'output preview' of Acrobat Professional. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openoffice.org-writer depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii libgcc11:4.4.0-5 GCC support library ii libicu40 4.0.1-2 International Components for Unico ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3 ii libstlport4.6ldbl 4.6.2-5 STLport C++ class library ii libwpd8c2a 0.8.14-1 Library for handling WordPerfect d ii libwps-0.1-1 0.1.2-1 Works text file format import filt ii openoffice.org-base-co 1:3.0.1-9 full-featured office productivity ii openoffice.org-core1:3.0.1-9 full-featured office productivity ii ure1.4.1+OOo3.0.1-9 OpenOffice.org UNO runtime environ ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages openoffice.org-writer recommends: ii java-gcj-compat 1.0.80-1 Java runtime environment using GIJ ii openoffice.org-emailmerge 1:3.0.1-9 full-featured office productivity ii openoffice.org-filter-binfilt 1:3.0.1-9 full-featured office productivity ii openoffice.org-java-common1:3.0.1-9 full-featured office productivity ii openoffice.org-math 1:3.0.1-9 full-featured office productivity ii openoffice.org-writer2latex 0.5.0.2-4 Writer/Calc to LaTeX converter ext ii sun-java6-jre 6-13-1 Sun Java(TM) Runtime Environment ( Versions of packages openoffice.org-writer suggests: ii openoffice.org-base 1:3.0.1-9 full-featured office productivity pn openoffice.org-gcjnone (no description available) Versions of packages openoffice.org-core depends on: ii fontconfig 2.6.0-3 generic font configuration library ii libc6 2.9-12GNU C Library: Shared libraries ii libcairo2 1.8.6-2+b1The Cairo 2D vector graphics libra ii libcurl3-gnutls7.18.2-8.1Multi-protocol file transfer libra ii libdb4.7 4.7.25-6 Berkeley v4.7 Database Libraries [ ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib ii libgcc11:4.4.0-5 GCC support library ii libglib2.0-0 2.20.1-2 The GLib library of C routines ii libgstreamer-plugins-b 0.10.23-2 GStreamer libraries from the base ii libgstreamer0.10-0 0.10.23-1 Core GStreamer libraries and eleme ii libgtk2.0-02.16.1-2 The GTK+ graphical user interface ii libhunspell-1.2-0 1.2.8-3 spell checker and morphological an ii libhyphen0 2.4-4 ALTLinux hyphenation library - sha ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libicu40 4.0.1-2 International Components for Unico ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libneon27 0.28.4-1 An HTTP and WebDAV client library ii libnspr4-0d4.7.4-3 NetScape Portable Runtime Library ii libnss3-1d 3.12.3-1 Network Security Service libraries ii librdf01.0.9-1 Redland Resource Description Frame ii libsm6 2:1.1.0-2 X11 Session Management library ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3 ii libstlport4.6ldbl 4.6.2-5 STLport C++ class library ii libx11-6 2:1.2.1-1 X11 client-side
Bug#529656: udev: deprecated sysfs layout
Greg KH wrote: On Wed, May 20, 2009 at 09:00:31PM +0300, Giorgos D. Pallas wrote: I get this kernel message during booting: [ 170.441135] udev: deprecated sysfs layout; update the kernel or disable CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly Is it a bug? No, disable that option in your kernel, and rebuild it, you should not be using that configuration anymore. I will get over Marco's rudeness, and point to Greg that 'I am not using any configuration'. I use the debian testing latest stock kernel and see this error message. So the problem is not mine; As I understand it is not udev's problem, so it may be a kernel's problem, or anyone's who uses this deprecated sysfs layout. So why Marco did not reassign the bug to a more relevant packet and chose instead to be rude and unhelpful? Italian tamperament most certainly :-) smime.p7s Description: S/MIME Cryptographic Signature
Bug#528366: extra info
I see in the source code of libpam-mount (loop.c):
static bool ehd_load_2(struct ehdmount_ctl *ctl)
{
int ret;
bool is_luks = false;
const char *start_args[11];
struct HXproc proc;
ret = ehd_is_luks(ctl-lower_device, true);
if (ret = 0) {
int argk = 0;
is_luks = ret == 1;
start_args[argk++] = cryptsetup;
if (ctl-readonly)
start_args[argk++] = --readonly;
if (ctl-cipher != NULL) {
start_args[argk++] = -c;
start_args[argk++] = ctl-cipher;
}
if (is_luks) {
start_args[argk++] = luksOpen;
start_args[argk++] = ctl-lower_device;
start_args[argk++] = ctl-crypto_name;
} else {
start_args[argk++] = --key-file=-;
start_args[argk++] = -h;
start_args[argk++] = ctl-hash;
start_args[argk++] = create;
start_args[argk++] = ctl-crypto_name;
start_args[argk++] = ctl-lower_device;
}
It can't have a keyfile if it is a luks volume.
I then noticed the obscure distinction in the documentation of
mount.crypt between a 'crypto' (=dm-crypt?) and a luks volume:
keyfile
The path to the key file. This option is mandatory for
normal crypto volumes and should not be used for LUKS volumes.
So, the conclusion is that mount.crypt which can successfully mount a
luks volume with a passphrase, cannot mount a luks volume with a
keyfile. Is that a feature? I think it is a bug...
smime.p7s
Description: S/MIME Cryptographic Signature
Bug#504917: network-manager-openvpn: cannot connect using method X509 certificates
Package: network-manager-openvpn Version: 0.3.2svn2855-1.1 Severity: important I am trying to connect using the X509 certificates method. I broke my pkcs12 to the three certs required (although I believe the gui should support directly pkcs12 files but that's another story) and filled the three fields. The key file is of course protected with a PEM passphrase. The problem is that the gui fails because it cannot unlock the key file, naturally because it never asks for the passphrase. Here's what I get on syslog: Nov 7 23:54:28 mordor NetworkManager: info Will activate VPN connection 'noc', service 'org.freedesktop.NetworkManager.openvpn', user_name 'gpall', vpn_data 'connection-type / x509 / remote / 155.207.212.10 / port / 53 / ca / /home/gpall/various/openvpn-certs/userca.pem / cert / /home/gpall/various/openvpn-certs/usercert.pem / key / /home/gpall/various/openvpn-certs/userkey.pem / cipher / DESX-CBC / comp-lzo / yes / shared-key / / username / [EMAIL PROTECTED] / local-ip / / remote-ip / / dev / tap / proto / udp / ta-dir / none', route ''. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 1 of 4 (Connection Prepare) scheduled... Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 1 of 4 (Connection Prepare) ran VPN service daemon org.freedesktop.NetworkManager.openvpn (PID 16008) Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 1 of 4 (Connection Prepare) complete. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 2 of 4 (Connection Prepare Wait) scheduled... Nov 7 23:54:28 mordor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' signaled state change 1 - 6. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 2 of 4 (Connection Prepare Wait) waiting... Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 2 of 4 (Connection Prepare Wait) complete. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 3 of 4 (Connect) scheduled... Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 3 of 4 (Connect) sending connect request. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 3 of 4 (Connect) request sent, waiting for reply... Nov 7 23:54:28 mordor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' signaled state change 6 - 3. Nov 7 23:54:28 mordor nm-openvpn[16010]: OpenVPN 2.1_rc11 i486-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] built on Sep 18 2008 Nov 7 23:54:28 mordor nm-openvpn[16010]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Nov 7 23:54:28 mordor nm-openvpn[16010]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 3 of 4 (Connect) reply received. Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 4 of 4 (IP Config Get) timeout scheduled... Nov 7 23:54:28 mordor NetworkManager: info VPN Activation (noc) Stage 3 of 4 (Connect) complete, waiting for IP configuration... Nov 7 23:54:43 mordor NetworkManager: WARN nm_vpn_service_process_signal(): VPN failed for service 'org.freedesktop.NetworkManager.openvpn', signal 'ConnectFailed', with message 'The VPN login failed because the VPN program could not connect to the VPN server.'. Nov 7 23:54:43 mordor nm-openvpn[16010]: ERROR: could not read Private Key username/password/ok/string from management interface Nov 7 23:54:43 mordor nm-openvpn[16010]: Exiting Nov 7 23:54:43 mordor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' signaled state change 3 - 5. Nov 7 23:54:43 mordor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' signaled state change 5 - 6. Nov 7 23:54:43 mordor NetworkManager: WARN nm_vpn_service_stop_connection(): (VPN Service org.freedesktop.NetworkManager.openvpn): could not stop connection 'noc' because service was 6. The same gui in Ubuntu Intrepid, for the same authentication method, has an extra field called Private Key password, and everything works fine there. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager-openvpn depends on: ii libc6 2.7-15 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-4simple interprocess messaging syst ii libdbus-glib-1-2 0.76-1 simple interprocess messaging syst ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii openvpn 2.1~rc11-1 virtual private network daemon network-manager-openvpn recommends
Bug#473630: traceroute: sim hops out of range error with -m values under 6
Package: traceroute Version: 2.0.11-2 Followup-For: Bug #473630 The bug still exists: Without any switches, all OK: [EMAIL PROTECTED]:~$ traceroute 155.207.0.31 traceroute to 155.207.0.31 (155.207.0.31), 30 hops max, 40 byte packets 1 gpall (192.168.1.1) 121.476 ms 123.869 ms 125.349 ms 2 bbras-llu-lsf-03L0.forthnet.gr (213.16.253.188) 130.152 ms 133.401 ms 137.775 ms 3 core-lsf-03-Gi0-0-0.forthnet.gr (194.219.41.177) 141.868 ms 146.057 ms 147.430 ms 4 core-ath-08-Gi1-1-3.forthnet.gr (212.251.94.117) 151.559 ms 156.232 ms 157.836 ms 5 aix1.forthnet.gr (212.251.94.94) 175.497 ms 176.972 ms 179.224 ms 6 grnet.aix.gr (195.130.89.1) 213.116 ms 146.844 ms 146.535 ms 7 larissa2-to-athens3.backbone.grnet.gr (195.251.27.33) 149.797 ms 152.218 ms 153.717 ms 8 thessaloniki2-to-larissa2.backbone.grnet.gr (195.251.27.58) 155.122 ms 159.204 ms 161.400 ms 9 clientRouter.auth.thessaloniki-2.access-link.grnet.gr (195.251.25.69) 64.610 ms 67.775 ms 69.275 ms 10 atlantas-bb.ccf.auth.gr (155.207.100.1) 70.696 ms 54.981 ms 56.523 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * [EMAIL PROTECTED]:~$ Using the -m switch, with a value over 5, all OK: [EMAIL PROTECTED]:~$ traceroute -m 6 155.207.0.31 traceroute to 155.207.0.31 (155.207.0.31), 6 hops max, 40 byte packets 1 gpall (192.168.1.1) 156.605 ms 158.185 ms 172.556 ms 2 bbras-llu-lsf-03L0.forthnet.gr (213.16.253.188) 198.904 ms 204.942 ms 206.435 ms 3 core-lsf-03-Gi0-0-0.forthnet.gr (194.219.41.177) 207.961 ms 210.272 ms 211.729 ms 4 core-ath-08-Gi1-1-3.forthnet.gr (212.251.94.117) 225.538 ms 227.017 ms 230.895 ms 5 aix1.forthnet.gr (212.251.94.94) 271.040 ms 272.580 ms 274.062 ms 6 grnet.aix.gr (195.130.89.1) 278.312 ms 192.324 ms 300.964 ms [EMAIL PROTECTED]:~$ But using the switch with a value under 6, it breaks, and I think it shouldn't... [EMAIL PROTECTED]:~$ traceroute -m 5 155.207.0.31 sim hops out of range [EMAIL PROTECTED]:~$ -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages traceroute depends on: ii libc6 2.7-14 GNU C Library: Shared libraries traceroute recommends no packages. traceroute suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501608: [Pkg-virtualbox-devel] Bug#501608: Bug#501608: virtualbox: Debian Lenny as VM system freezes
Frank Mehnert wrote: On Wednesday 08 October 2008, Joseph Rawson wrote: On Wednesday 08 October 2008 15:11:24 Γιώργος Πάλλας wrote: Package: virtualbox Version: 1.6.6-35336_Debian_lenny I'm using version 1.6.6-dfsg-2 . It looks like you're using on of the versions supplied by virtualbox.org . Right, this is the PUEL package. Note that there were several fixes after 1.6.6 was released (some of them were backported to the Debian OSE version 1.6.6) so I strongly suggest you to upgrade to the latest version (which is currently 2.0.2). Kind regards, Frank Sorry guys that I opened the bug on debian, without having the debian build installed... I thought that 'reportbug' would prevent me from filing the bug... Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Bug#501608: virtualbox: Debian Lenny as VM system freezes
Package: virtualbox Version: 1.6.6-35336_Debian_lenny Severity: grave Justification: renders package unusable There are several problems trying to install debian lenny on a virtualbox VM. Installation goes fine, and after that, almost 4 out of 5 times, when booting kernel it either freezes, either prints some garbage and freezes. I tried installing it twice and the behaviour is the same. Now, when it manages to boot, after some time of using the vm system, it freezes with no apparent reason... In your disposal for any additional info... Giorgos Pallas -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages virtualbox depends on: ii adduser3.110 add and remove users and groups ii debconf [debconf-2.0] 1.5.22Debian configuration management sy ii libc6 2.7-13GNU C Library: Shared libraries ii libgcc11:4.3.2-1 GCC support library ii libglib2.0-0 2.16.5-1 The GLib library of C routines ii libidl00.8.10-0.1library for parsing CORBA IDL file ii libqt3-mt 3:3.3.8b-5Qt GUI Library (Threaded runtime v ii libsdl1.2debian1.2.13-2 Simple DirectMedia Layer ii libssl0.9.80.9.8g-13 SSL shared libraries ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library ii libxcursor11:1.1.9-1 X cursor management library ii libxml22.6.32.dfsg-4 GNOME XML library ii libxslt1.1 1.1.24-2 XSLT processing library - runtime ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii psmisc 22.6-1Utilities that use the proc filesy Versions of packages virtualbox recommends: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina pn bridge-utilsnone (no description available) ii gcc 4:4.3.2-2The GNU C compiler ii kpdf [pdf-viewer] 4:3.5.9-3PDF viewer for KDE ii libasound2 1.0.16-2 ALSA library ii libhal1 0.5.11-3 Hardware Abstraction Layer - share ii libpulse0 0.9.10-3 PulseAudio client libraries pn libsdl-ttf2.0-0 none (no description available) ii linux-headers-2.6.2 2.6.26-5 Header files for Linux 2.6.26-1-68 ii make3.81-5 The GNU version of the make util pn uml-utilities none (no description available) virtualbox suggests no packages. -- debconf information: virtualbox/old-installation-found: * virtualbox/module-compilation-allowed: true virtualbox/update_version_change: false virtualbox/delete-old-modules: true * virtualbox/group-vboxusers: virtualbox/module-compilation-failed: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481104: [Pkg-cryptsetup-devel] /usr/sbin/update-initramfs: update-initramfs edits /etc/initramfs-tools/conf.d/cryptroot
David Härdeman wrote: On Wed, July 9, 2008 10:51, Giorgos D. Pallas wrote: David Härdeman wrote: ... (why do you have a cryptroot file by the way? It's supposed to be a cryptsetup internal config file) If I understood your question well, my answer is this: I have /etc/initramfs-tools/conf.d/*cryptroot containing the line: **target=lukspace,source=/dev/hda3,key=none,lvm=vg-root* because I have my root partition sitting on LVM, which sits on LUKS. So, somehow the initrd image must know that it has to find a LUKS partition and ask me for its passphrase. I hope I'm not talking nonsense. When I tried to set up encrypted root partition, I used googling, a bit hacking and imagination. So, there is the possibility that an easier method eludes me. Yes, the correct method would be to create a /etc/crypttab file with the mapping for your root device. See the documentation in /usr/share/doc/cryptsetup for details on how to do that. Once a proper crypttab is setup, cryptsetup will automagically generate initramfs config files for you. Not to my surprise, you were right :-) I just deleted the /etc/initramfs-tools/conf.d/cryptroot file, and run again update-initramfs -u. Laptop boots fine. Btw, I already had /etc/crypttab correctly configured, so it seems that the cryptroot file was redundant. So, probably the bug has to be closed since it was a consequence of a wrong practice, if I got it right. Thanks for all, Giorgos smime.p7s Description: S/MIME Cryptographic Signature
