Bug#1043112: (no subject)
In the last Testing: = Configurazione di linux-image-6.5.0-2-amd64 (6.5.6-1)... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.5.0-2-amd64. Sign command: /lib/modules/6.5.0-2-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j4 KERNELRELEASE=6.5.0-2-amd64 -C /lib/modules/6.5.0-2-amd64/build M=/var/lib/dkms/linux-apfs-rw/0.3.3+git20230810+ds-1/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.0-2-amd64 (x86_64) Consult /var/lib/dkms/linux-apfs-rw/0.3.3+git20230810+ds-1/build/make.log for more information. dkms autoinstall on 6.5.0-2-amd64/x86_64 failed for linux-apfs-rw(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.0-2-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: errore nell'elaborare il pacchetto linux-image-6.5.0-2-amd64 (--configure): il sottoprocesso installato pacchetto linux-image-6.5.0-2-amd64 script post-installation ha restituito lo stato di errore 1 Configurazione di libdebhelper-perl (13.11.7)... Configurazione di m17n-db (1.8.4-1)... Configurazione di debhelper (13.11.7)... Configurazione di ruby-rubygems (3.4.20-1)... dpkg: problemi con le dipendenze impediscono la configurazione di linux-image-amd64: linux-image-amd64 dipende da linux-image-6.5.0-2-amd64 (= 6.5.6-1); tuttavia: Il pacchetto linux-image-6.5.0-2-amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto linux-image-amd64 (--configure): problemi con le dipendenze - lasciato non configurato Configurazione di apache2-bin (2.4.58-1)... Configurazione di libwbclient0:amd64 (2:4.19.2+dfsg-1)... Configurazione di python3-pycurl (7.45.2-6)... Configurazione di apache2-doc (2.4.58-1)... Configurazione di calibre-bin (6.29.0+ds-1)... Configurazione di linux-headers-6.5.0-2-amd64 (6.5.6-1)... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.5.0-2-amd64. Sign command: /lib/modules/6.5.0-2-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j4 KERNELRELEASE=6.5.0-2-amd64 -C /lib/modules/6.5.0-2-amd64/build M=/var/lib/dkms/linux-apfs-rw/0.3.3+git20230810+ds-1/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.0-2-amd64 (x86_64) Consult /var/lib/dkms/linux-apfs-rw/0.3.3+git20230810+ds-1/build/make.log for more information. dkms autoinstall on 6.5.0-2-amd64/x86_64 failed for linux-apfs-rw(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.0-2-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.0-2-amd64.postinst line 11. dpkg: errore nell'elaborare il pacchetto linux-headers-6.5.0-2-amd64 (--configure): il sottoprocesso installato pacchetto linux-headers-6.5.0-2-amd64 script post-installation ha restituito lo stato di errore 1 Configurazione di apache2-data (2.4.58-1)... Configurazione di libldb2:amd64 (2:2.8.0+samba4.19.2+dfsg-1)... Configurazione di apache2-utils (2.4.58-1)... dpkg: problemi con le dipendenze impediscono la configurazione di linux-headers-amd64: linux-headers-amd64 dipende da linux-headers-6.5.0-2-amd64 (= 6.5.6-1); tuttavia: Il pacchetto linux-headers-6.5.0-2-amd64 non è ancora configurato. dpkg: errore nell'elaborare il pacchetto linux-headers-amd64 (--configure): problemi con le dipendenze - lasciato non configurato Configurazione di apache2 (2.4.58-1)... apache-htcacheclean.service is a disabled or a static unit not running, not starting it. Configurazione di apache2-suexec-pristine (2.4.58-1)... Configurazione di samba-libs:amd64 (2:4.19.2+dfsg-1)... Configurazione di calibre (6.29.0+ds-1)... Configurazione di libsmbclient:amd64 (2:4.19.2+dfsg-1)... Elaborazione dei trigger per desktop-file-utils (0.26-1)... Elaborazione dei trigger per hicolor-icon-theme (0.17-2)... Elaborazione dei trigger per libc-bin (2.37-12)... Elaborazione dei trigger per man-db (2.11.2-3)... Elaborazione dei trigger per shared-mime-info (2.2-1)... Elaborazione dei trigger per mailcap (3.70+nmu1)... Si sono verificati degli errori nell'elaborazione: linux-image-6.5.0-2-amd64 linux-image-amd64 linux-headers-6.5.0-2-amd64 linux-headers-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Configurazione di linux-image-6.5.0-2-amd64 (6.5.6-1)... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.5.0-2-amd64. Sign command: /lib/modules/6.5.0-2-amd6
Bug#1040910: Nvidia firmware missing on Testing
Package: firmware-misc-nonfree Version: 20230515-3 My machine (with Cinnamon) has Nvidia GTX 670. On Testing, after the last upgrades I receive: root@debian:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.3.0-1-amd64 W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/hs_bl_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/hs_bl_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/hs_bl_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/hs_bl_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/desc.bin for module nouveau Some drivers missing? Thnk you ms
Bug#996668: (no subject)
Same problem for me on Testing, obviously with Cinnamon and lightdm. I have no applet and, as always, only the TimeAndDate @ nightflame desklet. I noticed that if I log out of the session and inspect the system from lightdm, the problem does not arise
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I still fail to burn ISO even to blank CDs. The same for SAO or DAO to blank and than burn. I tried to "play" a bit with the few customizable fields in the Brasero plugins, basically two: cdrdao (enable the "--driver generic-mmc-raw" flag) and growisofs (allow the use of DAO), but the problems persist. Gconf is obsolete and now replaced by Dconf, but in fact I don't know where to put my hands. I try to deepen ... m Il 15/11/21 17:11, Thomas Schmitt ha scritto: Hi, i wrote: My only idea which does not need a code change is to employ the wodim plugin of Brasero and to hope that it burns by write type SAO. Mauro Sacchetto wrote: Which way? Good question. I have wodim installed. But last time when i tried, the wodim item was greyed out in the plugin list window which i somehow managed to pop up. Google brings me to https://github.com/lmedinas/brasero which in "Notes on plugins for advanced users" proposes to remove libburn (bleh !) or to use something named Gconf for changing plugin priorities. Wikipedia says: "GConf was a system used by the GNOME desktop". The riddle remains, i fear. Have a nice day :) Thomas
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
Il 15/11/21 14:58, Thomas Schmitt ha scritto: My only idea which does not need a code change is to employ the wodim plugin of Brasero and to hope that it burns by write type SAO. If so, then the drive would not get lost after a successful burn run. Which way? Thanx! m
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
Il 14/11/21 14:25, Thomas Schmitt ha scritto: The main question is: Is the drive unusable afterwards ? (I.e. do i have identified the culprit for your drive problem ?) I put the CD into the drive, mount and umount it: all goes. I lauch che command and obtain: == samiel@darkstar:~$ samiel@darkstar:~$ sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin bash: samiel@darkstar:~$: comando non trovato samiel@darkstar:~$ sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin SCSI Status: Check Condition Sense Information: Fixed format, current; Sense key: Illegal Request Additional sense: Unaligned write command == After this, the drive is unavailable: == Impossible to mount debian...iso Error mounting the system-managed device /dev/sr0: no medium fount o /dev/sr0 == m
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
Il 14/11/21 12:02, Thomas Schmitt ha scritto: Hi, i now have clear evidence from a run of sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin that the read attempt for sector 0x (= -1) brings the ASUS DRW-24D5MT into the unusable state. @ Mauro Sacchetto: Could you please try to reproduce this finding after installing sg3-utils. I obtain === samiel@darkstar:~$ sg_raw /dev/sr0 be 00 ff ff ff ff 00 00 01 10 00 00 --outfile=tdb_data.bin SCSI Status: Check Condition Sense Information: Fixed format, current; Sense key: Illegal Request Additional sense: Unaligned write command === Is it my test right and enough? - Possible remedies: We would need a Brasero developer to find a workaround, because not only the bad READ CD command needs to be avoided, but also a replacement for the code gesture to distinguish TAO CDs from SAO CDs would have to be developed. Maybe this distinction is not really necessary. It seems not to work properly on the TSSTcorp drive by making a false correction of the track size. But that would be up to a Brasero developer to decide. In fact I am a little surprised (although I don't know how these things are handled by the Debin team) that so far there has been no intervention by the packagers of Brasero
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I'm not sure it is what are you searching for, but Brasero produces a log launching from console it by : brasero -g --brasero-media-debug > log 2>&1 Then , I choose "Disk copy" and find ~/log Il 12/11/21 13:25, Thomas Schmitt ha scritto: I was not able to talk Brasero into showing me its session log for the failed "Copy" run. If my new theory is right there should be a log line "Checking for TDBs in track pregap." before nothing works any more.
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
Il 11/11/21 22:49, Thomas Schmitt ha scritto: Hi, Mauro Sacchetto wrote: that is (more or less): "Impossible to block unity". "unit", maybe ? The device. Yes, sorry for my bad English. After Brasero fails, it's impossible to erase the CD with K3, Either Brasero did its evil deed before trying to lock the unità or the failure to do so did not prevent further access to the drive. Do i get it right that you ordered Brasero to copy the CD to an image file, not a second CD/DVD/BD drive ? Something in Brasero's own activities for drive and medium inspection must be to blame. I will try the "Copy" task with fvwm tomorrow, just to be sure that it's not about the desktops. Yes: for I have only a drive, fist the Cd is copied in an image on HD, and then the image burned in a new support in the same drive Simon McVittie wrote: My understanding is that udisks does not automatically mount anything on its own If I'm not wrong, the CD is not automaticalli mounted. I see its name in Nemo -- Devices, but it needs a double click to mount it and to inspect its content
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
On Testing / Cinnamon it's impossible too "copy a disk"
(another voice of Brasero menu)
The CD-RW seems to be recognized and the burning begins,
but fails with:
Session error : Impossibile bloccare l'unità ((null))
(brasero_burn_record brasero-burn.c:2854)
that is (more or less): "Impossible to block unity".
The same on Stable / KDE with Brasero further installed
(obviously with all its dependencies).
After Brasero fails, it's impossible to erase the CD with K3,
and it's necessary to reboot ("No disk on /dev/sr0")
After reboot, K3B recognize the presence of the CD and blank it.
So, in Xfce, Cinnamon or KDE, the trouble is present
Il 11/11/21 15:12, Thomas Schmitt ha scritto:
Hi,
i managed to start fvwm2 (by Ctrl+Alt+F2 in the XFCE login window and
startx /usr/bin/fvwm2) and tried whether Brasero and ASUS drive have a
better relationship then.
They don't. It's as bad as with XFCE.
The Brasero run was started with a blank CD-RW in the drive and came,
with two pauses of a minute, up the "Checkreading" stage. Then it
complained that the drive was in use and the ASUS drive went unusable
as with the XFCE tests.
After a power cycle i verified that the CD was burned completely and
tried whether readom is to blame:
readom dev=/dev/sr0 f=cdimage.raw
It isn't. The drive stays usable after aborting readom with Ctrl+C because
it was stuck with futile retries to read the two TAO Run-out sectors at
the end of the track. The MD5 of cdimage.raw then matches the ISO image.
The CD does not get automounted with fvwm2. So this aspect of XFCE is
not a suspect any more.
Have a nice day :)
Thomas
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
ction BraseroLibburn TAO pre-track 01 : get_nwa(0)=1, d=0 , demand=396361728 , cap=736966656 BraseroLibburn called brasero_job_get_session_output_size BraseroLibburn called brasero_job_set_current_action ...BraseroLibburn syncing cache BraseroLibburn called brasero_job_get_session_output_size BraseroLibburn called brasero_job_set_current_action BraseroLibburn called brasero_job_get_session_output_size BraseroLibburn called brasero_job_set_current_action BraseroLibburn called brasero_job_get_session_output_size BraseroLibburn called brasero_job_set_current_action BraseroLibburn Async SYNCHRONIZE CACHE succeeded after 0.3 seconds BraseroLibburn Closing BraseroLibburn called brasero_job_set_dangerous BraseroLibburn called brasero_job_set_current_action BraseroLibburn Closing session BraseroLibburn Async CLOSE TRACK/SESSION succeeded after 6.0 seconds BraseroLibburn Writing BraseroLibburn Writing BraseroLibburn Write thread on drive 0 ended BraseroLibburn called brasero_job_set_dangerous BraseroLibburn Finished successfully session BraseroLibburn stopping Preparing to checksum (type 2 b710c178eb434d79ce40ce703d30a5f0) (brasero_burn_record_session brasero-burn.c:2483) BraseroChecksumImage called brasero_job_get_current_track BraseroChecksumImage called brasero_job_get_action BraseroChecksumImage called brasero_job_get_flags BraseroChecksumImage called brasero_job_get_action BraseroChecksumImage creating input BraseroChecksumImage called brasero_job_get_action BraseroReadom called brasero_job_get_action BraseroReadom linked to BraseroChecksumImage BraseroReadom getting varg BraseroReadom called brasero_job_get_action BraseroReadom called brasero_job_get_current_track BraseroReadom called brasero_job_get_output_typeBraseroChecksumImage called brasero_job_get_action BraseroReadom called brasero_job_get_current_trackBraseroChecksumImage called brasero_job_get_current_track BraseroReadom called brasero_job_get_output_type BraseroChecksumImage called brasero_job_set_current_action BraseroReadom reading from sector 0 to 193536 BraseroChecksumImage called brasero_job_get_current_trackBraseroReadom called brasero_job_get_fd_out BraseroChecksumImage called brasero_job_get_fd_inBraseroReadom called brasero_job_set_use_average_rate BraseroReadom got varg:BraseroChecksumImage Starting checksum generation live (size = 396361728) readomBraseroChecksumImage called brasero_job_set_nonblocking dev=/dev/sr0BraseroChecksumImage called brasero_job_get_fd_in -nocorr BraseroChecksumImage called brasero_job_get_fd_out -noerror BraseroChecksumImage called brasero_job_get_fd_in -sectors=0-193536 BraseroChecksumImage called brasero_job_get_fd_out -f=- BraseroReadom Launching command BraseroReadom called brasero_job_get_fd_in BraseroReadom called brasero_job_get_fd_out BraseroReadom stderr: readom: Device not ready. BraseroReadom called brasero_job_error BraseroReadom finished with an error BraseroReadom asked to stop because of an error error = 5 message = "L'unità è occupata" BraseroReadom stopping BraseroReadom got killed BraseroReadom disconnecting BraseroReadom from BraseroChecksumImage BraseroChecksumImage stopping BraseroChecksumImage closing connection for BraseroChecksumImage Session error : L'unità è occupata (brasero_burn_record brasero-burn.c:2854) And in fact: samiel@darkstar:~$ md5sum /dev/sr0 md5sum: /dev/sr0: Input/output error Il 10/11/21 13:09, Thomas Schmitt ha scritto: There seems to be involved a difference between Cinnamon of Debian Testing and XFCE of Debian 10. While Mauro Sacchetto does not get an unusable drive with Brasero and a blank CD-RW on Cinnamon, i get to that problem after writing succeeded but before the checksum gets verified by Brasero. (The CD verifies good in another drive by comparing the MD5s of ISO image and CD.) With non-blank CD-RW i experienced sometimes the problem already after inserting it into the ASUS drive while Brasero is running. Mauro Sacchetto did not report such an early problem.
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I smoothly burned the same ISO with Brasero to a DVD + RW, and the media was recognized immediately.On the other hand, the identification of the CD-RW is much slower (apart from the fact that the burn then fails) and this suggests that something else "occupies" the disc already, which is why Brasero does not find it and considers it unsupported. And let's go back to your hypotheses: either there is a perverse interaction between a Brasero component and the ASUS burner, or there is something else that interferes as soon as the media is inserted and before Brasero takes possession of it, which at this point does not manages to do. If there is any other test I can do (difficult, after all the ones you have done), I am always available. And thanks for your work! Il 09/11/21 16:44, Thomas Schmitt ha scritto: Do you have any idea what software might be doing this anomalous attempt, which is to try to read the data CD as if it were audio? Not yet. I normally don't use desktops but rather a window manager and i hate the kind of perky automats which i see on Debian 10 XFCE when i insert a medium or Brasero is done with writing a medium. Actually i use that machine mainly headless via ssh from an older machine which fits me like an old shoe. When i managed to get rid of XFCE i will try whether Brasero alone is able to spoil the drive. (I'd expect so, because the desktop's automats have enough opportunity to grope the medium after a xorriso run, but don't spoil the ASUS DVD burner.)
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I actually managed to burn a blank CD-RW with brasero as well. The problem arises when the CD-RW already has content. Do you have any idea what software might be doing this anomalous attempt, which is to try to read the data CD as if it were audio? Given their modest cost, I can of course also buy a more reliable burner. Have you encountered any models that offer greater guarantees than the ASUS in my possession? Thank you Il 09/11/21 14:41, Thomas Schmitt ha scritto: that the culprit is some software which wants to play the CD as audio CD
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I don't have the option of using more than one burner. I had done a simple experiment by installing Brasero (obviously with all its dependencies) on the partition where I have Stable with KDE. So different kernel and different version of Brasero. The behavior is the same as that found in Testing with Cinnamon. It is difficult to understand how we can get out of it. In any case from the console, both with wodim and with xorriso, it is possible to burn correctly, or by installing K3b, even if on Cinnamon it requires 125 packag
Bug#998718: (no subject)
Further experiment: I installed Brasero on a Stable (wih KDE) but receive the same behavior: Brasero crashes and make /dev/sr0 unavailable. On the contrary, K3b works fine
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
I eject the CD-RW, inser it again and try to mount it: root@darkstar:~# mount /home/samiel/debian-11.1.0-amd64-netinst.iso /media/cdrom mount: /media/cdrom0: WARNING: source write-protected, mounted read-only. So the drive itself is still operational after the mishap. Yes, but only as root, not as a simple user In Nemo -- Devices now I see twice the CD-RW, the old one (not inspectable) and the new one (inspectable). Looks like the drive was re-connected by the kernel without completely dropping the old connection. Possibly udev adjusted the symbolic link /dev/cdrom to the newer device file (/dev/sr1 ?). The only plausible theory which i have is that Brasero now hits a new problem in the kernel (5.14 ?) which may or may not involve the drive's firmware but does not show up with older kernels. (I have a kernel 5.10 which works well with 3 drives.) I installed on testing (kernel 5.14...) the kernel 5.10 from stable (backports), but I received the same error Thank you for your job!:)
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
== samiel@darkstar:~$ isoimage=/home/samiel/debian-11.1.0-amd64-netinst.iso samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed $isoimage xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. xorriso : NOTE : Disc status unsuitable for writing Drive current: -outdev '/dev/sr0' Media current: CD-RW Media status : is written , is closed Media summary: 1 session, 193536 data blocks, 378m data, 0 free Beginning to blank medium in mode 'fast'. xorriso : UPDATE : Blanking ( 1.0% done in 1 seconds ) ... xorriso : UPDATE : Blanking ( 97.8% done in 53 seconds ) Blanking done xorriso : NOTE : Re-assessing -outdev '/dev/sr0' Drive current: -outdev '/dev/sr0' Media current: CD-RW Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 703m free Beginning to write data track. xorriso : UPDATE : Thank you for being patient. Working since 0 seconds. ... xorriso : UPDATE : Thank you for being patient. Working since 43 seconds. xorriso : UPDATE : 0 of 378 MB written (fifo 99%) [buf 100%] 3.8x. ... xorriso : UPDATE : 378 of 378 MB written (fifo 0%) [buf 100%] 0.0x. xorriso : UPDATE : Thank you for being patient. Working since 728 seconds. Writing to '/dev/sr0' completed successfully. xorriso : NOTE : Re-assessing -outdev '/dev/sr0' xorriso : NOTE : Disc status unsuitable for writing Drive current: -outdev '/dev/sr0' Media current: CD-RW Media status : is written , is closed Media summary: 1 session, 193686 data blocks, 378m data, 0 free == It's all ok! Than I try to burn the ISO woth Brasero launching it by console: == samiel@darkstar:~$ brasero ** (brasero:2837): WARNING **: 01:07:35.934: Could not establish a connection to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Tracker3.Miner.Files was not provided by any .service files (brasero:2837): Gtk-WARNING **: 01:08:01.131: Failed to fetch network locations: È stato raggiunto il timeout Sense key: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x40 0xa0 0x03 0x21 0x04 0x00 0x00 0x00 0x00 0x00 Segmentazion fault == and Brasero crashes dmesg: == [ 1657.332142] sr 5:0:0:0: [sr0] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s [ 1657.332151] sr 5:0:0:0: [sr0] tag#10 CDB: Prevent/Allow Medium Removal 1e 00 00 00 01 00 [ 1657.332231] brasero[2837]: segfault at 2f400 ip 7fc57b9e0231 sp 7ffecc8f6368 error 4 in libc-2.32.so[7fc57b8a7000+149000] [ 1657.332268] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 == I eject the CD-RW, inser it again and try to mount it: == root@darkstar:~# mount /home/samiel/debian-11.1.0-amd64-netinst.iso /media/cdrom mount: /media/cdrom0: WARNING: source write-protected, mounted read-only. == In Nemo -- Devices now I see twice the CD-RW, the old one (not inspectable) and the new one (inspectable). But If I try to mount it not by console, but from Nemo (when there is only an occurence of the device) I receive: == Impossible to mount debiam-11iso Error mounting /dev/sr0 at /media/samiel7Debian...: no medium found on /dev/sro After this: == samiel@darkstar:~$ isoimage=/home/samiel/debian-11.1.0-amd64-netinst.iso samiel@darkstar:~$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed $isoimage xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. libburn : FAILURE : SCSI command 12h yielded host problem: 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?) libburn : FAILURE : Command: INQUIRY : 12 00 00 00 24 00 : dxfer_len= 36 libburn : FATAL : Lost connection to drive xorriso : FAILURE : Cannot acquire drive '/dev/sr0' xorriso : FAILURE : -as cdrecord: Job could not be performed properly. xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL' == Il 07/11/21 22:34, Thomas Schmitt ha scritto: Did you already try what happens if you eject the CD and insert it again after spoiling the drive state with Brasero and before using the drive for mounting or for xorriso -toc ?
Bug#998718: (no subject)
Better than my previous report: Putting the CD-RW into drivee: v root@darkstar:~# xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. TEST UNIT READY 00 00 00 00 00 00 2915 us [ 6174 ] INQUIRY 12 00 00 00 24 00 From drive: 36b 05 80 05 32 5b 00 00 00 41 53 55 53 20 20 20 20 44 52 57 2d 32 34 44 35 4d 54 20 20 20 20 20 20 32 2e 30 30 2729 us [ 9018 ] GET CONFIGURATION 46 00 00 00 00 00 00 00 08 00 From drive: 8b 00 00 01 7c 00 00 00 0a 3910 us [ 12968 ] GET CONFIGURATION 46 00 00 00 00 00 00 01 80 00 From drive: 384b 00 00 01 7c 00 00 00 0a 00 00 03 38 00 15 00 00 00 16 00 00 00 2b 00 00 00 1b 00 00 00 1a 00 00 00 14 00 00 00 13 00 00 00 12 00 00 00 11 00 00 00 10 00 00 00 0a 01 00 00 09 00 00 00 08 01 00 00 02 00 00 00 01 0b 08 00 00 00 07 01 00 00 00 00 02 07 04 02 00 00 00 00 03 0b 04 3b 00 00 00 00 04 08 04 02 00 00 00 00 10 01 08 00 00 08 00 00 01 01 00 00 1d 01 00 00 1e 09 04 03 00 00 00 00 1f 08 04 01 00 01 00 00 20 04 0c 00 00 00 00 00 00 08 00 00 00 01 00 00 21 0c 08 3d 0f 03 01 07 00 00 00 00 23 09 08 00 00 00 00 00 00 00 00 00 24 04 04 80 00 00 00 00 26 00 00 00 2a 04 04 01 00 00 00 00 2b 00 04 01 00 00 00 00 2c 00 04 03 00 00 00 00 2d 08 04 5f 00 00 00 00 2e 04 04 7f 00 0d 00 00 2f 08 04 4e 00 00 00 00 33 00 08 00 00 00 01 10 00 00 00 00 37 01 04 00 07 00 00 00 3b 00 04 01 00 00 00 01 00 07 04 00 00 00 00 01 01 00 04 00 00 00 00 01 03 00 04 03 00 01 00 01 04 04 04 00 00 00 00 01 05 07 04 00 00 00 00 01 06 00 04 00 00 00 01 01 07 15 04 1f 00 00 00 01 08 03 10 4b 4c 4a 4c 31 36 38 35 37 34 34 20 20 20 20 20 01 0a 00 0c 46 44 43 00 53 44 43 00 54 4f 43 00 01 0b 00 04 00 00 00 01 01 0c 03 10 32 30 31 39 30 36 31 37 31 30 34 39 20 20 00 00 3776 us [ 17057 ] MODE SENSE 5a 00 2a 00 00 00 00 00 1e 00 From drive: 30b 00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00 02 00 10 8a 00 10 02 c2 02 c2 5111 us [ 3 ] MODE SENSE 5a 00 2a 00 00 00 00 00 4c 00 From drive: 76b 00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00 02 00 10 8a 00 10 02 c2 02 c2 00 01 00 00 00 00 02 c2 00 01 00 00 02 c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2926 us [ 25256 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 00 03 00 From drive: 8b 00 00 00 14 00 00 00 00 2187 us [ 27482 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 01 03 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89 00 00 02 c1 1616 us [ 29158 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 01 03 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89 00 00 02 c1 1516 us [ 30725 ] GET PERFORMANCE ac 10 00 00 00 00 00 00 00 00 00 00 From drive: 8b 00 00 00 14 00 00 00 00 1012 us [ 31764 ] GET PERFORMANCE ac 10 00 00 00 00 00 00 00 01 00 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 00 0b 7c 00 02 f3 ff 00 00 1b 90 1053 us [ 32855 ] GET PERFORMANCE ac 10 00 00 00 00 00 00 00 01 00 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 00 0b 7c 00 02 f3 ff 00 00 1b 90 965 us [ 33860 ] MODE SENSE 5a 00 01 00 00 00 00 00 0c 00 From drive: 12b 00 12 21 00 00 00 00 00 01 0a 80 c0 582 us [ 34472 ] PREVENT/ALLOW MEDIA REMOVAL 1e 00 00 00 00 00 510 us [ 34991 ] START/STOP UNIT 1b 00 00 00 03 00 374 us [ 35390 ] TEST UNIT READY 00 00 00 00 00 00 1387 us [ 536936 ] PREVENT/ALLOW MEDIA REMOVAL 1e 00 00 00 01 00 2893 us [ 539878 ] START/STOP UNIT 1b 01 00 00 01 00 3156 us [ 543076 ] TEST UNIT READY 00 00 00 00 00 00 5605 us [ 1048864 ] START/STOP UNIT 1b 00 00 00 01 00 1562894 us [ 2611828 ] INQUIRY 12 00 00 00 24 00 From drive: 36b 05 80 05 32 5b 00 00 00 41 53 55 53 20 20 20 20 44 52 57 2d 32 34 44 35 4d 54 20 20 20 20 20 20 32 2e 30 30 524 us [ 2612573 ] MODE SENSE 5a 00 2a 00 00 00 00 00 1e 00 From drive: 30b 00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00 02 00 10 8a 00 10 02 c2 02 c2 3773 us [ 2616506 ] MODE SENSE 5a 00 2a 00 00 00 00 00 4c 00 From drive: 76b 00 4a 21 00 00 00 00 00 2a 42 3f 37 f1 77 2b 23 1b 90 01 00 02 00 10 8a 00 10 02 c2 02 c2 00 01 00 00 00 00 02 c2 00 01 00 00 02 c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5770 us [ 2622414 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 00 03 00 From drive: 8b 00 00 00 14 00 00 00 00 1529 us [ 2623993 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 01 03 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89 00 00 02 c1 1491 us [ 2625571 ] GET PERFORMANCE ac 00 00 00 00 00 00 00 00 01 03 00 From drive: 24b 00 00 00 14 00 00 00 00 00 00 00 00 00 05 7d a9 00 00 10 89 00 00 02 c1 1500 us [ 2627186 ] GET PERFORMANCE ac 10 00 00 00 00 00 00 00 00 00 00
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
thanx for your quick reply dmesg tell me: = [23315.697087] sr 5:0:0:0: [sr0] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s [23315.697092] sr 5:0:0:0: [sr0] tag#16 CDB: Prevent/Allow Medium Removal 1e 00 00 00 01 00 [23315.697128] brasero[9154]: segfault at 2f400 ip 7fb6350a5231 sp 7fff0e805918 error 4 in libc-2.32.so[7fb634f6c000+149000] [23315.697136] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 = xorriso tells me only = root@darkstar:~# xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. TEST UNIT READY 00 00 00 00 00 00 19 us [ 1091 ] INQUIRY 12 00 00 00 24 00 From drive: 36b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 us [ 1207 ] --- SG_IO: host_status= 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?) --- SG_IO: Gave up connection to drive libburn : FAILURE : SCSI command 12h yielded host problem: 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?) libburn : FAILURE : Command: INQUIRY : 12 00 00 00 24 00 : dxfer_len= 36 libburn : FATAL : Lost connection to drive xorriso : FAILURE : Cannot acquire drive '/dev/sr0' xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL' = Il 07/11/21 19:37, Thomas Schmitt ha scritto: Hi, i am upstream programmer of libburn, which might be in charge of burning underneath Brasero. Regrettably i cannot interpret Brasero's messages unless they come from libburn or libisofs. So i am not sure whether i can help with fixing Brasero. The statement by other software that no medium is found in /dev/sr0 surprises me. Such a status assessment is usually done by the drive and i am not aware of any regular means to let a drive ignore or deny its loaded medium. Do you see anything in dmesg that occured when Brasero failed and looks related to "sr" or "cdrom" ? Can i talk you into inquring the drive by xorriso and logging its SCSI transactions when the drive has gone mad from Brasero and a medium is still inserted ? xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log This would give insight into what the drive tells about its status without the programs-in-the-middle. The log is quite verbose and will have several hundred lines. Please post /tmp/xorriso.log as attachment or send it to me by private mail. (I wonder why udevadm monitor of Testing is so eager to insert blanks everywhere. But that would be a different bug, if it is not a copy+paste artefact.) Have a nice day :) Thomas -- Prof. Mauro Sacchetto Santa Croce 1332a 30135 Venezia tel.: 041 722938 cell.: 348 9690575 e-mail:mauro.sacche...@gmail.com Linux user no.: 353546 public key athttp://keyserver.linux.it
Bug#998718: (no subject)
To better clarify the nature of the problem, I installed on Testing / Cinnamon K3b (despite its many dependencies). K3b perfectly burns ISOs to CD-RW, unlike Brasero
Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW
Package: Brasero Version: 3.12.3-1 I work on Debian Testing (Bookworm) with Cinnamon, always kept up to date. The problem I point out is related to the burning of ISO to CD-RW using Brasero. I state that from the console using wodim I can both erase CD-RW and burn an ISO. Instead, if I proceed with Brasero with an already burned CD-RW (containing an ISO): a) if I try to erase the disk beforehand with the relative tool in the Tools menu, the disk is found but the operation is not carried out with the warning: === Unable to lock the drive === b) if I try to burn the ISO directly the disc is initially found, but the operation is not carried out with the warning: === Insert a writable CD or DVD. The disk in Asus DRW-24D5MT is not supported === After both types of attempts, the CD-RW (which has not been modified and still contains the paretenza ISO) is no longer found even by Nemo, with the warning: === Unable to mount Error mounting system-managed device / dev / sr0: no medium found on / dev / sr0 === If I reboot the system, the CD-RW is found again, and I can mount it from Nemo and inspect its contents. It seems that Brasero does not identify the CD-RW as such, ie as rewritable. The same operations succeed perfectly from a Stable with KDE, using K3b. I have compared the logs. Testing / Cinnamon gives me: === samiel @ darkstar: ~ $ udevadm monitor --property --udev monitor will print the received events for: UDEV - the event which udev sends out after rule processing UDEV [19048.365742] change /devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sr0 (block) ACTION = change DEVPATH = / devices / pci: 00/: 00: 1f.2 / ata6 / host5 / target5: 0: 0/5: 0: 0: 0 / block / sr0 SUBSYSTEM = block DISK_MEDIA_CHANGE = 1 DEVNAME = / dev / sr0 DEVTYPE = disk SEQNUM = 3051 USEC_INITIALIZED = 1848541 ID_CDROM = 1 SYSTEMD_MOUNT_DEVICE_BOUND = 1 ID_CDROM_CD_R = 1 ID_CDROM_CD_RW = 1 ID_CDROM_DVD = 1 ID_CDROM_DVD_R = 1 ID_CDROM_DVD_RAM = 1 ID_CDROM_DVD_R_DL_SEQ = 1 ID_CDROM_DVD_R_DL_JR = 1 ID_CDROM_DVD_PLUS_R_DL = 1 ID_CDROM_DVD_PLUS_R = 1 ID_CDROM_DVD_PLUS_RW = 1 ID_CDROM_DVD_RW_SEQ = 1 ID_CDROM_DVD_RW_RO = 1 ID_CDROM_CD = 1 ID_CDROM_RW_REMOVABLE = 1 ID_CDROM_DVD_RW = 1 ID_CDROM_DVD_R_DL = 1 ID_CDROM_MEDIA = 1 ID_CDROM_MEDIA_CD_RW = 1 ID_CDROM_MEDIA_STATE = complete ID_CDROM_MEDIA_SESSION_COUNT = 1 ID_CDROM_MEDIA_TRACK_COUNT = 1 ID_CDROM_MEDIA_TRACK_COUNT_DATA = 1 ID_ATA = 1 ID_TYPE = cd ID_BUS = ata ID_MODEL = DRW-24D5MT ID_MODEL_ENC = DRW-24D5MT \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 \ x20 ID_REVISION = 2.00 ID_SERIAL = DRW-24D5MT_KLJL1685744 ID_SERIAL_SHORT = KLJL1685744 ID_ATA_SATA = 1 ID_ATA_SATA_SIGNAL_RATE_GEN1 = 1 ID_WWN = 0x50014800 ID_WWN_WITH_EXTENSION = 0x50014800 ID_PATH = pci-: 00: 1f.2-ata-6.0 ID_PATH_TAG = pci-_00_1f_2-ata-6_0 ID_PATH_ATA_COMPAT = pci-: 00: 1f.2-ata-6 ID_FS_DATA_PREPARER_ID = XORRISO-1.5.0 \ x202018.09.15.133001 \ x2c \ x20LIBISOBURN-1.5.0 \ x2c \ x20LIBISOFS-1.5.0 \ x2c \ x20LIBBURN-1.5.0 ID_FS_UUID = 2021-11-03-15-04-45-00 ID_FS_UUID_ENC = 2021-11-03-15-04-45-00 ID_FS_BOOT_SYSTEM_ID = EL \ x20TORITO \ x20SPECIFICATION ID_FS_VERSION = Joliet Extension ID_FS_LABEL = Debian_testing_amd64_n ID_FS_LABEL_ENC = Debian \ x20testing \ x20amd64 \ x20n ID_FS_TYPE = iso9660 ID_FS_USAGE = filesystem ID_PART_TABLE_UUID = 7ed8b2bd ID_PART_TABLE_TYPE = dos ID_FOR_SEAT = block-pci-_00_1f_2-ata-6_0 MAJOR = 11 MINOR = 0 DEVLINKS = / dev / disk / by-id / wwn-0x50014800 / dev / disk / by-id / ata-DRW-24D5MT_KLJL1685744 /dev/disk/by-path/pci-:00:1f.2-ata-6 /dev/disk/by-path/pci-:00:1f.2-ata-6.0 / dev / cdrom / dev / disk / by-label / Debian \ x20testing \ x20amd64 \ x20n / dev / disk / by-uuid / 2021-11-03-15-04-45-00 TAGS =: systemd: uaccess: seat: CURRENT_TAGS =: systemd: uaccess: seat: === Stable / KDE gives to me: === samiel@darkstar:~$ udevadm monitor --property --udev monitor will print the received events for: UDEV - the event which udev sends out after rule processing UDEV [184.968927] change /devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sr0 (block) ACTION=change DEVPATH=/devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sr0 SUBSYSTEM=block DISK_MEDIA_CHANGE=1 DEVNAME=/dev/sr0 DEVTYPE=d
Bug#976987: lightdm-autologin-greeter inhibits the graphic server
package: lightdm-autologin-greeter version: 1.0-3 On Sid and Testing with Cinnamon, installing lightdm-autologin-greeter inhibits the graphic server. The screen remains black, with no cursor, and it is not possible to move to another shell even with key combinations. Eventually, you need to brutally reboot by shutting down your computer with the start key ms
Bug#969723: Impossible to install Lilypond on Sid because of python dependencies
Package: Lilypond
Version: 2.20.0-1
I'm trying to install Lilypond in Debian Sid:
==
root@darkstar:~# aptitude install lilypond
I seguenti pacchetti NUOVI (NEW) saranno installati:
lilypond{b} lilypond-data{a}
0 pacchetti aggiornati, 2 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 0 B/4.948 kB di archivi. Dopo l'estrazione,
verranno occupati 19,7 MB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
lilypond : Dipende: python:any which is a virtual package, provided by:
- python (2.7.17-2), ma non è installabile
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Mantenere i seguenti pacchetti alla versione attuale:
1) lilypond [Non installato]
Leave the following dependencies unresolved:
2) lilypond-data raccomanda lilypond (>= 2.20.0-1)
Accettare questa soluzione? [Y/n/q/?] q
Abbandonato ogni tentativo di risolvere queste dipendenze.
Uscita.
root@darkstar:~# aptitude install python
I seguenti pacchetti NUOVI (NEW) saranno installati:
python{b}
0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 22,9 kB di archivi. Dopo l'estrazione, verranno
occupati 69,6 kB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
python : Pre-dipende: python-minimal (= 2.7.17-2) ma non è installabile
Dipende: libpython-stdlib (= 2.7.17-2) ma non è installabile
Dipende: python2 (= 2.7.17-2) but 2.7.18-2 is installed
dh-python : Rompe: python but 2.7.17-2 is to be installed
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Mantenere i seguenti pacchetti alla versione attuale:
1) python [Non installato]
Accettare questa soluzione? [Y/n/q/?] q
Abbandonato ogni tentativo di risolvere queste dipendenze.
==
However, I'm not sure if it's a problem regarding just Lilypond,
or rather Python
Thank you
ms
Bug#953794: Gimp crashes at startup
package: Gimp version:2.10.14-2 and others After yesterday update, Gimp crashes on startup in Debian Sid (in my case, with Cinnamon): = ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-31' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex Thread model: posix gcc version 9.2.1 20200306 (Debian 9.2.1-31) using babl version 0.1.74 (compiled against version 0.1.74) using GEGL version 0.4.22 (compiled against version 0.4.22) using GLib version 2.64.0 (compiled against version 2.64.0) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Errore di segmentazione Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f560511b398] gimp-2.10(+0xd7980)[0x564f0cf64980] gimp-2.10(+0xd7da8)[0x564f0cf64da8] gimp-2.10(+0xd8419)[0x564f0cf65419] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14110)[0x7f5604612110] gimp-2.10(gimp_param_spec_layer_id+0x64)[0x564f0d2f1704] gimp-2.10(gimp_pdb_compat_param_spec+0x1c7)[0x564f0d209647] gimp-2.10(gimp_plug_in_handle_message+0x1197)[0x564f0d216067] gimp-2.10(gimp_plug_in_manager_call_query+0x191)[0x564f0d224681] gimp-2.10(gimp_plug_in_manager_restore+0x796)[0x564f0d21c606] gimp-2.10(+0x3ad24d)[0x564f0d23a24d] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x1a2)[0x7f56048a3fd2] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x26f06)[0x7f56048b6f06] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xbdf)[0x7f56048c254f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f56048c2edf] gimp-2.10(gimp_restore+0x102)[0x564f0d2397d2] gimp-2.10(app_run+0x4ab)[0x564f0cf642bb] gimp-2.10(main+0x37e)[0x564f0cf63a4e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f560445fe0b] gimp-2.10(_start+0x2a)[0x564f0cf63bda] ``` Thank you ms
Bug#943707: (no subject)
I'm interested i nunderstanding if it's really a bug, or depends from any wrong or different setting of my system thank you ms
Bug#949703: thunderbird doesn' start on Sid
Package: Thunderbird Version: 1:68.4.1-1+b1 after the last today update, thunderbird doesn' start on Sid. from console: === samiel@darkstar:~$ thunderbird ExceptionHandler::GenerateDump cloned child 4951 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... === ms
Bug#945974: For certain operations FF "recomposes" the screen and takes a long time
Package: FontForge Version: 1:20190801~dfsg-2 and others I installed the last version available for Sid. When I start a process as glyph simplification, adding extremum an so on, for every glyphs FontForge "recomposes" the screen every time as if browsed from top to bottom and consequently takes a very long time to perform glyph operations. I realize that my description is obscure, so I am attaching the screen shot. With the correct functioning, the screen is fixed, only the bar proceeds and consequently the process is very fast https://www.dropbox.com/s/5mguq0h8vmo1wyp/20191201_232044.mp4?dl=0 Thank you ms
Bug#943707: lilypond preinst fails if tetex-bin not installed
Package: lilypond
Version: 2.19.81+really-2.18.2-13
In Sid we find the bug already a long time ago reported:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336052
=
root@darkstar:~# aptitude install lilypond
I seguenti pacchetti NUOVI (NEW) saranno installati:
lilypond lilypond-data{a}
0 pacchetti aggiornati, 2 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 3.711 kB di archivi. Dopo l'estrazione, verranno
occupati 16,0 MB.
Continuare? [Y/n/?] Y
Get: 1 http://ftp.it.debian.org/debian sid/main amd64 lilypond-data all
2.19.81+really-2.18.2-13 [1.817 kB]
Get: 2 http://ftp.it.debian.org/debian sid/main amd64 lilypond amd64
2.19.81+really-2.18.2-13 [1.894 kB]
Scaricato 3.711 kB in 0s (15,8 MB/s)
Selezionato il pacchetto lilypond-data non precedentemente selezionato.
(Lettura del database... 315817 file e directory attualmente installati.)
Preparativi per estrarre
.../lilypond-data_2.19.81+really-2.18.2-13_all.deb...
Estrazione di lilypond-data (2.19.81+really-2.18.2-13)...
Preparativi per estrarre .../lilypond_2.19.81+really-2.18.2-13_amd64.deb...
/var/lib/dpkg/tmp.ci/preinst: 1: kpsewhich: not found
dpkg: errore nell'elaborare l'archivio
/var/cache/apt/archives/lilypond_2.19.81+really-2.18.2-13_amd64.deb
(--unpack):
il sottoprocesso nuovo pacchetto lilypond script pre-installation ha
restituito lo stato di errore 127
Si sono verificati degli errori nell'elaborazione:
/var/cache/apt/archives/lilypond_2.19.81+really-2.18.2-13_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Configurazione di lilypond-data (2.19.81+really-2.18.2-13)...
Elaborazione dei trigger per libc-bin (2.29-2)...
=
I specify that in my system I installed:
1) the vanilla version of Texlive 2019
(and not the "debianozed" version;
2) a "fake" package created with equivs for managing some dependencies,
that makes, fon example, TexStudio perfectly working.
At present, I'm using Cinnamon.
I still have the doubt that this is actually a bug. But if the problem
depends on equivs, I stress that it had not appeared in a Testing
installation with KDE as WM.
Thank you
ms
Bug#885629: impossible to install kdewebdev in Sid
Package: kdewebdev
Version: 4:16.04.3-1
It's impossible to install kdewebdev in Sid:
==
root@debian:~# aptitude install kdewebdev
I seguenti pacchetti NUOVI (NEW) saranno installati:
kdepimlibs-kio-plugins{a} kdewebdev kfilereplace{a} kimagemapeditor{a}
klinkstatus{a} kommander{a} libakonadi-kmime4{a} libkimap4{a}
libkrossui4{a} libmailtransport4{a}
0 pacchetti aggiornati, 10 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 2.595 kB di archivi. Dopo l'estrazione, verranno
occupati 7.280 kB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
kio-sieve : Rompe: kdepimlibs-kio-plugins but 4:4.14.10-9 is to be installed
kio-smtp : Rompe: kdepimlibs-kio-plugins but 4:4.14.10-9 is to be installed
kdepim-runtime : Rompe: kdepimlibs-kio-plugins but 4:4.14.10-9 is to be
installed
kio-ldap : Rompe: kdepimlibs-kio-plugins but 4:4.14.10-9 is to be installed
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Rimuovere i seguenti pacchetti:
1) kde-full [5:94 (now, unstable)]
2) kde-standard [5:94 (now, unstable)]
3) kdepim [4:16.04.3+5.94 (now, unstable)]
4) kdepim-doc [4:17.08.3-1 (now, unstable)]
5) kdepim-runtime [4:17.08.3-1 (now, unstable)]
6) kio-ldap [17.08.3-1 (now, unstable)]
7) kio-sieve [4:17.08.3-1 (now, unstable)]
8) kio-smtp [17.08.3-1 (now, unstable)]
9) kmail [4:17.08.3-1 (now, unstable)]
10) knotes [4:17.08.3-1 (now, unstable)]
11) konsolekalendar [4:17.08.3-1 (now, unstable)]
12) kontact [4:17.08.3-1 (now, unstable)]
13) korganizer [4:17.08.3-1 (now, unstable)]
Leave the following dependencies unresolved:
14) kontact raccomanda kmail
15) kontact raccomanda knotes
16) kopete raccomanda kdepim-runtime
17) kdepim raccomanda kdepim-doc
=
ms
Bug#883102: (no subject)
The same error for Italian version: == Preparativi per estrarre .../13-kwrite_4%3a17.08.3-1_amd64.deb... Estrazione di kwrite (4:17.08.3-1) su (4:16.08.3-1+b1)... dpkg: errore nell'elaborare l'archivio /tmp/apt-dpkg-install-pOWute/13- kwrite_4%3a17.08.3-1_amd64.deb (--unpack): tentata sovrascrittura di "/usr/share/doc/HTML/it/kwrite/index.cache.bz2" presente anche nel pacchetto kde-l10n-it 4:16.04.3-5 == ms
Bug#808094: Bug still present
In data martedì 25 ottobre 2016 17:13:44 CEST, Diederik de Haas ha scritto: > Control: merge -1 807902 > > Various people have reported that a newer qt version solved the issue for > them and I haven't seen the problem/crash in quite a while either. > > Does the bug still apply for you two? No, now all works fine thanx ms
Bug#841736: lilypond in Testing?
Package: lilypond Version: 2.18.2-4.1 Lilypond is not present in Testing. In DEVELOPER INFORMATION I read: == testing migration excuses: 294 days old (needed 5 days) == Is there any hope that, after almost one year, you plan to restore lilypond in Testing? tmanx ms
Bug#836601: (no subject)
same bug today on Testing
Bug#840674: Amule crashes in Testing
Package: amule Version: 1:2.3.2-1+b1 After the last upgrade in Testing,, amule crashes with the following backtrace: === samiel@debian:~$ amule 19:46:25: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8), and your program used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8). 2016-10-13 19:46:25: Initialising aMule 2.3.2 compiled with wxGTK2 v3.0.2 and Boost 1.61 2016-10-13 19:46:25: Checking if there is an instance already running... 2016-10-13 19:46:25: No other instances are running. A fatal error has occurred and aMule has crashed. Please assist us in fixing this problem by posting the backtrace below in our 'aMule Crashes' forum and include as much information as possible regarding the circumstances of this crash. The forum is located here: http://forum.amule.org/index.php?board=67.0 If possible, please try to generate a real backtrace of this crash: http://wiki.amule.org/wiki/Backtraces =| BACKTRACE FOLLOWS: |--- Current version is: aMule 2.3.2 compiled with wxGTK2 v3.0.2 and Boost 1.61 Running on: Linux 4.7.0-1-amd64 x86_64 [2] ?? in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f6710722cac] [3] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f67128bc100] Annullato Thanx ms
Bug#827138: (no subject)
this bug is the same of: https://www.mail-archive.com/debian-bugs-dist%40lists.debian.org/msg1428774.html
Bug#827138: Impossible to install language packs in Testing
Package: kde-l10n-it Version: 4.14.0-3 When I try to install the Italian KDE language pack on Testing, the following error occurs: = aptitude install kde-l10n-nl The following NEW packages will be installed: kde-l10n-nl 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/10.0 MB of archives. After unpacking 24.8 MB will be used. The following packages have unmet dependencies: plasma-desktop-data : Breaks: kde-l10n-it (< 4:4.14.0-4~) but 4:4.14.0.-3 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) kde-full 2) kde-plasma-desktop 3) kde-standard 4) plasma-desktop 5) plasma-desktop-data 6) task-kde-desktop Leave the following dependencies unresolved: 7) task-desktop raccomanda task-gnome-desktop | task-xfce-desktop | task- kde-desktop | task-lxde-de Accept this solution? [Y/n/q/?] q Abandoning all efforts to resolve these dependencies. Abort. = But there is no kde-l10n-it < 4:4.14.0-4~ package neither in Testing nor in Unstable... Thanx ms
Bug#825440: [Pkg-kde-extras] Bug#825440: K3b obsolete in TEsting
In data venerdì 27 maggio 2016 10:02:04, Dominique Dumont ha scritto: > On Thursday 26 May 2016 23:26:55 Mauro Sacchetto wrote: > > I don't find any reason > > for K3b was eliminated in Testing... > > Is it right or there ia a big mistake? > > k3b was automatically removed from testing because of #807853 > > it will be back once the issue with ffmpeg is fixed. > > All the best Is that issue fixed n Testing too, with the recent update of ffmpeg at 7:3.0.2-3 versione? thanx ms
Bug#807853: (no subject)
news about solutions for this bug? when will we see again k3b in Testing? tnax
Bug#825440: K3b obsolete in TEsting
Package: k3b Version: 2.0.3a-1+b1 I don't find any reason for K3b was eliminated in Testing... Is it right or there ia a big mistake? ms
Bug#813118: unetbootin in Testing?
Package: unetbootin Version: 608-1 For in "Testing migration" I read: «excuses: 471 days old (needed 5 days)» herewith I ask you if you plan to put unetbootin again in tesing in a reasonable time after one year and a half. thanx ms
Bug#808846: abook in Testing
Package: abook Version: 0.6.0~pre2 In Testing there is no migration foreseen after "131 days old (needed 5 days)" from Sid. Do u plan to bring abook in Testing sooner or later? thanx ms
Bug#808094: Konsole segmentation fault after closing it
Package: Konsole Version: 15.08.0 On Sid, Konsole seems to work fine, but when I close that application, happens a segmentation fault: == Application: konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f5dff7d11b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5dff7c75dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f5dff7c7c79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f5dff7bc2ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f5dff7bc399 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7f5dff10af52 in __run_exit_handlers (status=0, listp=0x7f5dff473698 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #12 0x7f5dff10afa5 in __GI_exit (status=) at exit.c:104 #13 0x7f5dff0f5877 in __libc_start_main (main=0x400710 , argc=1, argv=0x7ffd7800b908, init=, fini=, rtld_fini=, stack_end=0x7ffd7800b8f8) at libc-start.c:325 #14 0x00400749 in _start () == i don't know which other information you need... ms
Bug#778736: (no subject)
it strikes me that after more than one year versione 2.0.3 is not yet ready for Debian, while it's in all other major Linux distros
Bug#803732: (no subject)
The burning goes well and copies are correct. The crash happens later, if and whwn you chose to verify
Bug#803732: (no subject)
Hoping that this bug (if confermed) will be solved at least with the new release of K3b-2.0.3
Bug#803732: K3b crashes on verify
Package: K3b Versione: 2.0.2 On Sid (I'm not sure on Testing) K3b crashes in masterizing a CD/DVD if it's choosen to verify:: k3b(23696) K3b::Device::DeviceHandler::run: finished command: "(CommandDiskInfo|CommandToc|CommandCdText)" k3b(23696) K3b::JobProgressDialog::slotNewSubTask: "Verifying track 1" k3b(23696) K3b::ActivePipe::open: (K3b::ActivePipe) successfully opened pipe. k3b(23696) K3b::ActivePipe::open: (K3b::ActivePipe) successfully opened pipe. k3b(23696) K3b::MediaCache::blockDevice: "/dev/sr0" k3b(23696) K3b::LsofWrapper::checkDevice: (K3b::LsofWrapper) matched: app: "k3b" pid: 23696 KCrash: Application 'k3b' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/ombra/.kde/socket-lorenz/kdeinit4__0 QSocketNotifier: Invalid socket 11 and type 'Read', disabling... Unable to start Dr. Konqi Not forwarding the crash to Apport.
Bug#800020: KFontView doesn't work on plasma-desktop (Testing)
Package: plasma-desktop Version: 4:5.4.1-1 In Testing (so I mean KDE/Plasma45) I'm not able to see the fonts. The windows od KFontView appears empty ns
Bug#799640: KFontView doesn't work on Testing
Package: KFontView Version: 5.4.1 In Testing (so I mean KDE/Plasma45) I'm not able to see the fonts. The windows od KFontView appears empty
Bug#763314: (no subject)
gftp doesn't work anymore i nTesting too. Same problem: whrn you choose an address from bookmarks, it crashes: == samiel@debian:~$ gftp Attempt to unlock mutex that was not locked Annullato == I think this bug is GRAVE and not NORMAL... ms -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#759388: Os-prober doesn't notice initrd files other than debian's one
package: os-prober
version: 1.64
Os-prober doesn't notice initrd files other than debian's one.
In a partiion I've Slackware. I created a initd.gz for slaclware
(generic kernel needs a initrd for ext4 module, if not I receive
a kernel panic) and tried to make grub set it from debian.
Please, consider
1) in Slackware partition there is a initrd.gz
===
root@debian:~# ls /mnt/slackware/boot/
config elilo-ia32.efiinside.bmp System.map
vmlinuz
config-generic-3.10.17 elilo-x86_64.efi onlyblue.bmp System.map-
generic-3.10.17 vmlinuz-generic-3.10.17
config-huge-3.10.17 initrd.gz README.initrd System.map-
huge-3.10.17 vmlinuz-huge-3.10.17
efi
===
2) os-prober doesn't notice it:
===
root@debian:~# os-prober
/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sdc4:Slackware Linux (Slackware 14.1):Slackware:linux
===
and after, to control:
===
root@debian:~# linux-boot-prober /dev/sdc4
/dev/sdc4:/dev/sdc4::/boot/vmlinuz-generic-3.10.17::root=/dev/sdc4
/dev/sdc4:/dev/sdc4::/boot/vmlinuz-huge-3.10.17::root=/dev/sdc4
===
3) update-grub2 obviuosly doent's set that initrd:
===
root@debian:~# update-grub2
Creazione di grub.cfg...
Trovata immagine linux: /boot/vmlinuz-3.14-2-amd64
Trovata immagine initrd: /boot/initrd.img-3.14-2-amd64
Trovato Windows Boot Manager su /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Trovato Slackware Linux (Slackware 14.1) su /dev/sdc4
Adding boot menu entry for EFI firmware configuration
done
===
4) the relevant part of /boor/grub/grub.cfg:
===
menuentry 'Slackware Linux (Slackware 14.1)' --class gnu-linux --class gnu --
class os $menuentry_id_option 'osprober-gnulinux-simple-e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf' {
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-
efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sdc4
}
submenu 'Opzioni avanzate per Slackware Linux (Slackware 14.1)'
$menuentry_id_option 'osprober-gnulinux-advanced-e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf' {
menuentry 'Slackware Linux (Slackware 14.1) (su /dev/sdc4)' --class
gnu-linux --class gnu --class os $menuentry_id_option 'osprober-
gnulinux-/boot/vmlinuz-generic-3.10.17--e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf'
{
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4
--hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sdc4
}
menuentry 'Slackware Linux (Slackware 14.1) (su /dev/sdc4)' --class
gnu-linux --class gnu --class os $menuentry_id_option 'osprober-
gnulinux-/boot/vmlinuz-huge-3.10.17--e76be8b8-55fb-47bd-a5b7-2a30a50f4dbf' {
insmod part_gpt
insmod ext2
set root='hd2,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4
--hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4 e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
else
search --no-floppy --fs-uuid --set=root e76be8b8-55fb-47bd-
a5b7-2a30a50f4dbf
fi
linux /boot/vmlinuz-huge-3.10.17 root=/dev/sdc4
}
}
===
i dont' understand why it's impossible to choose
between huge and generic kernel, and above all why
it lacks all occorrences of initrd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#759111: Missing gimp-help-...
package: gimp-help-it version: 2.6.1-1 For Gimp help packages are the same ones for Unstable, Testing and Stable, it's hard to understand why the gimp-help-it package is missing only in Testing... Thanx MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734140: (no subject)
I confirm the trouble:
root@debian:~# aptitude full-upgrade
I seguenti pacchetti saranno aggiornati:
cups-filters{b}
1 pacchetti aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 339 kB di archivi. Dopo l'estrazione, verranno occupati
210 kB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
cups-filters : Va in conflitto: foomatic-filters ma 4.0.17-1 è installato.
Va in conflitto: ghostscript-cups ma 9.05~dfsg-8+b1 è
installato.
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Rimuovere i seguenti pacchetti:
1) foomatic-filters
2) ghostscript-cups
3) hpijs-ppds
Leave the following dependencies unresolved:
4) cups raccomanda foomatic-filters (>= 4.0)
ms
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731001: (no subject)
Respect to this old bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202955 Vim doesn't read nor texrc nor compiler.vim if present in a local configuration directory as ~/.vim/ftplugin/tex (or ~/.vim/ftplugin/latex-suite, it's the same). I have to copy both files with my own settings in system directories (/usr/share/vim/addons/ftplugin/latex-suite and /var/lib/vim/addons/ftplugin/latex-suite) to have it working. So this bug is relative not only to texrc file, but to all user configuration files -- Linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#731001: local configuration files for vim-latexsuite are not red
Package: vim-latexsuite Version: 20130116.788-1: all Distribution: Testing, Unstable i put some local configuration files for vim-latexsuite in ~/.vim/ftplugin/tex. They are the following ones: texrc, compiler.vim (to use biber and no more bibtex as biblatex backend). However, Vim continues to read the original system configuration files placed in /usr/share/vim/addons/ftplugin/latex-suite/ and in /var/lib/vim/addons/ftplugin/latex-suite. I saw this old bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202955 but at present my situation seems really close to that one described there. Any update, fix and so on ? thanx ms -- Linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725978: (no subject)
The same, obviously, not only in Unstable but in Testing too with latest updates... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719875: Wrong path of rotatelogs in /etc/init.d/jetty
Package: jetty Version: 6.1.26-1 In /etc/init.d/jetty is set the variable $ROTATELOGS at line 199, as it follows: ROTATELOGS=/usr/sbin/rotatelogs But actually rotatelogs, from the package apache2-utils, is present in /usr/bin, no more in /usr/sbin: see: "Move ab and logresolve from /usr/sbin to /usr/bin. Closes: #351450, #564061". So the script has to be corrected with the right path Thanx MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664218: Dependencies of page-crush
In data domenica 18 marzo 2012 16:45:47, Sylvain ha scritto:
>
> You're the second person to report it, to it's not an isolated case.
>
> Unfortunately I am not able to reproduce the problem, even after
> removing all dependencies and installing page-crunch again (without
> tk8.5).
>
> Can you experiment some more on your system?
I tried to remove the packages not all together:
=
oot@debian:~# aptitude purge page-crunch
I seguenti pacchetti saranno RIMOSSI:
page-crunch{p} psutils{u} tcl8.4{u} tk8.4{u}
0 pacchetti aggiornati, 0 installati, 4 da rimuovere e 0 non aggiornati.
È necessario prelevare 0 B di archivi. Dopo l'estrazione, verranno liberati
6435 kB.
Continuare? [Y/n/?]
(Lettura del database... 113078 file e directory attualmente installati.)
Rimozione di page-crunch...
Eliminazione dei file di configurazione di page-crunch...
Elaborazione dei trigger per man-db...
(Lettura del database... 113069 file e directory attualmente installati.)
Rimozione di psutils...
Rimozione di tk8.4...
Rimozione di tcl8.4...
Elaborazione dei trigger per man-db...
root@debian:~# aptitude purge tcl8.5 tk8.5
I seguenti pacchetti saranno RIMOSSI:
tcl8.5{p} tk8.5{p}
0 pacchetti aggiornati, 0 installati, 2 da rimuovere e 0 non aggiornati.
È necessario prelevare 0 B di archivi. Dopo l'estrazione, verranno liberati
6628 kB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
tcl: Dipende: tcl8.5 (>= 8.5.0-1) but it is not going to be installed.
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Rimuovere i seguenti pacchetti:
1) tcl
Accettare questa soluzione? [Y/n/q/?] Y
I seguenti pacchetti saranno RIMOSSI:
tcl{a} tcl8.5{p} tk8.5{p}
0 pacchetti aggiornati, 0 installati, 3 da rimuovere e 0 non aggiornati.
È necessario prelevare 0 B di archivi. Dopo l'estrazione, verranno liberati
6698 kB.
Continuare? [Y/n/?] Y
(Lettura del database... 112757 file e directory attualmente installati.)
Rimozione di tcl...
update-alternatives: viene usato /usr/bin/tclsh8.5 per fornire /usr/bin/tclsh
(tclsh) in modalità automatica.
Elaborazione dei trigger per man-db...
(Lettura del database... 112750 file e directory attualmente installati.)
Rimozione di tk8.5...
Eliminazione dei file di configurazione di tk8.5...
Rimozione di tcl8.5...
Eliminazione dei file di configurazione di tcl8.5...
Elaborazione dei trigger per man-db...
root@debian:~# dpkg -P `dpkg -l | grep ^rc | cut -f3 -d\ `
(Lettura del database... 112314 file e directory attualmente installati.)
Rimozione di kdebase-runtime-data...
Eliminazione dei file di configurazione di kdebase-runtime-data...
Rimozione di libaccess-bridge-java-jni...
Eliminazione dei file di configurazione di libaccess-bridge-java-jni...
Rimozione di libboost-program-options1.46.1...
Eliminazione dei file di configurazione di libboost-program-options1.46.1...
Rimozione di libraptor1...
Eliminazione dei file di configurazione di libraptor1...
Rimozione di tcl8.4...
Eliminazione dei file di configurazione di tcl8.4...
Rimozione di tk8.4...
Eliminazione dei file di configurazione di tk8.4...
root@debian:~# aptitude install page-crunch
I seguenti pacchetti NUOVI (NEW) saranno installati:
page-crunch psutils{a} tcl8.4{a} tk8.4{a}
0 pacchetti aggiornati, 4 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prelevare 2312 kB di archivi. Dopo l'estrazione, verranno
occupati 6435 kB.
Continuare? [Y/n/?] Y
Get: 1 http://ftp.it.debian.org/debian/ testing/main tcl8.4 i386 8.4.19-4
[1182 kB]
Get: 2 http://ftp.it.debian.org/debian/ testing/main tk8.4 i386 8.4.19-4 [1016
kB]
Get: 3 http://ftp.it.debian.org/debian/ testing/main psutils i386 1.17-31
[98,7 kB]
Get: 4 http://ftp.it.debian.org/debian/ testing/main page-crunch all 1.0 [14,6
kB]
Fetched 2312 kB in 15s (148 kB/s)
Selecting previously unselected package tcl8.4.
(Lettura del database... 112315 file e directory attualmente installati.
Estrazione di tcl8.4 (da .../tcl8.4_8.4.19-4_i386.deb)...
Selecting previously unselected package tk8.4.
Estrazione di tk8.4 (da .../tk8.4_8.4.19-4_i386.deb)...
Selecting previously unselected package psutils.
Estrazione di psutils (da .../psutils_1.17-31_i386.deb)...
Selecting previously unselected package page-crunch.
Estrazione di page-crunch (da .../page-crunch_1.0.1-2_all.deb)...
Elaborazione dei trigger per man-db...
Configurazione di tcl8.4 (8.4.19-4)...
update-alternatives: viene usato /usr/bin/tclsh8.4 per fornire /usr/bin/h
(tclsh) in modalità automatica.
Configurazione di tk8.4 (8.4.19-4)...
update-alternatives: viene usato /usr/bin/wish8.4 per fornire /usr/bin/w(wish)
in modalità automatica.
Configurazione di psutils (1.17-31)...
Configurazione di page-crunch (1.0.1-2)...
==
Bug#664218: Dependencies of page-crush
Package: page-crunch Version: 1.0.1-2 I tried to installa page-crunch on a updated Testing. Aptitude installed two dependencies too, not yet present on my system: tcl8.4 and tk8.4. However, launching the program from terminal, I received: == page-crunch 01.ps can't find package Tk while executing "package require Tk" (file "/usr/bin/page-crunch" line 71) == I solved installing manually tk8.5. Is there anything wrong in control file which cointain the actual dependencies of page-crush? Thanx MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648992: (no subject)
Any new? MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648992: (no subject)
From several days, the Kino page tells that it needs 10 days to enter it in Testing. SOme more accurate valutations? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648992: Kino not installable in Testing (with pinning)
Package: Kino
Version: 1.3.4-1.2
Using pinning in Testing in reference to Sid,
it's in any case impossible to install Kino
because of broken libreries dependence:
Kino requests f. e. libavcodec52, but only
libavcodec53 is available and so on
root@debian:~# apt-cache policy kino:
Installato: (nessuno)
Candidato:
Tabella versione:
1.3.4-1.2 0
850 http://ftp.it.debian.org/debian/ unstable/main i386 Packages
root@debian:~# aptitude -t unstable install kino
I seguenti pacchetti NUOVI (NEW) saranno installati:
kino{b}
0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 257 non aggiornati.
È necessario prelevare 4715 kB di archivi. Dopo l'estrazione, verranno
occupati 9535 kB.
I seguenti pacchetti hanno dipendenze non soddisfatte:
kino: Dipende: libavcodec52 (>= 4:0.6-1~) che è un pacchetto virtuale. o
libavcodec-extra-52 (>= 4:0.6-1~) che è un pacchetto
virtuale.
Dipende: libavformat52 (>= 4:0.6-1~) che è un pacchetto virtuale. o
libavformat-extra-52 (>= 4:0.6-1~) che è un pacchetto
virtuale.
Dipende: libavutil50 (>= 4:0.6-1~) che è un pacchetto virtuale. o
libavutil-extra-50 (>= 4:0.6-1~) che è un pacchetto virtuale.
Dipende: libswscale0 (>= 4:0.6-1~) che è un pacchetto virtuale. o
libswscale-extra-0 (>= 4:0.6-1~) che è un pacchetto virtuale.
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Mantenere i seguenti pacchetti alla versione attuale:
1) kino [Non installato]
Accettare questa soluzione? [Y/n/q/?] n
*** Nessun'altra soluzione disponibile ***
Le seguenti azioni permetteranno di soddisfare queste dipendenze:
Mantenere i seguenti pacchetti alla versione attuale:
1) kino [Non installato]
Accettare questa soluzione? [Y/n/q/?] q
Abbandonato ogni tentativo di risolvere queste dipendenze.
Uscita.
MS
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642261: (no subject)
I use Oxygen on KDE and LibreOffice the same -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642261: (no subject)
I use Oxygen on KDE and LibreOffice the same -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642261: (no subject)
The problem is due to libreoffice-kde If removed, the bug disappers. Perhaps it's better to open a new bug report on this last package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642261: Low bar to scroll the document doen't work in LibreOffice 3.4.3
Package: LibreOffice Version: 3.4.3 OOO340m1 (Build:302) I update LibreOffice in the last version available for Testing. In Writer as well as in Calc the orizontal bar to scroll the windows is blocked. You can see that even the arrows are not correctly visible. You don't see < > but only the over part MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639550: xul-ext-webdeveloper on testin
Package: xul-ext-webdeveloper Version: 1.1.8-5 xul-ext-webdeveloper in the current version in Testig (i.e. 1.1.8-5) doesn't work with Iceweasel 5.0 (the last build in Testing) MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596877: The last netinstall iso's don't install grub
Package: debian-testing-i386-netinst.iso Version: In the last days I downloaded various netinst iso's of Testing for i386. In all cases, at the end of installation process, I received the message: = Error. Impossibile to install Grub on /target directory = Not only Grub is not installed in MBR or elsewhere, but neither copied on HD. I share this trouble with other users... Thanx MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#587608: initrampf doesn't create initrd
Package: initramfs-tool Version: 0.97 When I try to add an "official" debian new kernel or install a kernel compiled by myself, I receive this error: == I seguenti pacchetti parzialmente installati saranno configurati: initramfs-tools linux-image-2.6.32-5-686 Nessun pacchetto verrà installato, aggiornato o rimosso. 0 pacchetti aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati. È necessario prelevare 0B di archivi. Dopo l'estrazione, verranno occupati 0B. Configurazione di initramfs-tools (0.97)... update-initramfs: deferring update (trigger activated) Configurazione di linux-image-2.6.32-5-686 (2.6.32-15)... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 update-initramfs failed to create initrd image. Failed to create initrd image. dpkg: errore nell'elaborare linux-image-2.6.32-5-686 (--configure): il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 Elaborazione dei trigger per initramfs-tools... update-initramfs: Generating /boot/initrd.img-2.6.30-2-686 update-initramfs: failed for /boot/initrd.img-2.6.30-2-686 dpkg: errore nell'elaborare initramfs-tools (--configure): il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: linux-image-2.6.32-5-686 initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) Errore durante l'installazione di un pacchetto. Tentativo di ripristino: Configurazione di initramfs-tools (0.97)... update-initramfs: deferring update (trigger activated) Configurazione di linux-image-2.6.32-5-686 (2.6.32-15)... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 update-initramfs failed to create initrd image. Failed to create initrd image. dpkg: errore nell'elaborare linux-image-2.6.32-5-686 (--configure): il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 Elaborazione dei trigger per initramfs-tools... update-initramfs: Generating /boot/initrd.img-2.6.30-2-686 update-initramfs: failed for /boot/initrd.img-2.6.30-2-686 dpkg: errore nell'elaborare initramfs-tools (--configure): il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: linux-image-2.6.32-5-686 initramfs-tools Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto Lettura delle informazioni sullo stato esteso... Fatto Inizializzazione dello stato dei pacchetti... Fatto Lettura delle descrizioni dei task... Fatto == and the new kernel is installed but not configured: in fact no initrd is created. With my own kernel, which doesn't need an initrd, I have to comment the line: update-initramfs -c -t -k ... in /etx/kernel/postinstall.d/initramfs-tools Thanx MS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#585401: Obsolete texlive-publishers
Package: texlive-publishers Version: 2009-7 In this package there are obsolete versions at least of: classicthesis[2009/08/01 v2.6] current is classicthesis[2010/05/01 v2.8] and arsclassica[2009/01/01 v2.5] current is arsclassica[2010/02/14 v2.7] Sometimes, this produces some troubles in compilation. Do u plan a quick update? Thanx MS -- linux user no.: 353546 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571714: Work around
I solved erasing a section of /etc/apache2/mods-available/php5.conf: SetHandler application/x-httpd-php SetHandler application/x-httpd-php-source # # #php_admin_value engine Off # # But why are there those lines which make apache doesn't work with /localhost/*/public_html ? MS -- linux user no.: 353546 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522453: fgconsole doesn't work as user
Il domenica 5 aprile 2009 10:41:46 Michael Schutte ha scritto: > This is true. It doesn’t only affect fgconsole, but also chvt, openvt > and any other kbd utility which tries to get a console file descriptor. [cut] > As none of these is able to respond to a VT_GETSTATE ioctl, fgconsole > and friends fail. I’m afraid this situation won’t change. Fgconsole fails in Slackware too, if I set the automatic access in X. So there is no real solution, if I don't use sudo? Thanx! Mauro -- linux user no.: 353546 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522453: fgconsole doesn't work as user
Package: kbd Version: 1.15-1 When I enter in a console, fgconsole works always fine. If I launch after the X-server, fgconsole works again. But if I enter with automatic login in X-server as simple user (I use KDE), fgconsole does work no more: == sam...@debian:~$ fgconsole Couldnt get a file descriptor referring to the console == for all /dev/tty are root's ownership. So it works fine only for root. Using Debian Testing with precompiled kernel or the last release, compiled by myslef MS -- linux user no.: 353546 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521202: fgconsole
Package: console-tools Version: 1:0.2.3dbs-65.1 When I enter in a console, fgconsole works fine. If I launch after the X-server, fgconsole works again. But if I enter with automatic login in X-server (I use KDE), fgconsole does work no more: == sam...@debian:~$ fgconsole Couldnt get a file descriptor referring to the console == for all /dev/tty are root's ownership. MS -- linux user no.: 353546 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498665: abookrc in abook
Package: abook
Version: 0.5.6-6
I'm using abook in Debian Lenny. The trouble is present
if I adopt a configuration file, abookrc. This is
the beginning of my abookrc:
==
field pager = Pager
field address_lines = Address, list
field birthday = Birthday, date
view CONTACT = name, email
view ADDRESS = address_lines, city, state, zip, country
view PHONE = phone, workphone, pager, mobile, fax
view OTHER = url, birthday
set preserve_fields=all
set autosave=true
set index_format=" {name:22} {email:40} {phone:12|workphone|mobile}"
=
When I launch abook, I receive this message:
=
[EMAIL PROTECTED]:~$ abook
/home/samiel/.abook/abookrc: parse error at line 5: unknown token field
/home/samiel/.abook/abookrc: parse error at line 6: unknown token field
/home/samiel/.abook/abookrc: parse error at line 7: unknown token field
/home/samiel/.abook/abookrc: parse error at line 10: unknown token view
/home/samiel/.abook/abookrc: parse error at line 11: unknown token view
/home/samiel/.abook/abookrc: parse error at line 12: unknown token view
/home/samiel/.abook/abookrc: parse error at line 13: unknown token view
/home/samiel/.abook/abookrc: parse error at line 16: unknown option
/home/samiel/.abook/abookrc: parse error at line 22: unknown option
Press enter to continue...
=
On the contrary, all works well in a more recent version of abook,
not yet included in Debian: the 0.6.0~pre2.
Thanx
Mauro Sacchetto
--
linux user no.: 353546
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464946: K3b crashes because of library problem
Package: k3b Version: 1.0.4-6 After the last upgrades on Sid, K3b crashes immediatly after launching it. This is the message from shell: k3b: symbol lookup error: /usr/lib/libk3b.so.3: undefined symbol: stat64 There i sno way to use it... I'm using Debian Sid with "official" kernel 2.6.24 Thanx for your attention MS -- linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464085: Tesseract-ocr 2.01-4 installs by default German linguistic file
Package: Tesseract-ocr Version: 2.01-4 When I install via apt-get tesseract-ocr, it's installed too by default tesseract-ocr-deu. For it doesn't interest me, I've to remove it manually. I think it would be better if tesseract-ocr would not install any of there linguistic files, leaving to user the possibility of a direct choise. System: Debian Lenny with kernel 2.6.24 compiled by myself Thanx MS -- linux user no. 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#463855: Testing ISO (DVD and Netinst)
I release (and with me another Debian user) that Lenny install moreover two not requested Samba packages, samba-common and samba-client... MS -- linux user no. 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452609: k3bmonkeyaudio plugin
Package: K3b Version: 1.0.4-2 Severity: wishlist I've got K3b 1.0.4-2 on Debian Sid. My propose is to make an official Debian package of K3b Monkeyaudio plugin, for it's very useful. In fact, a lot of files on the net are in .ape format. I know that Krueg didn't include some plugins of uncertain licence. So I think that, if he included this one in K3b, there is a good reason to produce a Debian package too... Thanx Mauro Sacchetto -- linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447964: (no subject)
Thanx for your answer. Following your indication, I fixed the problem. In any case, I hope the next Debian releases will be able to accomplish the whole configuration process, as well as in the past, for the former versions of Vim. Thanx MS -- linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#447964: Vim doesn't start ("command not found")
Package: Vim Version: 1:7.1-138+1 When I try to lauch Vim from shell, I obtain: "Command not found" and the program doesn't starts. = [EMAIL PROTECTED]:~$ vim bash: vim: command not found = Vim starts only if I write "vim.basic". Moreover, I installed a lot of related packages (vim-addon-manager, vim-doc, vim-full, vim-gnome, vim-gtk, vim-gui-common). Now it's possible to start Vim even by the command: "vim-gnome", but still not by "vim". Gvim too doesn't start from the KDE menu. I realized that all the executable (vi, vim etc.) in /usr/bin (which are only symbolic links) are orphan, and /ect/alternatives is empty. I'm using Debian Sid daily updated, with kernel 2.6.23 compiled by myself. Thanx MAuro Sacchetto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445058: K3b 1.0.3
Package: K3b Version: 1.0.3 with KDE 3.5.7 K3b doesn't seems able to handle .cue files. I tried with .cue files for flac and .ape, and after some upgrades, I'm no more able to burn these files. When I open "New audio project" and drag&drop the .cue file into thw windows, I receive the message: "Trouble in adding the files to the project. Impossibile to handle there file. Unsupported format". I'm not sure this is a bug of Debian package, in any case... I'm using Debian Sid always upgraded, kernel 2.6.22.1 compiled by myself Thanx for your attention MS -- linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435377: Xine segmentation fault
Package: Xine Version: 0.99.5 When I launch Xine or Gxine, the produce a segmentation fault. = [EMAIL PROTECTED]:~$ <[EMAIL PROTECTED]:%7E$> xine Questo è xine (X11 gui) - un riproduttore video libero v0.99.5. (c) 2000-2007 Team di xine. Segmentation fault [EMAIL PROTECTED]:~$ <[EMAIL PROTECTED]:%7E$> gxine gxine has suffered a fatal internal error. To get a backtrace, run gxine in a debugger such as gdb. Then, when the error occurs: (gdb) thread apply all bt gxine: errore: Fatal error: Segmentation fault Segmentation fault = After, I removed nvidia-glx and all begane to works fine again. PLease, note that nvidia drivers doesn't work too, as from my previous bug report (no. 435283) I use Debian Sid with kernel 2.6.22.1 compiled by myself. Thanx for your attention Mauro Sacchetto
Bug#435283: Xorg doesn't start in SId after the last upgrade
Package: xorg (?) Versione: last in Debian Sid After the last dist-upgrade, the server X doesn't start. I installed Nvidia driver by module-assistant, and all seems to be right. After, I tried to install the driver directly from the .run file downloaded fron Nvidia site, but the problem is still the same. This is the relevant part of xorg.conf: == Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8631] 1: [0xe420] Fatal server error: Caught signal 11. Server aborting == This happens on 2.6.21 kernel compiled from Debian sources and 2.6.22.1 compiled by me from vanilla. Note that before the last upgrade, all worked fine. I know that the information I submit are not clear, but I've no idea of which package can be the cause of this. Thanx for your attention Mauro Sacchetto
Bug#433287: ffmpeg
Package: ffmpeg Version: 0.cvs20070307-6 I'm no more able to handle -avi files. This the output: == [EMAIL PROTECTED] ffmpeg -i fils.avi -target dvd film.mpg FFmpeg version SVN-rUNKNOWN, Copyright (c) 2000-2007 Fabrice Bellard, et al. configuration: --enable-gpl --enable-pp --enable-swscaler --enable-pthreads -- enable-libvorbis --enable-libtheora --enable-libogg --enable-liba52 --enable-lib dts --enable-libgsm --enable-dc1394 --disable-debug --enable-shared --prefix=/usr libavutil version: 1d.49.3.0 libavcodec version: 1d.51.38.0 libavformat version: 1d.51.10.0 built on Jun 23 2007 14:31:53, gcc: 4.1.3 20070601 (prerelease) (Debian 4.1.2- 12) Seems stream 0 codec frame rate differs from container frame rate: 3.00 (300 00/1) -> 25.00 (25/1) Input #0, avi, from 'film.avi': Duration: 01:26:43.0, start: 0.00, bitrate: 1112 kb/s Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r) Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s Assuming PAL for target. Output #0, dvd, to 'film.mpg': Stream #0.0: Video: 0x, yuv420p, 720x576, q=2-31, 6000 kb/s, 25.00 fps(c) Stream #0.1: Audio: ac3, 48000 Hz, stereo, 448 kb/s Stream mapping: Stream #0.0 -> #0.0 Stream #0.1 -> #0.1 Unsupported codec for output stream #0.0 == I use Debian Sid with kernel 2.6.21 compiled by myself. Before the last upgrades, ffmpeg worked fine,,, Thanx for your attention MS -- linux user no.: 353546 public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#431617: aMule 2.1.3 crash
Package: aMule Version: 2.1.3 When I try to delete the results of a seach for files with the apposite button, aMule crashes. This is the console output (the first part is relative to aMule loading, the second one to the crash): === [EMAIL PROTECTED]:~$ amule Initialising aMule Checking if there is an instance already running... No other instances are running. Loading temp files from /home/samiel/.aMule/Temp. Loading PartFile 40 of 40 All PartFiles Loaded. ListenSocket: Ok. External connections disabled in config file *** Server UDP socket (TCP+3) at 0.0.0.0:4665 *** TCP socket (TCP) listening on 0.0.0.0:4662 *** Client UDP socket (extended eMule) at 0.0.0.0:4672 Adding file /home/samiel/.aMule/Temp/025.part.met to shares . Adding file /home/samiel/.aMule/Temp/022.part.met to shares Empty dir /home/samiel/.aMule/Incoming/ shared Empty dir /mnt/amule/.Trash-0/ shared Empty dir /mnt/amule/.Trash-0/files/ shared Empty dir /mnt/amule/.Trash-0/info/ shared Empty dir /mnt/amule/.Trash-1000/ shared Empty dir /mnt/amule/lost+found/ shared === (amule:8201): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkcontainer.c: line 2447 (gtk_container_propagate_expose): assertion failed: (child->parent == GTK_WIDGET (container)) aborting... Aborted [EMAIL PROTECTED]:~$ === Kernel: 2.6.21, compiled by myself on deb sources I'm using Debian Sid, upgraded to the last updates Thanx for your attention Mauro Sacchetto -- public key at http://keyserver.linux.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427671: Localization in OpenOffice 2.2.1~rc3-1
Package: OpenOffice.org Version: 2.2.1~rc3-1 Today, upgrading OpenOffice.org in Sid, I realize that there is a problem with the localization packages. I installed openoffice.org-l10n-it and openoffice.org-help-it too. User interface is set to default and Locale setting to Italian (Italy), but I see OO only in English. Moreover, If I try to open the Help, I read: «The help file for this topic is not installed. Please instal the openoffice.org-help-en-us package or the locale specific help package openoffice.org-help-. I reinstalled all those packages, but without results. I'm using Debian Lenny/Sid with kernel 2.6.21 compiled by myself. All previous versions of OO were not affected by this bug. Thanx for your attention Mauro Sacchetto -- linux user no.: 353546 public key at http://keyserver.linux.it
Bug#421675: Ogg files make K3b crash
:operator+=(): function is severel y deprecated. (K3bDevice::DeviceManager) request for empty device! k3b: (K3bMonkeyDecoderFactory) failed to open APE file with error 1002 *** glibc detected *** k3b: double free or corruption (!prev): 0x08555bb0 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb6695873] /lib/i686/cmov/libc.so.6(__libc_free+0x90)[0xb6698d30] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb68513b1] /usr/lib/kde3/libk3bmpcdecoder.so(_ZN13K3bMpcWrapperD1Ev+0x43)[0xb6303c33] /usr/lib/kde3/libk3bmpcdecoder.so(_ZN20K3bMpcDecoderFactory9canDecodeERK4KURL+0x 6f)[0xb630331f] /usr/lib/libk3b.so.3(_ZN22K3bAudioDecoderFactory13createDecoderERK4KURL+0x11c) [0 xb7ea7d0c] /usr/lib/libk3b.so.3(_ZN11K3bAudioDoc16getDecoderForUrlERK4KURLPb+0xe2) [0xb7e934 42] k3b[0x817f8b3] k3b[0x817fa65] /usr/lib/libqt-mt.so.3 (_ZN7QObject15activate_signalEP15QConnectionListP8QUObject +0x12f)[0xb6ea9e1b] /usr/lib/libqt-mt.so.3(_ZN7QSignal6signalERK8QVariant+0xad)[0xb7232f87] /usr/lib/libqt-mt.so.3(_ZN7QSignal8activateEv+0x86)[0xb6ec999e] /usr/lib/libqt-mt.so.3(_ZN16QSingleShotTimer5eventEP6QEvent+0x2e)[0xb6ed1370] /usr/lib/libqt-mt.so.3 (_ZN12QApplication14internalNotifyEP7QObjectP6QEvent+0x270 )[0xb6e41cf2] /usr/lib/libqt-mt.so.3(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1e7) [0xb6e43 b0f] /usr/lib/libkdecore.so.4(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x1ee) [0xb75 d2cce] /usr/lib/libqt-mt.so.3(_ZN12QApplication9sendEventEP7QObjectP6QEvent+0x5b) [0xb6d d54c1] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop14activateTimersEv+0x201)[0xb6e346c3] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop13processEventsEj+0xb6b)[0xb6de980f] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop9enterLoopEv+0x6b)[0xb6e5c245] /usr/lib/libqt-mt.so.3(_ZN12QApplication10enter_loopEv+0x25)[0xb6e43809] /usr/lib/libqt-mt.so.3(_ZN7QDialog4execEv+0xe1)[0xb705d24d] k3b[0x81809a5] k3b[0x8199d6e] k3b[0x819f588] /usr/lib/libqt-mt.so.3 (_ZN7QObject15activate_signalEP15QConnectionListP8QUObject +0x12f)[0xb6ea9e1b] /usr/lib/libqt-mt.so.3(_ZN7QSignal6signalERK8QVariant+0xad)[0xb7232f87] /usr/lib/libqt-mt.so.3(_ZN7QSignal8activateEv+0x86)[0xb6ec999e] /usr/lib/libqt-mt.so.3(_ZN16QSingleShotTimer5eventEP6QEvent+0x2e)[0xb6ed1370] /usr/lib/libqt-mt.so.3 (_ZN12QApplication14internalNotifyEP7QObjectP6QEvent+0x270 )[0xb6e41cf2] /usr/lib/libqt-mt.so.3(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1e7) [0xb6e43 b0f] /usr/lib/libkdecore.so.4(_ZN12KApplication6notifyEP7QObjectP6QEvent+0x1ee) [0xb75 d2cce] /usr/lib/libqt-mt.so.3(_ZN12QApplication9sendEventEP7QObjectP6QEvent+0x5b) [0xb6d d54c1] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop14activateTimersEv+0x201)[0xb6e346c3] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop13processEventsEj+0xb6b)[0xb6de980f] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop9enterLoopEv+0x6b)[0xb6e5c245] /usr/lib/libqt-mt.so.3(_ZN10QEventLoop4execEv+0x32)[0xb6e5c066] /usr/lib/libqt-mt.so.3(_ZN12QApplication4execEv+0x25)[0xb6e4388b] k3b[0x80a41bf] /lib/i686/cmov/libc.so.6(__libc_start_main+0xd8)[0xb6643878] k3b(_ZN9QComboBox11setEditTextERK7QString+0x59)[0x8087cb1] === Memory map: 08048000-08239000 r-xp 08:02 7470949 /usr/bin/k3b 08239000-0825 rw-p 001f1000 08:02 7470949 /usr/bin/k3b 0825-08597000 rw-p 0825 00:00 0 [heap] b510-b5121000 rw-p b510 00:00 0 b5121000-b520 ---p b5121000 00:00 0 b52e9000-b535a000 r--p 08:02 7540492 /usr/share/fonts/truetype/ttf-d ejavu/DejaVuSans-Oblique.ttf b535a000-b535c000 r-xp 08:02 7466981 /usr/lib/gconv/ISO8859-15.so b535c000-b535e000 rw-p 1000 08:02 7466981 /usr/lib/gconv/ISO8859-15.so b535e000-b5365000 r--s 08:02 7454892 /usr/lib/gconv/gconv-modules.ca che b5365000-b537 r-xp 08:02 7701749 /usr/lib/qt3/plugins/inputmetho ds/libqxim.so b537-b5371000 rw-p a000 08:02 7701749 /usr/lib/qt3/plugins/inputmetho ds/libqxim.so b5371000-b5395000 r-xp 08:02 7701748 /usr/lib/qt3/plugins/inputmetho ds/libqsimple.so b5395000-b5396000 rw-p 00024000 08:02 7701748 /usr/lib/qt3/plugins/inputmetho ds/libqsimple.so b5396000-b539f000 r-xp 08:02 7701745 /usr/lib/qt3/plugins/inputmetho ds/libqimsw-multi.so bKCrash: Application 'k3b' crashing... (gdb) quit I use Slackware too, and there I've not this trouble with a Slack package compiled by myself. So I'm convinced that it's not K3b bug. Please, tell me if u need some other information Thanx for your attention Mauro -- Prof. Mauro Sacchetto Santa Croce 1332a 30135 Venezia tel.: 041 5226494 cell.: 320 7414579 e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] linux user no.: 353546 public key at http://keyserver.linux.it
Bug#421675: Ogg files make K3b crash
Package: k3b Version: 1.0.1 On Debian Sid, when I drag&drop an or plus -ogg file creating a K3b projecy for a musical CD, Keb crashes immediatly instead of ripping the file(s). This doesn't happen with the same version of K3b in Slackware, so I think it's a problem of Debian package. Kernel: 2.6.20.7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
