Bugs:Stock answers
m (BUGS:Stock answers moved to Bugs:Stock answers: Please avoid block caps in namespaces) |
(add info from bug 3146) |
||
| Line 47: | Line 47: | ||
===MMC/SD card related (Product "System software/mmc-and-usb")=== | ===MMC/SD card related (Product "System software/mmc-and-usb")=== | ||
Has this happened with any other card? What is your card manufacturer, model and size? | Has this happened with any other card? What is your card manufacturer, model and size? | ||
| + | |||
| + | Could you check whether your card is corrupted (on device you can use "dosfsck -n" command, or you can plug USB cable and use your PC disk check utility) and save the information about the card configuration? | ||
| + | Would it also be possible for you to copy all the data from the card to safety[1], reformat the card using the device Filemanager (or if you do that from the PC, mention it) and try whether it still causes the lockup? | ||
| + | If not, copy the files back to the card to see whether it now causes lockup. So we can see whether lockup is caused by card itself, its formatting, the data on it, or corrupted file system. | ||
| + | [1] if you know Linux and don't mind some extra effort, it would be preferable to "dd" the whole mounted USB storage device content to an image file so that you get a disk image that can be copied directly back, otherwise you can use normal copy. | ||
===Charger issues=== | ===Charger issues=== | ||
Revision as of 10:01, 20 June 2008
Contents |
Bugzilla stock answers
Just a quick collection to share here... Feel free to edit/enhance! -User:Andre
General
version number
Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Does the crash give you any sort of error message? Was anything else running at the time?
Need a stacktrace (for Notes)
Is there any error message when it crashes? Can you please run Notes in a terminal window (Applications Menu -> Utilities > X Terminal, then enter the command "maemo-summoner /usr/bin/osso_notes.launch > log 2>&1" and hit the Enter key) and attach the resulting "log" file here after it has crashed?
Having a core dump could be even more useful. It requires installing the "sp-rich-core" package from the tools repository[1] and creating a "core-dumps" directory to the memory card with at least few megabytes of free space. You can get core dumps also without the rich-core package, but they are much less useful (and without it pre-installed applications core dumps are then named maemo-launcher-*).
[1] http://maemo.org/development/tools/
Duplicate
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.
Incomplete (after moreinfo keyword set)
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for/if you can still reproduce this. Thanks!
Potential Product specific answers
Internet Tablet Video Converter
AVI is just a container format, what matters is the codec. Can you please find out which codec your camera uses? You might want to check the camera manual. Thanks! Are there any error messages when the crash happens? Did the application install cleanly with no problems? Could you try to uninstall and reinstall again from a clean download please?
Input Methods
http://maemo.org/development/documentation/how-tos/4-x/extending_hildon_input_methods.html
Browser type (opera vs microb)
Can you please provide the output of "cat /home/user/.browser"
Power management
https://maemo.org/community/wiki/poweranddevicemanagement/
Reboot related
http://maemo.org/community/wiki/ReportingRebootIssues/
MMC/SD card related (Product "System software/mmc-and-usb")
Has this happened with any other card? What is your card manufacturer, model and size?
Could you check whether your card is corrupted (on device you can use "dosfsck -n" command, or you can plug USB cable and use your PC disk check utility) and save the information about the card configuration? Would it also be possible for you to copy all the data from the card to safety[1], reformat the card using the device Filemanager (or if you do that from the PC, mention it) and try whether it still causes the lockup? If not, copy the files back to the card to see whether it now causes lockup. So we can see whether lockup is caused by card itself, its formatting, the data on it, or corrupted file system. [1] if you know Linux and don't mind some extra effort, it would be preferable to "dd" the whole mounted USB storage device content to an image file so that you get a disk image that can be copied directly back, otherwise you can use normal copy.
Charger issues
Does the reboot loop stops when you disconnect the charger? Are you using the original N800 charger or something else? If you have another compatible charger, does the problem occur also with that? Does the crash/reboot happen only if you boot with charger, or if you plug the charger in when the device is already running?
Bluetooth DUN issues
Is there any error message displayed? Could you maybe provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/documentation/man_pages/hcidump.html ) of the situation? Which exact osso-ic version are you using? For your interest, there is also http://maemo.org/community/wiki/BluetoothDUN/ listing devices that are expected to work.