You are not logged in.
Same problem here with a fresh install under vmware at random when i start typing. For example i press the letter "o" to search something and it segfaults so i restart and press the same letter and the there it goes again but if i then press another letter first its fine for a while.....
Offline
Edit: I made a post in the wrong thread and it got moved here instead of deleted... I'm having the same problem in Arch x64.
Last edited by bdamos (2012-04-08 09:10:55)
Offline
I have the same issue as bdamos - I believe Chromium is segfaulting. This has started happening since an update yesterday, the following packages were upgraded;
[2012-04-07 19:55] removed sqlite3 (3.7.11-1)
[2012-04-07 19:55] upgraded automake (1.11.3-1 -> 1.11.4-1)
[2012-04-07 19:55] upgraded chromium (18.0.1025.142-1 -> 18.0.1025.151-1)
[2012-04-07 19:55] upgraded dhcpcd (5.5.5-1 -> 5.5.6-1)
[2012-04-07 19:55] warning: directory permissions differ on mnt/
filesystem: 777 package: 755
[2012-04-07 19:55] upgraded filesystem (2012.2-2 -> 2012.2-4)
[2012-04-07 19:55] installed sqlite (3.7.11-2)
[2012-04-07 19:55] upgraded firefox (11.0-2 -> 11.0-3)
[2012-04-07 19:55] upgraded gawk (4.0.0-2 -> 4.0.1-1)
[2012-04-07 19:55] upgraded git (1.7.9.6-1 -> 1.7.10-1)
[2012-04-07 19:55] upgraded gnutls (3.0.17-1 -> 3.0.18-1)
[2012-04-07 19:55] upgraded go (2:1-4 -> 2:1-5)
[2012-04-07 19:55] upgraded i3status (2.4-1 -> 2.4-2)
[2012-04-07 19:55] upgraded kmod (7-1 -> 7-2)
[2012-04-07 19:55] upgraded laptop-mode-tools (1.60-1 -> 1.60-2)
[2012-04-07 19:55] upgraded libpng (1.5.9-1 -> 1.5.10-1)
[2012-04-07 19:55] upgraded udev (181-5 -> 181-9)
[2012-04-07 19:55] upgraded util-linux (2.21-6 -> 2.21.1-2)
[2012-04-07 19:55] upgraded mkinitcpio (0.8.5-1 -> 0.8.6-2)
[2012-04-07 19:55] >>> Updating module dependencies. Please wait ...
[2012-04-07 19:55] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-04-07 19:55] ==> Building image from preset: 'default'
[2012-04-07 19:55] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-04-07 19:55] ==> Starting build: 3.2.14-1-ARCH
[2012-04-07 19:55] -> Parsing hook: [base]
[2012-04-07 19:55] -> Parsing hook: [udev]
[2012-04-07 19:55] -> Parsing hook: [autodetect]
[2012-04-07 19:55] -> Parsing hook: [pata]
[2012-04-07 19:55] -> Parsing hook: [scsi]
[2012-04-07 19:55] -> Parsing hook: [sata]
[2012-04-07 19:55] -> Parsing hook: [filesystems]
[2012-04-07 19:55] -> Parsing hook: [usbinput]
[2012-04-07 19:55] -> Parsing hook: [fsck]
[2012-04-07 19:55] ==> Generating module dependencies
[2012-04-07 19:55] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-04-07 19:55] ==> Image generation successful
[2012-04-07 19:55] ==> Building image from preset: 'fallback'
[2012-04-07 19:55] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-04-07 19:55] ==> Starting build: 3.2.14-1-ARCH
[2012-04-07 19:55] -> Parsing hook: [base]
[2012-04-07 19:55] -> Parsing hook: [udev]
[2012-04-07 19:55] -> Parsing hook: [pata]
[2012-04-07 19:55] -> Parsing hook: [scsi]
[2012-04-07 19:55] -> Parsing hook: [sata]
[2012-04-07 19:55] -> Parsing hook: [filesystems]
[2012-04-07 19:55] -> Parsing hook: [usbinput]
[2012-04-07 19:55] -> Parsing hook: [fsck]
[2012-04-07 19:55] ==> Generating module dependencies
[2012-04-07 19:55] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-04-07 19:55] ==> Image generation successful
[2012-04-07 19:55] upgraded linux (3.2.13-1 -> 3.2.14-1)
[2012-04-07 19:56] upgraded linux-headers (3.2.13-1 -> 3.2.14-1)
[2012-04-07 19:56] upgraded lm_sensors (3.3.2-1 -> 3.3.2-2)
[2012-04-07 19:56] upgraded man-pages (3.37-1 -> 3.38-1)
[2012-04-07 19:56] upgraded pcmciautils (018-2 -> 018-4)
[2012-04-07 19:56] upgraded rxvt-unicode (9.15-1 -> 9.15-2)
[2012-04-07 19:56] upgraded syslog-ng (3.3.4-4 -> 3.3.4-5)
[2012-04-07 19:56] upgraded tzdata (2012b-3 -> 2012c-1)
[2012-04-07 19:56] upgraded udisks (1.0.4-2 -> 1.0.4-3)
# later on in the day
[2012-04-08 09:33] starting full system upgrade
[2012-04-08 09:33] upgraded xf86-video-nv (2.1.18-5 -> 2.1.18-6)
Running 64 bit, all packages up to date.
Offline
I have the same issue as bdamos - I believe Chromium is segfaulting. This has started happening since an update yesterday, the following packages were upgraded;
Running 64 bit, all packages up to date.
See this thread for the bug report
Offline
Merged threads
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Posting to confirm that the bug no longer persists when downgrading to the previous build.
Offline
Confirming DarksideEE7
Does not happen any more in Chromium 18.0.1025.142 (Developer Build 0 Linux)
ArchLinux x86_64 on Dell Latitude E5410
Offline
The chromium package got an upgrade: https://projects.archlinux.org/svntogit … 440e30ee22
Let's hope this is fixed now.
Offline
The chromium package got an upgrade: https://projects.archlinux.org/svntogit … 440e30ee22
Let's hope this is fixed now.
Upgraded to release 3 a little while ago. No problems so far...
Offline
julian24 wrote:The chromium package got an upgrade: https://projects.archlinux.org/svntogit … 440e30ee22
Let's hope this is fixed now.
Upgraded to release 3 a little while ago. No problems so far...
The upgrade seems to have worked for me too. Not a segfault in sight after about 3-4 hours of use.
Offline
Me too. I <3 the Arch
sorry for my english. {Arch Linux, Debian} User
Offline
Yup moving from 18.0.1025.151-1 → 18.0.1025.151-3 seems to fix it (no crashes since the upgrade).
I must admit I've been quite surprised to see the error being displayed in dmesg.
Offline
Segfault persist on my Arch x86_64 with chromium-18.0.1025.151-3, crashes sometimes when I use omnibox.
Offline
Upgraded to 18.0.1025.151-3 and no segfaults since
Offline
I have chromium-18.0.1025.151-3 and still crashes.
Offline
I'm no longer experiencing crashes now that I updated to 18.0.1025.151-3
To others experiencing crashing still I would disable all of your addons and check any experimental features that are enabled in about:flags and test again. The omnibox bug seems to be fixed now, so an addon may be causing the seg faults.
Last edited by DarksideEE7 (2012-04-10 02:57:43)
Offline
All AddOns are deactivated, even the automatics has been disabled and yet it still crashes. Is there any x86_64 user who confirms if bug's gone?. I think that bugfix only works for 32 bits, Could it be?
Offline
All AddOns are deactivated, even the automatics has been disabled and yet it still crashes. Is there any x86_64 user who confirms if bug's gone?. I think that bugfix only works for 32 bits, Could it be?
I'm on x86_64 with no crashes.
Offline
The new package is much more stable, I advise everyone that downgraded to get the newest.
Offline