Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26948 - [chromium] Waiting for disk
Attached to Project:
Arch Linux
Opened by Leryan (Leryan) - Thursday, 17 November 2011, 16:16 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 23 November 2011, 12:12 GMT
Opened by Leryan (Leryan) - Thursday, 17 November 2011, 16:16 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 23 November 2011, 12:12 GMT
|
DetailsDescription:
Chromium is waiting for writing datas to disk when stopping it. killall -9 chromium does'nt work anymore. Additional info: * chromium 15.0.874.121-1 * tried with new configuration directory, no change. * the computer is totally unable to reboot or shutdown. Steps to reproduce: 1. Launch Chromium 2. Use it for a while 3. Close all windows Have a look in processes, there is still a chromium one waiting for disk. I don't know if it's a chromium or something else bug. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Wednesday, 23 November 2011, 12:12 GMT
Reason for closing: Works for me
Additional comments about closing: Unable to reproduce the issue. Reopen if you gather more information and/or can provide steps to reproduce.
Wednesday, 23 November 2011, 12:12 GMT
Reason for closing: Works for me
Additional comments about closing: Unable to reproduce the issue. Reopen if you gather more information and/or can provide steps to reproduce.
I cannot reproduce it. I've no chromium process after closing it
By « waiting for disk » I mean chromium is waiting access to disk, reading or writing I don't know.
Before posting this bug report I've made many times this procedure and always the same bug. After many days (and different updates of others packages than chromium), the bug was still here.
Today, no. Juste don't understand.
Seeing as you don't experience the bug anymore, I'll close this report.