Bug#1064394: release-notes: English language output for the commands into script session
On 21/02/24 at 23:49, Justin B Rye wrote: Sorry I missed the sense, what explanation? If we said "LC_ALL=C.UTF-8 LANGUAGE= script -T ..." it would have all sorts of disadvantages, including the fact that we'd have to explain all of it together. Much easier to explain about script, then suggest a "script -T..." commandline, *then* deal with locales separately. Yes, users have to choice if they want to change localization inside the "script" session. The question is, will users realise that they're putting the files in *root's* home directory, and will they even know where that is? A minimal assumption of knowledge base of the FHS ¹ and tilde-expansion should be take by Release Notes writers. I think we shouldn't worry about this. If we really can't suggest using /var/tmp for this, that seems a pity; that location *shouldn't* be wiped on reboot, and it's usable whether you're running "sudo; screen" or "sudo screen" or "screen; sudo". It's more popular to use a non-privileged home directory. Few people strictly adhere to the FHS ¹ specifications. This is why I am in favor of using tilde-expansion. No matters if the reader becomes root or runs "script" as non-privileged user: the files will always go in the home directory, where they will be used by "scriptreplay" command. By doing so we won't have to take care of where the files reside. ¹ https://refspecs.linuxfoundation.org/fhs.shtml -- Franco Martelli
Bug#1064394: release-notes: English language output for the commands into script session
On 21/02/24 at 16:00, Justin B Rye wrote: I like this idea; but it might work better if we turn things around and start with the possible problem before offering the solution. Yes, my English is so scholastic. A rephrased version: If you use a non-English locale during the upgrade, any progress or error messages are likely to be translated, so in the event of problems it may be difficult to get assistance from the Internet, or to submit a bug report. If you are comfortable using English then it is strongly recommended that you run the following command at the start of your 'script' session: # LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE This will give you command output in English. I agree (Or do we also need to warn users to say "yes" and not "si"?) It shouldn't be necessary, if the user is comfortable with English, already he should expect this. However end users behavior is unpredictable … This change it has been discussed on debian-user mailing-list here. ² The syntax of the command was designed to be portable to all shells, csh included. I'm sorry, but if you're doing vital root-privileged sysadmin tasks under csh, things have already gone badly wrong; the instructions in the Release Notes all assume a Bourne-family shell. For instance, the immediately preceding line invoking screen with a 2>~/foo redirection* won't work on csh (tested with bookworm's tcsh). Yes, the redirection of only stderr is not allowed in csh but with the new "script" command syntax this will be solved: # script -T ~/upgrade-trixie-step.time -a ~/upgrade-trixie-step.script So I'm not sure there's any point using anything longer than: # export LC_ALL=C.UTF-8 LANGUAGE= Yes, but what's wrong if we have a syntax portable to all shells? If available. (But doing it separately from starting "script" does make sense, if only to give us room for an explanation.) Sorry I missed the sense, what explanation? I don't think the Release Notes ever mention the fact that we assume a Bourne shell, but if you boot into an initrd rescue shell expecting it to be csh then your day hasn't finished getting worse. Again, only if available, why don't we use a portable syntax to all shells? Ah, yes, avoiding the tricky redirection syntax (worthwhile even if we don't care about csh). But if we're assuming this is already a root session, "~/foo" will put that log in /root/; maybe we should say that instead of using tilde-expansion? I'm for tilde-expansion I find it more elegant and more widespread use for referring to the home directory. -- Franco Martelli
Bug#1059509: release-notes: script -t is deprecated, should we recommend --log-timing?
Could I suggest that the syntax of "script" command in the "4.4.1. Recording the session" section ¹ it should be: # script -T ~/upgrade-trixie-step.time -a ~/upgrade-trixie-step.script ¹ https://www.debian.org/releases/testing/release-notes/upgrading.en.html#recording-the-session -- Franco Martelli
Bug#1042396: Skanlite fails to scan with message: "Document feeder empty"
Package: skanlite Version: 22.12.3-1 Skanlite fails to scan, the scanner is an HP ENVY 6030e, I started Skanlite from command-line when I click "Scan" button these lines appear in Konsole: ~$ skanlite -d escl:https://192.168.0.89:443 xmlns="http://www.hp.com/schemas/imaging/con/errors/2013/05/07; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:dd="http://www.hp.com/schemas/imaging/con/dictionaries/1.0/; xsi:schemaLocation="http://www.hp.com/schemas/imaging/con/errors/2013/05/07 ../schemas/Error.xsd"> IPG-LEDM-SVN.810 2014-09-04 409 conflictWithExisting /ScanSettings/Version Input Settings Mismatch Error! a popup window then is shown with this localized message: "Alimentatore dei documenti vuoto" (translated to English with Google Translator: "Document feeder empty") the locale's output: ~$ locale LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" LC_TIME="it_IT.UTF-8" LC_COLLATE="it_IT.UTF-8" LC_MONETARY="it_IT.UTF-8" LC_MESSAGES="it_IT.UTF-8" LC_PAPER="it_IT.UTF-8" LC_NAME="it_IT.UTF-8" LC_ADDRESS="it_IT.UTF-8" LC_TELEPHONE="it_IT.UTF-8" LC_MEASUREMENT="it_IT.UTF-8" LC_IDENTIFICATION="it_IT.UTF-8" LC_ALL= the workaround I found is to set LC_ALL=C environment variable at the beginning of the command: ~$ LC_ALL=C skanlite -d escl:https://192.168.0.89:443 doing so Skanlite makes scan regularly. Cheers -- Franco Martelli
Bug#1018779: nouveau DRM: Failure to read SCDC_TMDS_CONFIG: -6 error message
ints to avoid this message? TIA -- Franco Martelli
Bug#935536: Fwd: Compiling Linux with "bdver2" gcc optimization option
The Objtools maintainer told me to ignore the warnings unless live patching it's used. This probably it means "Won't Fix" status to this bug report, however if some kernel hacker will want to fix it I would be so glad to see those warnings go away. Messaggio Inoltrato Oggetto: Re: Compiling Linux with "bdver2" gcc optimization option Data: Thu, 8 Oct 2020 11:24:01 -0500 Mittente: Josh Poimboeuf A: Franco Martelli CC: pet...@infradead.org On Thu, Oct 08, 2020 at 06:00:41PM +0200, Franco Martelli wrote: > Hello dear Objtools Maintainers, > > I got your email address by running the command: > > ~/linux-source-5.8$ perl scripts/get_maintainer.pl -f > tools/objtool/objtool.c > > from long time I optimize Linux kernel builds using the "bdver2" GCC > optimization option but sadly it doesn't work anymore. I don't know from > which Linux kernel version up to now the bug appeared. > I submitted this bug report [1] to the Debian BTS. I would ask if you > could pay yours attention and fix it. > Should I submit the bug report also to https://bugzilla.kernel.org ? > > Thank you very much for yours patience, best regards. > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935536 Hi Franco, It will be difficult for objtool to support all the tuning options, especially since they're so rarely used. If you don't use live patching, it's probably safe to ignore the warnings. -- Josh
Bug#935536: Compiling Linux with "bdver2" gcc optimization option
_range_noflush()+0x2ec: return with modified stack frame mm/vmalloc.o: warning: objtool: vread()+0x1cf: stack state mismatch: cfa1=7+96 cfa2=7+88 mm/vmalloc.o: warning: objtool: vwrite()+0x176: stack state mismatch: cfa1=7+96 cfa2=7+88 arch/x86/kvm/cpuid.o: warning: objtool: do_cpuid_ent()+0x6b4: can't find jump dest instruction at .text+0xba6 arch/x86/kvm/pmu.o: warning: objtool: reprogram_fixed_counter()+0xbb: can't find jump dest instruction at .text+0x37d kernel/rcu/srcutree.o: warning: objtool: process_srcu()+0x50: stack state mismatch: cfa1=7+128 cfa2=7+120 kernel/rcu/srcutree.o: warning: objtool: __call_srcu()+0xba: sibling call from callable instruction with modified stack frame arch/x86/kernel/alternative.o: warning: objtool: apply_alternatives()+0x10f: stack state mismatch: cfa1=7+336 cfa2=7+328 arch/x86/kernel/alternative.o: warning: objtool: apply_paravirt()+0x118: stack state mismatch: cfa1=7+296 cfa2=7+288 arch/x86/kvm/hyperv.o: warning: objtool: kvm_hv_notify_acked_sint()+0x4a: can't find jump dest instruction at .text+0x20c mm/madvise.o: warning: objtool: swapin_walk_pmd_entry()+0x1ec: stack state mismatch: cfa1=7+88 cfa2=7+80 mm/madvise.o: warning: objtool: madvise_free_pte_range()+0x39e: stack state mismatch: cfa1=7+136 cfa2=7+128 arch/x86/kernel/tsc_msr.o: warning: objtool: cpu_khz_from_msr()+0x99: can't find jump dest instruction at .text+0x36 kernel/rcu/tree.o: warning: objtool: rcu_exp_wait_wake()+0x224: return with modified stack frame kernel/rcu/tree.o: warning: objtool: _synchronize_rcu_expedited.constprop.55()+0x1c7: stack state mismatch: cfa1=7+192 cfa2=7+184 arch/x86/kernel/tsc.o: warning: objtool: pit_hpet_ptimer_calibrate_cpu()+0x1c4: stack state mismatch: cfa1=7+112 cfa2=7+104 arch/x86/kernel/tsc.o: warning: objtool: tsc_refine_calibration_work()+0xd8: stack state mismatch: cfa1=7+48 cfa2=7+40 I guess that objtool has stopped recognize CPU instructions for -march=bdver2 gcc optimization flag. The only workaround I know it is to use -march=bdver1 instead this compiles without warnings. Is there a way to get the kernel optimized for my CPU as it happened in all the previous Debian versions? Kind regards -- Franco Martelli
Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point
For sake of clarity this is a schroot command issue related bug report, all works fine with chroot ordinary command. As you suggest I try the -M switch, once started schroot's session: $ kubuntu then open a new console and run these commands: ~# killall cupsd ~# service cups start then come back to schroot's console and logout: ~$ logout E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c': Device or resource busy E: kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c: Chroot setup failed: stage=setup-stop $ fuser -M /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c Specified filename /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c is not a mountpoint. fuser now tell me that it wasn't a mount point but it was indeed, although actually not mounted anymore: $ mount | grep /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c $ attempting to manually remove the directory it fails # LC_ALL=C rmdir /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c': Device or resource busy knowing that cupsd keeps busy the directory: # killall cupsd now removing the directory succeed: # LC_ALL=C rmdir /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c # A more interesting scenario, start a schroot session: $ kubuntu then open a new console and run these commands: ~# killall cupsd ~# service cups start search for mount-point grepping the device name: # mount | grep /dev/mapper/ld0-lv2 /dev/mapper/ld0-lv2 on /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85 type ext4 (rw,relatime,stripe=256,data=ordered) asking fuser which processes keeps busy the mount-point: # fuser /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85/ /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85: 5681r # fuser -m /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85/ /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85: 5681rce # fuser -M /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85/ /var/lib/schroot/mount/kubuntu-76da7862-ef1b-4b04-920b-459be3350e85: 5681r # systemctl status cups ● cups.service - CUPS Printing Service Loaded: loaded (/lib/systemd/system/cups.service; enabled) Active: active (running) since gio 2016-04-28 21:59:50 CEST; 38s ago Docs: man:cupsd(8) man:cupsd.conf(5) Main PID: 5723 (cupsd) CGroup: /system.slice/cups.service └─5723 /usr/sbin/cupsd -f fuser never report cupsd's PID(5723) the 5681 PID number reported refers to bash: # pstree -cpan | grep -B2 -A1 5681 | |-bash,1148 --rcfile ~/.bashrc_develop -i | | `-schroot,5608 -c kubuntu -- | | `-bash,5681 | `-bash,1152 --rcfile ~/.bashrc_develop -i HTH best regards On 25/04/2016 at 04:26, Craig Small wrote: > The problem is that fuser works off device numbers (it has to otherwise > symlinks would confuse it) and there is nothing much that makes the > chroots unique. A chroot is basically saying "start your tree here". My > chroots for example sit under /var/chroot > > Now, outside the chroot I can work out what process has that open with > fuser /var/chroot/wheezy (note the lack of -m because these are not > mount points). > > Remember when you use the -m command you are saying the device ID where > that file sits. It might be the actual mount point, or just a file (and > fuser works out where that file sits). > > If you really mean a mount point, then -M is a better idea. > I don't really understand your setup because you have other mounts > coming into your chroot. I think your tests are doing simple text > matching which causes a bunch of failed misses but need to be sure. > > /proc//mountinfo isn't the fix, because just like /proc//fd it > can be fooled by symlinks. > > - Craig > -- > Craig Small (@smallsees) http://enc.com.au/ csmall at : > enc.com.au <http://enc.com.au> > Debian GNU/Linux http://www.debian.org/ csmall at : > debian.org <http://debian.org> > GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- Franco Martelli
Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point
On 08/03/2016 at 10:52, Craig Small wrote: > It actually finds the process you are looking for, however it also finds > a lot of other processes. Yes, this is true, sorry my mistake. > > ~# fuser -m > /var/lib/schroot/mount/kubuntu-a3ca1d7f-7fce-4673-b84a-6c4835bd7316 > > Find something that is in that mount point OR the device of this file. But this is not always true, please consider this scenario: first start a schroot session: ~$ schroot -c kubuntu -- then open a terminal and as root type: ~# service cups restart ~# mount|grep -m1 kubuntu /dev/mapper/ld0-lv2 on /var/lib/schroot/mount/kubuntu-8565f027-6e05-4a41-811c-48836261f5ee type ext4 (rw,relatime,stripe=256,data=ordered) ~# fuser -m /var/lib/schroot/mount/kubuntu-8565f027-6e05-4a41-811c-48836261f5ee /var/lib/schroot/mount/kubuntu-8565f027-6e05-4a41-811c-48836261f5ee: 12936rce ~# then came back to the schroot's session shell and logout: ~$ logout E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-8565f027-6e05-4a41-811c-48836261f5ee': Device or resource busy E: kubuntu-8565f027-6e05-4a41-811c-48836261f5ee: Chroot setup failed: stage=setup-stop as you can see "fuser" shown only one process keeping busy the mount-point but also cups did it, in fact schroot fails on exit. Is it because cups does not open any file on that file-system? > > However there is something odd about that mount point. > > /proc/2061/mountinfo:196 41 253:3 / > /var/lib/schroot/mount/kubuntu-a3ca1d7f-7fce-4673-b84a-6c4835bd7316 > rw,relatime shared:135 - ext4 /dev/mapper/ld0-lv2 > rw,stripe=256,data=ordered > > Device 253:3 > I suspect this device is more than just your schroot. > It looks awfully like /dev/dm-3 > > $ ls -l /dev/dm-3 > brw-rw 1 root disk 253, 3 Mar 1 19:33 /dev/dm-3 > > so.. considering the chroot device id is the same as whatever /dev/dm-3 > is, you'll get a long list of processes because it probably something > like /home I get an useless list of processes querying "/var/lib/schroot/mount/kubuntu-a3ca1d7f-7fce-4673-b84a-6c4835bd7316" because it's the same as querying any other directory on the root file-system. However the device /dev/dm-3 has a symlink to ld0-lv2 that it was the properly schroot's device to mount: ~# ls -la /dev/mapper/ld0-lv2 lrwxrwxrwx 1 root root 7 mar 5 19:49 /dev/mapper/ld0-lv2 -> ../dm-3 ~# ls -la /dev/dm-3 brw-rw 1 root disk 253, 3 mar 5 19:49 /dev/dm-3 Thank again, best regards -- Franco Martelli
Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point
D: Device-1: /dev/md0 - active raid: 5 components: online: 3/3 - sdc1 sdb1 sda1 spare: sdd1 Sensors: System Temperatures: cpu: 10.6C mobo: N/A gpu: 28C Fan Speeds (in rpm): cpu: N/A Info: Processes: 193 Uptime: 1:27 Memory: 1213.5/7743.8MB Client: Shell (bash) inxi: 2.1.28 * Some details of the schroot configuration: ~$ cat /etc/schroot/desktop/fstab # fstab: static file system information for chroots. # Note that the mount point will be prefixed by the chroot path # (CHROOT_PATH) # # /sys/syssysfs rw,bind 0 0 /proc /proc procrw,bind 0 0 /dev/devdevtmpfs rw,bind 0 0 /dev/pts/dev/ptsdevpts rw,bind 0 0 # /home /home nonerw,bind 0 0 # /tmp/tmpnonerw,bind 0 0 # If you use gdm3, uncomment this line to allow Xauth to work #/var/run/gdm3 /var/run/gdm3 nonerw,bind 0 0 # For PulseAudio and other desktop-related things #/var/lib/dbus/var/lib/dbus ext4rw,bind 0 0 # It may be desirable to have access to /run, especially if you wish # to run additional services in the chroot. However, note that this # may potentially cause undesirable behaviour on upgrades, such as # killing services on the host. /run /runtmpfs rw,bind 0 0 /sys/kernel/security /sys/kernel/security securityfs rw,bind 0 0 /dev/shm /dev/shm tmpfs rw,bind 0 0 /run/lock /run/lock tmpfs rw,bind 0 0 # /run/shm /run/shmtmpfs rw,bind 0 0 /sys/fs/cgroup/ /sys/fs/cgroup/ tmpfs rw,bind 0 0 /sys/fs/cgroup/systemd /sys/fs/cgroup/systemd cgroup rw,bind 0 0 /sys/fs/pstore /sys/fs/pstore pstore rw,bind 0 0 /sys/fs/cgroup/cpuset /sys/fs/cgroup/cpuset cgroup rw,bind 0 0 /sys/fs/cgroup/cpu,cpuacct /sys/fs/cgroup/cpu,cpuacct cgroup rw,bind 0 0 /sys/fs/cgroup/devices /sys/fs/cgroup/devices cgroup rw,bind 0 0 /sys/fs/cgroup/freezer /sys/fs/cgroup/freezer cgroup rw,bind 0 0 /sys/fs/cgroup/net_cls,net_prio /sys/fs/cgroup/net_cls,net_prio cgroup rw,bind 0 0 /sys/fs/cgroup/blkio /sys/fs/cgroup/blkio cgroup rw,bind 0 0 /sys/fs/cgroup/perf_event /sys/fs/cgroup/perf_event cgroup rw,bind 0 0 /proc/sys/fs/binfmt_misc /proc/sys/fs/binfmt_misc autofs rw,bind 0 0 /sys/kernel/debug /sys/kernel/debug debugfs rw,bind 0 0 /dev/mqueue /dev/mqueue mqueue rw,bind 0 0 /dev/hugepages /dev/hugepages hugetlbfs rw,bind 0 0 # /sys/kernel/config /sys/kernel/config configfs rw,bind 0 0 # /sys/fs/fuse/connections /sys/fs/fuse/connections fusectl rw,bind 0 0 # tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=792100k,mode=700,uid=1000,gid=1000 0 0 ~$ cat /etc/schroot/chroot.d/kubuntu.conf [kubuntu] description=Kubuntu 15.10 type=block-device device=/dev/mapper/ld0-lv2 users=my-username preserve-environment=false environment-filter=XDG_RUNTIME_DIR profile=desktop setup.nssdatabases= ~$ *** * How to reproduce the bug: *** Once configured schroot you can start a schroot session: $ schroot -c kubuntu -- ~$ Now open a new terminal and having cups already running as root type: ~# service cups restart ~# then logout schroot's session (with errors): ~$ logout E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-d2c072e7-7e0c-4cfc-b48e-73defe8a4f0a': Device or resource busy E: kubuntu-d2c072e7-7e0c-4cfc-b48e-73defe8a4f0a: Chroot setup failed: stage=setup-stop Now fuser won't report cups as the process that keeps busy the mount-point. Please note that maybe this issue affect also docker's mount-point, I don't know, I never tried. Thanks for your attenction, best regards. -- Franco Martelli
Bug#681884: How to discover which process own the mount-point
parts: executing 20copyfiles, setup-stop, ok D(2): run_parts: 20copyfiles succeeded D(2): run_parts: executing 15killprocs, setup-stop, ok D(2): run_parts: 15killprocs succeeded D(2): run_parts: executing 15binfmt, setup-stop, ok D(2): run_parts: 15binfmt succeeded D(2): run_parts: executing 10mount, setup-stop, ok E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-eab1e6f8-60bd-4744-b26a-ba0c2801e600': Device or resource busy D(2): run_parts: 10mount failed with status 1 E: kubuntu-eab1e6f8-60bd-4744-b26a-ba0c2801e600: Chroot setup failed: stage=setup-stop HTH -- Franco Martelli
Bug#681884: How to discover which process own the mount-point
schroot works fine, no problem whether daily used. The misbehavior reported happens when the system is *resumed* from suspend-to-ram (not hibernate: suspend-to-disk) after a day. schroot has trouble when closing session because of the schroot's mount-point is reported busy: frank@itek:~$ logout E: 10mount: rmdir: failed to remove '/var/lib/schroot/mount/kubuntu-e762f326-f842-4ed3-933e-0e64b8e26f8c': Device or resource busy E: kubuntu-e762f326-f842-4ed3-933e-0e64b8e26f8c: Chroot setup failed: stage=setup-stop [frank@itek ~]$ fuser -m /var/lib/schroot/mount/kubuntu-e762f326-f842-4ed3-933e-0e64b8e26f8c /var/lib/schroot/mount/kubuntu-e762f326-f842-4ed3-933e-0e64b8e26f8c: 1rce 2rce 3rce 5rce 7rce 8rce 9rce10rce 11rce12rce13rce15rce16rce17rce18rce20rce 21rce22rce23rce25rce26rce27rce28rce30rce 31rce32rce33rce35rce36rce37rce38rce40rce 41rce42rce43rce45rce46rce47rce48rce49rce 50rce51rce52rce53rce54rce55rce56rce58rce 60rce61rce67rce68rce70rce 115rce 116rce 125rce 126rce 127rce 128rce 129rce 130rce 131rce 132rce 133rce 134rce 140rce 141rce 142rce 143rce 159rce 160rce 161rce 162rce 163rce 164rce 165rce 166rce 174rce 179rce 180rce 181rce 194rce 195rce 201rce 202rce 224rce 225rce 258rce 270rce 274rce 352rce 459rce 460rce 471rce 514rce 515rce 527rce 528rce 530rce 531rce 533rce 534rce 537rce 538rce 539rce 540rce 564rce 565rce 721rce 724rce 729rce 751rce 752rce 753rce 782rce 784rce 814rce 852rce 856rce 926rce 931rce 936rce 938rce 939rce 941rce 973rce 976rce 977rce 1014rce 1016rce 1018rce 1020rce 1023rce 1037rce 1073rce 1075rce 1076rce 1080rce 1087rce 1090rce 1106rce 1109rce 1112rce 1138rce 1142rce 1146rce 1147rce 1150rce 1151rce 1154rce 1158rce 1184rce 1186rce 1188rce 1194rce 1203rce 1209rce 1229rce 1232rce 1234rce 1238rce 1262rce 1329rce 1330rce 1331rce 1332rce 1333rce 1335rce 1336rce 1345rce 1371rce 1381rce 1957rce 2481rce 2653rce 2670rce 2699rce 2700rce 2701rce 2709rce 2711rce 2724rce 2962rce 2971rce 3689rce 3690rce 3765rce 3779rce 3926rce 3930rce 3932rce 3969rce 4099rce 4116rce 4140rce 4143rce The mount-point is an empty directory, the lsof utility returns no output and sadly fuser's output doesn't help me therefore as workaround I've to reboot and remove schroot's session files by hand. I'd be happy to avoid rebooting each time. Any idea? TIA -- Franco Martelli * Inglese - rilevata * Afrikaans * Albanese * Arabo * Bielorusso * Bulgaro * Catalano * Cinese * Cinese (Semplificato) * Cinese (Tradizionale) * Croato * Ceco * Danese * Olandese * Inglese * Estone * Filippino * Finlandese * Francese * Galiziano * Tedesco * Greco * Ebraico * Creolo haitiano * Hindi * Ungherese * Islandese * Indonesiano * Irlandese * Italiano * Giapponese * Coreano * Lettone * Lituano * Macedone * Malese * Maltese * Norvegese * Farsi * Polacco * Portoghese * Portoghese (Portogallo) * Romeno * Russo * Serbo * Slovacco * Sloveno * Spagnolo * Swahili * Svedese * Thai * Turco * Ucraino * Vietnamita * Gallese * Yiddish * Afrikaans * Albanese * Arabo * Bielorusso * Bulgaro * Catalano * Cinese * Cinese (Semplificato) * Cinese (Tradizionale) * Croato * Ceco * Danese * Olandese * Inglese * Estone * Filippino * Finlandese * Francese * Galiziano * Tedesco * Greco * Ebraico * Creolo haitiano * Hindi * Ungherese * Islandese * Indonesiano * Irlandese * Italiano * Giapponese * Coreano * Lettone * Lituano * Macedone * Malese * Maltese * Norvegese * Farsi * Polacco * Portoghese * Portoghese (Portogallo) * Romeno * Russo * Serbo * Slovacco * Sloveno * Spagnolo * Swahili * Svedese * Thai * Turco * Ucraino * Vietnamita * Gallese * Yiddish <javascript:void(0);> <#>
Bug#776515: Kwin crash when enabling OpenGL with Nvidia proprietary driver v. 331.113
,usb_storage,usbhid,usbserial,usbnet,usb_wwan,option,uvcvideo,cdc_ether,snd_usbmidi_lib,snd_usb_audio usb_common 12354 1 usbcore r8169 47008 0 mii12675 2 r8169,usbnet The nvidia-setting command crash: $ nvidia-settings The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 565 error_code 3 request_code 137 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The glxinfo command returns errors: $ glxinfo |grep render X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 137 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x2a3 Serial number of failed request: 34 Current serial number in output stream: 34 Prior to updating to Debian Wheezy 7.8.0 all works nicely, it looks like that it isn't related to a kernel issue because I've tested a custom kernel version 3.2.63 and when re-enable OpenGL in SystemSetting - DesktopEffect - Advanced I have a Kwin crash therefore it works without 3D effect anymore. You can look at log at the attachment file Xorg.0.log Thank you very much for paying attention, please let me to know what to do. -- Franco Martelli * Inglese - rilevata * Inglese * Italiano * Inglese * Italiano javascript:void(0); * Inglese * Italiano [60.582] X.Org X Server 1.12.4 Release Date: 2012-08-27 [60.582] X Protocol Version 11, Revision 0 [60.582] Build Operating System: Linux 3.16-2-amd64 x86_64 Debian [60.582] Current Operating System: Linux itek 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 [60.582] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/ld0-lv1 ro k10temp.force=1 loop.max_loop=16 quiet [60.582] Build Date: 09 December 2014 09:12:48PM [60.582] xorg-server 2:1.12.4-6+deb7u5 (Moritz Muehlenhoff j...@debian.org) [60.582] Current version of pixman: 0.26.0 [60.582]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [60.582] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [60.582] (==) Log file: /var/log/Xorg.0.log, Time: Wed Jan 28 21:15:53 2015 [60.582] (==) Using config directory: /etc/X11/xorg.conf.d [60.582] (==) Using system config directory /usr/share/X11/xorg.conf.d [60.583] (==) No Layout section. Using the first Screen section. [60.583] (**) |--Screen Screen0 (0) [60.583] (**) | |--Monitor default monitor [60.583] (**) | |--Device Card0 [60.583] (==) No monitor specified for screen Screen0. Using a default monitor configuration. [60.583] (==) Automatically adding devices [60.583] (==) Automatically enabling devices [60.583] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [60.583]Entry deleted from font path. [60.583] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [60.583]Entry deleted from font path. [60.583] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [60.583]Entry deleted from font path. [60.583] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [60.583]Entry deleted from font path. [60.583] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [60.583]Entry deleted from font path. [60.583] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [60.583]Entry deleted from font path. [60.583] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [60.583] (==) ModulePath set to /usr/lib/xorg/modules [60.583] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [60.583] (II) Loader magic: 0x7f5883879ae0 [60.583] (II) Module ABI versions: [60.583]X.Org ANSI C Emulation: 0.4 [60.583]X.Org Video Driver: 12.1 [60.583]X.Org XInput driver : 16.0 [60.583]X.Org Server Extension : 6.0 [60.585] (--) PCI:*(0:1:0:0) 10de:1284:1043:8461 rev 161, Mem @ 0xfd00/16777216, 0xd000/134217728, 0xd800/33554432, I/O @ 0xe000/128, BIOS @ 0x/524288 [60.585] (II) Open ACPI successful (/var/run/acpid.socket) [60.585] (II) LoadModule: extmod [60.585] (II) Loading /usr/lib
Bug#717665: script that let apt-cache show command to work properly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I wrote this bash script: $ cat apttranslation #!/bin/bash -l [ ! 0 -eq `/usr/bin/id -u` ] (/bin/echo -e '\n - Error: You must be root!\n') exit 1 ### Hard disk partition containing dvd iso images. mpoint=/media/sdb1 ### Mount each dvd iso images accordenly on /etc/fstab entries. for ((i=1;i=10;i++)) ; do mount $mpoint/wheezy/dvd-$i 2/dev/null done ### Change directory to apt packages description archive. [ ! -d /var/lib/apt/lists/ ] (/bin/echo -e '\n - Error: Failed to change directory to /var/lib/apt/lists/\n') exit 1 cd /var/lib/apt/lists/ ### Recursively find Translation-en.gz in dvd-1,dvd-2,dvd-n... up to 10. for ((i=1;i=10;i++)) ; do dvddir=$mpoint/wheezy/dvd-$i for f in $(find $dvddir -name Translation-en.gz) ; do ### Copy Translated-en.gz files renamed opportunely. g=$(echo $f | sed -e s/\//_/g) /bin/echo Copy translation archive: $g /bin/cp $f $g done done ### Once done then unmount dvd ido images. for ((i=1;i=10;i++)) ; do umount $mpoint/wheezy/dvd-$i 2/dev/null done Copying those files then apt-cache show command it shall show description-en contents. Regards. - -- Franco Martelli. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJR78pLAAoJEFM/ma7n+T+7+YgH/j/6V7nk9boqCxkI3D7UOIRV rFbAEIb7JaipuA+cPFKe65N8SZB+64wN1vJF2sWCVO8OWzFb4R78NI4zn/mp3s7b KUV/+e4b6SNJKseg4cvueQZLIpHSSkpM7mzZ6qds3q+ec7A30uWOEmPnvLJyt+qi yw0P7W53bOj+w8SslohtnfzxRX6+4rX9f3y0j75/InEFVg66pjTfzjwksOCzV+rI n81IZPU9Z4biW9n6G9zzwYzMuGLGFqW/2IGNrAbw7HHG6dqjpg+pBuJqtHa/SxV7 t639fm2VZmJbDV7ce0rcRnTX02dp1UIiOjQFwyY17M2Somw5VPmf0ws9wiUQE6I= =9Laq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717665: file URI in sources.list: apt-cache show description-en missing.
-Size: 286 Maintainer: Anibal Monsalve Salazar ani...@debian.org Architecture: amd64 Depends: libc6 (= 2.11), libtinfo5, debianutils (= 1.8) Description-en: pager program similar to more This package provides less, a file pager (that is, a memory-efficient utility for displaying text one screenful at a time). Less has many more features than the basic pager more. As part of the GNU project, it is widely regarded as the standard pager on UNIX-derived systems. . Also provided are lessecho, a simple utility for ensuring arguments with spaces are correctly quoted; lesskey, a tool for modifying the standard (vi-like) keybindings; and lesspipe, a filter for specific types of input, such as .doc or .txt.gz files. Homepage: http://www.greenwoodsoftware.com/less/ Description-md5: a2c2d2eff1fb9762b71faf7540cf8dce Tag: implemented-in::c, interface::text-mode, role::program, scope::utility, uitoolkit::ncurses, use::viewing, works-with::text Section: text Priority: standard Filename: pool/main/l/less/less_444-4_amd64.deb Size: 134872 ... Briefly, archives gets with file URI in sources.list they are missing of Translation-en.gz files in /var/lib/apt/list directory, while archives gets with http URI they have Translation-en and description-en are shown regularly. Therefore is it known behavior of the file URI? How can I enable Description-en gets via file URI without copy those Translation-en.gz files by hand? Thank you very much for your attention. Regards. -- Franco Martelli. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654416: less: fails to show characters with accent
Package: less Version: less 436 Files in doc-linux-it-text debian package aren't shown correctly. Characters with accent like èéàò aren't shown at all. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages less depends on: ii debianutils 3.4Miscellaneous utilities specific t ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-5 shared libraries for terminal hand less recommends no packages. less suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
