Bug#915070: wodim ignores -dummy

Package: wodim Version: 9:1.1.11-3+b2 Severity: critical Starting with a blank 4.7 Gb DVD-R in the optical drive "HL-DT-ST DVD+-RW GS30N", my_file.iso containing a freshly downloaded copy of Windows 10 (US English, x64), and issuing $ sudo wodim -v driver=mmc_cd_dvd dev=/dev/sg1 -dummy -dao spe

Bug#881658: mdrobiul, your recent order 963580 854a

Fuck you guys. I don’t hv any amazon account. Bull shit Sent from my iPhone > On Nov 13, 2017, at 5:06 PM, Amazon FinalNotice > wrote: > > welcome to amazon > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

Bug#723050: can't log in

your help! :-) -- Mathieu Le 28/03/2014 20:25, Maximiliano Curia a écrit : > ¡Hola Mathieu! > > El 2014-03-28 a las 19:12 +0100, Mathieu MD escribió: >>> But if you do, could you check the permissions of the >>> /sbin/unix_chkpwd command? > >> Permissions on

Bug#723050: can't log in

Hello Maximiliano, Thanks for still being around my bug report :-) > I don't know if the problem is still reproduceable for you, it was > never reproduceable for me. I am still using the same machine, and though up-to-date, this bug is still here. :( > But if you do, could you check the permis

Bug#723050: can't log in

Hi Maximiliano, I do use kdm to login. I tried to run xscreensaver as you told, but it did not change anything: I still cannot login back. Here is my pam files: # # /etc/pam.d/kdm - specify the PAM behaviour of kdm # auth required pam_no

Bug#723050: can't log in

Thanks for your feedback. It may have been the case the very first day, but now that I had reboot many times, and still the problem is the same, what could it be? (sorry for replying late: I did not received your message) -- Mathieu > I see you also pulled in the libc and pam updates. During t

Bug#723050: kscreensaver does not validate correct user password anymore

Package: kscreensaver Version: 4:4.10.5-2 Severity: critical Justification: breaks the whole system Dear Maintainer, After an upgrade this morning of packages xscreensaver (amd64 5.15-3) and kscreensaver (amd64 4:4.10.5-2) I cannot unlock the screensaver (both kscreensaver and xscreensaver) when

Bug#685200: base: ftdi_sio stop working after several hours

Package: base Severity: grave Justification: renders package unusable I control a four relays board throught an USB cable connected to a Xen Dom0 running Debian 6.0.5. It works great: I can switch on and off the relays through some "echo" into /dev/ttyUSB0 (echo -e "\xff\x01\x01" > /dev/ttyUSB0).

Bug#642243: [kdebindings] plasma-scriptengine-ruby is not installable

# apt-get install plasma-scriptengine-ruby libplasma-ruby libplasma-ruby1.8 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation an

Bug#282147: update-inetd interaction

OK then, if you have tested it feel free to NMU. -- ciao, Marco signature.asc Description: Digital signature

Bug#282147: Bug#298425: update-inetd interaction

On Nov 01, Roland Stigge <[EMAIL PROTECTED]> wrote: > attached you will find a patch that modifies update-inetd to use debconf > for interaction (and therefore non-interaction if non-interactive, with > reasonable defaults). This patch changes the semantic of the program, which currently asks the

Bug#383481: Must source code be easy to understand to fall under DFSG?

On Oct 31, Francesco Poli <[EMAIL PROTECTED]> wrote: > IMHO, DFSG#2 refers to source code, as is usually defined, that is to > say, as in the GNU GPL v2. No, it does not. As usual, you are just inventing new requirements which are not specified by the DFSG. > Deliberately obfuscated code is absol