Re: [gentoo-user] Re: plugin-containers missing libraries
On Wed, 27 May 2015 16:20:52 +1000, Adam Carter wrote: There's no firefox-bin in /usr/bin on my system, there's just # ls -l /usr/bin/firefox* lrwxrwxrwx 1 root root 26 May 9 19:13 /usr/bin/firefox - /usr/lib64/firefox/firefox And in that directory, again no shell script; # file /usr/lib64/firefox/firefox-bin /usr/lib64/firefox/firefox-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped System is ~amd64 for firefox/thunderbird It might help if you said which firefox and thunderbird packages you have installed. -- Neil Bothwick Why do they lock gas station bathrooms? Are they afraid someone will clean them? pgpfTgXFFO7sX.pgp Description: OpenPGP digital signature
Re: [gentoo-user] General weirdness - a tale of woe.
On 27/05/2015 14:31, Canek Peláez Valdés wrote: On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk mailto:pe...@prh.myzen.co.uk wrote: Hello list, Hi. Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. I have no idea what your problem can be. But as a friendly reminder, your setup (/usr under / and no initrd) hasn't been supported since at least a year and a half. I read what Peter said to mean that he doesn't have /usr as a separate volume - it is directly under / -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] General weirdness - a tale of woe.
On Wed, May 27, 2015 at 8:02 AM, Alan McKinnon alan.mckin...@gmail.com wrote: On 27/05/2015 14:31, Canek Peláez Valdés wrote: On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk mailto:pe...@prh.myzen.co.uk wrote: Hello list, Hi. Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. I have no idea what your problem can be. But as a friendly reminder, your setup (/usr under / and no initrd) hasn't been supported since at least a year and a half. I read what Peter said to mean that he doesn't have /usr as a separate volume - it is directly under / Oh, sorry, I understand the opposite. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
[gentoo-user] General weirdness - a tale of woe.
Hello list, Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. The first thing was that my screen saver was being overlaid with a plain default desktop. That was fixed by creating a new user for myself and setting it up from scratch. Tedium galore, especially importing into KMail. Then I found KMail creating duplicates of existing e-mails. It would make a few when I started the program, then some more when I told it to fetch mail, and even more when I clicked into the folder containing the copies. Several other little oddities were happening too, and I began to suspect my six-year-old disks. Well, I wanted to put some shiny new SSDs in anyway, so I used this as the excuse. That seemed to fix everything and I ran for a week or two in welcome peace. Then this morning when I came back to the machine (it runs 24x7x52 running BOINC projects) the screen saver overlay was back. Then I noticed that the three Konsole windows I keep on one desktop had been resized one pixel smaller, so that the last line didn't fit. I'm particular about that (OCPD?) and would never have left it that way. When I came to KMail I found that it wouldn't loop outside the current folder. I have it set to loop through all of them, so I changed it, restarted KMail, changed it back to loop through all folders and restarted KMail. It still wouldn't go outside the current folder. I also notice it's ignoring my one auto-correction setting - to capitalise the initial letter of a sentence. So I ran an emerge -eK world and restarted. No change. Clearly something is changing in my home directory tree, but what? I can't keep on creating new user accounts. The last thing is that at reboot the RAID-1 volume manager often fails to start. It says afterwards that it's running, but all the /dev/vg7/* are absent (that's where the logical volumes live). The file system root lives on /dev/md5 with metadata 1.0, while /dev/vg7 has metadata 1.0. The fact that it happens often but not always suggests a timing problem to me. # rc-update -s -v | grep -e raid -e lvm lvm | boot lvm-monitoring | lvmetad | mdraid | boot (This reminds me that since the last update of lvm2 I haven't been able to work out how to set it up to cause no errors.) Can anyone suggest a way to tackle all these? I'm puzzled in particular by the apparent consistency in symptoms, apart from the RAID problem which I think only became a nuisance after installing the SSDs. Gkrellm shows CPU temps of 50 to 55C, which seems normal enough. Could I have something misconfigured in the kernel? I'm reduced to making general arm-waving noises... -- Rgds Peter
Re: [gentoo-user] General weirdness - a tale of woe.
On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote: Hello list, Hi. Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. I have no idea what your problem can be. But as a friendly reminder, your setup (/usr under / and no initrd) hasn't been supported since at least a year and a half. From [1]: If you have / and /usr on separate file systems and you are not currently using an initramfs, you must set one up before this date. Otherwise, at some point on or after this date, upgrading packages will make your system unbootable. It is of course possible that your problem has nothing to do with not using an initramfs. Then again, *IT IS* also possible that you NEED an initramfs, and that's one of the many reasons the council decided to stop supporting such a configuration. Regards. [1] https://www.gentoo.org/support/news-items/2013-09-27-initramfs-required.html -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] General weirdness - a tale of woe.
On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote: This is a KDE amd64 system with /usr under / and no initrd. Just to clarify, is /usr on a separate filesystem, or the same as /? I don't think that is your problem in any case, but it might be relevant. ... bunch of KDE stuff I've had the odd KDE issue along the way, like having extra panels spawning off-screen with notifications showing up in wierd places as a result. That doesn't sound like your specific problem, but assuming a KDE expert doesn't chime in here you might consider pursuing those questions in a KDE forum/list, or maybe even in the Gentoo forums where there is a section for desktop environments. Again, assuming somebody doesn't recognize your problem here. The last thing is that at reboot the RAID-1 volume manager often fails to start. It says afterwards that it's running, but all the /dev/vg7/* are absent (that's where the logical volumes live). The file system root lives on /dev/md5 with metadata 1.0, while /dev/vg7 has metadata 1.0. The fact that it happens often but not always suggests a timing problem to me. I've sometimes seen this sort of thing with kernel raid autodetection, especially with metadata 1. I suspect that an initramfs might help you out, assuming the filesystems on that RAID are useful in early boot. However, openrc and the raid init scripts should do a good job of configuring your raid if your mdadm.conf and such is correct, so if you don't need those filesystems until late in boot I don't think an initramfs will make much of a difference, since it would likely use the exact same userspace tools as openrc already does. Make sure your mdadm.conf is set up to search all devices that could contain RAID (drive device names can get re-ordered), and it doesn't hurt to put ARRAY lines in mdadm.conf to give it hints. I do recommend just using an initramfs if you're using RAID for early-boot filesystems. While it is an extra step I find it is much more robust than kernel autodetection (and if something goes wrong you usually get an emergency shell where you can just manually get the RAID up and type exit and watch the system boot). It also lets you use metadata 1 and I find that to be a lot more robust in general. With an initramfs you can basically boot anything you can mount from a booted system, but without one your options are more limited. -- Rich
Re: [gentoo-user] General weirdness - a tale of woe.
On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote: On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote: This is a KDE amd64 system with /usr under / and no initrd. Just to clarify, is /usr on a separate filesystem, or the same as /? I don't think that is your problem in any case, but it might be relevant. I didn't realise I wasn't clear, sorry. It might have been better if I'd said usr/ is under /. Anyway, it's not a separate partition. ... bunch of KDE stuff I've had the odd KDE issue along the way, like having extra panels spawning off-screen with notifications showing up in wierd places as a result. That doesn't sound like your specific problem, but assuming a KDE expert doesn't chime in here you might consider pursuing those questions in a KDE forum/list, or maybe even in the Gentoo forums where there is a section for desktop environments. Again, assuming somebody doesn't recognize your problem here. Since writing, I've found that my fonts have all changed as well. It's almost as though something were cruising my home directories and flipping bits. And KMail insists on using American English in the composer, despite my telling it UK. That may not be new though. I'm signed up to the KDE-Linux list already but I see hardly any traffic, and I suspect dark things about what happens to posts of mine on it. The last thing is that at reboot the RAID-1 volume manager often fails to start. It says afterwards that it's running, but all the /dev/vg7/* are absent (that's where the logical volumes live). The file system root lives on /dev/md5 with metadata 1.0, while /dev/vg7 has metadata 1.0. The fact that it happens often but not always suggests a timing problem to me. I've sometimes seen this sort of thing with kernel raid autodetection, especially with metadata 1. More clarity needed on my part. The file-system root is /dev/md5 which has metadata 1.0. It's found reliably by kernel autodetection. Subsidiary partitions are in /dev/md7 which has metadata 1.0 and lvm2 volumes. Here's a bit of fstab: /dev/vg7/portage/usr/portageext4 relatime,discard 1 3 /dev/vg7/packages /usr/portage/packages ext4 relatime,discard 1 2 /dev/vg7/distfiles /usr/portage/distfiles ext4 relatime,discard 1 2 /dev/vg7/local /usr/local ext4 relatime,discard 1 2 It's the detection of md7 that often fails; I've had no trouble with md5. Several other directories are in lvm2 volumes in /dev/vg7, but nothing that's part of system. I suspect that an initramfs might help you out, assuming the filesystems on that RAID are useful in early boot. However, openrc and the raid init scripts should do a good job of configuring your raid if your mdadm.conf and such is correct, so if you don't need those filesystems until late in boot I don't think an initramfs will make much of a difference, since it would likely use the exact same userspace tools as openrc already does. Make sure your mdadm.conf is set up to search all devices that could contain RAID (drive device names can get re-ordered), and it doesn't hurt to put ARRAY lines in mdadm.conf to give it hints. Like this? ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5 ARRAY /dev/md7 devices=/dev/sda7,/dev/sdb7 I do recommend just using an initramfs if you're using RAID for early-boot filesystems. While it is an extra step I find it is much more robust than kernel autodetection (and if something goes wrong you usually get an emergency shell where you can just manually get the RAID up and type exit and watch the system boot). It also lets you use metadata 1 and I find that to be a lot more robust in general. With an initramfs you can basically boot anything you can mount from a booted system, but without one your options are more limited. Well, that's an interesting idea - thanks. I'll give it some thought. I've just switched on a few more sensors in gkrellm, and I see Vcor2 at 3.00 and +3.3v at 3.34. Is it worth fiddling with those and related settings in the BIOS? I've always hesitated to do that, preferring to let it sort itself out. -- Rgds Peter
[gentoo-user] Re: General weirdness - a tale of woe.
Peter Humphrey peter at prh.myzen.co.uk writes: Hello list, Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. 50 to 55C, which seems normal enough. Could I have something misconfigured in the kernel? Well I'm going to share a problem I have right now. If you suffer from it, it could affect a myriad of different applications with different symptoms. I do not know if this will help you, but it's work checking into. Eselect news list 2015-3-28 lists True multilib support on amd64 For me, I run a simple profile: [1] default/linux/amd64/13.0 * Because I run lxde and have experimented with several other minimalistic desktops, including lxqt. Currently, I run lxde. If I emerge with the --deep option, I get so much breakage that 3000 lines of scrollback is not enough to get to the head of the problem. Many errors contain the common string abi_x86_32 which is central to the aforementioned news item. I have read this news item many times, tried many ideas, and still have this phantom problem. I can delete some packages had at the update, hours to days, get it cleaned up to where -D works and a couple of emerge --syncs later the problem reappears. Global update without (-D) --deep are just fine. I have no idea if this phantom issue relates to yours or not. I have hesitated to post about it, because in a decade of gentoo usage (and there have been some ruff patches to say the least) I have never experienced a transient recurring problem like this. I think I need a much longer version of that news item and some cook_book syntax to fixing these (phantom) multilb issues on my amd64 systems that I am experiencing. Some simple questions:: 1. How do you test if indeed a system is multilib? 2. Can a system be change, readily, from multilib to not and then back? 3. Is a more specific profile needed for one where you intend to run only a minimalist (lxqt) desktop (than what I listed above)? Note:: My ultimate goal is minimal desktops (lxqt) on most systems and excess resources pledged (dynamically) to a meso cluster underneath my gentoo systems. Comments and guidance are warmly appreciated. Peter I'm not trying to hijack your thread, but enquire as to commonality. hth, James
Re: [gentoo-user] Re: General weirdness - a tale of woe.
On Wed, 27 May 2015 18:38:08 + (UTC), James wrote: Eselect news list 2015-3-28 lists True multilib support on amd64 For me, I run a simple profile: [1] default/linux/amd64/13.0 * Because I run lxde and have experimented with several other minimalistic desktops, including lxqt. Currently, I run lxde. If I emerge with the --deep option, I get so much breakage that 3000 lines of scrollback is not enough to get to the head of the problem. Many errors contain the common string abi_x86_32 which is central to the aforementioned news item. I have read this news item many times, tried many ideas, and still have this phantom problem. I can delete some packages had at the update, hours to days, get it cleaned up to where -D works and a couple of emerge --syncs later the problem reappears. Global update without (-D) --deep are just fine. I have no idea if this phantom issue relates to yours or not. I have hesitated to post about it, because in a decade of gentoo usage (and there have been some ruff patches to say the least) I have never experienced a transient recurring problem like this. I think I need a much longer version of that news item and some cook_book syntax to fixing these (phantom) multilb issues on my amd64 systems that I am experiencing. Some simple questions:: 1. How do you test if indeed a system is multilib? It is, as you are not using a no-multilib profile. 2. Can a system be change, readily, from multilib to not and then back? No. 3. Is a more specific profile needed for one where you intend to run only a minimalist (lxqt) desktop (than what I listed above)? No, that is a fairly basic profile. Comments and guidance are warmly appreciated. Peter I'm not trying to hijack your thread, but enquire as to commonality. Your problem is different but has been covered in previous threads, as well as the news item. You could add ABI_X86=32 64 to make.conf, but that won't fit in with your desire for minimalism. So you need to run emerge with --autounmask-write then run etc-update or equivalent to apply the changes to package.use. -- Neil Bothwick If someone with multiple personalities threatens to kill himself, is it considered a hostage situation? pgpaiXp8FQVMt.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: General weirdness - a tale of woe.
On Wednesday 27 May 2015 21:09:27 Neil Bothwick wrote: On Wed, 27 May 2015 18:38:08 + (UTC), James wrote: Eselect news list 2015-3-28 lists True multilib support on amd64 For me, I run a simple profile: [1] default/linux/amd64/13.0 * Because I run lxde and have experimented with several other minimalistic desktops, including lxqt. Currently, I run lxde. If I emerge with the --deep option, I get so much breakage that 3000 lines of scrollback is not enough to get to the head of the problem. Many errors contain the common string abi_x86_32 which is central to the aforementioned news item. I have read this news item many times, tried many ideas, and still have this phantom problem. I can delete some packages had at the update, hours to days, get it cleaned up to where -D works and a couple of emerge --syncs later the problem reappears. Global update without (-D) --deep are just fine. I have no idea if this phantom issue relates to yours or not. I have hesitated to post about it, because in a decade of gentoo usage (and there have been some ruff patches to say the least) I have never experienced a transient recurring problem like this. I think I need a much longer version of that news item and some cook_book syntax to fixing these (phantom) multilb issues on my amd64 systems that I am experiencing. Some simple questions:: 1. How do you test if indeed a system is multilib? It is, as you are not using a no-multilib profile. 2. Can a system be change, readily, from multilib to not and then back? No. 3. Is a more specific profile needed for one where you intend to run only a minimalist (lxqt) desktop (than what I listed above)? No, that is a fairly basic profile. Comments and guidance are warmly appreciated. Peter I'm not trying to hijack your thread, but enquire as to commonality. Your problem is different but has been covered in previous threads, as well as the news item. You could add ABI_X86=32 64 to make.conf, but that won't fit in with your desire for minimalism. So you need to run emerge with --autounmask-write then run etc-update or equivalent to apply the changes to package.use. Only to add that maintainers are regularly updating packages and this is why you may find that suddenly new packages require USE=abi_x86_32, when a week ago they didn't. It is worth noting that one multilib box of mine has not asked me (yet) to set USE=abi_x86_32 on any of its packages, while my laptop is regularly prompting me to do so. I have concluded that the former has no packages which are using 32bit code, while the latter does (I know that at least Skype is a culprit). So in extremis you could I guess purge any 32bit coded packages from your PC and the abi_x86_32 prompts should leave you alone. I shouldn't forget to add your usual disclaimer: YMMV :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] General weirdness - a tale of woe.
On Wednesday 27 May 2015 15:16:35 Peter Humphrey wrote: On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote: On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote: This is a KDE amd64 system with /usr under / and no initrd. Just to clarify, is /usr on a separate filesystem, or the same as /? I don't think that is your problem in any case, but it might be relevant. I didn't realise I wasn't clear, sorry. It might have been better if I'd said usr/ is under /. Anyway, it's not a separate partition. It was clear to me. It did a double take after Canek's email and still arrived at the same conclusion, but I accept that others read it differently. ... bunch of KDE stuff I've had the odd KDE issue along the way, like having extra panels spawning off-screen with notifications showing up in wierd places as a result. That doesn't sound like your specific problem, but assuming a KDE expert doesn't chime in here you might consider pursuing those questions in a KDE forum/list, or maybe even in the Gentoo forums where there is a section for desktop environments. Again, assuming somebody doesn't recognize your problem here. Since writing, I've found that my fonts have all changed as well. It's almost as though something were cruising my home directories and flipping bits. And KMail insists on using American English in the composer, despite my telling it UK. That may not be new though. I'm signed up to the KDE-Linux list already but I see hardly any traffic, and I suspect dark things about what happens to posts of mine on it. Disclaimer: I am not using the full KDE desktop, but use a few KDE apps with an enlightenment desktop. In the last week or two I noticed an oddity with kdeinit4, which I haven't yet been able to explain. I share it here in case it is related to your problem, but even so my setup is different to yours and I have no explanation for it: When away from base using insecure WiFi I run 'proxychains kdeinit4' to tunnel back to a local machine at home and bounce off to the Internet from there. Suddenly, my (old) Kmail-1.13.7 stopped using the tunnel. My (new) Knode-4.4.11 is also not using the tunnel. They both just hang not establishing a connection whatsoever. Konsole-2.14.2 is not using the tunnel either. Strangely, Konqueror-4.14.3 *is* using the tunnel as before. Launching konsole directly with 'proxychains konsole' is using the tunnel. Kmail just fails to get anywhere even when invoked directly with proxychains, rather than via kdeinit4. Proxychains was updated a couple of weeks ago and this problem may be related to it (I've raised a bug just in case), or it may be that something changed in KDE and this is the cause of both of our problems? The last thing is that at reboot the RAID-1 volume manager often fails to start. It says afterwards that it's running, but all the /dev/vg7/* are absent (that's where the logical volumes live). The file system root lives on /dev/md5 with metadata 1.0, while /dev/vg7 has metadata 1.0. The fact that it happens often but not always suggests a timing problem to me. I've sometimes seen this sort of thing with kernel raid autodetection, especially with metadata 1. More clarity needed on my part. The file-system root is /dev/md5 which has metadata 1.0. It's found reliably by kernel autodetection. Subsidiary partitions are in /dev/md7 which has metadata 1.0 and lvm2 volumes. Here's a bit of fstab: /dev/vg7/portage/usr/portageext4 relatime,discard 1 3 /dev/vg7/packages /usr/portage/packages ext4 relatime,discard 1 2 /dev/vg7/distfiles /usr/portage/distfiles ext4 relatime,discard 1 2 /dev/vg7/local /usr/local ext4 relatime,discard 1 2 It's the detection of md7 that often fails; I've had no trouble with md5. Several other directories are in lvm2 volumes in /dev/vg7, but nothing that's part of system. I suspect that an initramfs might help you out, assuming the filesystems on that RAID are useful in early boot. However, openrc and the raid init scripts should do a good job of configuring your raid if your mdadm.conf and such is correct, so if you don't need those filesystems until late in boot I don't think an initramfs will make much of a difference, since it would likely use the exact same userspace tools as openrc already does. Make sure your mdadm.conf is set up to search all devices that could contain RAID (drive device names can get re-ordered), and it doesn't hurt to put ARRAY lines in mdadm.conf to give it hints. Like this? ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5 ARRAY /dev/md7 devices=/dev/sda7,/dev/sdb7 No, I have always used something like: ARRAY /dev/md7 metadata=1.2 UUID=f9516418:7ef43875:4e922ca1:43796eb1 \ name=data_server:0 It may be that the /dev/sdaX takes longer to settle and
[gentoo-user] Re: General weirdness - a tale of woe.
Mick michaelkintzios at gmail.com writes: Your problem is different but has been covered in previous threads, as well as the news item. You could add ABI_X86=32 64 to make.conf, but that won't fit in with your desire for minimalism. So you need to run emerge with --autounmask-write then run etc-update or equivalent to apply the changes to package.use. Only to add that maintainers are regularly updating packages and this is why you may find that suddenly new packages require USE=abi_x86_32, when a week ago they didn't. It is worth noting that one multilib box of mine has not asked me (yet) to set USE=abi_x86_32 on any of its packages, while my laptop is regularly prompting me to do so. I have concluded that the former has no packages which are using 32bit code, while the latter does (I know that at least Skype is a culprit). So in extremis you could I guess purge any 32bit coded packages from your PC and the abi_x86_32 prompts should leave you alone. I shouldn't forget to add your usual disclaimer: YMMV Well, here are my extensions found in the make.conf, of interests:: EMERGE_DEFAULT_OPTS=--with-bdeps y --autounmask-write y It been in there a while. However, I must fess up that often it does not work and i have to issue --autounmask-write manually followed up by etc-update. Maybe I need to do this all at once, but for @system or something? I did not want to build all of those 32 bit libraries, but maybe that is necessary? How can I get the listing of packages that need those 32 bit libs? Maybe that the way to go? It just seems like I keep cleaning this up over and over again. James
Re: [gentoo-user] Re: plugin-containers missing libraries
Adam Carter wrote: On Wed, May 27, 2015 at 3:24 PM, Franz Fellner alpine.art...@gmail.com wrote: Look at usually means Read the file - look at the content ;) Lets pretend for one minute that i'm a dumbass. In what way would I read a binary executable, and how is that relevant to plugin-container? Just have a look and don't pretend it's a binary file ;) $ cat /usr/bin/firefox-bin #!/bin/sh unset LD_PRELOAD LD_LIBRARY_PATH=/opt/firefox/ GTK_PATH=/usr/lib/gtk-2.0/ exec /opt/firefox/firefox $@
Re: [gentoo-user] Re: plugin-containers missing libraries
On Wed, May 27, 2015 at 4:03 PM, Franz Fellner alpine.art...@gmail.com wrote: Adam Carter wrote: On Wed, May 27, 2015 at 3:24 PM, Franz Fellner alpine.art...@gmail.com wrote: Look at usually means Read the file - look at the content ;) Lets pretend for one minute that i'm a dumbass. In what way would I read a binary executable, and how is that relevant to plugin-container? Just have a look and don't pretend it's a binary file ;) $ cat /usr/bin/firefox-bin #!/bin/sh unset LD_PRELOAD LD_LIBRARY_PATH=/opt/firefox/ GTK_PATH=/usr/lib/gtk-2.0/ exec /opt/firefox/firefox $@ There's no firefox-bin in /usr/bin on my system, there's just # ls -l /usr/bin/firefox* lrwxrwxrwx 1 root root 26 May 9 19:13 /usr/bin/firefox - /usr/lib64/firefox/firefox And in that directory, again no shell script; # file /usr/lib64/firefox/firefox-bin /usr/lib64/firefox/firefox-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped System is ~amd64 for firefox/thunderbird
Re: [gentoo-user] General weirdness - a tale of woe.
On Wednesday 27 May 2015 21:40:37 Mick wrote: On Wednesday 27 May 2015 15:16:35 Peter Humphrey wrote: On Wednesday 27 May 2015 09:21:37 Rich Freeman wrote: I suspect that an initramfs might help you out, assuming the filesystems on that RAID are useful in early boot. However, openrc and the raid init scripts should do a good job of configuring your raid if your mdadm.conf and such is correct, so if you don't need those filesystems until late in boot I don't think an initramfs will make much of a difference, since it would likely use the exact same userspace tools as openrc already does. Make sure your mdadm.conf is set up to search all devices that could contain RAID (drive device names can get re-ordered), and it doesn't hurt to put ARRAY lines in mdadm.conf to give it hints. Like this? ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5 ARRAY /dev/md7 devices=/dev/sda7,/dev/sdb7 No, I have always used something like: ARRAY /dev/md7 metadata=1.2 UUID=f9516418:7ef43875:4e922ca1:43796eb1 \ name=data_server:0 My mdadm.conf is now this: DEVICE /dev/sd[ab]1 DEVICE /dev/sd[ab]5 DEVICE /dev/sd[ab]7 ARRAY /dev/md1 devices=/dev/sda1,/dev/sdb1 ARRAY /dev/md5 devices=/dev/sda5,/dev/sdb5 ARRAY /dev/md7 devices=/dev/sda7,/dev/sdb7 I'll see how that goes; so far no complaints about finding no arrays in the config file. I've never used UUIDs, preferring to be able to read what I'm specifying. It may be that the /dev/sdaX takes longer to settle and this causes your problem, but I can't tell for sure. That does sound unlikely, especially as /dev/sdXN is suggested in the comments in mdadm.conf. I've just switched on a few more sensors in gkrellm, and I see Vcor2 at 3.00 and +3.3v at 3.34. Is it worth fiddling with those and related settings in the BIOS? I've always hesitated to do that, preferring to let it sort itself out. If you haven't O/C'ed it, I'd leave it alone. However, if the voltage used to be something different in the past and is now registering a lower value using the same version BIOS firmware, then you could have a failing PSU. No, no over-clocking here. Let the hardware work as designed, say I. And I haven't looked at voltages before so I don't know what's normal. Failing PSU? Could be, and I have wondered. Maybe I'll make yet another attempt at setting up a new user and run without BOINC for a while, see if it's been applying too much load to this old bone-shaker. We all know that this will inevitably lead to behavioural problems (inc. waving your arms around and making noises ... :-)) :-) Thanks for your comments, Mick and friends. -- Rgds Peter
[gentoo-user] problems debugging a systemd problem
Hi folks. I spent a very frustrating time last night trying to figure out why my systemd would not boot using systemd. I am using dracut and its version is 041r2. Now what was happening is that the system would get to the pre-init-queue -- and I even set the rd.break there, but after that the system would not boot -- when I used debug it endlessly said calling setl forever. Now it turned out that the problem was that I had mistyped an rd.lv= line -- instead of ssd-files/usr I had ssd-files/-usr . Now, what I would like to know is how could I tell that it was trying to look for a non-existent lv? At the point of the break. no lvm volumes were active, although strangely enough I saw a e2fsck for the real root file system which was an lvm volume. I am finding its generally hard to debug systemd problems, several other times the system just sat there till I figured it out some other way. Any observations on this would be appreciated, but I don't want to get into a flame war, I just want to minimize the down time. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] General weirdness - a tale of woe.
On Wednesday 27 May 2015 15:16:35 I wrote: Since writing, I've found that my fonts have all changed as well. Yet more clarity: fonts have not been affected in applications that control their own fonts - KMail, Firefox... - but system functions and boinc-mgr (which uses whatever fonts are given it) are showing fonts several sizes larger than before. When I go to set them back again I find they're set right, so one part of KDE thinks fonts are, say, 14 points, and the rest of it thinks they're 18 points. How is this possible? I'm signed up to the KDE-Linux list already but I see hardly any traffic, Nothing at all in May, in fact. and I suspect dark things about what happens to posts of mine on it. Paranoia as well as OCPD! -- Rgds Peter
[gentoo-user] Blocking certain sites the easy way ?
Hi, With wireshark I found, that firefox accesses sites on startup, from which I dont know, for what reason this access is needed or whether the NSA, CIA, FBI, BDN, MOSSAD (fill in what organisation you ever suspect to do such things) has invaded my PC. I want to block such accesses for two reasons: First is ...hmmm... to block that accesses...second is to find out what will not work than. I dont want to install and configure a complete full blown firewalled SEL-Linux thingy here and I dont want to reboot my Linux box for every new site I added. I am looking for a simple solution, which I can use without studying the history of TCP/IP and others... ;))) What can I use for this purpose? Thank you very much in advance for any help! Best regards, Meino
Re: [gentoo-user] Blocking certain sites the easy way ?
On Thursday 28 May 2015 06:11:08 meino.cra...@gmx.de wrote: Hi, With wireshark I found, that firefox accesses sites on startup, from which I dont know, for what reason this access is needed or whether the NSA, CIA, FBI, BDN, MOSSAD (fill in what organisation you ever suspect to do such things) has invaded my PC. It may none of the above, but FF and any addons checking what the latest version is of themselves, as well as the Google search on the default hope page doing a DNS query or some such. I want to block such accesses for two reasons: First is ...hmmm... to block that accesses...second is to find out what will not work than. I dont want to install and configure a complete full blown firewalled SEL-Linux thingy here and I dont want to reboot my Linux box for every new site I added. I am looking for a simple solution, which I can use without studying the history of TCP/IP and others... ;))) What can I use for this purpose? You could try an application layer filter[1], but I think it won't work insofar the connections you observed are probably using ports and protocols same as your day to day browsing activity. Therefore you will likely need to use iptables to block individual domains or IP addresses and then regularly add to the list when the servers your browser wants to contact change in that amorphous and reconfiguring cloud out there. You don't have to reboot your box when you change rules, but you'll need to reload iptables. [1] http://l7-filter.sourceforge.net/HOWTO-kernel -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 12:09 AM, cov...@ccs.covici.com wrote: Hi folks. I spent a very frustrating time last night trying to figure out why my systemd would not boot using systemd. I am using dracut and its version is 041r2. Now what was happening is that the system would get to the pre-init-queue -- and I even set the rd.break there, but after that the system would not boot -- when I used debug it endlessly said calling setl forever. Now it turned out that the problem was that I had mistyped an rd.lv= line -- instead of ssd-files/usr I had ssd-files/-usr . Now, what I would like to know is how could I tell that it was trying to look for a non-existent lv? At the point of the break. no lvm volumes were active, although strangely enough I saw a e2fsck for the real root file system which was an lvm volume. I am finding its generally hard to debug systemd problems, several other times the system just sat there till I figured it out some other way. Any observations on this would be appreciated, but I don't want to get into a flame war, I just want to minimize the down time. Usually if you can get an emergency shell by adding emergency to the kernel command line (both GRUB and Gummiboot allow you to edit the kernel command line), then is easy to see what the problem is. My experience with LVM has been consistently pretty awful, which is why I don't use in any of my machines, but I suppose a systemctl --all --full will tell you what unit files have failed, and then you can journalctl -b -u them. Also journalctl -b by itself would tell you many times what the problem is. The only problem with the emergency shell is that sometimes is too early in the boot process for the keyboard drivers to have been loaded, but that is easily solved by adding a drivers+= line to a conf file in /etc/dracut.conf.d. Also, and I cannot stress this enough, you never delete your old (and working) kernel+initramfs until you have tested the new one. I would also recommend to leave the entries for the old kernel+initramfs in the GRUB/Gummiboot menu, but you can manage without them. Finally, and this is tooting my own horn, maybe you could try kerninst[1]? It's a little script I started a couple of years ago to automatically compile and install my kernels and generate my initramfs'. I use it in all my machines, and now my kernel update is just a matter of eselecting the new version, and running kerninst. I follow ~amd64 vanilla-sources, so this is roughly every week or two. Beware, though, that I don't use LVM nor RAID nor Luks, but in theory if you have a working kernel+dracut+[grub|gummitboot] configuration, it should also work with them. Regards. [1] https://github.com/canek-pelaez/kerninst -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
[gentoo-user] wine cpu usage
hello everyone. To run a windows application I installed the wine package.
But cpu usage of wine it a little high. using virtualbox is a lot
smoother(9% = 3% cpu usage) .
Is it normal?
my wine config:
[I] app-emulation/wine
Available versions: 1.6.2^t (~)1.7.0^t (~)1.7.3^t (~)1.7.4^t
(~)1.7.8^t (~)1.7.9^t (~)1.7.10^t (~)1.7.11^t (~)1.7.12^t (~)1.7.13^t
(~)1.7.14^t (~)1.7.15^t (~)1.7.16^t (~)1.7.17^t (~)1.7.18^t (~)1.7.19-r1^t
(~)1.7.20^t (~)1.7.21^t (~)1.7.22^t (~)1.7.28^t (~)1.7.29^t (~)1.7.33^t
(~)1.7.38^t (~)1.7.39^t (~)1.7.40^t (~)1.7.41^t (~)1.7.42^t (~)1.7.43^t
**^t {+X +alsa capi cups custom-cflags dos +fontconfig +gecko gphoto2
gsm gstreamer +jpeg (+)lcms ldap +mono mp3 ncurses netapi nls odbc openal
opencl +opengl osmesa oss pcap +perl pipelight +png +prelink pulseaudio
+realtime +run-exes s3tc samba scanner selinux +ssl staging test +threads
+truetype +udisks v4l vaapi (+)xcomposite xinerama +xml ABI_MIPS=n32 n64
o32 ABI_PPC=32 64 ABI_S390=32 64 ABI_X86=(+)32 (+)64 x32
ELIBC=glibc LINGUAS=ar bg ca cs da de el en en_US eo es fa fi fr he hi
hr hu it ja ko lt ml nb_NO nl or pa pl pt_BR pt_PT rm ro ru sk sl
sr_RS@cyrillic sr_RS@latin sv te th tr uk wa zh_CN zh_TW}
Installed versions: 1.7.43^t(12:50:01 AM 05/28/2015)(X alsa
fontconfig gecko jpeg lcms ldap mono mp3 ncurses nls opengl perl png
prelink realtime run-exes ssl threads truetype udisks xcomposite xml -capi
-cups -custom-cflags -dos -gphoto2 -gsm -gstreamer -netapi -odbc -openal
-opencl -osmesa -oss -pcap -pipelight -pulseaudio -s3tc -samba -scanner
-selinux -staging -test -v4l -vaapi -xinerama ABI_MIPS=-n32 -n64 -o32
ABI_PPC=-32 -64 ABI_S390=-32 -64 ABI_X86=32 64 -x32 ELIBC=glibc
LINGUAS=-ar -bg -ca -cs -da -de -el -en -en_US -eo -es -fa -fi -fr -he -hi
-hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro
-ru -sk -sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN
-zh_TW)
thanks
Re: [gentoo-user] Re: plugin-containers missing libraries
On Wednesday, May 27, 2015 04:20:52 PM Adam Carter wrote: On Wed, May 27, 2015 at 4:03 PM, Franz Fellner alpine.art...@gmail.com wrote: Adam Carter wrote: On Wed, May 27, 2015 at 3:24 PM, Franz Fellner alpine.art...@gmail.com wrote: Look at usually means Read the file - look at the content ;) Lets pretend for one minute that i'm a dumbass. In what way would I read a binary executable, and how is that relevant to plugin-container? Just have a look and don't pretend it's a binary file ;) $ cat /usr/bin/firefox-bin #!/bin/sh unset LD_PRELOAD LD_LIBRARY_PATH=/opt/firefox/ GTK_PATH=/usr/lib/gtk-2.0/ exec /opt/firefox/firefox $@ There's no firefox-bin in /usr/bin on my system, there's just # ls -l /usr/bin/firefox* lrwxrwxrwx 1 root root 26 May 9 19:13 /usr/bin/firefox - /usr/lib64/firefox/firefox And in that directory, again no shell script; # file /usr/lib64/firefox/firefox-bin /usr/lib64/firefox/firefox-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, stripped System is ~amd64 for firefox/thunderbird I'm also using ~amd64 firefox (37.0.2) and mine is also a binary. Anyways, what this means is that the library is not loaded by the loader but by firefox at runtime so it's nothing to worry about. I guess some versions or build use a script to preload the library.
