Chromium

[dibl]

Not really a warning, just a little advice.  The runtime configuration of chromium is controlled by /usr/share/applications/chromium.desktop.  For example, I have moved the chromium cache location to /run/user/1000/chromium-cache, using a startup script, and then editing /usr/share/applicatons/chromium.desktop to change this line near the end of the file:

Code: [Select]

Exec=/usr/bin/chromium %U
to

Code: [Select]

Exec=/usr/bin/chromium --disk-cache-dir=/run/user/1000/chromium-cache %U
to reduce the writes on my SSD.  However, I learned some time ago that every update of chromium overwrites /usr/share/applications/chromium.desktop and sets it back to default.  And of course there is no user feedback about this.  So you have to remember to fix it every time.

[cas]

actually I have a much bigger problem with chromium.
It doesn't start at all. It doesn't even show an empty page without problems.
it  only says "aw, snap. something went wrong while dispaying this webpage.  to continue reload or go to another webpage."

There are also some popups saying that my extensions have crashed.


an instant before i installed the pepperflashplugin. i wanted to know whether it works.
no idea whether this is related to the not working chromium.

Code: [Select]

cas@lifo:/home/casDecember$ LANG=C chromium&
[1] 23716
cas@lifo:/home/casDecember$ [23716:23716:0612/212506:ERROR:component_loader.cc(138)] Failed to parse extension manifest.
ATTENTION: default value of option force_s3tc_enable overridden by environment.

cas@lifo:/home/casDecember$ apt-cache policy chromium
chromium:
  Installiert:           35.0.1916.153-1
  Installationskandidat: 35.0.1916.153-1
  Versionstabelle:
     36.0.1985.49-1 0
          1 http://cdn.debian.net/debian/ experimental/main i386 Packages
 *** 35.0.1916.153-1 0
        500 http://http.debian.net/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status
cas@lifo:/home/casDecember$

purge and reinstall didn't help.

greetings, c

[dibl]

$ [23716:23716:0612/212506:ERROR:component_loader.cc(138)] Failed to parse extension manifest.
ATTENTION: default value of option force_s3tc_enable overridden by environment.

Not sure exactly what that error is, but (since it is already not working), I would go into ~/.cache and ~/.config and delete the chromium folders and everything in them, and then exit X and restart your login, or just reboot and then run chromium and see what you get with a new configuration.


You do have the correct version installed.

Code: [Select]

root@imerabox:/# apt-cache policy chromium
chromium:
  Installed: 35.0.1916.153-1
  Candidate: 35.0.1916.153-1
  Version table:
     36.0.1985.36-1 0
          1 http://ftp.us.debian.org/debian/ experimental/main amd64 Packages
 *** 35.0.1916.153-1 0
        500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

[cas]

[~/.cache and ~/.config and delete the chromium folders and everything in them, and then exit X and restart your login, or just reboot

didn't help unfortunately

[cas]

dmesg yields

Code: [Select]

[ 1665.840137] chromium[16997]: segfault at 1010 ip b34a081a sp bfa51100 error 4 in chromium[b0ee1000+68f0000]
[ 1666.366069] chromium[17008]: segfault at 1010 ip b280ebca sp bfa513c0 error 4 in chromium[b0ee1000+68f0000]
[ 2695.462218] chromium[25944]: segfault at 1010 ip b33e281a sp bfdc9170 error 4 in chromium[b0e23000+68f0000]
[ 2695.888644] chromium[25954]: segfault at 1010 ip b2750bca sp bfdc9430 error 4 in chromium[b0e23000+68f0000]


[dibl]

Hmmmmm.


Let's have a look at your hardware and drivers.

Code: [Select]

inxi -F

[ghstryder]

Hi dibl.

For what it's worth, I have the identical problem on my laptop - it is running 32bit not Siduction, so I haven't brought the problem here. Pepperflash has been running on it for at least a couple of weeks. It (Chromium) updated the day before yesterday.

64 bit Siduction desktop - no Chromium update on that same day. There may have been one a few days ago. Also running Pepperflash, with no problems whatsoever. Chromium works fine on the desktop machine.

Please note that I am not asking for support on the 32bit box, since it isn't running Siduction. I am just advising that this is more than a random 1 user issue.

To my inexperienced eye, this appears to agree that the problem might be confined to 32bit installs.

http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1228563.html

Regards

[cas]

my old thinkpad x60 (32bit)

Code: [Select]

System:    Host: lifo Kernel: 3.15-0.towo-siduction-686 i686 (32 bit) Desktop: KDE 4.13.2
           Distro: siduction 13.2.0 December - kde - (201312310247)
Machine:   System: LENOVO product: 1707WS5 v: ThinkPad X60
           Mobo: LENOVO model: 1707WS5 Bios: LENOVO v: 7BETD8WW (2.19 ) date: 03/31/2011
CPU:       Dual core Intel T2400 (-MCP-) cache: 2048 KB
           Clock Speeds: 1: 1000 MHz 2: 1833 MHz
Graphics:  Card: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics Controller
           Display Server: X.Org 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x768@50.0hz
           GLX Renderer: Mesa DRI Intel 945GM x86/MMX/SSE2 GLX Version: 2.1 Mesa 10.1.4
Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k3.15-0.towo-siduction-686
Network:   Card-1: Intel 82573L Gigabit Ethernet Controller driver: e1000e
           IF: eth0 state: down mac: 00:16:d3:2d:e9:2e
           Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945
           IF: wlan0 state: up mac: 00:18:de:89:e1:05
Drives:    HDD Total Size: 128.0GB (53.6% used) ID-1: /dev/sda model: SAMSUNG_SSD_830 size: 128.0GB
Partition: ID-1: / size: 20G used: 10G (53%) fs: ext4 dev: /dev/sda7
           ID-2: /home size: 55G used: 38G (74%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 4.65GB used: 0.01GB (0%) fs: swap dev: /dev/sda8
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 59.0C mobo: 50.0C
           Fan Speeds (in rpm): cpu: 2783
Info:      Processes: 179 Uptime: 3:26 Memory: 784.5/2016.2MB Client: Shell (bash) inxi: 2.1.28

chromium on my modern 64-bit desktop runs

[dibl]

I fired up my little 32-bit netbook this morning to update it, and now I see the chromium "aw snap" problem is here too.  So, the good news is, you do not necessarily have anything wrong with your system or configuration, but the bad news is, the 32-bit chromium package is defective.  I assume, since the 64-bit packages is OK, that this is a packaging problem of some kind.  Meanwhle, there's always iceweasel or the other browsers.

[cas]

newest version runs fine

Code: [Select]

apt-cache policy chromium
chromium:
  Installiert:           35.0.1916.153-2
  Installationskandidat: 35.0.1916.153-2
  Versionstabelle:
     36.0.1985.49-1 0
          1 http://cdn.debian.net/debian/ experimental/main i386 Packages
 *** 35.0.1916.153-2 0
        500 http://http.debian.net/debian/ unstable/main i386 Packages
        100 /var/lib/dpkg/status


[dibl]

Not on my mirror yet, but I'm glad it's fixed.

[grondilu]

I also use a SSD (a USB-key to be exact) where I mounted / (and /home as it's on the same partition), so I wanted to use my hard disk (mounted on /media/disk) for the chromium cache.


Instead of configuring the chromium config file I just made a symbolic link $HOME/.cache/chromium to /media/disk/chromium-cache.


It seems to work fine but I hope I'm not missing something because I'm not 100% happy with chromium's performance.

[dibl]

Instead of configuring the chromium config file I just made a symbolic link $HOME/.cache/chromium to /media/disk/chromium-cache.

That's a great idea to get the cache off the USB stick, although it won't be quite as fast as /run/user would be, which is only in memory.  But at least you won't have to fix the chromium.desktop file every time there is an update.

It seems to work fine but I hope I'm not missing something because I'm not 100% happy with chromium's performance.

What isn't working well?

[grondilu]

What isn't working well?

Pages take a bit of time to load sometimes.  Also, if you want to know, I happen to play chess on lichess.org and I lose quite a bit of time because of chromium's lack of responsiveness.

[dibl]

That could be chromium, or it could be your internet latency to that particular website, or the capability of your hardware, or some combination.  You could use iceweasel and/or konqueror to do a comparison, just to get a better idea of where the slowness is.  A very brief check of lichess.org here, with 7 tabs open in chromium, and it seems fully responsive.  What is your ping number at the bottom of a page on that site? I'm seeing numbers mostly in the 125 - 150ms range, but occasionally it jumps way over 200ms for a short bit.