[OT] Firefox 45: Adblock or uBlock origin filters
Hi, Am struggling with what should be a very simple task: defining a uBlock Origin filter that would block all URLs that contain "q;_ylt" (without quotes). Tried a number of options but none seems to be working working. Any ideas? Thanks Firefox 45.2.0 on wheezy
Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found
On Wed, 8/26/15, Pascal Hambourg wrote: // Didn't you install a more recent version of GRUB (possibly from a new // installation) at some time on that disk ? That could be it. The drive originally had a working wheezy installation that booted properly and worked just fine. I then decided to upgrade this working wheezy installation to testing/stretch, just to see how it would go. It did not go too well, so I decided to revert back to wheezy by restoring the data from my backup drive. The /boot partition was restored by dd-ing the data from /boot partition of the working backup drive (/dev/sda1): # dd if=/dev/sda1 of=/dev/sdb1 conv=sync,noerror // Can you see the GRUB version which boots ? When booting, GRUB immediately drops me into the "grub rescue" mode. I did not see any version number nor I found any way to check the version number from "grub rescue" mode. Thanks
Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found
On Tue, 8/25/15, Pascal Hambourg wrote: // What does "ls (hd0,msdos1)/grub/" show ? Just a few files // and directories or plenty of *.mod files? I have the drive disconnected at the moment but, as far as I remember, "ls (hd0,msdos1)/grub/" shows all the files that are normally expected to be there. The /boot partition of the problem drive was restored using dd: # dd if=/dev/sda1 of=/dev/sdb1 conv=sync,noerror where /dev/sda1 is the /boot partion of the good working HD that boots properly /dev/sdb1 is the /boot partion of the HD that fails to boot and that I'm trying to get working Thanks
Re: Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found
On Mon, 8/24/15, Brian wrote: // If the device and path for prefix is correct you should see a grub // directory in the output of // // ls ((hd0,msdos1)/ // // Do you? Yes. grub rescue> ls (hd0,msdos1)/ config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found System.map-3.2.0-4-amd64 vmlinuz-3.2.0-4-amd64 grub rescue> set prefix=(hd0,msdos1)/grub grub rescue> insmod normal file '/grub/i386-pc/normal.mod not found grub rescue> insmod (hd0,msdos1)/grub/normal.mod file '/grub/i386-pc/gfxterm.mod not found// writing from memory, I think it was gfxterm.mod grub rescue> insmod (hd0,msdos1)/grub/gfxterm.mod file '/grub/i386-pc/video.mod not found // It would be more usual for the prefix to be (hd0,msdos1)/boot/grub on a // Debian machine with a standard installation. (hd0,msdos1) is my boot partion, not /. The HD is partitioned as follows: /dev/sda1 /boot partition /dev/sda2 / partition /dev/sda3 swap partition Thanks
Wheezy amd64 grub2 error: file '/grub/i386-pc/normal.mod' not found
Hi, Am trying to restore my regular working HD from backup HD but booting from the restored HD results in "file '/grub/i386-pc/normal.mod' not found" error. This seems a bit odd since 1) my wheezy system is amd64 and 2) I can boot from my backup HD just fine. My regular working and backup HDs have the same size, the same partition structure and, at least in theory, the same data. I used dd to copy /boot partition data between my regular and backup HDs: ## backup /boot partition. Booting from the backup HD works fine. # dd if=/dev/sda1 of=/dev/sdb1 conv=sync,noerror What I tried: 1. Reinstall grub on the main HD (/dev/sdb, as the system is running off the backup HD which for now is /dev/sda). Did not help, the same "file '/grub/i386-pc/normal.mod' not found" error persists. ## /dev/sdb1 is /boot partiion # mount /dev/sdb1 /mnt/1 # grub-install /dev/sdb --boot-directory=/mnt/1 2. In the grub rescue mode: grub rescue> set prefix=(hd0,msdos1)/grub grub rescue> insmod normal file '/grub/i386-pc/normal.mod not found grub rescue> insmod linux file '/grub/i386-pc/linux.mod not found Any ideas? Thanks # aptitude show grub-pc Package: grub-pc State: installed Automatically installed: no Multi-Arch: foreign Version: 1.99-27+deb7u2 # uname -a Linux tsr7 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u3 x86_64 GNU/Linux
Re: From wheezy to stretch: can't start X session when logging in from kdm
On Sun, 8/23/15, Jimmy Johnson wrote: // While kdm still works in upstream stretch/testing, I've been told it is // no longer being supported by systemd and has been replaced with sddm, // but if you want to see your desktop currently you need to follow the // instructions I gave you. For plasma 5 questions the best place to go is // linux.debian.maint.kde, I'm trying to help the best I can. Thanks for the explanation, I appreciate your help.
Re: From wheezy to stretch: can't start X session when logging in from kdm
On Sun, 8/23/15, Jimmy Johnson wrote: > It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098 It may be the same issue though I'm not sure why I was getting the error about missing /home/luser/.Xsession file. I manually copied /etc/kde4/kdm/Xsession file as /home/luser/.Xsession but that can't be a part of the normal installation procedure. Even stranger, wheezy was able to start KDE from kdm just fine without any .Xsession / .xsession file in my home dir. Any ideas? Thanks
From wheezy to stretch: can't start X session when logging in from kdm
Hi, Tried upgrading from wheezy to stretch, just to see how it would go. It mostly went OK though there is an issue: when trying to log in from kdm the system now complains that it's unable to start X session --- no /home/luser/.xsession file, no /home/luser/.Xsession file, no session managers, no window managers, and no terminal emulators found; aborting. If I copy /etc/kde4/kdm/Xsession file as /home/luser/.Xsession to my home directory the system hangs instead of giving the above error. Any ideas? Thanks
Re: [SOLVED] Re: Wheezy: making a bootable HD with Grub
% I decided to follow the path you suggested as it seemed the simplest and easiest % for me to do. Here's what I did in case if anyone is trying to resolve a similar % issue: % % 0. Copy /boot and / partition data from the old drive to the new one % 1. Run "blkid" to get patition UUIDs of old and new drives % 2. Edit /etc/fstab and /boot/grub/grub.cfg and replace old partiion UUIDs with % the respective new ones. What it did for me was that the system would now drop % into the grub CLI -- which is a lot nicer -- instead of grub rescue CLI. % 3. Run the following in the grub CLI % grub> set prefix=(hd0,msdos1)/grub % grub> insmod normal % grub> insmod linux % grub> linux (hd0,msdos1)/vmlinuz-3.2.0-4-amd64 root=/dev/sda2 % grub> initrd (hd0,msdos1)/initrd.img-3.2.0-4-amd64 % grub> boot % 4. The system now boots and is working % 5. # grub-install /dev/sda % 6. # update-grub % 7. Reboot the system, the system reboots and comes back just fine. % % There is one small issue that I'm not sure what to attribute to. The grub % selection menu that's shown when the system boots now has different colors and % kind of shifted to the left of the screen so a small part of it is cut of. % Different resolution perhaps? It would be nice to fix it. The issue has been resolved. The selection menu color/shift quirk went away once the HD was properly installed into the PC. Guess it was some kind of interference/poor connection thing. Thanks to everyone who responded. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430210677.86535.yahoomailba...@web126101.mail.ne1.yahoo.com
[SOLVED] Re: Wheezy: making a bootable HD with Grub
On Mon, 4/27/15, Brian wrote: > Not only is there no TAB completion and command history but you have to > handle module loading yourself. 'insmod normal' and 'insmod linux' are > needed. I decided to follow the path you suggested as it seemed the simplest and easiest for me to do. Here's what I did in case if anyone is trying to resolve a similar issue: 0. Copy /boot and / partition data from the old drive to the new one 1. Run "blkid" to get patition UUIDs of old and new drives 2. Edit /etc/fstab and /boot/grub/grub.cfg and replace old partiion UUIDs with the respective new ones. What it did for me was that the system would now drop into the grub CLI -- which is a lot nicer -- instead of grub rescue CLI. 3. Run the following in the grub CLI grub> set prefix=(hd0,msdos1)/grub grub> insmod normal grub> insmod linux grub> linux (hd0,msdos1)/vmlinuz-3.2.0-4-amd64 root=/dev/sda2 grub> initrd (hd0,msdos1)/initrd.img-3.2.0-4-amd64 grub> boot 4. The system now boots and is working 5. # grub-install /dev/sda 6. # update-grub 7. Reboot the system, the system reboots and comes back just fine. There is one small issue that I'm not sure what to attribute to. The grub selection menu that's shown when the system boots now has different colors and kind of shifted to the left of the screen so a small part of it is cut of. Different resolution perhaps? It would be nice to fix it. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430147983.14766.yahoomailba...@web126106.mail.ne1.yahoo.com
Re: Wheezy: making a bootable HD with Grub
On Sun, 4/26/15, Brian wrote: > (hd0,swap) is more likely to be (hd0,msdos3) Yes, you're probably right. I was writing from memory. > One of the partitions holds the kernel and initrd image. Another has the > files vmlinuz and initrd.img. 'ls ((hd0,msdos1)/' etc should help with > locating them. Where are they? (hd0,msdos1) is my new boot partition and I copied all the files from my old boot partition to the new one. So, I expect the output would show all the files and directories that I copied: grub rescue> ls (hd0,msdos1)/ config-3.2.0-4-amd64 grub initrd.img-3.2.0-4-amd64 lost+found System.map-3.2.0-4-amd64 vmlinuz-3.2.0-4-amd64 What's not clear to me is how it helps me. Perhaps I could try to boot the system from grub rescue (see below)? grub> linux (hd0,msdos1)/vmlinuz root=(hd0,msdos2) grub> initrd (hd0,msdos1)/initrd.img grub> boot Perhaps the system will boot this way. Then what? There's still the question of making the new HD bootable the normal way that remains. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430102770.35105.yahoomailba...@web126102.mail.ne1.yahoo.com
Re: Wheezy: making bootable HD with Grub
Patrick Bartek gmail.com> wrote: > Edit any other files on the new drive that reflect the old drive > chroot to the new drive. This has to be done a certain way. Why you > need detailed instructions for the transfer procedure. The problem is I'm not sure what other files I need to edit and how to chroot to the new drive in a "certain way". I obviously have looked for the instructions but failed ones that would be clear enough for me to follow. I sure hope there's an easier way to make a disk bootable. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430102378.82500.yahoomailba...@web126102.mail.ne1.yahoo.com
Re: Wheezy: making a bootable HD with Grub
On Sun, 4/26/15, Brian wrote: > You get the bare minimum with grub rescue>; not even TAB completion, Yes, that's how it looked to me. The problem was I couldn't get much done with grub rescue CLI. > You need to to get the system booting so that you run 'update-grub' > and maybe, for good measure, 'install-grub' prior to that command. As I understand it, "update-grub" runs "grub-mkconfig -o /boot/grub/grub.cfg". I think it will simply update my existing and working grub config file at my old /dev/sda drive. Actually, after I ran "grub-install" I copied all files from /dev/sda1 boot partition to /dev/sdb1. > Let's see the output of 'ls', please. I have the new HD offline at the moment. As I remember it, "ls" output looked like the following: (hd0,msdos1) (hd0,msdos2), (hd0,swap), something like that. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430063840.48211.yahoomailba...@web126102.mail.ne1.yahoo.com
Wheezy: Need some help making bootable HD with Grub.
Hi, Need some help making bootable HD with Grub. I have two HDs of the same size: 1. /dev/sda - my old and working HD which has grub properly installed, the system boots and works properly. /dev/sda has the following partitions: /dev/sda1 /boot /dev/sda2 / /dev/sda3 swap 2. /dev/sdb, my new HD, it has the same structure as /dev/sda: sdb1 (/boot), sdb2 (/) and sdb3 (swap), though the size of the partitions is slightly different. I want to transfer my data from sda to sdb (that part was done) and make sdb bootable. sdb will then be the only drive in the system. I ran "grub-install /dev/sdb" and it said that it completed without errors. The PC however fails to boot from the new drive, which was the only HD in the system at that time. After some delay the boot process drops me not even into the Grub CLI but into some "grub rescue>" CLI where even "help" command does not work. "ls" does work though. Any ideas as to what needs to be done to make sdb bootable just like sda is? Thanks # grub-install -v grub-install (GRUB) 1.99-27+deb7u2 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1430051501.36997.yahoomailba...@web126103.mail.ne1.yahoo.com
Wheezy: motion app error: "Unable to find a compatible palette format"
Hi, Am trying to get my webcam to work with the motion app. The webcam is working fine with VLC, I can save the webcam's output to a file without any problems, but the motion app fails with the same webcam with "Unable to find a compatible palette format" error (see [1] below). Some people seem to be able to resolve this error by preloading v4l1compat.so, tried that, the error message seems a bit different but the app still doesn't work for me (see [2] below). Any ideas? Thanks $ cat /proc/version Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.63-2+deb7u2 [1] $ /usr/bin/motion -n [0] Processing thread 0 - config file /etc/motion/motion.conf [0] Motion 3.2.12 Started [0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478785 [0] Thread 1 is from /etc/motion/motion.conf [0] motion-httpd/3.2.12 running, accepting connections [0] motion-httpd: waiting for data on port TCP 8080 [1] Thread 1 started [1] cap.driver: "uvcvideo" [1] cap.card: "GENERAL - UVC " [1] cap.bus_info: "usb-:00:12.2-1" [1] cap.capabilities=0x0401 [1] - VIDEO_CAPTURE [1] - STREAMING [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] Selected palette MJPG [1] VIDIOC_TRY_FMT failed for format MJPG: Input/output error [1] Unable to find a compatible palette format. [1] ioctl (VIDIOCGCAP): Invalid argument [1] Could not fetch initial image from camera [1] Motion continues using width and height from config file(s) [1] Resizing pre_capture buffer to 1 items [1] Started stream webcam server in port 8081 [1] Retrying until successful connection with camera [1] cap.driver: "uvcvideo" [1] cap.card: "GENERAL - UVC " [1] cap.bus_info: "usb-:00:12.2-1" [1] cap.capabilities=0x0401 [1] - VIDEO_CAPTURE [1] - STREAMING [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] Selected palette MJPG [1] VIDIOC_TRY_FMT failed for format MJPG: Input/output error [1] Unable to find a compatible palette format. [1] ioctl (VIDIOCGCAP): Invalid argument [1] Retrying until successful connection with camera [1] cap.driver: "uvcvideo" [1] cap.card: "GENERAL - UVC " [1] cap.bus_info: "usb-:00:12.2-1" [1] cap.capabilities=0x0401 [1] - VIDEO_CAPTURE [1] - STREAMING [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] Selected palette MJPG [1] VIDIOC_TRY_FMT failed for format MJPG: Input/output error [1] Unable to find a compatible palette format. [1] ioctl (VIDIOCGCAP): Invalid argument ^C[1] Thread exiting [0] httpd - Finishing [0] httpd Closing [0] httpd thread exit [0] Motion terminating [2] $ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so /usr/bin/motion -n [0] Processing thread 0 - config file /etc/motion/motion.conf [0] Motion 3.2.12 Started [0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478785 [0] Thread 1 is from /etc/motion/motion.conf [1] Thread 1 started [0] motion-httpd/3.2.12 running, accepting connections [0] motion-httpd: waiting for data on port TCP 8080 [1] cap.driver: "uvcvideo" [1] cap.card: "GENERAL - UVC " [1] cap.bus_info: "usb-:00:12.2-1" [1] cap.capabilities=0x0501 [1] - VIDEO_CAPTURE [1] - READWRITE [1] - STREAMING [1] Test palette YU12 (320x240) libv4l2: error setting pixformat: Input/output error [1] Error setting pixel format VIDIOC_S_FMT: Input/output error [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] 1: RGB3 (RGB3) [1] 2: BGR3 (BGR3) [1] 3: YU12 (YU12) [1] 4: YV12 (YV12) [1] Selected palette YU12 [1] Test palette YU12 (320x240) libv4l2: error setting pixformat: Input/output error [1] Error setting pixel format VIDIOC_S_FMT: Input/output error [1] VIDIOC_TRY_FMT failed for format YU12: Input/output error [1] Unable to find a compatible palette format. libv4l2: error setting pixformat: Input/output error libv4l1: error setting pixformat: Input/output error [1] Failed with YUV420P, trying YUV422 palette: Input/output error [1] Failed with YUV422, trying YUYV palette: Invalid argument [1] Failed with YUYV, trying RGB24 palette: Invalid argument libv4l2: error setting pixformat: Input/output error libv4l1: error setting pixformat: Input/output error [1] Failed with RGB24, trying GREYSCALE palette: Input/output error [1] Failed with all supported palettes - giving up: Invalid argument [1] Could not fetch initial image from camera [1] Motion continues using width and height from config file(s) [1] Resizing pre_capture buffer to 1 items [1] Started stream webcam server in port 8081 [1] Retrying until successful connection with camera [1] cap.driver: "uvcvideo" [1] cap.card: "GENERAL - UVC " [1] cap.bus_info: "usb-:00:12.2-1" [1] cap.capabilities=0x0501 [1] - VIDEO_CAPTURE [1] - READWRITE [1] - STREAMING [1] Test palette YU12 (320x240) libv4l2: error setting pixformat: Input/output error [1] Error setting pixel format VIDIOC_S_FMT
Wheezy: Changing date format in LibreOffice Calc
Hi, I am trying to change a date format in LibreOffice Calc (LOC). I thought it would be a simple thing to do but for some reason it doesn't work for me. What I did: 1. Open LOC, start a new spreadsheet 2. Enter 6 new rows in column A as follows: 20.11.2013 21.11.2013 22.11.2013 23.11.2013 24.11.2013 25.11.2013 3. Clear any existing formatting to be sure: select column A, Menu > Format > Clear Direct Formatting 4. Apply MM/DD/ formatting: select column A, Menu > Format > Cells > Date > MM/DD/ > OK The above steps result in no change for me, the dates are still shown as DD.MM., no warning or error message is given. Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384943759.66445.yahoomailba...@web163003.mail.bf1.yahoo.com
Re: Wheezy: Konqueror disk activity
> For some reason, Konqueror is writing a small amount of data > every 10 seconds or so in my setup, even if Konqueror is > just showing content of a folder with no other activity > taking place. atop shows something like the following when > Konqeror is running: > > RDDSK WRDSK WCANCL DSK CMD > OK 8K 8K 100% konqueror > > > Even though the write is supposedly canceled according to > the above, the hard disk activity light briefly comes on and > the disk makes a sound like it's doing something. > > I mostly use Konqueror as a file manager and am puzzled why > it needs to write something to disk every 10 seconds or if > there is a setting somewhere that would disable this > behavior. > > Any ideas? Thanks Is anyone having similar issue? Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1383245933.88789.yahoomailba...@web163001.mail.bf1.yahoo.com
Wheezy: Konqueror disk activity
Hi, For some reason, Konqueror is writing a small amount of data every 10 seconds or so in my setup, even if Konqueror is just showing content of a folder with no other activity taking place. atop shows something like the following when Konqeror is running: RDDSK WRDSK WCANCL DSKCMD OK 8K 8K 100% konqueror Even though the write is supposedly canceled according to the above, the hard disk activity light briefly comes on and the disk makes a sound like it's doing something. I mostly use Konqueror as a file manager and am puzzled why it needs to write something to disk every 10 seconds or if there is a setting somewhere that would disable this behavior. Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1382714819.64901.yahoomailba...@web163003.mail.bf1.yahoo.com
