Bug#992325: rdiff-backup: '::' prefix on target directory causes crash - contrary to documentation (and earlier versions) version graph
This (documentation) issue is fixed since a long time. KR, Eric On 04/02/2023 00:07, Otto Kekäläinen wrote: Hello Alexis! Thanks for using rdiff-backup and reporting about https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992325 Please test if this issue still exists in latest rdiff-backup 2.2.2-1 in Debian. If it still exists, please report the issue upstream at https://github.com/rdiff-backup/rdiff-backup and mark this Debian bug report as forwarded. Alternatively you could consider contributing to the man page upstream to at least update it to explain that this feature no longer behaves in the same way as you expected.
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.1.0+cvs20150211-3 Followup-For: Bug #704259 Hi, I recently updated to the latest version at e-tobi.net and the issue is still there, so that I can't hope that it will be fixed anytime in Debian. Despite my profound lack of knowledge in gdb and C/C++, I tried to follow what's going on but I'm stuck: - I installed the -gdb packages for vdr, vdr-plugin-imonlcd and vdr-plugin-xineliboutput - I get a core file once I try to stop a media playing (video, audio, internet radio, no big difference). - dmesg and journalctl both give a very similar complain: dmesg: [ 1430.792871] iMonLCD: watch [1880]: segfault at 2bb0 ip 7ff90aa63a5a sp 7ff909b37d20 error 4 in libvdr-xineliboutput.so.2.2.0[7ff90aa3a000+84000] journalctl: Mär 15 13:22:12 hdvdr kernel: iMonLCD: watch [1880]: segfault at 2bb0 ip 7ff90aa63a5a sp 7ff909b37d20 error 4 in libvdr-xineliboutput.so.2.2.0[7ff90aa3a000+84000] - call $ gdb --core=core-imon-xvdr_2015-03-15_13-22 --directory=/home/ericl/VDR/vdr-plugin-xineliboutput-1.1.0+cvs20150211 /usr/bin/vdr [...] Reading symbols from /usr/bin/vdr...Reading symbols from /usr/lib/debug/.build-id/08/b6fa0bc86ab4336a245917720818380c3b2520.debug...done. done. [New LWP 1880] [...] [New LWP 1867] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/bin/vdr -v /var/lib/video -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr/'. Program terminated with signal SIGSEGV, Segmentation fault. #0 cXinelibDevice::PlayFileCtrl (this=0xf0, Cmd=0x7ff90aa9e5bb GETLENGTH, TimeoutMs=-1) at device.c:861 861 if(m_server) And here I'm already stuck because I don't understand how this line can cause an issue... (gdb) p m_server Cannot access memory at address 0x2bb0 The only thing I could think of is that the memory address is very short, as is the memory address of the 'this' variable (see following backtrace), but my knowledge doesn't allow me to tell if it's really an issue and what the cause could be. (gdb) bt #0 cXinelibDevice::PlayFileCtrl (this=0xf0, Cmd=0x7ff90aa9e5bb GETLENGTH, TimeoutMs=-1) at device.c:861 #1 0x7ff90aa7cb06 in GetLength (this=0x1c0fca0) at media_player.c:79 #2 cXinelibPlayer::GetIndex (this=0x1c0fca0, Current=@0x7ff909b37e48: 0, Total=@0x7ff909b37e4c: 0, SnapToIFrame=optimized out) at media_player.c:152 #3 0x7ff909d9fafa in GetIndex (SnapToIFrame=false, Total=@0x7ff909b37e4c: 0, Current=@0x7ff909b37e48: 0, this=optimized out) at /usr/include/vdr/player.h:102 #4 ciMonWatch::ReplayPosition (this=optimized out, current=@0x7ff909b37e48: 0, total=@0x7ff909b37e4c: 0, dFrameRate=@0x7ff909b37da0: 25) at watch.c:740 #5 0x7ff909da10e8 in ciMonWatch::ReplayTime (this=this@entry=0x19a31c8, current=@0x7ff909b37e48: 0, total=@0x7ff909b37e4c: 0) at watch.c:787 #6 0x7ff909da14d6 in ciMonWatch::Action (this=0x19a31c8) at watch.c:286 #7 0x0050f3cf in cThread::StartThread (Thread=0x19a3218) at thread.c:262 #8 0x7ff9100690a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7ff90ea8304d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Any help would be really appreciated to get this bug fixed. Don't hesitate to give me further instructions. Thanks, Eric -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16.7-ckt2+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.19-15 ii libextractor3 1:1.3-2+b1 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii vdr [vdr-abi-2.2.0-multipatch] 2.2.0-1~etobi4 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput 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#766839: vdr: Hangs after changing time from summer to winter
Package: vdr
Version: 2.0.3-2+b1
Severity: normal
Hi,
tonight the time was switched back by one hour and this morning I started
my VDR, it had the old time (no NTP). After a while VDR does switch back
the time by one hour, based on time from a TV station.
The issue is that it hangs right after, even though even systemctl doesn't
detect it. I can't switch channel or do actually anything, both GUI
and VDR itself seem to be dead.
I also attach a log of how it happens.
The issue was already there before the Bin-NMU so it can't be the reason.
Thanks, Eric
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.3+vdr1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages vdr depends on:
ii adduser3.113+nmu3
ii debconf [debconf-2.0] 1.5.53
ii libc6 2.19-11
ii libcap21:2.24-6
ii libfontconfig1 2.11.0-6.1
ii libfreetype6 2.5.2-2
ii libgcc11:4.9.1-16
ii libjpeg62-turbo1:1.3.1-8
ii libstdc++6 4.9.1-16
ii psmisc 22.21-2
Versions of packages vdr recommends:
ii fonts-freefont-ttf [ttf-freefont] 20120503-4
ii lirc 0.9.0~pre1-1.1
ii ttf-bitstream-vera 1.10-8
ii ttf-freefont 20120503-4
Versions of packages vdr suggests:
pn vdr-plugin-dvbsddevice none
-- Configuration Files:
/etc/default/vdr changed:
ENABLED=1
ENABLE_SHUTDOWN=1
OPTIONS=-w 60
ENABLE_CORE_DUMPS=1
/etc/vdr/command-hooks/commands.custom.conf changed:
Restart X-VDR : sudo /usr/local/bin/restart-xvdr
Network {
Network status : /sbin/ifconfig ping -c 4 192.168.1.1
LAN neu-starten : sudo /sbin/ifdown eth0 sudo /sbin/ifup eth0
LAN stoppen : sudo /sbin/ifdown eth0
LAN starten : sudo /sbin/ifup eth0
}
CD-ROM {
CD einziehen/rauswerfen : /usr/bin/eject -T /dev/sr0
CD einziehen: /usr/bin/eject -t /dev/sr0
CD rauswerfen : /usr/bin/eject /dev/sr0
}
System status {
Dmesg : dmesg
Journal : sudo journalctl --no-pager
Apt : sudo aptitude update
}
/etc/vdr/keymacros.conf changed:
Red @xineliboutput Ok
Green @xineliboutput Down Ok
Blue@xineliboutput Down Down Ok
User1 Commands 3 2
User2 Commands 3 3
User3 Commands 1
User8 @xineliboutput Down Down Down Ok
User9 @xineliboutput Down Down Down Down Ok
/etc/vdr/plugins/order.conf changed:
nordlichtsepg
epgsearch
xineliboutput
radiolist
-vdrcd
-dvd
-vcd
-mp3
-mplayer
osdteletext
ttxtsubs
tvonscreen
screenshot
femon
undelete
vdrc
vdrrip
imonlcd
remote
/etc/vdr/vdr.groups changed:
vdr
video
audio
-- debconf information:
vdr/create_video_dir: false
* vdr/select_dvb_card: Cable
journalctl.vdrtime.txt.gz
Description: application/gzip
Bug#764085: kde-runtime: Unable to start Dr. Konqi
Package: kde-runtime Version: 4:4.14.1-1 Severity: normal Hello, I have currently an issue with digikam [1] but also the issue that Dr. Konqi doesn't start after such a crash, making it difficult to provide a proper report. The output from the command line looks like this: $ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/ericl/.kde/socket-emil/kdeinit4__0 digikam: Fatal IO error: client killed Fatal Error: Accessed global static 'FileReadWriteLockStaticPrivate *static_d()' after destruction. Defined at /tmp/buildd/digikam-4.3.0/core/libs/threadimageio/filereadwritelock.cpp:385 Unable to start Dr. Konqi Let me know if I can do more to help resolve this issue. Thanks, Eric [1] already reported as Bug#763991: digikam: Digikam crashes with SIGSEGV while creating preview images -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-runtime depends on: ii kde-runtime-data4:4.14.1-1 ii kdelibs5-plugins4:4.14.1-1 ii libasound2 1.0.28-1 ii libattica0.40.4.2-1 ii libc6 2.19-11 ii libcanberra00.30-2.1 ii libexiv2-13 0.24-4 ii libgcc1 1:4.9.1-15 ii libgcrypt20 1.6.2-3 ii libgpgme++2 4:4.14.1-1 ii libgpgme11 1.5.1-6 ii libjpeg88d1-1 ii libkactivities6 4:4.13.3-1 ii libkcmutils44:4.14.1-1 ii libkdeclarative54:4.14.1-1 ii libkdecore5 4:4.14.1-1 ii libkdesu5 4:4.14.1-1 ii libkdeui5 4:4.14.1-1 ii libkdewebkit5 4:4.14.1-1 ii libkdnssd4 4:4.14.1-1 ii libkemoticons4 4:4.14.1-1 ii libkfile4 4:4.14.1-1 ii libkhtml5 4:4.14.1-1 ii libkio5 4:4.14.1-1 ii libkmediaplayer44:4.14.1-1 ii libknewstuff3-4 4:4.14.1-1 ii libknotifyconfig4 4:4.14.1-1 ii libkparts4 4:4.14.1-1 ii libkpty44:4.14.1-1 ii libkxmlrpcclient4 4:4.14.1-1 ii libntrack-qt4-1 016-1.3 ii libopenexr6 1.6.1-8 ii libphonon4 4:4.8.0-1 ii libplasma3 4:4.14.1-1 ii libpulse-mainloop-glib0 5.0-6 ii libpulse0 5.0-6 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-script 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtwebkit42.3.2.dfsg-4 ii libsmbclient2:4.1.11+dfsg-1 ii libsolid4 4:4.14.1-1 ii libssh-gcrypt-4 0.6.3-3+b1 ii libstdc++6 4.9.1-15 ii libwebp50.4.1-1.2+b1 ii libx11-62:1.6.2-3 ii libxcursor1 1:1.1.14-1 ii oxygen-icon-theme 4:4.14.0-1 ii perl5.20.1-1 ii phonon 4:4.8.0-1 ii plasma-scriptengine-javascript 4:4.14.1-1 kde-runtime recommends no packages. Versions of packages kde-runtime suggests: pn djvulibre-bin none pn finger none pn icoutils none -- 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#763991: digikam: Digikam crashes with SIGSEGV while creating preview images
Package: digikam
Version: 4:4.3.0-1
Severity: important
Hello,
Digikam has stopped working today, it did work yesterday, and I did an
upgrade of digikam:amd64 (4.1.0-1+b2, 4.3.0-1) in between. So, even if
the segmentation fault is in libexiv2, I suspect the issue with digikam.
Anyway, feel free to re-assign or ask for more information, here the bug
description...
Digikam starts first, to the point where the hint dialog shows up, then
it crashes.
When starting it from the gdb, I get the following output (I don't get
more when starting digikam normally):
(gdb) run
Starting program: /usr/bin/digikam --sync --nocrashhandler
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x7fffd125e700 (LWP 7889)]
[New Thread 0x7fffca7b3700 (LWP 7890)]
[New Thread 0x7fffc9fb2700 (LWP 7891)]
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QString)
[New Thread 0x7fffc97b1700 (LWP 7892)]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
still in use, all queries will cease to work.
[Thread 0x7fffc97b1700 (LWP 7892) exited]
[New Thread 0x7fffc97b1700 (LWP 7893)]
[New Thread 0x7fffb52ac700 (LWP 7895)]
[Thread 0x7fffb52ac700 (LWP 7895) exited]
[New Thread 0x7fffb52ac700 (LWP 7896)]
[New Thread 0x7fffb0aaa700 (LWP 7897)]
[New Thread 0x7fffabfff700 (LWP 7898)]
[New Thread 0x7fffab7fe700 (LWP 7899)]
[New Thread 0x7fffaaffd700 (LWP 7900)]
[New Thread 0x7fffaa7fc700 (LWP 7901)]
[New Thread 0x7fffa9ffb700 (LWP 7902)]
[New Thread 0x7fffa97fa700 (LWP 7903)]
[New Thread 0x7fffa8ff9700 (LWP 7904)]
[New Thread 0x7fff87fff700 (LWP 7905)]
[New Thread 0x7fff877fe700 (LWP 7906)]
[New Thread 0x7fff86ffd700 (LWP 7907)]
[New Thread 0x7fff867fc700 (LWP 7908)]
[New Thread 0x7fff85ffb700 (LWP 7909)]
[New Thread 0x7fff857fa700 (LWP 7910)]
[New Thread 0x7fff84ff9700 (LWP 7911)]
[New Thread 0x7fff77fff700 (LWP 7912)]
[New Thread 0x7fff777fe700 (LWP 7913)]
[New Thread 0x7fff76ffd700 (LWP 7914)]
[New Thread 0x7fff767fc700 (LWP 7915)]
[New Thread 0x7fff75ffb700 (LWP 7916)]
[New Thread 0x7fff757fa700 (LWP 7917)]
[New Thread 0x7fff74ff9700 (LWP 7918)]
[New Thread 0x7fff747f8700 (LWP 7919)]
[New Thread 0x7fff73ff7700 (LWP 7920)]
[New Thread 0x7fff737f6700 (LWP 7921)]
[New Thread 0x7fff72ff5700 (LWP 7922)]
[New Thread 0x7fff727f4700 (LWP 7923)]
[New Thread 0x7fff71ff3700 (LWP 7924)]
[New Thread 0x7fff717f2700 (LWP 7925)]
[New Thread 0x7fff70ff1700 (LWP 7926)]
[New Thread 0x7fff707f0700 (LWP 7927)]
[New Thread 0x7fff6ffef700 (LWP 7928)]
[New Thread 0x7fff6f7ee700 (LWP 7929)]
[New Thread 0x7fff6efed700 (LWP 7930)]
[New Thread 0x7fff6e7ec700 (LWP 7931)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff727f4700 (LWP 7923)]
0x7fffedd266e5 in Exiv2::PreviewManager::getPreviewImage (
this=0x7fffc400e450, properties=...) at preview.cpp:1157
1157preview.cpp: No such file or directory.
(gdb) backtrace full
#0 0x7fffedd266e5 in Exiv2::PreviewManager::getPreviewImage (
this=0x7fffc400e450, properties=...) at preview.cpp:1157
loader = optimized out
buf = {pData_ = 0x7fff727f3320 \240\063\177r\377\177, size_ = 0}
#1 0x75c11902 in KExiv2Iface::KExiv2Previews::data(int) ()
from /usr/lib/libkexiv2.so.11
No symbol table info available.
#2 0x75c11a8b in KExiv2Iface::KExiv2Previews::image(int) ()
from /usr/lib/libkexiv2.so.11
No symbol table info available.
#3 0x7551717b in
Digikam::ThumbnailCreator::createThumbnail(Digikam::ThumbnailInfo
const, QRect const) const ()
from /usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#4 0x7551adf9 in Digikam::ThumbnailCreator::load(QString
const, QRect const, bool) const () from
/usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#5 0x7551b790 in Digikam::ThumbnailCreator::pregenerate(QString
const) const () from /usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#6 0x7552a480 in ?? () from
/usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#7 0x754ffc8e in Digikam::LoadSaveThread::run() ()
from /usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#8 0x755343ee in
Digikam::DynamicThread::DynamicThreadPriv::run() ()
from /usr/lib/digikam/libdigikamcore.so.4.3.0
No symbol table info available.
#9 0x71c508a4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
No symbol table info available.
#10 0x71c5d3ff in ?? () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
No symbol table info available.
#11 0x7fffecd790a4 in start_thread (arg=0x7fff727f4700)
at pthread_create.c:309
__res = optimized out
pd = 0x7fff727f4700
now = optimized out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140735114331904,
Bug#761473: digikam: Crash at startup with Floating point exception
Package: digikam Version: 4:4.1.0-1+b1 Severity: grave Justification: renders package unusable Hi, I can't use anymore digikam because it crashes each time I try to start it: - Start digikam (from the console or from the KDE menu) - Digikam appears, starts to build up the pictures, the hint window is even there. - wait a bit or try to click away the hint window - digikam crashes The crash handler states: Executable: digikam PID: 7033 Signal: Floating point exception (8) Time: 2014-09-14 08:26:52 Started from the console, I also see: $ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. digikam(7033)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: /srv/photos/PhotosPatricia KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/ericl/.kde/socket-emil/kdeinit4__0 [1]+ Stopped digikam Hope you can help, I can't anymore manage my images, Thanks, Eric -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages digikam depends on: ii digikam-data 4:4.1.0-1 ii digikam-private-libs 4:4.1.0-1+b1 ii kde-runtime 4:4.14.0-2 ii libc6 2.19-10 ii libgcc1 1:4.9.1-12 ii libgphoto2-6 2.5.4-1.1 ii libgphoto2-port10 2.5.4-1.1 ii libkdcraw23 4:4.14.0-1 ii libkdecore5 4:4.14.0-1 ii libkdeui5 4:4.14.0-1 ii libkexiv2-11 4:4.14.0-1+b1 ii libkhtml5 4:4.14.0-1 ii libkio5 4:4.14.0-1 ii libkipi11 4:4.13.3-1 ii libknotifyconfig4 4:4.14.0-1 ii libkparts44:4.14.0-1 ii libopencv-core2.4 2.4.9+dfsg-1+b1 ii libopencv-imgproc2.4 2.4.9+dfsg-1+b1 ii libphonon44:4.7.2-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libsolid4 4:4.14.0-1 ii libstdc++64.9.1-12 ii libthreadweaver4 4:4.14.0-1 ii perl 5.20.0-6 ii phonon4:4.7.2-1 Versions of packages digikam recommends: ii iceweasel [www-browser] 31.1.0esr-1 ii kipi-plugins 4:4.1.0-1+b1 ii konqueror [www-browser] 4:4.14.0-1 ii mplayerthumbs4:4.14.0-1 ii w3m [www-browser]0.5.3-17 Versions of packages digikam suggests: pn digikam-doc none ii systemsettings 4:4.11.11-1 -- 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#736106: Sourceless file
Hi, Why not 3. Create a separate package with a recommend/suggest relation between both? Eric Felix Natter fnat...@gmx.net wrote: Felix Natter fnat...@gmx.net writes: hello Bastien, thanks for pointing this out. Can we keep the package (in main) until I fix this in Freeplane 1.3.x (will be released in a few months [1]), or do I need to fix it _right now_? [1] Then I would fix it cleanly and disable the Flash export upstream. I've talked to upstream and it turns out the source code is in another git repository: https://github.com/freeplane/misc/tree/master/flash-browser I see two solutions: 1. tell upstream to include the source (~300k) in all source packages 2. ZIP those files and include them as a Debian patch. (2) could easily be done for 1.2.23. Thanks and Best Regards, -- Felix Natter __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions. -- Sent from my tablet. Please excuse my brevity.
Bug#735892: libknopflerfish-osgi-framework-java: doesn't depend on default-jre and enforces installation of version 6 openjdk
Package: libknopflerfish-osgi-framework-java Version: 2.3.3-2 Severity: normal Hi, as the subject says, the package doesn't depend on default-jre which leads to installation to openjdk-6-jre in addition to the version 7 that is already installed. One could argue that it's a wish rather than a bug, but given that we want to get rid of openjdk6 for the next release of Debian, I allowed myself to log this report as a normal bug. Cheers, Eric -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731041: plasma-widgets-workspace: device notifier reacts to inserted removable medias only after action on it.
Hello, I did the tests and that was interesting: On 02/12/13 08:10, Eric Lavarde wrote: - did you try this using different users accounts? (special bonus if you try in a newly created one). Other users: yes. New user, no, but I'll do together with the below tests and come back to you. Other (new) user: exactly same behavior. - run udisksctl monitor and then plug one of the devices you mentioned in your bug. Please attach the output. That was the interesting bit: I did this, and udisksctl showed the same behaviour: the SD-card appeared only after I had executed file -s on it (though it would appear in dmesg), and the same thing for disappearing by the way (which I didn't notice before). Output is attached as udisksctl.monitor.log and contains also my comments in the form === COMMENT === so that you have the correct time sequence of events. Interestingly enough, I tried a few more things with 2 USB sticks (captured in udisksctl.stick.monitor.log): - a USB3/partitioned with FAT and ext4 stick behaves normally. - a USB2/ISO partitioned stick doesn't appear at all in KDE, even when using the magic 'file -s' command. - send the output of dpkg -l udisks2 $ dpkg -l udisks2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii udisks22.1.1-1 amd64D-BUS service to access and manip Please note that I'm just asking the normal questions as I could find for this issue on the web, I'm not familiar with how KDE does handle this things. That's the point, everything outside of KDE (dmesg, pmount) looks the same as before to me, only KDE behaves strange. And GIMF as well OK, now I'm a bit confused, if it's a udisks2 or KDE issue, or some of both... It could be related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978 which shows a very similar behavior. The kernel parameter given at the end helps indeed, but the USB stick with ISO filesystem still doesn't appear. Perhaps two different issues, but no time left for further tests, I'll come back later. Any further idea welcome, Eric Monitoring the udisks daemon. Press Ctrl+C to exit. 12:32:31.795: The udisks-daemon is running (name-owner :1.19). === SD-card plugged in (nothing happens) === === file -s /dev/sde === 12:32:47.134: /org/freedesktop/UDisks2/drives/Crucial_CT120M500SSD1_1319093B5946: org.freedesktop.UDisks2.Drive.Ata: Properties Changed SmartUpdated: 1385983967 12:32:47.239: /org/freedesktop/UDisks2/drives/WDC_WD10EARX_00N0YB0_WD_WCC0S0232458: org.freedesktop.UDisks2.Drive.Ata: Properties Changed SmartUpdated: 1385983967 12:34:14.657: /org/freedesktop/UDisks2/block_devices/sde: Added interface org.freedesktop.UDisks2.PartitionTable Type: dos 12:34:14.658: /org/freedesktop/UDisks2/drives/Generic__SD_2fMMC_2002153705700: org.freedesktop.UDisks2.Drive: Properties Changed TimeMediaDetected:1385984054653811 MediaAvailable: true Size: 1967128576 12:34:14.659: /org/freedesktop/UDisks2/block_devices/sde: org.freedesktop.UDisks2.Block: Properties Changed Size: 1967128576 12:34:15.192: Added /org/freedesktop/UDisks2/block_devices/sde1 org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice:'/' Device: /dev/sde1 DeviceNumber: 2113 Drive: '/org/freedesktop/UDisks2/drives/Generic__SD_2fMMC_2002153705700' HintAuto: true HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: false Id: by-uuid-48F1-0A02 IdLabel:KINGSTON2GB IdType: vfat IdUUID: 48F1-0A02 IdUsage:filesystem IdVersion: FAT16 MDRaid: '/' MDRaidMember: '/' PreferredDevice:/dev/sde1 ReadOnly: true Size: 1967058432 Symlinks: /dev/disk/by-id/usb-Generic-_SD_MMC_2002153705700-0:2-part1 /dev/disk/by-label/KINGSTON2GB /dev/disk/by-path/pci-:00:1d.7-usb-0:5:1.0-scsi-0:0:0:2-part1 /dev/disk/by-uuid/48F1-0A02 org.freedesktop.UDisks2.Filesystem: MountPoints: org.freedesktop.UDisks2.Partition: Flags: 0 IsContained:false IsContainer:false Name: Number
Bug#731041: plasma-widgets-workspace: device notifier reacts to inserted removable medias only after action on it.
Package: plasma-widgets-workspace Version: 4:4.10.5-3 Severity: normal Hi, I apologize for the clumsy subject, but I didn't know how to summarize the issue properly. Here is what happens anyway: 1. I plug a removable media (SD-card, Android phone as mass storage, no difference). 2. The device notifier doesn't show it in its list (dmesg shows it though). 3. if I call 'file -s /dev/sdi' then device notifier shows the media at once (file without -s doesn't do the trick, no clue what it makes for a difference to KDE), and I can mount it at a click of a mouse. 4. If I unplug and replug the device, it then _generally_ works as expected and KDE recognizes the device without help. I hope you can fix this, because the workaround is not exactly something I can explain to my users (wife, daughter...). Let me know if you need more information, the problem is repeatable. Thanks, Eric -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widgets-workspace depends on: ii libc6 2.17-93 ii libkdecore5 4:4.11.3-2 ii libkdeui5 4:4.11.3-2 ii libkdewebkit5 4:4.11.3-2 ii libkio5 4:4.11.3-2 ii libkunitconversion4 4:4.11.3-2 ii libplasma34:4.11.3-2 ii libplasmaclock4abi3 4:4.10.5-3 ii libqt4-declarative4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-network4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-xml4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtcore44:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtwebkit4 2.2.1-7 ii libstdc++64.8.2-1 ii libx11-6 2:1.6.2-1 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-1 ii libxfixes31:5.0.1-1 ii libxrender1 1:0.9.8-1 ii plasma-dataengines-workspace 4:4.10.5-3 plasma-widgets-workspace recommends no packages. plasma-widgets-workspace 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#731041: plasma-widgets-workspace: device notifier reacts to inserted removable medias only after action on it.
Hi (again), Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: I can explain to my users (wife, daughter...). Let me know if you need more information, the problem is repeatable. Well, I can't reproduce this behavior. Actually I normally use a lot the device notifier and I don't remember it failing since the version in Wheezy. Wheezy was working well, I have the issue since moved to Jessie. I would like to ask you: - did you try this in more than one machine? That assumes I have another machine to try it on - did you try this using different users accounts? (special bonus if you try in a newly created one). Other users: yes. New user, no, but I'll do together with the below tests and come back to you. - run udisksctl monitor and then plug one of the devices you mentioned in your bug. Please attach the output. - send the output of dpkg -l udisks2 Please note that I'm just asking the normal questions as I could find for this issue on the web, I'm not familiar with how KDE does handle this things. That's the point, everything outside of KDE (dmesg, pmount) looks the same as before to me, only KDE behaves strange. And GIMF as well Anyway, thanks for caring, Eric Kinds regards, Lisandro. -- Sent from my tablet. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729742: blinken: Fails to produce sounds
Package: blinken Version: 4:4.8.4-1 Severity: important Hi, I just installed blinken for my daughter and it mostly doesn't produce sounds. When I press one of the four buttons, it generally remains silent, but sometimes it produces half a sound (like it would start a sound but then it's cut in the middle). I didn't really find any hint on where the problem might lie, but here some info: 1. Started from the console, the only output is: [0x11462a8] main services discovery error: no suitable services discovery module 2. ~/.xsession-errors doesn't contain anything suspicious (just the start of blinken is registered). 3. Blinken is the only application impacted, everything else works (e.g. Skype). 4. Testing sound in the KDE Audio Setup / Phonon KDE Controle Module works as well. 5. I am the opinion that on the same machine, but with Debian 32 bits, the sound did work (but it's already a while ago that I reinstalled in 64 bits). Let me know if I can do something to help find the issue. Eric -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blinken depends on: ii kde-runtime 4:4.8.4-2 ii libc62.13-38 ii libkdecore5 4:4.8.4-4 ii libkdeui54:4.8.4-4 ii libphonon4 4:4.6.0.0-3 ii libqt4-svg 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui44:4.8.2+dfsg-11 ii libstdc++6 4.7.2-5 ii phonon 4:4.6.0.0-3 ii ttf-sjfonts 2.0.2-1.1 blinken recommends no packages. Versions of packages blinken suggests: ii khelpcenter4 4:4.8.4-2 -- 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#681691: os-prober relies on grub-mount which fails silently on missing fuse module
Package: os-prober Version: 1.58 Followup-For: Bug #681691 Hello, there was no reaction on this bug which actually makes my life miserable each time there is a kernel update, because I need to mount all relevant partitions by hand. Anyway, I looked a bit more about it and found the following: 1. os-prober calls /usr/lib/os-prober/newns /usr/bin/os-prober which itself calls /usr/lib/os-probes/50mounted-tests /dev/sda2 (for example). 2. 50mounted-tests relies itself on grub-mount to mount the partition. 3. The call to grub-mount looks as such: mounted= if type grub-mount /dev/null 21 \ type grub-probe /dev/null 21 \ grub-mount $partition $tmpmnt 2/dev/null; then mounted=1 4. Calling grub-mount gives then the following error: # grub-mount /dev/sda2 /mnt fuse: device not found, try 'modprobe fuse' first # echo $? 0 # modprobe fuse FATAL: Module fuse not found. i.e. we have multiple errors combined to make a big mess: a. grub-mount relies on a fuse module which doesn't exist (by default). b. it fails with an error message but a successful return code. c. 50mounted-tests thinks that the command is successful (and hides the error message which could have been helpful). Conclusion, I think this bug should be duplicated, once to fix grub-mount resp. grub-common package, once to fix os-prober (at least to improve error handling, at best to stop using grub-mount). I'd be more than happy to read your opinion. Thanks, Eric -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (1000, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8.11+vdr2 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.17-93 os-prober recommends no packages. os-prober 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#681691: os-prober relies on grub-mount which fails silently on missing fuse module
Hello again, On 09/11/13 14:34, Eric Lavarde wrote: i.e. we have multiple errors combined to make a big mess: a. grub-mount relies on a fuse module which doesn't exist (by default). b. it fails with an error message but a successful return code. c. 50mounted-tests thinks that the command is successful (and hides the error message which could have been helpful). Small correction: the fuse module does (of course, stupid me) exist per default, but points b and c remain valid, failure must be properly handled. Thanks again, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714524: [freeplane] Keystrokes no longer recognised during use
Hi, as written on another thread, it would be good to know if you can reproduce the issue with another Java application like jedit (packaged in Debian). This way we would know if it's a Java or Freeplane/FreeMind issue. Cheers, Eric On 01/11/13 09:29, Omega Weapon wrote: Good to see that someone other than me has this issue too :) On 31/10/13 18:51, Felix Natter wrote: hi, @Martin: unfortunately I cannot reproduce your problem (same JDK, same Freeplane, same kernel/architecture; I am also using jessie) from your description. (Upstream can only try to fix this if it's reproducible) Just to be sure: did you try to press ESC when this happens? Best Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725017: closed by Markus Koschany a...@gambaru.de (Bug#713144: fixed in freemind 0.9.0+dfsg-3)
Hi, On 18/10/13 19:52, Edward Welbourne wrote: Do you know of other applications that use the same UI toolset, that I could test out to see if they have the same problem ? As former maintainer of the Freeplane/FreeMind packages, let me jump in here: we often used jedit in the past as a guinea pig that shows if a problem is due to Java and its environment, or to FreeMind/Freeplane. Hope this helps, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726879: jedit: depends solely on virtual packages (javaX-runtime)
Package: jedit Version: 5.0.0+dfsg-3 Severity: normal Hi, I just noticed that jedit depends only on java7-runtime | java6-runtime, which are both virtual packages. It is allegedly a breach of policy, I've been told but the only place I could find is chapter 7.4: To specify which of a set of real packages should be the default to satisfy a particular dependency on a virtual package, list the real package as an alternative before the virtual one. Anyway, from a practical standpoint, it means that a user trying to install this package without having yet the dependency resolved, will get a question about which package he wants to install to resolve the virtual dependency, and it's a question normal/dumb/simple users don't know how to answer (and don't need to). This dependency in the control file would simply solve the issue: Depends: default-jre | java7-runtime | java6-runtime Cheers, Eric -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723582: Bug#724324: RFS: metar/0.2-1 ITP
The other question might be if this new package is really required because both
seem to do the same thing...
Fernando, you're the upstream author, you might want to join forces with the
other author.
Eric
Tobias Frost t...@frost.de wrote:
Hallo Fernando,
please do not open new bug when you upload a new (not-uploaded)
version
to mentors, just reply to your old bug. (I merged both bugs)
There, you should describe what you changed since the last update.
Ok, lets take a look.
-- Package name metar is already taken. You'll need a differnt one.
http://packages.qa.debian.org/m/metar.html
-- Check your linitian warnings before uploading.
Because you created a native package, which is not what you want.
See the linitan messges (W) native-package-with-dash-version and
(I) missing-debian-source-format
-- (W) binary-without-manpage /usr/bin/metar does not have a manpage.
-- please fix (I) mdescription-synopsis-might-not-be-phrased-properly
-- As you are upstream, please add upstream a changelog.
-- please add a dep5-style debian/copyright file.
-- I'd suggest debian/compat 9 not 8 (and build-depend on debhelper
9)
-- before uploading, you should update the timestamp in your
changelog.
(dch -r)
-- There's a warning: package metar: unused substitution variable
${perl:Depends} --- You need to depend in your binary package on
${perl:Depends} not just on perl, I think
Best regards,
coldtobi
Am Montag, den 23.09.2013, 20:42 +0200 schrieb Fernando:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package metar
* Package name: metar
Version : 0.2-1
Upstream Author : Fernando Iazeolla xna...@yahoo.it
* URL : http://githib.com/elboza/metar
* License : GPL
Section : utils
It builds those binary packages:
metar - a simple command line metar and taf.
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/metar
Alternatively, one can download the package with dget using this
command:
dget -x
http://mentors.debian.net/debian/pool/main/m/metar/metar_0.2-1.dsc
More information about metar can be obtained from
http://github.com/elboza/metar.
Changes since the last upload:
metar (0.2-1) unstable; urgency=low
* Initial release (Closes: #723827)
-- Fernando Iazeolla xna...@yahoo.it Mon, 09 Sep 2013 22:32:41
+0200
Regards,
Fernando Iazeolla
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive:
http://lists.debian.org/1379965383.12473.15.ca...@mordor.loewenhoehle.ip
--
Sent from my tablet. Please excuse my brevity.
Bug#585149: iceweasel: No sound in videos using the html5 audio tag
Package: iceweasel
Version: 22.0-1~bpo70+1
Followup-For: Bug #585149
Hello,
I'd like to come back on this bug as it's flagged 'more info'. I found
out that 2 different pages on the same server and, obviously, the same
browser and browser environment show different behaviors depending on
the procedure used to produce sound.
If you go to the page http://www.heise.de/ct/Mitmachen/Browserdemo/ and
open the first (1. Platz/Landschaft) and the third (3. Platz/Doc Snyder)
demos and click on the blue button labeled Demo öffnen, you'll notice the
following:
* I hear the sound of the 1st demo, whereas it's playing sound using
JavaScript function (in demo.js using code like
'audio = new Audio(music.wav); etc...').
(Side note: you can click either Ohne Schatten or Mit Schatten,
it's just to get the demo without or with shadows).
* But I don't hear the sound of the 2nd demo where it's rendered using
the audio tag as in
audio id=soundtrack preload=auto loop=loop
source src=audio/ct_intro.ogg type=audio/ogg/
source src=audio/ct_intro.mp3 type=audio/mpeg/
/audio
So, if it's not the desktop environment and not the server environment,
there must be something wrong with the browser, which should be able to
render sound independently from the method used to make it render this
sound.
Hope this helps,
Eric
-- Package-specific info:
-- Extensions information
Name: CheckPlaces
Location: ${PROFILE_EXTENSIONS}/checkpla...@andyhalford.com.xpi
Status: enabled
Name: Default theme
Location:
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: Deutsch (DE) Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-de
Status: enabled
Name: English (GB) Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack-en...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-en-gb
Status: enabled
Name: Flash and Video Download
Location: ${PROFILE_EXTENSIONS}/{bee6eb20-01e0-ebd1-da83-080329fb9a3a}
Status: enabled
Name: Français Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-fr
Status: enabled
Name: Lazarus: Form Recovery
Location: ${PROFILE_EXTENSIONS}/laza...@interclue.com.xpi
Status: enabled
Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled
Name: Novell Moonlight
Location: ${PROFILE_EXTENSIONS}/moonli...@novell.com
Status: app-disabled
Name: Polski Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-pl
Status: enabled
-- Plugins information
Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Accelerator
Location: /opt/google/talkplugin/libnpgtpo3dautoplugin.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled
Name: Shockwave Flash (11,2,202,297)
Location: /usr/lib/flashplayer-mozilla/libflashplayer.so
Package: flashplayer-mozilla
Status: enabled
Name: Skype Buttons for Kopete
Location: /usr/lib/mozilla/plugins/skypebuttons.so
Package: kopete
Status: enabled
-- Addons package information
ii flashplayer-mo 3:11.2.202.2 amd64Macromedia Flash Player.
ii google-talkplu 4.4.2.0-1amd64Google Talk Plugin
ii iceweasel 22.0-1~bpo70 amd64Web browser based on Firefox
ii iceweasel-l10n 1:22.0-1~bpo all German language package for Icewe
ii iceweasel-l10n 1:22.0-1~bpo all English (United Kingdom) language
ii iceweasel-l10n 1:22.0-1~bpo all French language package for Icewe
ii iceweasel-l10n 1:22.0-1~bpo all Polish language package for Icewe
ii kopete 4:4.8.4-1+b1 amd64instant messaging and chat applic
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iceweasel depends on:
ii debianutils 4.3.2
ii fontconfig 2.9.0-7.1
ii libatk1.0-0 2.4.0-2
ii libc6 2.13-38
ii libcairo2 1.12.2-3
ii libfontconfig1 2.9.0-7.1
ii libfreetype62.4.9-1.1
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-02.33.12+really2.32.4-5
ii libgtk2.0-0 2.24.10-2
ii libnspr42:4.10-1~bpo70+1
ii libpango1.0-0 1.30.0-1
ii libsqlite3-03.7.13-1+deb7u1
ii libstdc++6 4.7.2-5
ii procps
Bug#720675: kipi-plugins: Export to HTML doesn't use selected search but current view
Package: kipi-plugins Version: 4:2.6.0-1+b2 Severity: normal Hello, I've started to use again the HTML export function (from within digikam) after a long while, and it doesn't work anymore the way it should: 1. create a stored search 2. select _another_ search or another album (in order to be able to make the difference and see that something is wrong). 3. Menu Export - Export to HTML... - My Searches 4. Select the search created at step 1 5. The output contains the images from the view selected on step 2 and not what is chosen on step 4. If you select multiples searches in step 4, you get multiple times the same wrong output! It doesn't depend on the export theme chosen. I would appreciate a bugfix in Wheezy because I don't know how to work around this bug. Thanks, Eric -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kipi-plugins depends on: ii digikam 4:2.6.0-1+b2 ii kde-runtime 4:4.8.4-2 ii kipi-plugins-common 4:2.6.0-1 ii libc6 2.13-38 ii libexpat1 2.1.0-1 ii libgcc1 1:4.7.2-5 ii libgl1-mesa-glx [libgl1] 8.0.5-4+deb7u2 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgomp1 4.7.2-5 ii libgpod4-nogtk0.8.2-7 ii libjpeg8 8d-1 ii libkcalcore4 4:4.8.4-2 ii libkdcraw20 4:4.8.4-1 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkexiv2-10 4:4.8.4-1 ii libkio5 4:4.8.4-4 ii libkipi8 4:4.8.4-1 ii libksane0 4:4.8.4-1 ii libopencv-core2.3 2.3.1-11 ii libopencv-highgui2.3 2.3.1-11 ii libopencv-imgproc2.3 2.3.1-11 ii libopencv-legacy2.3 2.3.1-11 ii libopencv-objdetect2.32.3.1-11 ii libphonon44:4.6.0.0-3 ii libpng12-01.2.49-1 ii libqca2 2.0.3-4 ii libqjson0 0.7.1-7 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-network4:4.8.2+dfsg-11 ii libqt4-opengl 4:4.8.2+dfsg-11 ii libqt4-svg4:4.8.2+dfsg-11 ii libqt4-xml4:4.8.2+dfsg-11 ii libqt4-xmlpatterns4:4.8.2+dfsg-11 ii libqtcore44:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsolid4 4:4.8.4-4 ii libstdc++64.7.2-5 ii libthreadweaver4 4:4.8.4-4 ii libtiff4 3.9.6-11 ii libxml2 2.8.0+dfsg1-7+nmu1 ii libxrandr22:1.3.2-2+deb7u1 ii libxslt1.11.1.26-14.1 ii phonon4:4.6.0.0-3 Versions of packages kipi-plugins recommends: ii enblend 4.0+dfsg-4+b3 ii enfuse 4.0+dfsg-4+b3 ii hugin2011.4.0+dfsg-5 ii imagemagick 8:6.7.7.10-5 ii konqueror4:4.8.4-2 Versions of packages kipi-plugins suggests: pn gallery none ii gimp 2.8.2-2 ii kmail 4:4.4.11.1+l10n-3+b1 pn vorbis-tools none -- 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#720451: Program scan unusable for KabelBW users; no longer works with file, /usr/share/dvb/dvb-c/de-KabelBW
Hi, On 22/08/13 07:15, David wrote: Program scan is now unusable for users of Cable Digital TV KabelBW - file /usr/share/dvb/dvb-c/de-KabelBW Cause: Unknown. The reason might just be that KabelBW quite heavily re-shuffled its programs a few months ago (I don't know if it helps the resolution though :-)). Cheers, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684604: eclipse 3.8 hangs on splash screen if workspace uses unavailable plugins
Package: eclipse Version: 3.8.0~rc4-1 Followup-For: Bug #684604 Hi, I have had the same (or a very similar) problem. I have solved it on my own but I wanted to tell my experience to help for a better resolution. Basically, I had done a complete reinstall of my PC (formerly with architecture i386, new with amd64, in case it's important), but kept my home drive (with workspaces and ~/.eclipse directories). Using the command /usr/lib/eclipse/eclipse -consoleLog -debug, I noticed error messages regarding missing plugin libraries (com.android Sorry, I didn't keep it). The solution was then to open a new workspace, reinstall all the missing plugins, and then restart into the old faulty workspace, which worked without further issue. One of my tries was to delete ~/.eclipse but it didn't help, but perhaps it was part of the final resolution, difficult to tell now. Two last remarks: 1. Perhaps not all plugins lead to this issue, I suspect strongly the Android ADT plugin and/or dependencies, but I had other plugins like egit. 2. Even if it's possible to overcome this issue of missing plugins, it should still be handled more nicely by eclipse, providing a clear message to the user about missing plugins and allowing him/her to install these missing plugins, without having to create a new workspace to do this. Hope this helps, Eric -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eclipse depends on: ii eclipse-jdt 3.8.0~rc4-1 ii eclipse-pde 3.8.0~rc4-1 eclipse recommends no packages. eclipse suggests no packages. Versions of packages eclipse-platform depends on: ii ant1.8.2-4 ii ant-optional 1.8.2-4 ii default-jre [java6-runtime]1:1.6-47 ii eclipse-platform-data 3.8.0~rc4-1 ii eclipse-rcp3.8.0~rc4-1 ii gconf-service 3.2.5-1+build1 ii java-common0.47 ii libc6 2.13-38 ii libcommons-codec-java 1.6-1 ii libcommons-httpclient-java 3.1-10.2 ii libcommons-logging-java1.1.1-9 ii libgconf-2-4 3.2.5-1+build1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libjetty8-java 8.1.3-4 ii libjsch-java 0.1.42-2 ii liblucene2-java2.9.4+ds1-4 ii libservlet3.0-java 7.0.28-4 ii multiarch-support 2.13-38 ii openjdk-6-jre [java6-runtime] 6b27-1.12.6-1~deb7u1 ii sat4j 2.3.1-1 Versions of packages eclipse-platform recommends: ii eclipse-pde 3.8.0~rc4-1 Versions of packages eclipse-platform suggests: ii eclipse-jdt 3.8.0~rc4-1 Versions of packages eclipse-pde depends on: ii default-jre [java6-runtime]1:1.6-47 ii eclipse-jdt3.8.0~rc4-1 ii eclipse-platform 3.8.0~rc4-1 ii libasm3-java 3.3.2-1 ii openjdk-6-jre [java6-runtime] 6b27-1.12.6-1~deb7u1 eclipse-pde suggests no packages. Versions of packages eclipse-jdt depends on: ii default-jre [java6-runtime]1:1.6-47 ii eclipse-platform 3.8.0~rc4-1 ii junit 3.8.2-8 ii junit4 4.10-3 ii libhamcrest-java 1.2-2 ii openjdk-6-jre [java6-runtime] 6b27-1.12.6-1~deb7u1 Versions of packages eclipse-jdt recommends: ii default-jdk 1:1.6-47 eclipse-jdt 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#661335: linux-image-3.9-1-amd64: Bug still present in version 3.9.1
Hi, On 22/06/13 13:36, ygmarchi wrote: Package: src:linux Version: 3.9.6-1 Followup-For: Bug #661335 Dear Maintainer, as of version 3.9-1 the problem still persist (and after on 1 and a half year after having been reported). Interestingly enough: the problem has gone away since version 3.6 for me (see https://bugzilla.kernel.org/show_bug.cgi?id=42955) and is still absent on 3.8 (I didn't try to move to 3.9, yet), but the fix hasn't yet been back-ported to 3.2/wheezy. As the bug hasn't really been fixed but just happened to disappear (for me), it might be that it reappeared on 3.9, or that we are facing 2 issues. Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697885: iceweasel: Search engine keywords disappear during upgrade
Package: iceweasel
Version: 20.0-1
Followup-For: Bug #697885
Hi,
I recently upgraded (almost pure wheezy) from 10.0.12esr-1 (wheezy) to 20.0-1
(experimental) and all the keywords I had entered for search engines
have disappeared, making the search shortcuts (as described by the original
reporter) not work anymore. I didn't notice that any search engine
disappeared, but, with few exceptions, I mostly use only my own search
engines.
It would be nice to have an upgrade procedure that doesn't lose the
keywords.
Thanks, Eric
-- Package-specific info:
-- Extensions information
Name: CheckPlaces
Location: ${PROFILE_EXTENSIONS}/checkpla...@andyhalford.com.xpi
Status: enabled
Name: Default theme
Location: /usr/lib/iceweasel/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: Deutsch (DE) Language Pack locale
Location: /usr/lib/iceweasel/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-de
Status: enabled
Name: English (GB) Language Pack locale
Location: /usr/lib/iceweasel/extensions/langpack-en...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-en-gb
Status: enabled
Name: Flash and Video Download
Location: ${PROFILE_EXTENSIONS}/{bee6eb20-01e0-ebd1-da83-080329fb9a3a}
Status: enabled
Name: Français Language Pack locale
Location: /usr/lib/iceweasel/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-fr
Status: enabled
Name: Lazarus: Form Recovery
Location: ${PROFILE_EXTENSIONS}/laza...@interclue.com.xpi
Status: enabled
Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled
Name: Novell Moonlight
Location: ${PROFILE_EXTENSIONS}/moonli...@novell.com
Status: app-disabled
Name: Polski Language Pack locale
Location: /usr/lib/iceweasel/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-pl
Status: enabled
-- Plugins information
Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Accelerator
Location: /opt/google/talkplugin/libnpgtpo3dautoplugin.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled
Name: HP Virtual Rooms Plug-in
Location: /home/ericl/.mozilla/plugins/hpvirtualrooms-plugin.so
Status: enabled
Name: IcedTea-Web Plugin (using IcedTea-Web 1.3.2 (1.3.2-1))
Location: /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so
Package: icedtea-7-plugin:i386
Status: enabled
Name: Shockwave Flash
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled
Name: Skype Buttons for Kopete
Location: /usr/lib/mozilla/plugins/skypebuttons.so
Package: kopete
Status: disabled
-- Addons package information
ii google-talkplu 3.17.0.0-1 i386 Google Talk Plugin
ii icedtea-7-plug 1.3.2-1 i386 web browser plugin based on OpenJ
ii iceweasel 20.0-1 i386 Web browser based on Firefox
ii iceweasel-l10n 1:20.0-1 all German language package for Icewe
ii iceweasel-l10n 1:20.0-1 all English (United Kingdom) language
ii iceweasel-l10n 1:20.0-1 all French language package for Icewe
ii iceweasel-l10n 1:20.0-1 all Polish language package for Icewe
ii kopete 4:4.8.4-1+b1 i386 instant messaging and chat applic
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iceweasel depends on:
ii debianutils 4.3.2
ii fontconfig 2.9.0-7.1
ii libc6 2.13-38
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-02.33.12+really2.32.4-5
ii libgtk2.0-0 2.24.10-2
ii libnspr42:4.9.2-1
ii libnspr4-0d 2:4.9.2-1
ii libsqlite3-03.7.13-1+deb7u1
ii libstdc++6 4.7.2-5
ii procps 1:3.3.3-3
ii xulrunner-20.0 20.0-1
iceweasel recommends no packages.
Versions of packages iceweasel suggests:
pn fonts-stix | otf-stix none
ii libgssapi-krb5-2 1.10.1+dfsg-5
pn mozplugger none
Versions of packages xulrunner-20.0 depends on:
ii libasound21.0.25-4
ii libatk1.0-0 2.4.0-2
ii libbz2-1.01.0.6-4
ii libc6 2.13-38
ii libcairo2 1.12.2-3
ii libdbus-1-3 1.6.8-1
ii libdbus-glib-1-2 0.100.2-1
ii libevent-2.0-52.0.19-stable-3
ii libfontconfig12.9.0-7.1
ii libfreetype6 2.4.9-1.1
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-02.26.1-1
ii libglib2.0-0
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Hello, I tried to log a bug upstream towards imonlcd [1] but the owner rejected it with reference to a 2 years old bug report [2] stating that the issue is in cXinelibPlayer. It would be really nice to _not_ be bumped between two plugins throwing the fault at each other... Thanks, Eric [1] http://projects.vdr-developer.org/issues/1364 [2] http://projects.vdr-developer.org/issues/611 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Hi again, sorry for the noise, but following the traces of this bug, I found this bug entry for https://sourceforge.net/projects/xineliboutput/ : https://sourceforge.net/tracker/?func=detailaid=3285701group_id=160063atid=814342 (2 years old, no update) Eric On 11/05/13 12:28, Eric Lavarde wrote: Hello, I tried to log a bug upstream towards imonlcd [1] but the owner rejected it with reference to a 2 years old bug report [2] stating that the issue is in cXinelibPlayer. It would be really nice to _not_ be bumped between two plugins throwing the fault at each other... Thanks, Eric [1] http://projects.vdr-developer.org/issues/1364 [2] http://projects.vdr-developer.org/issues/611 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #704259 Hello again, my disk crashed and I had to reinstall almost from crash :-( After this, I decided to redo a thorough test, and finished by doing two: 1. the first one, marked with 4946, shows a strange behavior where vdr-sxfe even complains that it can't open a non-seekable file, see vdr-sxfe.4946.log 2. the second one is the traditionnal issue with a segfault in iMonLCD (see vdr.5272.syslog), but the core file analysis sounds to me a bit different than previous ones. As always, core files available: http://eric.lavar.de/comp/TEST/vdr.4946.core.xz http://eric.lavar.de/comp/TEST/vdr.5272.core.xz As I'm conscious that debugging is made difficult by the fact that you don't have an imonlcd, just give me instructions and I'll do my best. Thanks, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (1001, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8.5+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.13-38 ii libextractor3 1:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-2.0.0-multipatch] 2.0.1-1~etobi1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++-==-==--== ii libdvdread44.2.0+20120521-2 amd64 library for reading DVDs un libxine-xvdr keine (keine Beschreibung vorhanden) ii libxine2-xvdr 1.0.7+cvs20130223.2117-6 amd64 Xine input plugin for vdr-plugin-xineliboutput streams ii libxine2-xvdr-dbg 1.0.7+cvs20130223.2117-6 amd64 Xine input plugin for vdr-plugin-xineliboutput streams un linux-doc-3.8.5+vdr1 keine (keine Beschreibung vorhanden) ii linux-image-3.8.5+vdr1 3.8.5-1~experimental.1+vdr1amd64 Linux kernel binary image for version 3.8.5+vdr1 un linux-image-3.8.5+vdr1-dbg keine (keine Beschreibung vorhanden) un linux-source-3.8.5+vdr1keine (keine Beschreibung vorhanden) ii vdr2.0.1-1~etobi1 amd64 Video Disk Recorder for DVB cards un vdr-abi-2.0.0-multipatch keine (keine Beschreibung vorhanden) ii vdr-addon-acpiwakeup 0.0.11 all Addon that enables vdr to wakeup itself using ACPI ii vdr-dbg2.0.1-1~etobi1 amd64 Debug symbols for the VDR Video Disc Recorder ii vdr-dev2.0.1-1~etobi1 all Video Disk Recorder for DVB cards ii vdr-markad 0.1.4-5amd64 Tool to mark advertisements in VDR recordings un vdr-plugin-dvbsddevice keine (keine Beschreibung vorhanden) ii vdr-plugin-dvd 0.3.6~b03+cvs20090426.0013-19 amd64 DVD playback plugin for VDR ii vdr-plugin-epgsearch 1.0.1~beta3-5 amd64 VDR plugin that provides extensive EPG searching capabilities ii vdr-plugin-femon 1.7.19-4 amd64 DVB frontend status monitor plugin for VDR ii vdr-plugin-imonlcd 1.0.1-3amd64 VDR plugin to show information on SoundGraph iMON LCD displays ii vdr-plugin-imonlcd-dbg 1.0.1-3amd64 VDR plugin to show information on SoundGraph iMON LCD displays ii vdr-plugin-live0.2.0+git20130305-6amd64 Web administration plugin for VDR ii vdr-plugin-markad 0.1.4-5amd64 Plugin for VDR to mark advertisements in recordings ii vdr-plugin-osdteletext
Bug#666742: xine image size issue.
reassign 666742 libxine2 thanks Thanks for jumping in, Darren, and thanks to Tobias for finding the root cause. Small email to reassign the bug to the right package, and, of course, I'd be more than happy to test soon your new version in experimental ;-) This said, I understand the point of being otherwise busy. Cheers, Eric Darren Salt said: You wrote: On 27/04/13 18:40, Tobias Grimm wrote: # xvinfo | grep -i image size maximum XvImage size: 4096 x 4096 Yep, my integrated Intel Graphic (on both my PCs), shows: maximum XvImage size: 2048 x 2048 I don't have a solution for this at hand, but will forward this issue upstream. Obviously xine should at least handle this gracefully. Well, asking for an image of the size of the screen and resizing the image from the file on the fly to make it fit would sound like an approach that would avoid the issue, but let's see what upstream suggests. https://bugs.xine-project.org/show_bug.cgi?id=108 and http://anonscm.debian.org/hg/xine-lib/xine-lib-1.2/rev/5da1bfeb appear to be relevant. This should have been back-ported some time ago (for various reasons, I've been... inactive); too late for wheezy now, I think, and I'm not aware of anything which would fix this for vdpau (and I can't usefully test vdpau anyway). All being well, there should be a new xine-lib release once wheezy's out. -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666742: xine image size issue.
Hi, On 27/04/13 18:40, Tobias Grimm wrote: # xvinfo | grep -i image size maximum XvImage size: 4096 x 4096 Yep, my integrated Intel Graphic (on both my PCs), shows: maximum XvImage size: 2048 x 2048 I don't have a solution for this at hand, but will forward this issue upstream. Obviously xine should at least handle this gracefully. Well, asking for an image of the size of the screen and resizing the image from the file on the fly to make it fit would sound like an approach that would avoid the issue, but let's see what upstream suggests. Thanks a lot for your patience, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking bigimages with xineliboutput plugin
Hi, Tobias Grimm said: On 21.04.2013 12:57, Eric Lavarde wrote: http://eric.lavar.de/comp/TEST/xine-no-dbg.core.gz http://eric.lavar.de/comp/TEST/xine-with-dbg.core.gz Not downloadable (403). Sorry, fixed now (wrong rights). Can you please provide some more failing images? I really would like to reproduce this somehow. Is this request still valid after my last email (the one where I create a blank picture and it still fails with xine, starting with a certain size)? The only major CPU difference between your system and mine is, that you have 4 cores while I only have 2. But we both use the MMX extensions. Should we ask on the VDR list people to do the same tests with ImageMagick and xine and see if we recognize a pattern? I can send the mail, just asking for your opinion before. Thanks, Eric -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #666742 Hi, you seem to be right, xine with the same image fails as well. I tried with and without the xine-dbg and libxine2-dbg packages installed, and you can find the result as usual attached; it didn't change the behavior, just the error output. The core files in both cases are again to be found under http://eric.lavar.de/comp/TEST/xine-no-dbg.core.gz http://eric.lavar.de/comp/TEST/xine-with-dbg.core.gz As a last minute idea, I also attach the output of xine on multiple images: you'll see that xine fails on big pictures, though in slightly different manners, but succeeds on smaller ones. Thanks, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.13-38 ii libextractor3 1:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-2.0.0-multipatch] 2.0.1-1~etobi1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information xine-dump.tgz Description: GNU Zip compressed data xine-no-dbg.multiple.out.gz Description: GNU Zip compressed data
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Hi,
I tried on my normal PC (I can't try VDR, but I can try xine), and I do
get a very similar behavior: big photos - bang, small photos - works.
After that, I got really curious and created test images:
$ i=100; while [ $i -le 3000 ]; do if [ $i -lt 1000 ]; then j=0$i; else
j=$i; fi; convert -size ${i}x${i} xc:white test${j}.jpg; i=$((i+100)); done
and tested them:
$ for i in test*.jpg; do echo $ixine.test; xine $i; echo RETURN:
$?xine.test; done
And found out this way that the problem appears between 2000x2000 and
2100x2100 pixels, and refining the result again and again, came to the
following results:
2048x2048 works
2049x2049 crashes
2048x2049 crashes
2049x2048 works
2050x2048 crashes
1024x4096 crashes
4096x1024 crashes
(sounds like someone has a buffer of a given size here...)
I also attach the output of /proc/cpuinfo (also an Intel-CPU, but 2
cores and older). BTW, my VDR is installed 64bits, my normal PC is 32bits.
Cheers, Eric
PS: as I assume that you will re-assign to libxine2, find below the specs.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (1001, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libxine2 depends on:
ii libxine2-bin 1.2.2-4
ii libxine2-misc-plugins 1.2.2-4
Versions of packages libxine2 recommends:
ii libxine2-doc [libxine-doc] 1.2.2-4
ii libxine2-ffmpeg 1.2.2-4
Versions of packages libxine2 suggests:
pn gxinenone
ii xine-ui 0.99.7-1
-- no debconf information
proc_cpuinfo.gz
Description: GNU Zip compressed data
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Package: xineliboutput-sxfe Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #666742 Hello, here the result from the debug exercise. The files with 18935 are the result without graphicsmagic-dbg installed, and with 21190 after I had installed graphicsmagic-dbg. The corresponding core files can be found as http://eric.lavar.de/comp/TEST/vdr-sxfe.18935.core.gz resp. http://eric.lavar.de/comp/TEST/vdr-sxfe.21190.core.gz The error seems to happen in libgraphicsmagick3 (version 1.3.16-1.1) but that doesn't explain why I should have the problem and not you. Hope this helps further anyway, Eric PS: the introduction of dbg capability was a great idea! I don't want to give the impression to only complain :P -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.6.8-1 ii libc6 2.13-38 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100.2-1 ii libgl1-mesa-glx [libgl1] 8.0.5-4 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libglu1-mesa [libglu1]8.0.5-4 ii libjpeg8 8d-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxine2 1.2.2-4 ii libxine2-x1.2.2-4 ii libxine2-xvdr 1.0.7+cvs20130223.2117-6 ii libxinerama1 2:1.1.2-1 ii libxrender1 1:0.9.7-1 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe suggests no packages. -- no debconf information vdr-sxfe.20130420.tgz Description: GNU Zip compressed data
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #704259 Hi, I've installed your library and it seems to work, somehow: 1. nothing especially bad happened 2. vdr doesn't dump anymore (but reproducing the bug is not always easy) 3. but vdr-sxfe now crashes without core dump (I attach the vdr-sxfe.log file). And I also had vdr-sxfe hang (without crashing), when I _started_ once the radio but it showed only in the syslog (attached). I also attach the vdr-sxfe.log file but I don't see anything of interest. There is also a core file due to me Ctrl+C-ing the vdr-sxfe, let me know if it could be of interest. So, to me it seems the imonlcd issue is probably fixed, but I'm now encountering other issues that were perhaps hidden behind that first bug. Let me know how I should proceed in terms of bug handling and overall further debugging. Sorry to keep you busy, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.13-38 ii libextractor3 1:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-2.0.0-multipatch] 2.0.1-1~etobi1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput 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#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Hello, sorry, I made a mistake: VDR did crash at the same time, and there was a core file (according to timestamp): I've uploaded it to http://eric.lavar.de/comp/TEST/vdr.Apr20_11-45.core.gz Sorry for the confusion but it looks like the problem is still there. Eric PS: the hang when starting an Internet Radio seems to be another problem then. Should I create a separate bug report? On 20/04/13 12:00, Eric Lavarde wrote: Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #704259 Hi, I've installed your library and it seems to work, somehow: 1. nothing especially bad happened 2. vdr doesn't dump anymore (but reproducing the bug is not always easy) 3. but vdr-sxfe now crashes without core dump (I attach the vdr-sxfe.log file). And I also had vdr-sxfe hang (without crashing), when I _started_ once the radio but it showed only in the syslog (attached). I also attach the vdr-sxfe.log file but I don't see anything of interest. There is also a core file due to me Ctrl+C-ing the vdr-sxfe, let me know if it could be of interest. So, to me it seems the imonlcd issue is probably fixed, but I'm now encountering other issues that were perhaps hidden behind that first bug. Let me know how I should proceed in terms of bug handling and overall further debugging. Sorry to keep you busy, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.13-38 ii libextractor3 1:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-2.0.0-multipatch] 2.0.1-1~etobi1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information ___ pkg-vdr-dvb-devel mailing list pkg-vdr-dvb-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-vdr-dvb-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20130223.2117-6 Followup-For: Bug #704259 Hello, I upgraded VDR using e-tobi as recommended, including the debug instructions (I also added a 'ulimit -c unlimited' and restarted VDR) and got a core dump. I refrain from attaching it to this bug report (13M compressed) but attach the output of the given gdb instructions (and also the stderr output, though I doubt that it is relevant), plus the corresponding extract from the syslog. Dmesg output looks like this: [ 234.965453] iMonLCD: watch [3332]: segfault at 2ba0 ip 7fea192337a6 sp 7fea1830ecf0 error 4 in libvdr-xineliboutput.so.2.0.0[7fea19207000+85000] [ 235.309405] release [ 235.310152] release [ 237.328482] WARNING: You are using an experimental version of the media stack. [ 237.328482] As the driver is backported to an older kernel, it doesn't offer [ 237.328482] enough quality for its usage in production. [ 237.328482] Use it with care. [ 237.328482] Latest git patches (needed if you report a bug to linux-me...@vger.kernel.org): [ 237.328482] 1323024fd3296537dd34da70fe70b4df12a308ec [media] siano: fix build with allmodconfig [ 237.328482] 6d9a06f27a640967fc95a36ccb2f2d69e2e71f8a Revert [media] siano: fix build with allmodconfig [ 237.328482] b41a536cf9806c3478b2fa68d59edafd0787e8aa [media] ds3000: remove useless 'locking' [ 237.328482] experimental: 97792f0dbfd3cc74eab03021cf563fcab7ce9462 experimental: Use the latest working release of media_build (2012-11-24). [ 237.328482] ngene-octopus-test: f8e6de9145a3d65737aa053253a79b42cf19456b ddbridge: Support Digital Devices Octopus CI single. [ 237.329103] Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH [ 237.329149] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter [ 237.329179] HW 00010007 REG 00010003 [ 237.329257] DDBridge :03:00.0: irq 49 for MSI/MSI-X [ 237.331011] Port 0 (TAB 1): DUAL DVB-C/T [ 237.331869] Port 1 (TAB 2): NO MODULE [ 237.332486] Port 2 (TAB 3): NO MODULE [ 237.332736] DVB: registering new adapter (DDBridge) [ 237.332738] DVB: registering new adapter (DDBridge) [ 237.333637] stv0367 found [ 237.605857] tda18212dd: ChipID 4724 [ 237.606314] tda18212dd: PowerState 01 [ 237.730570] DDBridge :03:00.0: DVB: registering adapter 0 frontend 0 (STV0367 DVB-C DVB-T)... [ 237.731689] stv0367 found [ 238.000291] tda18212dd: ChipID 4724 [ 238.000758] tda18212dd: PowerState 00 [ 238.254371] DDBridge :03:00.0: DVB: registering adapter 1 frontend 0 (STV0367 DVB-C DVB-T)... The core dump is available (for a limited time) at http://eric.lavar.de/comp/TEST/vdr.Apr13_12-35.core.gz Hope this helps to pin-point the issue, let me know what I can do further. Thanks, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc6 2.13-38 ii libextractor3 1:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-2.0.0-multipatch] 2.0.0-1~etobi4 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information vdr.Apr13_12-35.tgz Description: GNU Zip compressed data
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20120609.1902-1 Followup-For: Bug #704259 Hi, will try this in my test environment, in the mean time, I found a little bit more but it puzzles me a bit more also. I found in the syslog a segfault message coming from the kernel/iMonLCD (?!) before each VDR restart: # grep segfault /var/log/syslog Feb 24 19:53:09 hdvdr1 kernel: [11912.930544] iMonLCD: watch [3502]: segfault at 27e6020 ip 027e6020 sp 7fadd7180d68 error 15 Feb 28 20:00:17 hdvdr1 kernel: [ 2695.052721] iMonLCD: watch [2655]: segfault at 2ab8 ip 7f66e7dd2e86 sp 7f66dbcb6d20 error 4 in libvdr-xineliboutput.so.1.7.28[7f66e7da7000+84000] Mar 10 13:14:24 hdvdr1 kernel: [25714.757858] iMonLCD: watch [4826]: segfault at 2ab8 ip 7ffb6db7be86 sp 7ffb6b262d20 error 4 in libvdr-xineliboutput.so.1.7.28[7ffb6db5+84000] Mar 11 09:49:24 hdvdr1 kernel: [ 3296.484567] iMonLCD: watch [2638]: segfault at 2ab8 ip 7f5922403e86 sp 7f59167fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f59223d8000+84000] Mar 11 19:08:25 hdvdr1 kernel: [ 3398.925571] iMonLCD: watch [2648]: segfault at 2ab8 ip 7f99265f5e86 sp 7f991a7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f99265ca000+84000] Mar 12 19:56:57 hdvdr1 kernel: [ 2495.471267] iMonLCD: watch [2787]: segfault at 2ab8 ip 7f15d266be86 sp 7f15be7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f15d264+84000] Mar 15 19:59:09 hdvdr1 kernel: [ 7334.664648] iMonLCD: watch [2657]: segfault at 7f1b28075c90 ip 7f1b28075c90 sp 7f1b2effcd68 error 15 Mar 23 20:35:21 hdvdr1 kernel: [24330.004845] iMonLCD: watch [3802]: segfault at 2ab8 ip 7f01953e6e86 sp 7f0192accd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f01953bb000+84000] Mar 29 13:33:24 hdvdr1 kernel: [ 1653.994505] iMonLCD: watch [2825]: segfault at 2ab8 ip 7f45db070e86 sp 7f45ce7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f45db045000+84000] Mar 30 21:30:52 hdvdr1 kernel: [13016.569726] iMonLCD: watch [2794]: segfault at 0 ip (null) sp 7f2ca8ff8d98 error 14 in vdr[40+154000] Apr 3 21:32:08 hdvdr1 kernel: [ 1840.532476] iMonLCD: watch [2817]: segfault at 2ab8 ip 7fdb04c47e86 sp 7fdaf3ffed20 error 4 in libvdr-xineliboutput.so.1.7.28[7fdb04c1c000+84000] Apr 4 21:36:17 hdvdr1 kernel: [ 8452.432894] iMonLCD: watch [2822]: segfault at 2ab8 ip 7f497710fe86 sp 7f496a7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f49770e4000+84000] The lines before are irrelevant and the lines after more or less always the same and just documenting the restart of VDR (I've attached the latest example nevertheless). Cheers, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc62.13-38 ii libextractor31:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-1.7.28-debian] 1.7.28-1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information syslog-restart.txt.gz Description: GNU Zip compressed data
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Hi, On 05/04/13 21:25, Tobias Grimm wrote: On 05.04.2013 11:06, Eric Lavarde wrote: will try this in my test environment, in the mean time, I found a little bit more but it puzzles me a bit more also. I found in the syslog a segfault message coming from the kernel/iMonLCD (?!) before each VDR restart: Do you have the imonlcd-Plugin installed? yes, sources taken from your site, recompiled by myself for Debian (testing/unstable): # dpkg -s vdr-plugin-imonlcd Package: vdr-plugin-imonlcd Status: install ok installed Priority: extra Section: video Installed-Size: 161 Maintainer: Debian VDR Team pkg-vdr-dvb-de...@lists.alioth.debian.org Architecture: amd64 Version: 0.0.5+git20120512-1.3 Depends: libc6 (= 2.2.5), libfreetype6 (= 2.2.1), libgcc1 (= 1:4.1.1), libstdc++6 (= 4.1.1), zlib1g (= 1:1.1.4), vdr-abi-1.7.28-debian [...] Cheers, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704254: xineliboutput-sxfe: vdr-sxfe fails if VDR isn't running or restarted
Package: xineliboutput-sxfe Version: 1.0.7+cvs20120609.1902-1 Severity: wishlist Hi, the situation is quite clear: if vdr isn't running or is being restarted, vdr-sxfe fails ungracefully. After a while, in general, vdr restarts gain, but vdr-sxfe is dead and needs to be restarted. A behavior such that vdr-sxfe shows an error message but waits until VDR is back would be much more user friendly. Thanks, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.6.8-1 ii libc6 2.13-38 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-2 0.100.2-1 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libglu1-mesa [libglu1]8.0.5-3 ii libjpeg8 8d-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxine2 1.2.2-4 ii libxine2-x1.2.2-4 ii libxine2-xvdr 1.0.7+cvs20120609.1902-1 ii libxinerama1 2:1.1.2-1 ii libxrender1 1:0.9.7-1 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe 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#704154: vdr - Fails if started without any of CAP_SYS_TIME, CAP_SYS_NICE or CAP_NET_RAW
Hi Bastian, On 29/03/13 01:38, Tobias Grimm wrote: I'm not sure, if this qualifies for a serious severity, turning this into an RC bug. A serious bug is, quoting [1], a severe violation of Debian policy (roughly, it violates a must or required directive), or, in the package maintainer's or release manager's opinion, makes the package unsuitable for release. I checked again the Debian policy but couldn't spot anything relevant, so it would be nice to get a pointer, or alternatively an argument why the package should be unsuitable for release, especially so late into the freeze period. No Debian user would appreciate losing VDR in wheezy because of a bug happening in the seldom case someone considers their VDR system so sensitive in terms of security that they remove capabilities. Furthermore this bug is possibly security-related but definitely not a security hazard, which would anyway qualify for grave and not serious. Thanks, Eric [1] http://www.debian.org/Bugs/Developer#severities -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20120609.1902-1 Severity: normal Tags: upstream Hello, I hesitated to create this bug because now that I'm addressing it I can't reproduce it but it happens so often, it will come again, the question is if I'll be ready to check it at that time, so here you are... I'm using the xineliboutput plugin to hear Internet Radio under VDR (there are other means but they are even less stable), by creating a playlist (some attached) which can be browsed to and played like any other music file. The issue is that, after having been heard a while (some hours in general, but I don't know the limit which makes testing difficult), VDR crashes when I press the stop or the blue button. I lived with it until now because I'm generally not in a situation to debug when it happens, and because I had other issues with VDR that I tackled in the mean time, so now I'd like to have a harder look at it. Hence I created this bug for multiple reasons: 1. learn if I'm the only one who has this issue... 2. ask if someone has a smart idea how I could debug such an irregular bug which takes so much time to appear. 3. in general, I'm really willing to learn how to debug VDR as to avoid the same situation as for Bug#666742 where I seem to be the only having the issue. Just give me clear instructions (RTFM _with a link_ is fine as well)! Thanks, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc62.13-38 ii libextractor31:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-1.7.28-debian] 1.7.28-1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information m3u.tgz Description: GNU Zip compressed data
Bug#701578: nodm considers uid instead of euid at start
Package: nodm
Version: 0.11-1.3
Followup-For: Bug #701578
Hello,
after adding an strace to the call of nodm, I think I found the problem:
nohup strace -ff -t -o /var/tmp/nodm_$$ /etc/init.d/nodm start
/var/tmp/nodm_$$.out 21
I get at the end of /var/tmp/nodm_4218.4385 (the one of the nodm binary
according to /var/run/nodm.pid, which remains after the failed call):
11:59:28 getuid() = 103
11:59:28 write(2, nodm: can only be run by root\n, 30) = 30
11:59:28 exit_group(1) = ?
Adding then an 'id' call to the /etc/pm/sleep.d/10_vdr-dvb, I get the
following result in /var/log/pm-suspend.log:
uid=103(vdr) gid=106(vdr) euid=0(root)
Gruppen=0(root),24(cdrom),29(audio),44(video),46(plugdev),106(vdr)
(notice the euid=0)
According to the limited understanding I got through the reading of
http://www.enggresources.com/classroom/viewans.php?qid=889
I think that the correct behavior should be to call geteuid and not getuid,
as I assume that the only intent is to check that the user has root rights
(and not that they is a specific user).
It would be really nice to fix this (a sudo-based workaround will probably
be feasible but is ugly).
Thanks, Eric
PS: I attach the complete strace output in case you'd like to analyse deeper.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nodm depends on:
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-37
ii libpam0g 1.1.3-7.1
ii libx11-6 2:1.5.0-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
nodm recommends no packages.
nodm suggests no packages.
-- Configuration Files:
/etc/init.d/nodm changed:
set -e
set -x
PATH=/bin:/usr/bin:/sbin:/usr/sbin
DESC=Automatic Display Manager
NAME=nodm
PIDDIR=/var/run/
PIDFILE=${PIDDIR}/${NAME}.pid
NODM_ENABLED=no
NODM_XINIT=/usr/bin/xinit
NODM_FIRST_VT=7
NODM_XSESSION=/etc/X11/Xsession
NODM_X_OPTIONS=-nolisten tcp
NODM_USER=root
NODM_MIN_SESSION_TIME=60
if [ -f /etc/default/$NAME ]
then
. /etc/default/$NAME
fi
export NODM_XINIT NODM_XSESSION NODM_X_OPTIONS NODM_USER NODM_MIN_SESSION_TIME
NODM_FIRST_VT
[ -x /usr/sbin/nodm ] || exit 0
.. /lib/init/vars.sh
.. /lib/lsb/init-functions
case $1 in
start)
[ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME
if [ $NODM_ENABLED = no ] || [ $NODM_ENABLED = false ]
then
log_warning_msg Not starting $NAME because
NODM_ENABLED is '$NODM_ENABLED' in /etc/default/$NAME
else
start-stop-daemon --start --verbose --oknodo --pidfile
${PIDFILE} --make-pidfile --background --exec /usr/sbin/nodm
fi
[ $VERBOSE != no ] log_end_msg $?
;;
stop)
[ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME
start-stop-daemon --stop --pidfile ${PIDFILE} --oknodo
rm -f ${PIDFILE}
[ $VERBOSE != no ] log_end_msg $?
;;
restart|force-reload)
$0 stop
$0 start
;;
*)
log_success_msg Usage: $0 {start|stop|restart|force-reload}
2
exit 1
;;
esac
exit 0
-- debconf information:
nodm/min_session_time: 60
nodm/enabled: true
nodm/xsession: /etc/X11/Xsession
nodm/x_options: -nolisten tcp
nodm/first_vt: 7
nodm/user: vdr
nodm_4218.tgz
Description: GNU Zip compressed data
Bug#701951: libecj-java-gcj: Not installable with /var on 9p(non-hdd) filesystem
Hi, Daniel Dickinson said: This appears to be due to a permissions problem of some kind due to use a 9p filesystem rather than native ext4 or the like. Probably fails on nfs too, but I haven't tried that. Or maybe use of extended attributes (not sure 9p supports them or not)? I don't know what the policy is in such a case (best effort? Implement if patch provided?) but according to [1] 9p is not even part of the standard Debian kernel (and I suspect that there might be a reason for this). Cheers, Eric [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696292 -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701578: nodm doesn't start after hibernate but doesn't complain either
Package: nodm
Version: 0.11-1.3
Severity: normal
Hi,
I stop nodm before going for hibernation and try to restart during thawing,
but nodm isn't started and doesn't given any hint at why it doesn't start,
and I can't add parameters to the nodm start as start-stop-daemon doesn't
allow for it.
In more details:
$ find /etc/pm -type f
/etc/pm/sleep.d/10_vdr-dvb
/etc/pm/config.d/10_vdr-dvb
vdr@hdvdr1:/etc/pm$ cat /etc/pm/sleep.d/10_vdr-dvb
#!/bin/sh
case $1 in
hibernate|suspend)
/etc/init.d/nodm stop
killallvdr-sxfe # sometimes it stays stuck
killall -9 vdr-sxfe # sometimes it stays even more stuck
/etc/init.d/vdr stop
;;
thaw|resume)
/etc/init.d/vdr start
echo VDR started 2
sleep 1 # give time to vdr to start properly, so that vdr-sxfe succeeds
echo SLEEP finished 2
/etc/init.d/nodm start
echo NODM started 2
;;
esac
vdr@hdvdr1:/etc/pm$ cat /etc/pm/config.d/10_vdr-dvb
SUSPEND_MODULES=zd1211rw ddbridge
As you can see in the configuration files section, I've modified
/etc/init.d/nodm to spit more information (I added set -x and --verbose
to start-stop-daemon), and the result in /var/log/pm-suspend.log is attached
to this report.
You'll see there that start-stop-daemon starts nodm but then nothing more
to see, nodm is definitely NOT re-started and I have no clue how to analyse
deeper what the issue might be. I think it would be good to change the
verbosity of nodm based on environment variables, but I'm open to any
other suggestion.
Thanks, Eric
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nodm depends on:
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-37
ii libpam0g 1.1.3-7.1
ii libx11-6 2:1.5.0-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
nodm recommends no packages.
nodm suggests no packages.
-- Configuration Files:
/etc/init.d/nodm changed:
set -e
set -x
PATH=/bin:/usr/bin:/sbin:/usr/sbin
DESC=Automatic Display Manager
NAME=nodm
PIDDIR=/var/run/
PIDFILE=${PIDDIR}/${NAME}.pid
NODM_ENABLED=no
NODM_XINIT=/usr/bin/xinit
NODM_FIRST_VT=7
NODM_XSESSION=/etc/X11/Xsession
NODM_X_OPTIONS=-nolisten tcp
NODM_USER=root
NODM_MIN_SESSION_TIME=60
if [ -f /etc/default/$NAME ]
then
. /etc/default/$NAME
fi
export NODM_XINIT NODM_XSESSION NODM_X_OPTIONS NODM_USER NODM_MIN_SESSION_TIME
NODM_FIRST_VT
[ -x /usr/sbin/nodm ] || exit 0
.. /lib/init/vars.sh
.. /lib/lsb/init-functions
case $1 in
start)
[ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME
if [ $NODM_ENABLED = no ] || [ $NODM_ENABLED = false ]
then
log_warning_msg Not starting $NAME because
NODM_ENABLED is '$NODM_ENABLED' in /etc/default/$NAME
else
start-stop-daemon --start --verbose --oknodo --pidfile
${PIDFILE} --make-pidfile --background --exec /usr/sbin/nodm
fi
[ $VERBOSE != no ] log_end_msg $?
;;
stop)
[ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME
start-stop-daemon --stop --pidfile ${PIDFILE} --oknodo
rm -f ${PIDFILE}
[ $VERBOSE != no ] log_end_msg $?
;;
restart|force-reload)
$0 stop
$0 start
;;
*)
log_success_msg Usage: $0 {start|stop|restart|force-reload}
2
exit 1
;;
esac
exit 0
-- debconf information:
nodm/min_session_time: 60
nodm/enabled: true
nodm/xsession: /etc/X11/Xsession
nodm/x_options: -nolisten tcp
nodm/first_vt: 7
nodm/user: vdr
Initial commandline parameters:
So 24. Feb 15:26:35 CET 2013: Running hooks for hibernate.
Running hook /usr/lib/pm-utils/sleep.d/000kernel-change hibernate hibernate:
/usr/lib/pm-utils/sleep.d/000kernel-change hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate:
Linux hdvdr1 3.6.9+vdr1 #1 SMP Sat Dec 8 14:47:07 CET 2012 x86_64 GNU/Linux
Module Size Used by
loop 22961 0
firewire_sbp2 17957 0
snd_hda_codec_hdmi 31040 1
snd_hda_codec_realtek55298 1
tda18212dd 12843 2
arc4 12544 2
usbhid 40793 0
hid81613 1 usbhid
rc_imon_pad12398 0
imon 25747 1
rc_core18383 3 imon,rc_imon_pad
coretemp 12855 0
kvm_intel 118206 0
kvm 304736 1 kvm_intel
crc32c_intel 12748 0
Bug#698164: mandate unique package names in Debian Java policy
Hi, Daniel Pocock said: B. I doubt that such a badly named package would be of enough interest / quality for Debian packaging (but I might be wrong, I don't know any example) There are examples like this. It has been argued by some developers that to compile using some toolchains (e.g. Blackberry builds done on Windows), they have to shorten the package names, otherwise they end up with filenames that are too long And who are we, packagers, to decide that this argument is wrong? And again, perfect example: if we change the package name on Debian, programs built on Debian wouldn't work on Windows and vice versa, and possibly neither on Blackberry which would make the principle of a toolchain quite absurd, wouldn't it. Wonderful result for a language supposedly portable... Having this in Debian policy would help underline best practice and show people evidence why they shouldn't deviate from it. I quickly checked other Debian language policies (Perl, Python) and couldn't anything even similar to this proposal, which confirms me in my opinion that policies are (rightly IMHO) about packaging not about programming best practices. Conclusion: I vote against + close the bug. Can you leave the bug open so other people can comment for now? It is not RC after all Sure, I meant to say that I vote to close the bug. Unless someone disagrees, I would suggest to leave it open until next week (gives one more week-end for people to react) and then close it (if votes continue to go in the same direction, of course). Cheers, Eric -- You don't need to CC me on debian-java, debian-mentors and pkg-java-maintainers. Please CC me on other Debian lists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698164: mandate unique package names in Debian Java policy
Hello, On 14/01/13 19:48, Daniel Pocock wrote: A few projects exist without following this convention, and sooner or later somebody may try to package one of them. According to the Java Language Specification, using a domain name is a suggested convention and not a mandatory obligation. Nonetheless, in an environment such as Debian where we have to keep many different packages concurrently on a single system, I would contend that we should mandate the use of this suggestion http://docs.oracle.com/javase/specs/jls/se7/html/jls-6.html#d5e6504 The package domain is a decision of upstream, not of the packager, hence I don't think that such recommendation has its place in the Java policy: 1. it doesn't create any collision in terms of packaging 2. it might create collision in terms of using two such libraries BUT a. developers using two such libraries have to cope with this issue also outside of Debian anyway b. and in terms of portability, any developer using one of both libraries would thank us (irony!) if we'd change the package name as it would force them to change their import statements only for Debian This said, we can put a suggestion in the Java Policy to influence upstream to fix their package naming convention, but: A. it's the same as for any other upstream bug, so why document the obvious? B. I doubt that such a badly named package would be of enough interest / quality for Debian packaging (but I might be wrong, I don't know any example) Conclusion: I vote against + close the bug. Cheers, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691596: sqlite3-doc: Register to doc-base
Package: sqlite3-doc Version: 3.7.13-1 Severity: wishlist Hi, it would be nice if you could add a documentation registration file to /usr/share/doc-base/. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash sqlite3-doc depends on no packages. Versions of packages sqlite3-doc recommends: ii sqlite3 3.7.13-1 sqlite3-doc 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#691367: xsane: E-mail is sent with incorrect charset
Package: xsane Version: 0.998-3+b1 Severity: normal Hello, the email option seems to send all emails with charset=iso-8859-1 even if the environment is using something else, in my case UTF-8. The result is that all accentued characters are garbage at arrival, which is quite ugly. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xsane depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgimp2.0 2.8.2-1 ii libglib2.0-02.33.12+really2.32.4-2 ii libgtk2.0-0 2.24.10-2 ii libjpeg88d-1 ii liblcms11.19.dfsg-1.2 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libsane 1.0.22-7.4 ii libtiff43.9.6-9 ii xsane-common0.998-3 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages xsane recommends: ii cups-client 1.5.3-1 ii iceweasel [www-browser] 10.0.9esr-1 ii konqueror [www-browser] 4:4.8.4-1 ii w3m [www-browser]0.5.3-8 Versions of packages xsane suggests: ii gimp 2.8.2-1 pn gocr none pn gv none pn hylafax-client | mgetty-fax none -- 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#686930: plasma-widgets-workspace: Task Manager widget looses iceweasel from time to time
Package: plasma-widgets-workspace Version: 4:4.8.4-3 Severity: minor Hi, from time to time, the task manager from KDE looses the iceweasel windows, i.e. they're not listed anymore in the task bar. I didn't find any specific pattern for this to appear but it appears quite regularly, and (till now) for no other application, not even icedove. Cheers, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widgets-workspace depends on: ii libc6 2.13-35 ii libgcc1 1:4.7.1-7 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkdewebkit5 4:4.8.4-3 ii libkio5 4:4.8.4-3 ii libkunitconversion4 4:4.8.4-3 ii libkworkspace4abi14:4.8.4-3 ii libplasma34:4.8.4-3 ii libplasmaclock4abi3 4:4.8.4-3 ii libqt4-dbus 4:4.8.2-2+b1 ii libqt4-network4:4.8.2-2+b1 ii libqt4-xml4:4.8.2-2+b1 ii libqtcore44:4.8.2-2+b1 ii libqtgui4 4:4.8.2-2+b1 ii libqtwebkit4 2.2.1-4+b1 ii libsolid4 4:4.8.4-3 ii libstdc++64.7.1-7 ii libx11-6 2:1.5.0-1 ii libxcomposite11:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxfixes31:5.0-4 ii libxrender1 1:0.9.7-1 ii plasma-dataengines-workspace 4:4.8.4-3 plasma-widgets-workspace recommends no packages. plasma-widgets-workspace 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#685533: keepassx: Sort on last update date is buggy
Package: keepassx Version: 0.4.3-2 Severity: normal Hi, if I try to sort my entries by last update, they are somewhat sorted following a certain logic related to the date but it's neither increasing nor decreasing (see attached snapshot). I made a blunder and modified 2 copies of the same file, so I'm trying to find out where I did my changes and this bug is making it very complicated. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keepassx depends on: ii libc6 2.13-35 ii libgcc1 1:4.7.1-2 ii libqt4-xml 4:4.8.2-2+b1 ii libqtcore4 4:4.8.2-2+b1 ii libqtgui4 4:4.8.2-2+b1 ii libstdc++6 4.7.1-2 ii libx11-62:1.5.0-1 ii libxtst62:1.2.1-1 keepassx recommends no packages. keepassx suggests no packages. -- no debconf information attachment: keepass_kind_of_sorted.jpg
Bug#682181: icedove-l10n depends on icedove is wrong and breaks localization
Package: icedove-l10n-de Version: 1:10.0.2-1 Severity: grave Tags: l10n Justification: renders package unusable Hello, as icedove 10.0.5 is currently stuck in unstable, but icedove-l10n-??? 10.0.5 have moved to testing, and they don't work with icedove 10.0.4 (localization just doesn't happen, which my users/family do complain about, because they don't speak English), they are useless and force me to downgrade icedove-l10n-??? to 10.0.2 after each 'aptitude safe-upgrade'. This is obviously due to a wrong depends on icedove: Depends: icedove (= 10), icedove (= 10.1) which should more correctly read: Depends: icedove (= 10.0.5), icedove (= 10.1) Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove-l10n-de depends on: ii icedove 10.0.4-1 Versions of packages icedove-l10n-de recommends: ii myspell-de-de 20120607-1 icedove-l10n-de 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#583750: [licensecheck] Patch to provide structured output
Hello, On 17/07/12 11:20, Benjamin Drung wrote: tags 583750 - patch thanks Am Sonntag, den 15.07.2012, 20:38 +0200 schrieb Eric Lavarde: my initial patch was never included, here an updated version, perhaps it'll have more chance this time. Your patch seems to be incomplete. It adds a --machine flag, but it is not used anywhere. Can you please update the licensecheck man page? Uups, absolutely sorry. I'm not too sure what actually happened, but here is the complete patch. Don't you generate the man page out of the (already updated) perldoc in the script!? I (quickly) looked at your package and didn't find any other place... You can gain extra points by adding test cases to test/test_licensecheck. Extra points would be good, but I didn't plan to look actually at your package, just at your script. I nevertheless tried to quickly look at it, but the test script is using shunit2, which I don't know, so I stopped there (sorry, I do my best to help with my limited time). Hope it nevertheless helps, Eric licensecheck.patch.gz Description: GNU Zip compressed data
Bug#681691: os-prober and linux-boot-prober fail to mount alternate partition
Package: os-prober Version: 1.54 Severity: important Hello, very recently, I noticed that update-grub didn't discover Linux Debian installed on other partitions (/dev/sda2) than the current one (/dev/sda1), and I brought the issue down to os-prober which somehow fails to mount /dev/sda2 in order to properly discover it: root@hdvdr:/usr/src# os-prober umount: /var/lib/os-prober/mount: not mounted root@hdvdr:/usr/src# mount /dev/sda2 /mnt root@hdvdr:/usr/src# os-prober /dev/sda2:Debian GNU/Linux (wheezy/sid):Debian:linux root@hdvdr:/usr/src# linux-boot-prober /dev/sda2 /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.4-trunk-amd64:/boot/vmlinuz-3.4-trunk-amd64:/boot/initrd.img-3.4-trunk-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro quiet /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.4-trunk-amd64 (Wiederherstellungsmodus):/boot/vmlinuz-3.4-trunk-amd64:/boot/initrd.img-3.4-trunk-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro single /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.2.0-3-amd64:/boot/vmlinuz-3.2.0-3-amd64:/boot/initrd.img-3.2.0-3-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro quiet /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.2.0-3-amd64 (Wiederherstellungsmodus):/boot/vmlinuz-3.2.0-3-amd64:/boot/initrd.img-3.2.0-3-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro single /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.8+vdr1:/boot/vmlinuz-3.1.8+vdr1:/boot/initrd.img-3.1.8+vdr1:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro quiet /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.8+vdr1 (Wiederherstellungsmodus):/boot/vmlinuz-3.1.8+vdr1:/boot/initrd.img-3.1.8+vdr1:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro single /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.0-1-amd64:/boot/vmlinuz-3.1.0-1-amd64:/boot/initrd.img-3.1.0-1-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro quiet /dev/sda2:/dev/sda2:Debian GNU/Linux, mit Linux 3.1.0-1-amd64 (Wiederherstellungsmodus):/boot/vmlinuz-3.1.0-1-amd64:/boot/initrd.img-3.1.0-1-amd64:root=UUID=4d1901af-273e-4fdf-8128-b014f0b88e30 ro single root@hdvdr:/usr/src# umount /dev/sda2 root@hdvdr:/usr/src# linux-boot-prober /dev/sda2 umount: /var/lib/os-prober/mount: not mounted I've done an 'fsck -f' prior to the above test and I've also tried to mkdir /var/lib/os-prober/mount prior to similar tests, but it didn't make any difference. The report was set to important as it is impacting greatly its usage. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.8+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.13-33 os-prober recommends no packages. os-prober 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#583750: /usr/bin/licensecheck: [licensecheck] Patch to provide structured output
Package: devscripts Version: 2.11.9 Followup-For: Bug #583750 Hi, my initial patch was never included, here an updated version, perhaps it'll have more chance this time. Eric -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- Not present -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devscripts depends on: ii dpkg-dev 1.16.4.3 ii libc6 2.13-33 ii perl 5.14.2-12 ii python 2.7.3~rc2-1 ii python2.6 2.6.8-0.2 ii python2.7 2.7.3~rc2-2.1 Versions of packages devscripts recommends: ii at3.1.13-2 ii dctrl-tools 2.22.2 ii debian-keyring2012.06.01 ii dput 0.9.6.3 ii equivs2.0.9 ii fakeroot 1.18.4-2 ii gnupg 1.4.12-4+b1 ii libcrypt-ssleay-perl 0.58-1 pn libdistro-info-perl none pn libjson-perl none ii libparse-debcontrol-perl 2.005-3 ii libsoap-lite-perl 0.714-1 ii liburi-perl 1.60-1 ii libwww-perl 6.04-1 ii lintian 2.5.10 ii man-db2.6.2-1 ii patch 2.6.1-3 ii patchutils0.3.2-1.1 ii python-debian 0.1.21 ii python-magic 5.11-1 ii sensible-utils0.0.7 ii strace4.5.20-2.3 ii unzip 6.0-7 ii wdiff 1.1.2-1 ii wget 1.13.4-3 ii xz-utils 5.1.1alpha+20120614-1 Versions of packages devscripts suggests: ii bsd-mailx [mailx]8.1.2-0.2006cvs-1 ii build-essential 11.5 pn cvs-buildpackage none pn devscripts-elnone pn gnuplot none ii heirloom-mailx [mailx] 12.5-2 pn libauthen-sasl-perl none ii libfile-desktopentry-perl0.04-3 pn libnet-smtp-ssl-perl none pn libterm-size-perlnone ii libtimedate-perl 1.2000-1 pn libyaml-syck-perlnone ii mutt 1.5.21-6 ii openssh-client [ssh-client] 1:6.0p1-2 pn svn-buildpackage none ii w3m 0.5.3-8 -- no debconf information licensecheck.patch.gz Description: GNU Zip compressed data
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Hi, On 24/06/12 22:50, Tobias Grimm wrote: On 24.06.2012 18:21, Eric Lavarde wrote: Anyway, I updated my system and the problem is still there... I attach some more logs (also a vdr-err log I found in my /tmp directory) but I didn't notice anything significantly different from my last logs. The libextractor messages in vdr-err look weird - haven't seen these yet on my system. Which version of libextractor is installed? Can you try I used reportbug to create the following report: Package: libextractor3 Version: 1:0.6.3-4+b1 Severity: normal -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libextractor3 depends on: ii libbz2-1.0 1.0.6-3 ii libc6 2.13-33 ii libgcc11:4.7.0-8 ii libltdl7 2.4.2-1 ii libpoppler19 0.18.4-2 ii librpm34.10.0-2 ii libstdc++6 4.7.0-8 ii multiarch-support 2.13-33 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages libextractor3 recommends: ii libextractor-plugins 1:0.6.3-4+b1 Versions of packages libextractor3 suggests: pn libextractor-java none pn python-extractor none disabling the Scan for metainfo option in the xineliboutput settings? I did it but didn't notice anything special (no change in behavior). /tmp/vdr-err.xxx contains only one line INFO: validating live server ip '0.0.0.0' Eric Tobias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661335: Bug still in 3.2.0-2, 3.2.0-3 and 3.4-trunk ([3.1 - 3.2.4 regression] ASUS P8H67-M EVO: No HDMI sound on HDAintel)
found 661335 linux-2.6/3.2.20-1 found 661335 linux-2.6/3.2.21-3 found 661335 linux-2.6/3.4.4-1~experimental.1 thanks Hello, I'm getting a bit nervous due to the fact that the wheezy freeze is approaching, that I'm still stuck on an outdated kernel (3.1), with all the security and supportability implications, and I don't have the impression that anything is happening to resolve the issue. Is there anything I can do to help make this bug disappear before the release of wheezy? As you can guess from the control orders, I've tried successfully to reproduce the bug on all versions of the kernel I could find. Thanks, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Package: xineliboutput-sxfe Version: 1.0.7+cvs20120609.1902-1 Followup-For: Bug #666742 Hi, sorry for the time taking to answer but it's a live system, so difficult to find the right time between me being awake, not at work, and nobody wanting to look TV for long enough ;-) Anyway, I updated my system and the problem is still there... I attach some more logs (also a vdr-err log I found in my /tmp directory) but I didn't notice anything significantly different from my last logs. Could it be that it has to do with my xine configuration and used filters or something like this?! Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.6.0-1 ii libc6 2.13-33 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-2 0.98-1 ii libgl1-mesa-glx [libgl1] 8.0.3-1 ii libglib2.0-0 2.32.3-1 ii libglu1-mesa [libglu1]8.0.3-1 ii libjpeg8 8d-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxine2 1.2.2-3+b1 ii libxine2-x1.2.2-3+b1 ii libxine2-xvdr 1.0.7+cvs20120609.1902-1 ii libxinerama1 2:1.1.2-1 ii libxrender1 1:0.9.7-1 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe suggests no packages. -- no debconf information user.log.gz Description: GNU Zip compressed data vdr-err.log.gz Description: GNU Zip compressed data vdr-sxfe.4184.log.gz Description: GNU Zip compressed data
Bug#663374: xine-ui: xine fails on polskie radio trojka stream
Package: xine-ui Version: 0.99.7~hg20120125-1 Followup-For: Bug #663374 Hello, I didn't get any feedback on this bug and then I realised that I had installed libxine2 from deb-multimedia (I also had the same issue on another system anyway). So, I've cleaned up the system on which I report the issue and here you are, the problem is still there. I hope I can now count on your support. Thanks, Eric PS: I don't know where the debsums error on xine.desktop comes, I've removed the file and 'aptitude reinstall xine-ui' and the error was still there. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xine-ui depends on: ii libc62.13-32 ii libcurl3-gnutls 7.25.0-1 ii libjpeg8 8d-1 ii liblircclient0 0.9.0~pre1-1 ii libpng12-0 1.2.49-1 ii libreadline6 6.2-8 ii libx11-6 2:1.4.99.901-2 ii libxext6 2:1.3.1-2 ii libxft2 2.2.0-3 ii libxine2 1.2.1-2 ii libxine2-ffmpeg 1.2.1-2 ii libxine2-x 1.2.1-2 ii libxinerama1 2:1.1.2-1 ii libxtst6 2:1.2.1-1 ii libxv1 2:1.0.7-1 ii libxxf86vm1 1:1.1.2-1 Versions of packages xine-ui recommends: ii xdg-utils 1.1.0~rc1+git20111210-6 xine-ui suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /var/lib/xine/xine.desktop (from xine-ui package) xine.log.gz Description: GNU Zip compressed data
Bug#674692: libnepomuk4: Nepomuk complains about missing virtuoso server resp. virtuoso soprano plugin
Package: libnepomuk4 Version: 4:4.7.4-4 Severity: normal Hi, cleaning up my system from packages without source, I removed all the virtuoso packages; aptitude didn't complain about any missing dependency but since then I get from KDE the attached message: Semantic Data Storage - Nepomuk Semantic Desktop needs the Virtuoso RDF server to store its data. Installing the Virtuoso Soprano plugin is mandatory for using Nepomuk. I am NOT complaining about the fact that Virtuoso disappeared from testing, I am complaining about the fact that Nepomuk doesn't depend on Virtuoso but complains that it is absolutely required to work. In my opinion, this should be at least a warrant for a Recommends if not a Depends. I have seen that libnepomuk4 depends on libsoprano4 which depends on soprano-daemon which _suggests_ virtuoso-minimal, but that is definitely not a strong enough dependency, or Nepomuk shouldn't complain about a missing Virtuoso and confuse (and annoy to be honest) Debian users. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnepomuk4 depends on: ii libc62.13-32 ii libkdecore5 4:4.7.4-4 ii libkdeui54:4.7.4-4 ii libqt4-dbus 4:4.8.1-1 ii libqtcore4 4:4.8.1-1 ii libqtgui44:4.8.1-1 ii libsoprano4 2.7.5+dfsg.1-1 ii libstdc++6 4.7.0-8 libnepomuk4 recommends no packages. libnepomuk4 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#668146: Acknowledgement (openjdk-6-jre:i386: SIGSEGV on libdbus dbus_set_error)
For information: the bug doesn't appear with OpenJDK 7 version 7~u3-2.1-3. Cheers, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668146: openjdk-6-jre:i386: SIGSEGV on libdbus dbus_set_error
Package: openjdk-6-jre:i386 Version: 6b24-1.11.1-3 Severity: normal Hello, after a while not using the program, I tried to use BT747 2.0.3 from http://bt747.org/ and when I try to visualize a track on a map (Convert To Table in GUI), I get a crash: $ bt747 ericl@emil:/home/photos/DigitalPhotos$ /usr/local/share/bt747/lib/rxtx-2.1-7-bins-r2/Linux/i686-unknown-linux-gnu PATH = /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games 6883 - BT747 2.0.3 Build:BT747_mdeweerd.3.20110515132709849 6884 - Initial: 1019x582 Screen: 1920x1080 Final: 1019x582 6884 - Linux 6884 - i386 6884 - 3.2.0-2-686-pae 6885 - 1.6.0_24 6885 - 32 6885 - Fail com.sun.java.swing.plaf.windows.WindowsLookAndFeel Fail com.sun.java.swing.plaf.windows.WindowsClassicLookAndFeel Success com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel javax.swing.plaf.metal.MetalLookAndFeel com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel com.sun.java.swing.plaf.motif.MotifLookAndFeel com.sun.java.swing.plaf.gtk.GTKLookAndFeel 11042 - Classgps.connection.GPSRxTxPort Experimental: JNI_OnLoad called. RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyACM0 11065 - Port opened 11067 - Attempting saving settings to /home/ericl/.bt747/settings.pdb 11067 - Writing settings success for /home/ericl/.bt747/settings.pdb Conversion done 70265 - Time to convert: 557ms # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x67bb2d36, pid=6968, tid=1745017712 # # JRE version: 6.0_24-b24 # Java VM: OpenJDK Server VM (20.0-b12 mixed mode linux-x86 ) # Derivative: IcedTea6 1.11.1 # Distribution: Debian GNU/Linux unstable (sid), package 6b24-1.11.1-3 # Problematic frame: # C [libdbus-1.so.3+0x13d36] dbus_set_error+0x15e6 # # An error report file with more information is saved as: # /home/photos/DigitalPhotos/hs_err_pid6968.log # # If you would like to submit a bug report, please include # instructions how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # The interesting thing is that I didn't have the issue a while ago, and that I get a very similar error with Sun's (sorry Oracle's) Java, hence I assume that it has something to do with Debian's platform. I'll attach both error log files (Oracle's and OpenJDK's one). Let me know if I can provide more information. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openjdk-6-jre:i386 depends on: ii libasound2 1.0.25-2 ii libatk-wrapper-java-jni 0.30.4-1 ii libc62.13-27 ii libgif4 4.1.6-9 ii libjpeg8 8d-1 ii libpng12-0 1.2.47-2 ii libpulse01.1-3+b1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxi6 2:1.4.5-1 ii libxrender1 1:0.9.6-2 ii libxtst6 2:1.2.0-4 ii openjdk-6-jre-headless 6b24-1.11.1-3 ii zlib1g 1:1.2.6.dfsg-2 Versions of packages openjdk-6-jre:i386 recommends: ii icedtea-netx 1.1.4-1 ii ttf-dejavu-extra 2.33-2 Versions of packages openjdk-6-jre:i386 suggests: pn icedtea-plugin none -- no debconf information hs_err_pid4758_sunjre6.log.gz Description: GNU Zip compressed data hs_err_pid6968_openjdk6.log.gz Description: GNU Zip compressed data
Bug#666742: more information
Hello, I forgot to note: even if I restart vdr-sxfe it shows only a black screen with No Sender (or something like this) written in red, whereas I can see in my LCD screen (imon) that the plugin is still showing the name of the photo and switching between them as I use my remote control. Eric -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666742: xineliboutput-sxfe: vdr-sxfe fails on looking big images with xineliboutput plugin
Package: xineliboutput-sxfe Version: 1.0.7+cvs20120325.0846-1 Severity: normal Hello, when I try to look at images, vdr-sxfe segfaults on big images. I tried to limit the range and come to the result that 1365x2048 works but 1728x2592 resp. 2592x1728 doesn't). I attach the output of: $ vdr-sxfe --fullscreen --verbose --post tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1 --audio=alsa --tcp xvdr+tcp://127.0.0.1:37890 2vdr-sxfe.log 2 (the command also outputs a 'Speicherzugriffsfehler' - memory access error) The only thing found in /var/log/syslog is: Apr 1 15:05:47 hdvdr vdr: [2023] TS buffer on device 1 thread ended (pid=1669, tid=2023) Apr 1 15:05:47 hdvdr vdr: [2022] buffer stats: 3948 (0%) used Apr 1 15:05:47 hdvdr vdr: [2022] receiver on device 1 thread ended (pid=1669, tid=2022) Apr 1 15:05:47 hdvdr vdr: [1699] [xine..put] Client connection 0 closed Apr 1 15:05:47 hdvdr kernel: [ 418.728106] vdr-sxfe[2042]: segfault at 7f5503ec ip 7f551ea291e5 sp 7f55094d5c30 error 7 in libxine.so.2.1.0[7f551e9f2000+61000] Apr 1 15:05:47 hdvdr vdr: [1699] [xine..put] Closing connection 0 Apr 1 15:06:06 hdvdr vdr: [1669] [xine..put] cXinelibServer::Xine_Control_Result: Timeout (PLAYFILE Loop 0 none file:/media/ANITAKEY/0325_KamellenhofMiriam/4020_IMG.JPG, 2 ms) 16 (the last line is indeed the photo that makes vdr-sxfe crash) Let me know if I can provide more information, Eric -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.5.12-1 ii libc6 2.13-27 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.32.0-3 ii libglu1-mesa [libglu1]7.11.2-1 ii libjpeg8 8d-1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxine2 1.2.1-2 ii libxine2-x1.2.1-2 ii libxine2-xvdr 1.0.7+cvs20120325.0846-1 ii libxinerama1 2:1.1.1-3 ii libxrender1 1:0.9.6-2 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe suggests no packages. -- no debconf information vdr-sxfe.log.gz Description: GNU Zip compressed data
Bug#663374: xine-ui: xine fails on polskie radio trojka stream
Package: xine-ui Version: 0.99.7~hg20120125-1 Severity: normal Hello, until recently, xine did work with mms://stream.polskieradio.pl/program3 resp. http://stream.polskieradio.pl/program3 but doesn't anymore, whereas vlc does still work, though with some strange errors. As I use xine mainly as plugin for VDR, switching to VLC isn't an option in this case. I attach the different error messages to this bug report. Let me know if you need more information. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xine-ui depends on: ii libc62.13-27 ii libcurl3-gnutls 7.24.0-1 ii libjpeg8 8d-1 ii liblircclient0 0.9.0~pre1-1 ii libpng12-0 1.2.47-1 ii libreadline6 6.2-8 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxft2 2.2.0-3 ii libxine2 1:1.2.1-0.1 ii libxine2-ffmpeg 1:1.2.1-0.1 ii libxine2-x 1:1.2.1-0.1 ii libxinerama1 2:1.1.1-3 ii libxtst6 2:1.2.0-4 ii libxv1 2:1.0.6-2 ii libxxf86vm1 1:1.1.1-2 Versions of packages xine-ui recommends: ii xdg-utils 1.1.0~rc1+git20111210-6 xine-ui suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /var/lib/xine/xine.desktop (from xine-ui package) vlc.log.gz Description: GNU Zip compressed data xine.log.gz Description: GNU Zip compressed data
Bug#661335: [3.1 - 3.2.4 regression] ASUS P8H67-M EVO: No HDMI sound on HDAintel
Hi, Jonathan Nieder said: I'll attach also the output of alsa-info.sh as recommended in Bug #657302 Did you get a chance to try this? Erh, yes: the output was already attached to the original submission. The future mode was meant as after I've left this editor :-) Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660316: libxine2-xvdr: xine cannot find input plugin for MRL xvdr+tcp://127.0.0.1:37890#nocache
Package: libxine2-xvdr Version: 1.0.7+cvs20120214.0259-2 Followup-For: Bug #660316 Hi, in my almost Debian-pure environment (libxine2 comes from debian-multimedia), I also have the problem... Also the following command complains about missing MRL: xine xvdr+tcp://127.0.0.1:37890#nocache I will now side-grade and see what happens. Eric -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxine2-xvdr depends on: ii libavutil51 5:0.10-0.0 ii libc62.13-26 ii libxine2 1:1.2.0-5.1 ii libxine2-ffmpeg 1:1.2.0-5.1 libxine2-xvdr recommends no packages. libxine2-xvdr 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#660316: libxine2-xvdr: xine cannot find input plugin for MRL xvdr+tcp://127.0.0.1:37890#nocache
Package: libxine2-xvdr Version: 1.0.7+cvs20120214.0259-2 Followup-For: Bug #660316 Hi, ok, side-grade to 1.2.1 shows that the issue was with the packages of debian-multimedia. I think we can close the bug. Cheers, Eric -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxine2-xvdr depends on: ii libavutil-extra-51 4:0.8.0.1+b1 ii libc6 2.13-26 ii libxine21.2.1-1 ii libxine2-ffmpeg 1.2.1-1 libxine2-xvdr recommends no packages. libxine2-xvdr 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#659655: Downgrade severity of bug report
severity 659655 normal thanks As the issue appeared to be affecting only a specific part of the app (radio) and has an acceptable workaround (shut off vizualization), bug is being downgraded in severity. Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661319: vdr-plugin-xineliboutput: plugin fails to play DVDs with missing /dev/dvd
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20120214.0259-2 Severity: minor Hi, since recently, I couldn't look DVDs anymore using the plugin and the only error messages I could find were: Feb 26 10:42:57 hdvdr vdr: [19962] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB Feb 26 10:42:57 hdvdr vdr: [20096] Metadata scanner thread started (pid=19962, tid=20096) Feb 26 10:42:57 hdvdr vdr: [20096] [xine..put] ID3Scanner Started Feb 26 10:42:57 hdvdr vdr: [20096] [xine..put] ID3Scanner Done. Feb 26 10:42:57 hdvdr vdr: [20096] Metadata scanner thread ended (pid=19962, tid=20096) Feb 26 10:42:57 hdvdr vdr: [19962] [xine..put] cXinelibPlayer playing dvd:/ (FAIL) Feb 26 10:42:58 hdvdr vdr: [19962] [xine..put] cXinelibDvdPlayerControl: EndOfStreamReached Feb 26 10:43:01 hdvdr vdr: [19962] switching to channel 301 Using xine directly xine dvd:/ I then got the error message: libdvdread: Can't stat /dev/dvd And indeed I don't have /dev/dvd anymore but only /dev/dvd1 (don't know why but that's another story). It would be nice if the plugin could be as sensible as to output the same kind of helpful error message! It would be even more perfect if it would come to the GUI. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc62.13-26 ii libextractor1c2a 1:0.5.23+dfsg-7.1 ii libgcc1 1:4.6.2-15 ii libstdc++6 4.6.2-15 ii vdr [vdr-abi-1.7.23-debian] 1.7.23-1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput 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#661335: linux-image-3.2.0-1-amd64: No HDMI sound on HDA intel with kernel 3.2
Package: linux-2.6 Version: 3.2.6-1 Severity: important Hello, since I've upgraded to version 3.2 of the kernel, HDMI sound doesn't work, booting back to 3.1 (exactly 3.1.8-2) it works again. For my tests, I use the following command, directly from the console (no X whatsoever): In relation in both cases to: # aplay -L null Discard all samples (playback) or generate zero samples (capture) sysdefault:CARD=PCH HDA Intel PCH, ALC892 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog Front speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, ALC892 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=PCH,DEV=0 HDA Intel PCH, HDMI 0 HDMI Audio Output hdmi:CARD=PCH,DEV=1 HDA Intel PCH, HDMI 1 HDMI Audio Output # speaker-test -D front:CARD=PCH,DEV=0 -c2 (sound works in this case under 3.1 and 3.2) # speaker-test -D hdmi:CARD=PCH,DEV=1 -c2 (sound works only under 3.1 and NOT under 3.2) (I don't know what exactly hdmi:CARD=PCH,DEV=0 is but it doesn't work in either cases) I'll attach also the output of alsa-info.sh as recommended in Bug #657302 (exactly http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302#20). The same issue was already there in kernel 3.2.4 and, obviously, I haven't touched /var/lib/alsa/asound.state between reboots. I don't know if it's of importance but I'm also using self-compiled kernels (from the Debian sources) and I have the same behavior there. Let me know if you need more info, I'm currently stuck on 3.1. Thanks, Eric -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.6-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-14) ) #1 SMP Fri Feb 17 05:17:36 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 root=UUID=be935a63-0884-43eb-8220-1182aa00fa33 ro quiet ** Not tainted ** Kernel log: [2.689700] input: PC Speaker as /devices/platform/pcspkr/input/input3 [2.696485] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [2.703524] asus_wmi: ASUS WMI generic driver loaded [2.705349] usbcore: registered new interface driver uas [2.708162] input: iMON Panel, Knob and Mouse(15c2:0038) as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/input/input4 [2.708445] Initializing USB Mass Storage driver... [2.708965] scsi6 : usb-storage 2-1.6:1.0 [2.709342] asus_wmi: Initialization: 0x0 [2.709367] asus_wmi: BIOS WMI version: 0.9 [2.709425] asus_wmi: SFUN value: 0x0 [2.709481] usbcore: registered new interface driver usb-storage [2.709483] USB Mass Storage support registered. [2.709730] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input5 [2.709853] IR NEC protocol handler initialized [2.711045] asus_wmi: Backlight controlled by ACPI video driver [2.711574] IR RC5(x) protocol handler initialized [2.712560] IR RC6 protocol handler initialized [2.713675] IR JVC protocol handler initialized [2.715033] IR Sony protocol handler initialized [2.715251] mtrr: type mismatch for c000,1000 old: write-back new: write-combining [2.715253] [drm] MTRR allocation failed. Graphics performance may suffer. [2.715512] i915 :00:02.0: irq 53 for MSI/MSI-X [2.715517] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [2.715518] [drm] Driver supports precise vblank timestamp query. [2.715545] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.716372] IR MCE Keyboard/mouse protocol handler initialized [2.718212] lirc_dev: IR Remote Control driver registered, major 250 [2.718698] IR LIRC bridge handler initialized [2.736922] Registered IR keymap rc-imon-pad [2.737023] input: iMON Remote (15c2:0038) as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/rc/rc0/input6 [2.737125] rc0: iMON Remote (15c2:0038) as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/rc/rc0 [2.745069] imon 2-1.7:1.0: iMON device (15c2:0038, intf0) on usb2:4 initialized [2.745095]
Bug#660316: Acknowledgement (libxine2-xvdr: xine cannot find input plugin for MRL xvdr+tcp://127.0.0.1:37890#nocache)
Hello, I can confirm that the issue is due to the latest upgrade: downgrading back to version 1.0.7+cvs20120130.2334-2 from version 1.0.7+cvs20120214.0259-2 removed the issue for now (but I can't upgrade...). Hope this helps, Eric /var/cache/apt/archives# ls libxine2-xvdr* vdr-plugin-xineliboutput* xineliboutput-sxfe* libxine2-xvdr_1.0.7+cvs20120130.2334-2_amd64.deb libxine2-xvdr_1.0.7+cvs20120214.0259-2_amd64.deb vdr-plugin-xineliboutput_1.0.7+cvs20120130.2334-2_amd64.deb vdr-plugin-xineliboutput_1.0.7+cvs20120214.0259-2_amd64.deb xineliboutput-sxfe_1.0.7+cvs20120130.2334-2_amd64.deb xineliboutput-sxfe_1.0.7+cvs20120214.0259-2_amd64.deb /var/cache/apt/archives# dpkg -i libxine2-xvdr_1.0.7+cvs20120130.2334-2_amd64.deb vdr-plugin-xineliboutput_1.0.7+cvs20120130.2334-2_amd64.deb xineliboutput-sxfe_1.0.7+cvs20120130.2334-2_amd64.deb [...] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660316: libxine2-xvdr: xine cannot find input plugin for MRL xvdr+tcp://127.0.0.1:37890#nocache
Package: libxine2-xvdr Version: 1.0.7+cvs20120214.0259-2 Severity: grave Justification: renders package unusable Hello, Sorry to create again a grave bug, but since the last upgrade (see attached aptitude log), vdr-sxfe has stopped working (hence I can't see TV or hear Radio, see other attached log), where I think that the relevant parts are: xine: cannot find input plugin for MRL [xvdr+tcp://127.0.0.1:37890#nocache] [3039] [vdr-fe] fe_xine_open: xine_open(xvdr+tcp://127.0.0.1:37890#nocache) failed Error opening xvdr+tcp://127.0.0.1:37890 I use the e-tobi packages but I am currently building a pure Debian test and development environment, and had the same issue there. Let me know if I can provide more information. Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libxine2-xvdr depends on: ii libavutil51 5:0.10-0.0 ii libc62.13-26 ii libxine2 1:1.2.0-5.1 ii libxine2-ffmpeg 1:1.2.0-5.1 libxine2-xvdr recommends no packages. libxine2-xvdr 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#659655: xineliboutput-sxfe: vdr-sxfe segfaults error 4 inxineplug_inp_xvdr.so since upgrade to libxine2
Hi, Tobias Grimm said: On 12.02.2012 22:19, Eric Lavarde wrote: vdr-sxfe is just starting and dropping with a segfault: [ 3817.674930] vdr-sxfe[6098]: segfault at 8 ip 7f1285ce3f36 sp 7f1287ffebd0 error 4 in xineplug_inp_xvdr.so[7f1285ccf000+25000] Sorry, I can't reproduce this. Can you play videos and VDR recordings with Xine and VLC? Yes, flawlessly. In the mean time, I think that the issue only appeares with radio stations (didn't yet have time to do many tests), and it seems I'm not alone: http://www.vdr-portal.de/board17-developer/board25-patches/86804-patches-xine-lib-1-2-xineliboutput-xine-plugin-verbesserter-vdr-support/index82.html?s=d9ea1b7c1c0ebe8db3cac27f9085d8c43052b78b (starting with last entry on this page). I've just uploaded a new upstream snapshot, you might want to try this version 1.0.7+cvs20120214.0259-1. Didn't yet find time, need to work now... Eric Tobias -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659655: xineliboutput-sxfe: vdr-sxfe segfaults error 4 inxineplug_inp_xvdr.so since upgrade to libxine2
Hello again, Tobias Grimm said: I've just uploaded a new upstream snapshot, you might want to try this version 1.0.7+cvs20120214.0259-1. Sorry, where did you upload it to? Even after 'aptitude update', I don't get it offered: # apt-cache policy xineliboutput-sxfe xineliboutput-sxfe: Installiert: 1.0.7+cvs20120130.2334-2 Kandidat:1.0.7+cvs20120130.2334-2 Versionstabelle: *** 1.0.7+cvs20120130.2334-2 0 1001 http://e-tobi.net/vdr-experimental/ sid/vdr-multipatch amd64 Packages 100 /var/lib/dpkg/status 1.0.7+cvs20111211.1625-1 0 500 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages 1.0.7+cvs20110820.1342-1 0 1001 http://e-tobi.net/vdr-experimental/ sid/vdr-multipatch amd64 Packages Thanks, Eric -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659655: xineliboutput-sxfe: vdr-sxfe segfaults error 4 inxineplug_inp_xvdr.so since upgrade to libxine2
Eric Lavarde - Debian Bugs said: Sorry, I can't reproduce this. Can you play videos and VDR recordings with Xine and VLC? Yes, flawlessly. In the mean time, I think that the issue only appeares with radio stations (didn't yet have time to do many tests), and it seems I'm not alone: http://www.vdr-portal.de/board17-developer/board25-patches/86804-patches-xine-lib-1-2-xineliboutput-xine-plugin-verbesserter-vdr-support/index82.html?s=d9ea1b7c1c0ebe8db3cac27f9085d8c43052b78b (starting with last entry on this page). I confirm and precise: the visualization for radio channels is responsible; without visualization, vdr-sxfe doesn't segfault. Eric -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659655: xineliboutput-sxfe: vdr-sxfe segfaults error 4 in xineplug_inp_xvdr.so since upgrade to libxine2
Package: xineliboutput-sxfe Version: 1.0.7+cvs20120130.2334-2 Severity: grave Justification: renders package unusable Hello, sorry to block a severity grave but as I can't use my VDR anymore, I think it's justified. I've just updated my system (aptitude protocol attached) and since then, vdr-sxfe is just starting and dropping with a segfault: [ 3817.674930] vdr-sxfe[6098]: segfault at 8 ip 7f1285ce3f36 sp 7f1287ffebd0 error 4 in xineplug_inp_xvdr.so[7f1285ccf000+25000] I've also attached the log of the following call from the command line: $ DISPLAY=:0 vdr-sxfe --silent --post tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1 --audio=alsa --tcp xvdr+tcp://127.0.0.1:37890 --verbose 2/tmp/vdr-sxfe.txt 12 Speicherzugriffsfehler Hope you can fix this quickly, I'm currently stuck without TV (more time for reading you could say, but not sure my daughter will see it like this...). Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.4.16-1 ii libc6 2.13-26 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.30.2-6 ii libglu1-mesa [libglu1]7.11.2-1 ii libjpeg8 8d-1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxine2 1:1.2.0-5.1 ii libxine2-x1:1.2.0-5.1 ii libxine2-xvdr 1.0.7+cvs20120130.2334-2 ii libxinerama1 2:1.1.1-3 ii libxrender1 1:0.9.6-2 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe suggests no packages. -- no debconf information vdr_bug.tgz Description: GNU Zip compressed data
Bug#657714: grep: dmesg reports that grep uses deprecated ipv6 sysctl
Package: grep Version: 2.10-1 Severity: minor Hi, I just noticed that dmesg reported the following: [ 3385.178033] process `grep' is using deprecated sysctl (syscall) net.ipv6.neigh.default.retrans_time; Use net.ipv6.neigh.default.retrans_time_ms instead. I didn't notice any negative impact but I'm not using IPv6 either (and I'm not sure either what grep has to do with network, but that's another story...). Cheers, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grep depends on: ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libc6 2.13-24 grep recommends no packages. Versions of packages grep suggests: ii libpcre3 8.12-4 -- 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#656890: xineliboutput-sxfe: crashes when trying to see images
Package: xineliboutput-sxfe Version: 1.0.7+cvs20110820.1342-1 Severity: normal Hello, when trying to look at image using the xineliboutput, sxfe crashes. The most relevant information I could find was in the user.log: Jan 22 18:35:10 hdvdr vdr: [1335] [xine..put] cXinelibOsd::CanHandleAreas(): Dev ice does not support ARGB Jan 22 18:35:17 hdvdr vdr: [1771] ttxtsubs player thread ended (pid=1335, tid=17 71) Jan 22 18:35:17 hdvdr vdr: [1335] buffer stats: 0 (0%) used Jan 22 18:35:17 hdvdr vdr: [1335] ttxtsubs: teletext subtitles replayer started with initial page 000 Jan 22 18:35:17 hdvdr vdr: [1968] ttxtsubs player thread started (pid=1335, tid= 1968) Jan 22 18:35:17 hdvdr vdr: [1335] saved setup to /var/lib/vdr/setup.conf Jan 22 18:35:17 hdvdr vdr: [1364] [xine..put] Client connection 0 closed Jan 22 18:35:17 hdvdr vdr: [1364] [xine..put] Closing connection 0 Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] Client 0 connected: 127.0.0.1:5019 8 Jan 22 18:35:19 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/all owed_hosts.conf Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): g ot 262142 bytes Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] Client 1 connected: 127.0.0.1:5019 9 Jan 22 18:35:19 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/all owed_hosts.conf Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): g ot 262142 bytes Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] Data connection (TCP) requested Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] cBackgroundWriterI initialized (bu ffer 512 kb) Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] cTcpWriter initialized (buffer 512 kb) Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] cXinelibServer::Xine_Control_Resul t: Timeout (GETPOS, 300 ms) 6 Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] Client connection 0 closed Jan 22 18:35:19 hdvdr vdr: [1364] [xine..put] Closing connection 0 Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] Client 0 connected: 127.0.0.1:50200 Jan 22 18:35:20 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] Client 1 connected: 127.0.0.1:50201 Jan 22 18:35:20 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] Data connection (TCP) requested Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] cBackgroundWriterI initialized (buffer 512 kb) Jan 22 18:35:20 hdvdr vdr: [1364] [xine..put] cTcpWriter initialized (buffer 512 kb) Jan 22 18:35:21 hdvdr vdr: [1364] [xine..put] cXinelibServer::Xine_Control_Result: Timeout (GETPOS, 300 ms) 7 Jan 22 18:35:21 hdvdr vdr: [1364] [xine..put] Client connection 0 closed Jan 22 18:35:21 hdvdr vdr: [1364] [xine..put] Closing connection 0 Jan 22 18:35:37 hdvdr vdr: [1335] [xine..put] cXinelibServer::Xine_Control_Result: Timeout (PLAYFILE Loop 0 goom:width=720,height=576,fps=25 file:/media/cdrom/2011_Mama%20i%20Gosia%20w%20Singapurze%20i%20na%20Bali,%2019.12%20-%2021.12.2011/IMG_5787.JPG, 2 ms) 5 Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] Client 0 connected: 127.0.0.1:50202 Jan 22 18:35:52 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] Client 1 connected: 127.0.0.1:50203 Jan 22 18:35:52 hdvdr vdr: [1364] loading /var/lib/vdr/plugins/xineliboutput/allowed_hosts.conf Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] Data connection (TCP) requested Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] cBackgroundWriterI initialized (buffer 512 kb) Jan 22 18:35:52 hdvdr vdr: [1364] [xine..put] cTcpWriter initialized (buffer 512 kb) Not a lot I imagine, but sxfe is not really stable, some improvement would be really nice. Let me know if I can provide more information. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.4.16-1 ii freeglut3 2.6.0-1.1 ii libc6 2.13-24 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.30.2-4 ii libglu1-mesa [libglu1]7.11.2-1 ii libjpeg8 8c-2 ii libx11-6 2:1.4.4-4 ii libxext6
Bug#656890: xineliboutput-sxfe: crashes when trying to see images
Package: xineliboutput-sxfe Followup-For: Bug #656890 Hi again, I don't know if it's related but I tried to install vdr-plugin-image to conpemsate for this bug, and sxfe doesn't crash but each image is only shown for less than a second before the screen becomes black. Perhaps sxfe has issues with still images? Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xineliboutput-sxfe depends on: ii dbus 1.4.16-1 ii freeglut3 2.6.0-1.1 ii libc6 2.13-24 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.30.2-4 ii libglu1-mesa [libglu1]7.11.2-1 ii libjpeg8 8c-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxine1 1:1.1.19-3.3 ii libxine1-x1:1.1.19-3.3 ii libxine1-xvdr 1.0.7+cvs20110820.1342-1 ii libxinerama1 2:1.1.1-3 ii libxrender1 1:0.9.6-2 xineliboutput-sxfe recommends no packages. xineliboutput-sxfe 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#656897: vdr-plugin-imonlcd: Please show section names when jumping between them
Package: vdr-plugin-imonlcd Version: 0.0.5-1 Severity: wishlist Hello, the plugin works really well, but when pressing right and left to jump between channel sections (the ones starting with a column in the channels.conf), it doesn't show the section selected so that one has to navigate blind. It would be really nice to have this additional feature. Thanks, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-imonlcd depends on: ii libc62.13-24 ii libfreetype6 2.4.8-1 ii libgcc1 1:4.6.2-11 ii libstdc++6 4.6.2-11 ii vdr [vdr-abi-1.7.20-multipatch] 1.7.20-1~ctvdr1 ii zlib1g 1:1.2.3.4.dfsg-3 vdr-plugin-imonlcd recommends no packages. vdr-plugin-imonlcd 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#656732: vdr-plugin-xineliboutput: PLS playlists are parsed wrongly so that equal (=) sign remains
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20110820.1342-1 Severity: minor Hello, when I use a .pls playlist to play a web radio, the vdr-plugin-imonlcd shows =Radio ZET (in the attached example). Using a .m3u playlist (which is a workaround as both formats are pretty equivalent), the title is properly shown as Radio ZET, so that I don't assume that it's an imonlcd issue (which doesn't know about playlists anyway). Thanks, Eric PS: I use the packages from http://e-tobi.net/vdr-experimental/ sid/vdr-multipatch amd64 Packages but I understand that it's the same maintainer behind the Debian packages and that it's OK to report bugs here... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.6+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc62.13-24 ii libextractor1c2a 1:0.5.23+dfsg-7.1 ii libgcc1 1:4.6.2-11 ii libstdc++6 4.6.2-11 ii vdr [vdr-abi-1.7.20-multipatch] 1.7.20-1~ctvdr1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information ZET.tgz Description: GNU Zip compressed data
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 17/01/12 20:40, Jonathan Nieder wrote: Eric Lavarde wrote: Could it be that the BIOS overwrites my command line entry at shutdown time, but not at suspend time? Sure, I can believe that. It's also possible that when you try to enter S5, something goes wrong and the machine ends up powering off completely and then the BIOS writes to the RTC at bootup. Here's an experiment to try: echo shutdown/sys/power/disk echo disk/sys/power/state It performs a suspend-to-disk but enters S5 instead of S4. Bingo! The PC doesn't come back up after this, so it's a difference between S4 and S5. Stupid question: do you know if it would be possible to shutdown (going through init and all this) into S4? After that: maybe RTC or ACPI folks can help (see the MAINTAINERS file[1], and please cc me or this bug log if contacting them so we can track it). But I'd be more inclined to work on getting Will do. Thanks a lot for your help so far! suspend-to-disk working without unloading the media capture driver first. I will also follow-up on this, fine with me, but I'm more a friend of clean shutdowns :-) so it'll be either as fallback strategy or for the community. Cheers, Eric [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=MAINTAINERS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hello, On 14/01/12 17:33, Jonathan Nieder wrote: Eric Lavarde wrote: I'm surely not experienced in these topics, but I thought that there should be no difference for the BIOS / ACPI between a pure shutdown and a suspend to disk. Nah, they are different. Suspend to disk happens with ACPI cooperation. [...] Let me know if I can test / do anything further to solve the issue, It's possible your machine only supports wake from S4 and not S5, in which case the best bet would be to get your (out-of-tree?) driver to suspend to disk sanely. By the way, has there been any effort to get that out-of-tree driver merged upstream? Please file a bug describing the missing functionality it provides, and I can try working on that. All that said, I see no reason _in principle_ that a machine that can wake from S4 should not be able to wake from S5. It might be possible to debug this as an ACPI or RTC issue. Please test 3.2-rc7 from experimental without any out-of-tree drivers, and provide: i. full dmesg output from booting, setting the wakeup timer, hibernating with echo disk/sys/power/state, and waking up ii. information about what happens if you instead boot, set the wakeup time, shutdown with shutdown -h now, and wake up Done (see attached files from an xterm -l logfile + the script used) - in the 2nd case it doesn't wake up, so that's easy... Also, when you set the wakeup timer, is it visible from the CMOS menus? If it is, that might help in comparing what happens in cases (i) and (ii). With CMOS menus you mean the BIOS? If yes, then it doesn't appear, I only see what I enter in the BIOS. Perhaps interesting: if I do a 'cat /proc/driver/rtc' after a reboot (i.e. before having entered myself a time), I see what I entered manually in the BIOS under alrm_time and alrm_date: rtc_time: 07:39:05 rtc_date: 2012-01-17 alrm_time : 18:15:00 alrm_date : 2012-01-17 alarm_IRQ : yes alrm_pending: no update IRQ enabled : no periodic IRQ enabled: no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr: yes periodic_IRQ: no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay If I read the rtc after resume from suspend, I see the time I had entered from the command line before the suspend: rtc_time: 07:53:29 rtc_date: 2012-01-17 alrm_time : 07:52:21 alrm_date : 2012-01-17 alarm_IRQ : yes alrm_pending: no update IRQ enabled : no periodic IRQ enabled: no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr: yes periodic_IRQ: no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay Could it be that the BIOS overwrites my command line entry at shutdown time, but not at suspend time? I have the impression that the BIOS has 2 places with wake-up time: A for the configuration itself (what has been entered in the BIOS by the user, me, and is visible in the BIOS GUI) and B to actually get the PC to wake-up, and it copies A to B at shutdown time... What do you think? Am I f* up? Thanks, Jonathan I thank you, Eric Xterm.log.emil.2012.01.17.08.13.05.DISKSUSPEND.gz Description: GNU Zip compressed data Xterm.log.emil.2012.01.17.08.24.24.HALT.gz Description: GNU Zip compressed data acpi_test.sh.gz Description: GNU Zip compressed data
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 24/12/11 08:24, Jonathan Nieder wrote: forwarded 650081 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 quit Eric Lavarde wrote: [ 581.247437] I2C timeout [ 581.247442] IRS 0001 [... hundreds of line of this type ...] Let's take this upstream, starting with this bit, under the principle fix the most egregiously broken piece first. Many thanks, Jonathan Sorry for the delay and possibly for the confusion, but holiday and the VDR is in production so my users r my family doesn't like extensive test sessions (or they can't look TV ;-) ). Anyway, as already written in the answer to [1], I've now the possibility to do tests with a clean kernel and the result is exactly the same: waking up after a halt / poweroff does NOT work, waking up after a 'disk' suspend DOES work (even with latest Kernel linux-image-3.1.0-1-amd64 / 3.1.8-2). I'm surely not experienced in these topics, but I thought that there should be no difference for the BIOS / ACPI between a pure shutdown and a suspend to disk. Checking what is done differently in the kernel might tell us what the issue is, no?! Let me know if I can test / do anything further to solve the issue, I can possibly work around the other issues with suspend to disk (probably the right rmmod at the right place) but I'm not a big fan of suspend as I favor stability over speed of boot. Thanks, Eric [1] http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 24/12/11 08:24, Jonathan Nieder wrote: forwarded 650081 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 quit Eric Lavarde wrote: [ 581.247437] I2C timeout [ 581.247442] IRS 0001 [... hundreds of line of this type ...] Let's take this upstream, starting with this bit, under the principle fix the most egregiously broken piece first. Many thanks, Jonathan Sorry for the delay and possibly for the confusion, but holiday and the VDR is in production so my users r my family doesn't like extensive test sessions (or they can't look TV ;-) ). Anyway, as already written in the answer to [1], I've now the possibility to do tests with a clean kernel and the result is exactly the same: waking up after a halt / poweroff does NOT work, waking up after a 'disk' suspend DOES work (even with latest Kernel linux-image-3.1.0-1-amd64 / 3.1.8-2). I'm surely not experienced in these topics, but I thought that there should be no difference for the BIOS / ACPI between a pure shutdown and a suspend to disk. Checking what is done differently in the kernel might tell us what the issue is, no?! Let me know if I can test / do anything further to solve the issue, I can possibly work around the other issues with suspend to disk (probably the right rmmod at the right place) but I'm not a big fan of suspend as I favor stability over speed of boot. Thanks, Eric [1] http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652803: simplyhtml: FTBFS: testsanity fails
Interesting, your automatism (I guess it was an automatism) managed to avoid the really relevant parts of the error by exactly one line before and one line after: * 1 line before: /usr/share/cdbs/1/rules/simple-patchsys.mk:31: WARNING: simple-patchsys.mk is deprecated - please use source format 3.0 (quilt) instead * 1 line after: You must specify a valid JAVA_HOME or JAVACMD! dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Eric On 20/12/11 16:10, Lucas Nussbaum wrote: Source: simplyhtml Version: 0.13.1-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111220 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/simplyhtml-GOOFxc/simplyhtml-0.13.1' make[1]: Nothing to be done for `reverse-config'. make[1]: Leaving directory `/build/simplyhtml-GOOFxc/simplyhtml-0.13.1' if [ reverse-patches = reverse-patches ]; then rm -f debian/stamp-patched; fi patches: debian/patches/10_build_xml.patch debian/patches/30_manifest.patch Patch debian/patches/30_manifest.patch is not applied. Patch debian/patches/10_build_xml.patch is not applied. if [ reverse-patches != reverse-patches ]; then touch debian/stamp-patched; fi if [ reverse-patches != reverse-patches ] ; then \ /usr/bin/make -f debian/rules update-config ; \ fi for dir in debian/patches ; do \ rm -f $dir/*.log ; \ done make: *** [testsanity] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/12/20/simplyhtml_0.13.1-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652972: grub-pc: Grep complains input file `/boot/grub/grub.cfg.new' is also the output
Package: grub-pc
Version: 1.99-14
Severity: minor
Hi,
I haven't seen any negative effect yet, but after the last kernel
update, there is an error message when grub is updated that doesn't
sound right:
[...]
Setting up linux-image-3.1.0-1-686-pae (3.1.5-1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.1.0-1-686-pae
/boot/vmlinuz-3.1.0-1-686-pae
update-initramfs: Generating /boot/initrd.img-3.1.0-1-686-pae
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.1.0-1-686-pae
/boot/vmlinuz-3.1.0-1-686-pae
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.1.0-1-686-pae
/boot/vmlinuz-3.1.0-1-686-pae
run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.1.0-1-686-pae
/boot/vmlinuz-3.1.0-1-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.1.0-1-686-pae...
P: Installing debian theme... done.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.1.0-1-686-pae
/boot/vmlinuz-3.1.0-1-686-pae
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.1.0-1-686-pae
Found initrd image: /boot/initrd.img-3.1.0-1-686-pae
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
grep: input file `/boot/grub/grub.cfg.new' is also the output
done
Setting up binutils (2.22-2) ...
[...]
The 2nd line from the bottom.
Eric
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/588e89f5-b621-4e38-b5c9-5aabaf74cb45 / ext4
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/sda5 /data ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/sda6 /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/disk/by-uuid/588e89f5-b621-4e38-b5c9-5aabaf74cb45
/data/CHROOTS/debian-sid/tmp ext4
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST3250820AS_9QE5R7SJ
(hd1) /dev/disk/by-id/usb-WD_My_Book_57442D574341534A30313737333832-0:0
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 588e89f5-b621-4e38-b5c9-5aabaf74cb45
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 588e89f5-b621-4e38-b5c9-5aabaf74cb45
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 588e89f5-b621-4e38-b5c9-5aabaf74cb45
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae' --class debian --class
gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root
588e89f5-b621-4e38-b5c9-5aabaf74cb45
echo'Loading Linux 3.1.0-1-686-pae ...'
linux /boot/vmlinuz-3.1.0-1-686-pae
root=UUID=588e89f5-b621-4e38-b5c9-5aabaf74cb45 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.1.0-1-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root
588e89f5-b621-4e38-b5c9-5aabaf74cb45
echo'Loading Linux 3.1.0-1-686-pae ...'
linux /boot/vmlinuz-3.1.0-1-686-pae
root=UUID=588e89f5-b621-4e38-b5c9-5aabaf74cb45 ro
Bug#650173: udev: Music cdroms cannot be read
Hello Marco, On 05/12/11 03:04, Marco d'Itri wrote: On Nov 27, Eric Lavardebugs.debian.nos...@lavar.de wrote: since I've upgraded from squeeze to wheezy, I can't read music CDs anymore. If I put such a CD in the drive, I get the following dmesg: How are you supposed to /read/ music CDs? Don't you consider making a copy of a music CD with dd or ddrescue like 'reading' the music CD? I don't know, it's the first time I try to save a music CD that is scratched, but isn't it yet another block device? I don't know which method it uses but even k3b fails to do 'clone copy' aka image creation of music CDs (normal copy, which creates wav files, works), and I'm quite sure I already used this feature under squeeze. You might ask what it has to do with udev, but when searching for these error messages on the net, the most relevant hit was http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591290 so here you are. Not very relevant. You're the expert! What happens if you kill udevd and then try to read your CD? The error messages in dmesg don't appear anymore but ddrescue and dd don't work better. OK, so it seems that there is a failing element that causes udev to create error msgs and keeps dd* from working. Any educated guess what it could be in order to reassign the bug? Simply the kernel, or something else? Thanks, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648521: Login fails sometimes with screen issues
Hi, On 04/12/11 17:11, Lisandro Damián Nicanor Pérez Meyer wrote: On Sun, Dec 4, 2011 at 1:04 PM, dE .de.tec...@gmail.com wrote: On 12/03/11 20:39, Eric Lavarde wrote: [snip] Intel is giving problems? This's unlikely. This has to be a Debian bug. No, that would not be surprising at all. I assume dE was being sarcastic but that doesn't really help me. I accept your opinion that the Intel driver are less than optimal but, on the other hand, they've worked flawlessly under Squeeze with KDE, so we've got a regression somewhere. In order to avoid ping-pong between KDE, kernel, and xorg, it would be already helpful to get instructions on how to pin down the issue in one of the 3 areas. And as KDE is the first one (from a user perspective) to fail without saying where, I would start there to make him spit more information. My question is how? (I'm computer literate but no C/C++/debug guru). Thanks, Eric PS: after some days of practical experience, shutting off compositing didn't really help after all, the issue is still there and my user (my wife) is getting upset. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651605: plasma-widgets-workspace: Device Notifier shows Android UMS Composite as title without label
Package: plasma-widgets-workspace Version: 4:4.6.5-3 Severity: normal Hello, since I upgraded from Squeeze to Wheezy, the KDE Device Notifier doesn't show Android disks with their label but only as 'Android UMS Composite'. This is an issue because I have a Galaxy S which exports 2 disks (internal and external) and it's now impossible to tell which entry in the device notifier is which one, I have to mount and check with a 50% chance of success. The same could happen to anybody having 2 Android devices. Interestingly enough, the disks are mounted under their label: $ mount [...] /dev/sdg on /media/ANDROIDIN08 type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,uhelper=udisks) but they still appear as 'Android UMS Composite' e.g. in Dolphin. It might mean that it's some piece of the KDE framework that gives the wrong name to the Device Notifier and to Dolphin, but I have no clue which one it might be (it was difficult enough to find out to which package, the device notifier belongs). Let me know if I can provide more information, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plasma-widgets-workspace depends on: ii libc6 2.13-21 ii libgcc1 1:4.6.2-5 ii libkcmutils4 4:4.6.5-2+b1 ii libkdecore5 4:4.6.5-2+b1 ii libkdeui5 4:4.6.5-2+b1 ii libkdewebkit5 4:4.6.5-2+b1 ii libkio5 4:4.6.5-2+b1 ii libkunitconversion4 4:4.6.5-2+b1 ii libkworkspace44:4.6.5-3 ii libplasma34:4.6.5-2+b1 ii libplasmaclock4abi1 4:4.6.5-3 ii libqt4-dbus 4:4.7.3-5 ii libqt4-network4:4.7.3-5 ii libqt4-xml4:4.7.3-5 ii libqtcore44:4.7.3-5 ii libqtgui4 4:4.7.3-5 ii libqtwebkit4 2.1.0~2011week13-2 ii libsolid4 4:4.6.5-2+b1 ii libstdc++64.6.2-5 ii libx11-6 2:1.4.4-4 ii libxcomposite11:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxfixes31:5.0-4 ii libxrender1 1:0.9.6-2 ii plasma-dataengines-workspace 4:4.6.5-3 plasma-widgets-workspace recommends no packages. plasma-widgets-workspace 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#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 26/11/11 13:02, Jonathan Nieder wrote: I hope to find time to look at this more soon. For now I've assigned you bug#650081. If these turn out to have the same cause, we can merge them later. After a look at [1], I extracted the ACPI tables according to: acpidump acpidump # cp your ACPI tables from memory to disk acpixtract -a acpidump # extract them into raw, single tables and attach them here. I must admit that the rest looks like voodoo to me, but if you can provide some more specific instructions, I'd be more than happy to help drive this forward. Thanks, Eric [1] http://lwn.net/Articles/237085/ ASUS_P8H67-M_EVO_acpi.tgz Description: application/compressed-tar
Bug#648521: Login fails sometimes with screen issues
Hi Pino, On 10/12/11 14:02, Pino Toscano wrote: Can you please check whether #651316 could be also your case? i.e., downgrade libdrm-intel1 to 2.4.27-1, and in case also attach the dmesg log. I already have libdrm-intel1 2.4.27-1 Regarding dmesg, I'd like to do it, but in general, once I've got the issue, I need to reboot and I don't have access to any console... Anyway, I've done 'dmesg -c dmesg.txt' and then called 'sleep 90; dmesg dmesg1.txt' before bringing the whole thing to crash but the resulting dmesg1.txt is empty. I attach dmesg.txt but I guess that it's relatively useless. Eric dmesg.txt.gz Description: GNU Zip compressed data
Bug#648521: Login fails sometimes with screen issues
Hi, On 10/12/11 17:55, dE . wrote: syslog also logs kernel and X messages, check those out. I already attached all this to the initial bug report... Also do a memtest. the problem appeared as I upgraded from Squeeze to Wheezy, it would be quite bad luck that it'd be due to a memory error at the same time. But ok it can't hurt... I'll let you know. Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648521: Login fails sometimes with screen issues
On 10/12/11 18:31, Eric Lavarde wrote: Also do a memtest. the problem appeared as I upgraded from Squeeze to Wheezy, it would be quite bad luck that it'd be due to a memory error at the same time. But ok it can't hurt... I'll let you know. Mem test done, nothing wrong here. Thanks, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648521: Login fails sometimes with screen issues
Hi, On 03/12/11 15:06, dE . wrote: This looks like a graphics or bad hardware issues. Do you have composting enabled? Also what's your graphic chip? Compositing: I guess so, if I go to System Settings - Desktop effects are ON. I shut it off and the problems seems to have gone, BUT: 1. the first time I tried to re-open the desktop effects settings, KDE threw me out of the desktop, back to KDM. 2. now everything is greyed out with an information message Desktop effects are not available on this system due to the following technical issues: (but no issue description). Graphic chip: Intel [16.906] (II) intel(0): Integrated Graphics Chipset: Intel(R) 965Q 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) [0.992347] Linux agpgart interface v0.103 [0.992462] agpgart-intel :00:00.0: Intel 965Q Chipset [0.992545] agpgart-intel :00:00.0: detected gtt size: 524288K total, 262144K mappable [0.993377] agpgart-intel :00:00.0: detected 8192K stolen memory [0.993501] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xe000 So, something between drivers and KDE indeed. Any further idea? Thanks, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648521: Login fails sometimes with screen issues
Hello, some more information: it appears that the issue is sometimes accompanied by screen disturbances, i.e. the screen appears scrambled and multiple times on the monitor (but not always), in which case I can only reboot the PC to get rid of the problem. Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hello, for what's it's worth, I've contacted ASUS and their only answer, beside we don't support Linux because there are so many of them, was that their board supports the ACPI Specification 2.0a. Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650173: udev: Music cdroms cannot be read
Package: udev
Version: 172-1
Severity: important
Hello,
since I've upgraded from squeeze to wheezy, I can't read music CDs
anymore. If I put such a CD in the drive, I get the following dmesg:
[ 988.152171] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 988.152177] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 988.152183] Info fld=0x10, ILI
[ 988.152185] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this
track
[ 988.152193] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00
02 00
[ 988.152204] end_request: I/O error, dev sr0, sector 64
[ 988.152210] Buffer I/O error on device sr0, logical block 16
[ 988.152214] Buffer I/O error on device sr0, logical block 17
[ 988.159271] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 988.159276] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 988.159282] Info fld=0x10, ILI
[ 988.159284] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this
track
[ 988.159290] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00
02 00
[ 988.159301] end_request: I/O error, dev sr0, sector 64
[ 988.159305] Buffer I/O error on device sr0, logical block 16
[ 988.159308] Buffer I/O error on device sr0, logical block 17
[ 988.171518] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 988.171524] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 988.171529] Info fld=0x10, ILI
[ 988.171531] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this
track
[ 988.171538] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00
02 00
[ 988.171549] end_request: I/O error, dev sr0, sector 64
[ 988.171553] Buffer I/O error on device sr0, logical block 16
[ 988.171556] Buffer I/O error on device sr0, logical block 17
You might ask what it has to do with udev, but when searching for these
error messages on the net, the most relevant hit was
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591290 so here you are.
I tried to remove /etc/udev/rules.d/70-persistent-cd.rules and reboot,
but without noticeable improvement or even difference. I attach the
rule.
Any help would be appreciated, let me know if I can provide more
information,
Eric
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-21
ii libselinux12.1.0-4
ii libudev0 172-1
ii lsb-base 3.2-28
ii util-linux 2.19.1-5
Versions of packages udev recommends:
ii pciutils 1:3.1.7-12
ii usbutils 1:004-2
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/title/upgrade:
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.
# HL-DT-ST_DVD-RAM_GSA-H60L (pci-:00:1f.2-scsi-1:0:0:0)
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.2-scsi-1:0:0:0, SYMLINK+=cdrom,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.2-scsi-1:0:0:0, SYMLINK+=cdrw,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.2-scsi-1:0:0:0, SYMLINK+=dvd,
ENV{GENERATED}=1
SUBSYSTEM==block, ENV{ID_CDROM}==?*,
ENV{ID_PATH}==pci-:00:1f.2-scsi-1:0:0:0, SYMLINK+=dvdrw,
ENV{GENERATED}=1
Bug#650191: digikam: Geolocation using Marble not available
Package: digikam Version: 2:1.9.0-3+b1 Severity: normal Hello, I recently upgraded from squeeze to wheezy, and why the new digikam, I get a greyed out Geolocation window on the right hand side of digiKam, and a message stating Geolocation using Marble not available even if the image has GPS coordinates (I see them in the metadata). I don't think it's related but there was a similar bug report in the past http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569729 Nothing marble-alike seems to be a dependency of digiKam anymore, but the changelog doesn't say anything either, so I don't know... Anyway Marble stuff seems correctly installed: ii libmarblewidget11 4:4.6.5-1+b1Marble globe widget library ii marble-data 4:4.6.5-1 data files for Marble ii marble-plugins 4:4.6.5-1+b1plugins for Marble Thanks for your help, Eric -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages digikam depends on: ii digikam-data 2:1.9.0-3 ii kdebase-runtime4:4.6.5-1+b1 ii kdepim-runtime 4:4.4.11.1-2 ii libc6 2.13-21 ii libgcc11:4.6.2-4 ii libglib2.0-0 2.28.8-1 ii libgphoto2-2 2.4.11-3.1 ii libgphoto2-port0 2.4.11-3.1 ii libjasper1 1.900.1-11 ii libjpeg8 8c-2 ii libkabc4 4:4.6.5-1 ii libkcmutils4 4:4.6.5-2+b1 ii libkdcraw9 4:4.6.5-3 ii libkde3support44:4.6.5-2+b1 ii libkdecore54:4.6.5-2+b1 ii libkdeui5 4:4.6.5-2+b1 ii libkemoticons4 4:4.6.5-2+b1 ii libkexiv2-94:4.6.5-3 ii libkfile4 4:4.6.5-2+b1 ii libkhtml5 4:4.6.5-2+b1 ii libkidletime4 4:4.6.5-2+b1 ii libkio54:4.6.5-2+b1 ii libkipi8 4:4.6.5-3 ii libkjsapi4 4:4.6.5-2+b1 ii libknotifyconfig4 4:4.6.5-2+b1 ii libkparts4 4:4.6.5-2+b1 ii libkprintutils44:4.6.5-2+b1 ii libkresources4 4:4.6.5-1 ii libkutils4 4:4.6.5-2+b1 ii liblcms1 1.19.dfsg-1+b1 ii liblensfun00.2.4-1 ii liblqr-1-0 0.4.1-1.1 ii libnepomuk44:4.6.5-2+b1 ii libnepomukutils4 4:4.6.5-2+b1 ii libphonon4 4:4.6.0really4.5.0-5 ii libpng12-0 1.2.46-3 ii libqt4-dbus4:4.7.3-5 ii libqt4-network 4:4.7.3-5 ii libqt4-qt3support 4:4.7.3-5 ii libqt4-sql 4:4.7.3-5 ii libqt4-sql-sqlite 4:4.7.3-5 ii libqt4-svg 4:4.7.3-5 ii libqt4-xml 4:4.7.3-5 ii libqtcore4 4:4.7.3-5 ii libqtgui4 4:4.7.3-5 ii libsolid4 4:4.6.5-2+b1 ii libsoprano42.6.0+dfsg.1-4 ii libstdc++6 4.6.2-4 ii libtiff4 3.9.5-2 ii libx11-6 2:1.4.4-4 ii libxau61:1.0.6-4 ii libxdmcp6 1:1.1.0-4 ii phonon 4:4.6.0really4.5.0-5 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages digikam recommends: ii iceweasel [www-browser] 8.0-3 ii kipi-plugins 1.9.0-2+b1 ii konqueror [www-browser] 4:4.6.5-1 ii mplayerthumbs4:4.6.5-3 ii w3m [www-browser]0.5.3-4 Versions of packages digikam suggests: pn digikam-doc none -- 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#650173: Exact behavior
Hello again, I think I've sent this report a bit too fast; sorry for this but since I've migrated to wheezy, I seem to stumble from one issue to the next (I know, I know, testing and I wanted to help test, but...). Anyway, some more info: # file -s /dev/sr0 /dev/sr0: ERROR: cannot read `/dev/sr0' (Input/output error) # dd of=/tmp/test.dd if=/dev/sr0 dd: reading `/dev/sr0': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00705761 s, 0.0 kB/s And (g)ddrescue doesn't work either (which is my main issue, to be honest, because one of my CDs is scratched somewhere in the middle). On the other hand, K3B is able to rip the CD (up to the middle in this specific case) and KSCD is able to play it, but the device notifier of KDE doesn't show the CD as it used to do. Hope the issue is now clearer, Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
