Chromium (Alien Bob SlackBuild) 53.x.x.x - Segmentation Fault
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Once again, back to version 51.x.x.x. with the original chromium config files. All's well. No errors on startup. No crashes.
And once again:
1) "new chrome" requires "new kernel", so it works with new kernel, but it does not work with old kernel,
2) "old chrome" does not require "new kernel", so it works with both new and old kernel.
OK, the sqlite locks seem to be an old bug from a while ago... still unresolved. It happens because Chromium does not shut down cleanly. When restarting, the databases are still locked from the previous instance.
And once again:
1) "new chrome" requires "new kernel", so it works with new kernel, but it does not work with old kernel,
2) "old chrome" does not require "new kernel", so it works with both new and old kernel.
.
So, what you're saying here is that EVERYONE who upgraded from 3.10.17 to 3.10.103 back in August had problems with Alien Bob's Chromium SlackBuilds? I don't think so, but thanks for the suggestions.
So, what you're saying here is that EVERYONE who upgraded from 3.10.17 to 3.10.103 back in April had problems with Alien Bob's Chromium SlackBuilds? I don't think so, but thanks for the suggestions.
What you are taking about? The Linux kernel 3.10.103 was released on 2016-08-28. I am too stupid for this topic, so I give up. Anyway, I wish you good luck in solving your problem.
What you are taking about? The Linux kernel 3.10.103 was released on 2016-08-28. I am too stupid for this topic, so I give up. Anyway, I wish you good luck in solving your problem.
.
Note the date on the Slackware Announcement below: Date: Mon, 29 Aug 2016 18:19:16 -0700 (PDT)
Quote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[slackware-security] kernel (SSA:2016-242-01)
New kernel packages are available for Slackware 14.1 to fix a security issue.
Here are the details from the Slackware 14.1 ChangeLog:
+--------------------------+
patches/packages/linux-3.10.103/*: Upgraded.
A flaw was found in the implementation of the Linux kernels handling of
networking challenge ack where an attacker is able to determine the shared
counter. This may allow an attacker located on different subnet to inject
or take over a TCP connection between a server and client without having to
be a traditional Man In the Middle (MITM) style attack.
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2016-5389
(* Security fix *)
+--------------------------+
Where to find the new packages:
+-----------------------------+
Thanks to the friendly folks at the OSU Open Source Lab
(http://osuosl.org) for donating FTP and rsync hosting
to the Slackware project! :-)
Also see the "Get Slack" section on http://slackware.com for
additional mirror sites near you.
Upgrade the packages as root:
# upgradepkg kernel-*.txz
If you are using an initrd, you'll need to rebuild it.
For a 32-bit SMP machine, use this command:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103-smp | bash
For a 64-bit machine, or a 32-bit uniprocessor machine, use this command:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103 | bash
Please note that "uniprocessor" has to do with the kernel you are running,
not with the CPU. Most systems should run the SMP kernel (if they can)
regardless of the number of cores the CPU has. If you aren't sure which
kernel you are running, run "uname -a". If you see SMP there, you are
running the SMP kernel and should use the 3.10.103-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 3.10.103 as the version.
If you are using lilo or elilo to boot the machine, you'll need to ensure
that the machine is properly prepared before rebooting.
If using LILO:
By default, lilo.conf contains an image= line that references a symlink
that always points to the correct kernel. No editing should be required
unless your machine uses a custom lilo.conf. If that is the case, be sure
that the image= line references the correct kernel file. Either way,
you'll need to run "lilo" as root to reinstall the boot loader.
If using elilo:
Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish
to use, and then run eliloconfig to update the EFI System Partition.
+------------------------------------------------------------------------+
| To leave the slackware-security mailing list: |
+------------------------------------------------------------------------+
| Send an email to majordomo@slackware.com with this text in the body of |
| the email message: |
| |
| unsubscribe slackware-security |
| |
| You will get a confirmation message back containing instructions to |
| complete the process. Please do not reply to this email address. |
+------------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Oh, and you're not stupid at all. I think we're just misunderstanding each other. I really do appreciate you posting help/suggestions, though. Thanks, zk1234.
I'm going to uninstall 51.x and reinstall 53.x with a brand new profile and set it up from scratch to see what happens.
What you are taking about? The Linux kernel 3.10.103 was released on 2016-08-28. I am too stupid for this topic, so I give up. Anyway, I wish you good luck in solving your problem.
.
Ah! I see why you were wondering... I typed "April" above, but meant August. Sorry. Mea culpa.
OK, YAY! I found Alien's build just previous to this one that I can't get to work. I had a copy in my hard media backups (DVD). So, I'm installing chromium-52.0.2743.82-x86_64-1alien.txz and I'm going to leave it at that for a while. I've spent the whole day screwing with this. Time to move on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
