Maemo Wiki Mirror - User contributions [en]

CSSU Requests

2011-08-22T08:58:55Z

82.208.42.129: Fix typos, note that this is just wishful thinking

This is to serve as a placeholder to record all suggestions for CSSU features.

'''For Developers:''' Please feel free to incorporate these in upcoming CSSU. Please also add practical challenges to implementation where possible in remarks.

'''For Community in general:''' Please add inputs into what new features would be great. If needed update the impact on Remarks, so that Developers, and the rest of us can understand why the feature is important. Note that manpower is limited so please avoid false hopes.

== Feature Requests ==

{{ambox | text ='''Important note:''' Follow up from the discussion thread.}}
{| class="wikitable sortable"
! width="125" | Category
! width="50" | S.No.
! width="300" | Request
! width="300" | Remarks
! width="10" | Done?
|-
|Hildon Desktop || 1 || Up or down swipe to launch preconfigured application || Currently swiping left and right in the landscape homescreen changes desktops. On the other hand swiping up and down has no functionality. The request is to add functionality so that a downswipe can bring the menu, and an upswipe can bring x-term or whatever || No
|-
|Contacts || 1 || Searchbox functionality in contacts app || To help search using virtual keyboard, instead of having open HW keyboard each time || No
|-
|Maps|| 1 || Fix for voice guidance || Currently patches exist to configure it. Not required. || No
|-
|<add>|| 1 || <add> || <add> || No
|-
|<add>|| 1 || <add> || <add> || No
|-
|<add>|| 1 || <add> || <add> || No
|-
|<add>|| 1 || <add> || <add> || No

|}

[[Category:Community]]
[[Category:Fremantle]]

Community SSU

2011-08-22T08:57:12Z

82.208.42.129: fix typo

<div style="float:right">
<imagemap>
Image:ClickToInstall.png|center|thumb|Testing
desc none
default [http://repository.maemo.org/community-testing/community-testing-fremantle.install Install testing]
</imagemap>
</div><div style="float:right">
<imagemap>
Image:ClickToInstallDisabled.png|center|thumb|Stable
desc none
default [[Community SSU/Stable]]
</imagemap>
</div><div style="float: right">
<imagemap>
Image:Bugsquad-logo-wazd-small.png|84px|center|thumb|Report bug
desc none
default [https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU]
</imagemap>
</div><div style="float: right">
[[Image:cssu-108.png]]
</div>

==What is it?==
Seamless Software Update ([[Seamless Software Update|SSU]]), is the term Nokia formerly used for over-the-air updates of Maemo (generally marketed as Maemo Update as of Maemo 5).

The Community Seamless Software Update (CSSU) is being developed by the Maemo community as a continuation of, and expansion on, Nokia's update support. It aims to deliver fixes which would be difficult to deliver through Extras (like core Maemo packages). It won't, however, bundle software which can be installed through the Extras repositories.

'''There are two such efforts for the Maemo platform.''' This page describes the one for Fremantle (Maemo 5, as used in the Nokia N900). The '''[[Diablo Community Project]]''' is doing the same for Diablo (Maemo 4.1, as used in the Nokia N800, N810 and N810 WiMAX Edition).
<br clear="all">

==Who is it for?==
'''Long-term:''' all N900 users/owners.

'''For now:''' power-users, developers, Nokia/Maemo/MeeGo engineers, testers, documentation writers and those willing to risk a re-flash in order to help.

==Installation==

"Newbie" Video Tutorial: http://www.youtube.com/watch?v=uMHxo1ALXNE

# Upgrade to [[Maemo 5/PR1.3|PR1.3]], Nokia's last official Maemo 5 update. If you're unsure if you have, ''Settings > About product'' should show ''Version'' beginning with '''20.2010.36'''.
# Click on the [http://repository.maemo.org/community-testing/community-testing-fremantle.install Install testing] button above. (http://j.mp/communityssu for a quick link to this page from your N900)
# Hildon Application Manager (HAM) will launch and begin processing (be patient). There are a series of installations for which it will prompt you with messages and warnings. Click "Accept" and "Done" for each to install.
# Once this is completed, close HAM and go into the applications menu. Tap the ''Community SSU'' icon. This will run through a series of scripts to ensure the community repository are set up.
# HAM will re-open and present a system upgrade called ''Maemo 5 Community SSU''. Once installed, your device will reboot.

Problems? Check the [[Community_SSU/Installation_FAQ|Installation FAQ]]

==Features==
{{main|Community SSU/Features}}

How to use new features such as [http://thpmaemo.blogspot.com/2011/02/community-ssu-features-to-look-forward.html Thomas Perl's hildon-desktop improvements] and the status of applications in [[Portrait Mode]] with <code>forcerotation</code>.

==Changelog==
{{main|Community SSU/Changelog}}

Changes in the SSU between PR1.3 and various SSU releases.

==Contributing==
{| style="background: #e8d8c8; border: 1px solid #666; width: 100%; text-align: center"
| Get involved on [[IRC]] (<code>#maemo-ssu</code>), [http://talk.maemo.org/showthread.php?t=67905 Talk], [https://bugs.maemo.org/buglist.cgi?resolution=FIXED&resolution=WONTFIX&resolution=---&classification=Extras&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&product=Maemo%205%20Community%20SSU Bugzilla] and [http://gitorious.org/community-ssu Gitorious].
|}

'''Can you write documentation?''' If so, it'd be great to flesh out the wiki page with installation instructions (to make it easy for users to install without worrying about missing a step or getting it wrong); explain more about the SSU and generally spruce up the wiki page and maintain things like the changelogs etc.

'''Were you involved in developing Maemo?''' If so, with Nokia now looking to Harmattan and MeeGo, we'd love to see your itches addressed in the Community SSU (CSSU). Have you always wanted to implement something in hildon-desktop, but Management stood in your way? We'd love to have it!

'''Have you written a patch for Maemo?''' Raise a bug and let's get it in the CSSU.

'''Are you a developer?''' There are numerous patches floating around for hildon-desktop; but they can't be included in the CSSU until they are configurable (via gconf) and default to off.

'''Want to test?''' Not only testing this release, but writing [[Community_SSU/QA#Test scripts|test scripts]] so that each release of the CSSU can get sanity checked before unleashing it into a "stable" repo for end-users. How do we do it? What should be tested? How is it organised?

'''Want to organise?''' There's still lots of process left to organise; hopefully there'll be bugs and features to triage and manage in bugs.maemo.org as well as communication of the testing, releases and end-user readiness of the CSSU.

'''Have great ideas?''' If you have suggestions that you think could be picked up by the CSSU developers, please add them here: [[CSSU Requests]]

For more information: contact MohammadAG on #maemo-ssu on FreeNode IRC or [mailto:council@maemo.org council@maemo.org].

== QA and bugs ==
{{main|Community SSU/QA}}

Quality is of paramount importance to the Community SSU. There are, therefore, two repositories: ''testing'' and ''stable''. Changes are carefully tested, with an extensive set of tests, before things are made "stable".

If you have found a bug, in either the ''testing'' or ''stable'' releases, please [https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU raise a bug]. Getting involved through testing, bug triaging and running of the tests is a good way to get involved; as, of course, is writing documentation!

== Development ==

{{main|Community SSU/Development}}

The Community SSU is developed and managed through [http://gitorious.org/community-ssu Gitorious]. Bugs are tracked in [https://bugs.maemo.org/buglist.cgi?resolution=FIXED&resolution=WONTFIX&resolution=---&classification=Extras&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&product=Maemo%205%20Community%20SSU Bugzilla]. Collaboration largely [http://mg.pov.lt/maemo-ssu-irclog/ happens on IRC]. Getting involved through development, bug triaging and managing developers is a good way to get involved.

[[Category:Community]]
[[Category:Fremantle]]

Bugs:Stock answers

2010-12-15T16:29:47Z

82.208.42.129: Add Third Party apps command

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==

To find out what is causing the issue, first check "top" (preferably from SSH console to avoid X etc CPU usage happening when doing this from Xterm) to see which process/es are using most CPU. Provide this information in a corresponding bug with a detailed description on how to trigger the issue.

If others aren't able to reproduce the issue, more information is need. Depending on what is using the CPU, output from different tools may need to be added to the bug:
* If D-BUS server or Tracker is using noticeable amount of CPU, run "dbus-monitor --session" and "dbus-monitor --system" commands.
* If X server is using noticeable amount of CPU, install "xresponse"[1] and run "xresponse -w 0 -a '*'" (this must be done from SSH console) to see which applications are updating their windows.
* Otherwise install "strace"[1] and trace the syscalls from the CPU consuming process with "strace -f -p <PID>".
* If even strace isn't telling enough, install "oprofile"[1] and provide Oprofile data on the issue.

[1] You get these tools from the SDK tools repository, see: http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle).

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there 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/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install ''sp-memusage'' package from the tools repository according to the instructions here: http://wiki.maemo.org/Documentation/devtools/maemo5.

''mem-smaps-private'' script from that package can be used to get most accurate values on process memory usage. ''mem-cpu-monitor'' tool can be used to track system and specified processes memory and CPU usage changes (most relevant values).

To track changes in usage of all device resources (not just memory) over longer period of time, install the ''sp-endurance'' package. The data its ''save-incremental-endurance-stats'' script stores, can be post-processed to a HTML report (with some bar graphs) using the ''parse-endurance-measurements'' script from the sp-endurance-postproc package.

Then attach the information provided by these tools to the corresponding bug.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox on how to analyze memory leaks using the x86 Scratchbox environment.

==Duplicate==
Thanks for reporting this.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

Please feel free to search for existing reports first to avoid filing duplicates.

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

==Third party applications==
Please list your third party applications installed. You can get a list of them by running "maemo-list-user-packages" in the terminal.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
**Short cut: In most cases this command executed as root should give enough information (after running it you can attach the file sip.pcap to the bug).
For WiFi/Wlan:
tcpdump -n -w sip.pcap -s 1500 -i wlan0
For mobile data connections:
tcpdump -n -w sip.pcap -s 1500 -i gprs0
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX PUSH issues===
If you have time it would be useful to also get an HCI log of the issue.

This is done by installing the hcidump package and running "hcidump -XVt" as root when performing the transfer. Please start hcidump before making the Bluetooth connection to get proper parsing of the OBEX packets.

To enable obexd and bluetoothd syslog output execute
"killall -USR2 obexd" and "killall -USR2 bluetoothd" (as root).

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known issues or any restrictions in place? (Like, traffic shaping of some sort)
* Please provide the SIM status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_sim_status
* Please provide the Network registration status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status

===Operator Setup Wizard===
* In case of missing cellular operators or similar issues, please provide MCC and MNC which are part of the IMSI. To do this, please open the X Terminal, and post the first six digits of the output of "string" after entering the command
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_imsi

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===ICD===
As ICD does not print anything to syslog and in order to get some logging, please become root (see http://wiki.maemo.org/Root_access ) to manually turn logging on using following command:
icd2-rotate-loglevel.sh DEBUG

===Wifi/WLAN===

====Connection problems====
If you are able to reproduce this, can you please provide a syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information) and then enable the wlancond debugging with the two commands
gconftool-2 --set --type int '/system/osso/connectivity/IAP/wlancond_debug_level' '2'
killall wlancond
and after this if you are able to reproduce this attach the /var/log/syslog file
from the device here.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

====Misc====

Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:
* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:
* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
Virtual keyboard: When this happens please start X Terminal and provide the output of
gconftool-2 -g /system/osso/af/slide-open

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
<code>run-standalone.sh /usr/bin/hildon-desktop</code>
From [[Terminal|console]] you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Restarting the Desktop (in Fremantle)===
Run "killall hildon-home" if for example the device becomes unresponsive (high memory usage) and you suspect some Desktop widgets to be the root cause of this.

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch -s (in Maemo5) or
/usr/bin/maemo-summoner /usr/bin/modest.launch showui (in Maemo4)
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ (Diablo) or http://wiki.maemo.org/Documentation/devtools/maemo5 and http://wiki.maemo.org/Documentation/devtools/maemo5/strace (Fremantle) for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

===Wrong file type===
If an audio file is played as video or the other way round:
* Please provide a testcase file
* If you have a linux desktop machine available, please provide the output of the following commands (and replace the filename accordingly):
gvfs-info filename.type
file filename.type
mp4info filename.type
gst-launch -t -m playbin uri=file:/path/to/file/filename.type

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle). Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===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?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===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?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]
[[Category:Quality Assurance]]

Mail for Exchange

2010-09-09T10:54:33Z

82.208.42.129: /* How can I check what version of the software is installed in my N900? */

''For general information on synchronizing your N900 with a mail or calendar server, please see the [[sync]] page''

This page answers questions which are commonly asked by new N900 MfE users.
It is mostly based on the analysis of the [http://talk.maemo.org/showthread.php?t=35136 MfE support thread.]

The current version of the page addresses three versions of MfE:

* PR1.0, also known as "Sales release" (1.2009.42-11)
* [[Maemo 5/PR1.1|PR1.1]] (2.2009.51-1). [http://conversations.nokia.com/2010/01/14/nokia-n900-software-update-part-2/ PR1.1 firmware update]
* [[Maemo_5/PR1.1.1|PR1.1.1]] (3.2010.02-8)

See [[#How can I check what version of the software is installed in my N900?|How can I check what version of the software is installed in my N900?]] for steps to check what version of the software is installed in your device.

If you use PR1.0 (sales release) it is strongly advised to update to PR1.1.1
See [[Maemo_5/PR1.1.1|PR1.1.1 summary]] for additional details and update instructions.

== Compatibility ==

=== Which server versions are supported by N900 MfE client? ===

==== PR 1.0 ====

Microsoft Exchange 2007 with service packs on top. MS Exchange 2010 also works fine according to [http://talk.maemo.org/showthread.php?t=34981 users reports.]

In more technical terms, only EAS protocol 12.1 is supported and implementation is tested against MS Exchange 2007 servers. See [[#How can I check what versions of EAS protocol are supported by my server?|How can I check what versions of EAS protocol are supported by my server?]] to check what EAS protocols are supported by your server.

==== PR 1.1 and PR 1.1.1 ====

* Microsoft Exchange 2007 with and without service packs on top. MS Exchange 2010 also works fine according to [http://talk.maemo.org/showthread.php?t=34981 users reports.]
* Microsoft Exchange 2003.

In more technical terms, EAS protocols 2.5, 12.0 and 12.1 are supported and implementation is tested against MS Exchange 2003 and 2007 servers. See [[#How can I check what versions of EAS protocol are supported by my server?|How can I check what versions of EAS protocol are supported by my server?]] to check what EAS protocols are supported by your server.

=== Which server versions are NOT supported by N900 MfE client? ===

==== PR 1.0 ====

* Microsoft Exchange 2003 is not supported.
* Microsoft Exchange 2007 without service packs is not supported.

The only way to get MfE working with these servers is to install PR.1.1 update which is [[#How can I check what version of the software is installed in my N900?|highly recommended.]]

==== PR 1.1 and PR 1.1.1 ====

* All non-MS services, although there has been [[Sync#Synchronising with Google|reported success]] synchronizing with Google and other non-MS services.

=== Why is feature XXX present in MfE for S60 but not for the N900? ===

S60 and Maemo MfE are different implementations.

The table below tries to summarize the most important differences between S60 and Maemo MfE implementations.

{| class="wikitable" border="1"
|-
! Feature
! S60 status
! Maemo status
|-
| ''E-Mail''
| YES, subfolders are not synced
| YES, subfolders are synced
|-
| ''Calendar''
| YES
| YES
|-
| ''Tasks''
| YES
| YES
|-
| ''Notes''
| ?
| NO
|-
| ''Meeting invitations replying''
| YES
| NO
|-
| ''Private appointments''
| YES
| NO
|-
| ''Corporate address book (GAL)''
| YES
| YES (*)
|-
| ''Exchange servers support''
| 2003, 2007
| 2003, 2007
|-
| ''Autodiscover''
| YES
| YES
|-
| ''Provisioning support''
| Partly YES
| NO
|}

(*) This feature is supported in PR1.1 and PR1.1.1 releases but not in PR1.0 (sales release).

Lack of provisioning support in MfE for the N900 is the most common cause of problems with corporate Exchange servers in North America. See [[#Provisioning|Provisioning]] for additional details.

== Known issues ==

=== Provisioning ===

N900 is considered to be "non provisioning device" from Exchange server point of view. It basically means that it can not be managed from Exchange server - administrator can not wipe your device, request you to use autolock and so on. Basically, all the provisioning data received from the server is ignored and the server is informed that N900 MfE does not support this feature.

Exchange administrator can configure the server in two ways - he/she can allow to use non-provisioning devices or disallow. In the second case N900 MfE will not work as server will reject the connection.

[http://talk.maemo.org/showpost.php?p=350081&postcount=33 Post with Exchange server 2003 management console]

=== GAL support for Exchange 2003 in PR1.1 release ===

==== PR 1.1 ====

Corporate phone book support is broken for PR 1.1 release. Update to PR1.1.1 or later releases of the software. It is broken only in PR1.1 release and only for Exchange 2003 servers (in more technical terms, for the EAS protocol 2.5).

=== SSL-related errors ===

The error message is displayed "Exchange server requires secure connection or account is disabled".

This infamous error message is caused by the fact that server certificate is untrusted from Maemo MfE client point of view.

Possible root causes and workarounds:

==== Server certificate is either self-signed or signed by the non-trusted authority (root certificate is not visible in N900 "Certificates" application).====

In this case, the server certificate shall be added to N900 certificate storage. Check [http://talk.maemo.org/showpost.php?p=401238&postcount=171 this message] and the thread after it for additional details.

Keep in mind - self-signed certificate shall have "CA" field. Otherwise, N900 certificate manager will not allow to install it. [http://talk.maemo.org/showpost.php?p=474320&postcount=871 This message] tells how to check does certificate has "CA" field or not.

Unfortunately, there is no way to disable certificates check at the client side in the current MfE releases (both PR1.0 and PR1.1/PR1.1.1).

==== PR1.0 ====

Disclaimer:

''The content of this section is applicable only for sales release (PR1.0). If you use this release, it is [[#How can I check what version of the software is installed in my N900?|highly recommended]] to upgrade the software to PR1.1 or later releases instead of following the advices below.''

* [http://talk.maemo.org/showpost.php?p=422732&postcount=312 Another important hint about importing certificates.]
* Server certificate is valid and trusted but MfE fails to sync. Check [https://bugs.maemo.org/show_bug.cgi?id=7357 this bug.]

=== HTML Messages ===

If you are using Exchange 2003 HTML messages will show as plain text. This is due to limitations of the ActiveSync protocol in this version of Exchange. The only way to get HTML support is to upgrade your server to Exchange 2007.

=== Sync with Exchange 2003 is broken. "Error in communication with Exchange Server" is displayed===

[http://talk.maemo.org/showpost.php?p=520334&postcount=1152 Problem statement.] Occurs only in PR1.1 and PR1.1.1 releases of the software.

This bug is fixed in the releases of the software later than PR.1.1.1.

The workaround is [[#How can I disable the synchronization of specific folders ?|to use mfefolders application]] and disable synchronization of "Deleted Items" folder.

== Troubleshooting ==

=== How can I check what version of the software is installed in my N900? ===

* Open "Settings" view
* Scroll to the "General" section
* Open "About product" applet
* Check the "Version" string

Versions strings versus releases:

{| class="wikitable" border="1"
|-
! Version
! Release
|-
| 1.2009.42-11
| PR 1.0 (sales)
|-
| 2.2009.51-1
| PR 1.1
|-
| 3.2010.02-8
| PR 1.1.1
|-
| 10.2010.19-1
| PR 1.2
|}

If you do not use the latest version it is strongly advised to update to PR1.2.
See [[Maemo 5/PR1.2|PR1.2 summary]] for additional details and update instructions.

=== How can I check what versions of EAS protocol are supported by my server? ===

# Take the logs following the steps described in the section [[#How can I turn the logging ON or OFF?|How can I turn the logging ON or OFF?]]
# Grep (search) for "MS-ASProtocolVersions:" in the logs. It will contain the EAS protocol versions supported by your server.

=== How can I turn the logging ON or OFF? ===

Warning:

''Before sending the logs to somebody (including Nokia) or publishing them, check that the log files do not contain any data which you treat as private or confidentional!''

==== Turning the logging ON ====

# [[Documentation/devtools/maemo5/syslog|Install syslog]] and reboot the device
# open terminal
# Execute the command:<pre>sudo gainroot</pre>
# Execute the command:<pre>cat /dev/null > /var/log/syslog</pre>
# Execute the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
# Reboot the device
# Initiate the synchronization session

<code>/var/log/syslog</code> will contain the logs. In order to filter only activesync-specific logs the following command can be used:

grep activesync /var/log/syslog

In order to copy the activesync log to your computer follow the steps below:

# Make sure your N900 is not connected to any other device (including your desktop computer) through USB
# Open xterm (if it is not opened yet)
# Issue the command '''sudo gainroot''' (if it was not issued yet)
# Issue the command: '''grep activesync /var/log/syslog > /home/user/MyDocs/activesync.log'''
# Close xterm
# Connect your N900 to the computer through USB
# Wait while flash drive(s) will appear in your computer
# Find activesync.log in one of the disk drives
# Copy it to your computer
# Remove the file from N900
# (Safely) disconnect N900 from the computer

==== Turning the logging OFF ====

In order to turn the logs OFF, execute the following commands from xterm:

<pre>
gconftool-2 -u /apps/activesync/AsDaemon/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/modest/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsProvider/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsBackup/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/asapplet/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsStatusApplet/Syslog/MinLogLevel
</pre>

After device reboot the logs will not be collected.

==== Extended logging ====

There is the extended logging option for getting logged all data which are transmitted and received by ActiveSync protocol. This option requires as-daemon logging to be turned on as described above. Then, as-daemon process needs to receive USR2 signal. This also can be done from a device console:

$ ps ax | grep as-daemon

This command will produce output like this:

1503 user 25756 S /usr/sbin/as-daemon -D --pidfile=/var/lock/as-daemon

where 1503 is the <pid> value needed for the next command. The next command is kill -USR2 <pid>, so for this case, it is:

$ kill -USR2 1503

After that, extended logging is turned on and ready to be used. This option does not survive over reboots. It can be turned off by sending the same kill -USR2 <pid> command again.

Warning:

''Before sending the logs to somebody (including Nokia) or publishing them, check that the log files do not contain any data which you treat as private or confidentional!''

=== Pre-setting EAS protocol to be used on sync/ disable auto-negotiation ===

In certain scenarios it might be useful to disable MfE's built in auto-negotiation function on what sync protocol (EAS 2.5, 12.0 or 12.1) to be used during syncs and use a pre-defined default one instead. Some users report error messages/ fails in sync when trying to establish a connection with e.g. a Scalix Groupware server. For the time being (until solved on either side) a workaround has been established by presetting the sync protocol to EAS 2.5 manually. Scalix Groupware Server with Scalix-AS-1.0.2-addon has been reported working with EAS 2.5 on basic sync (calendar, contacts and email). Before forcing MfE to use a specific protocol version make sure it is supported on the server-side.

To force MfE to use a particular protocol follow these steps:

# Start MfE configuration wizard entering the credentials on the first page and press "next". Do not enter the server address on page 2 yet!
# Open xterm and execute: '''sudo gainroot'''
# Execute the following commands:
##'''gconftool-2 -s --type=string /apps/activesync/ActiveSyncAccount1/use_version 2.5'''
##'''gconftool-2 -s --type=string /apps/activesync/ActiveSyncAccount1Temp/use_version 2.5'''
# Now continue MfE setup wizard and enter server address. Click next and follow the procedure to finish the wizard.

To check whether your changes have succesfully been submitted make sure you have [[Documentation/devtools/maemo5/syslog|syslog]] installed and type in xterm:

sudo gainroot tail -f /var/log/syslog | grep "Created factory"

There won't be a output right away but when

* credentials are verified
* first sync started
* Wizard setup completed

you should be able to see *Created factory for version 2.5* on the terminal. Pressing Ctrl+C will bring you back to the shell.

To disable the preset/ return to auto-negotiation it is recommended to delete the MfE-account and create a new one with the wizard from scratch.

Of course the above described way will also let you set EAS 12.0 or 12.1 as default protocols. Simply change the values on use_version in the respective gconftool commands.

=== Debugging possible certificate errors on self-signed certificates ===

You might experience an error message like "Either exchange server requires a secure connection or your account is disabled". This mostly occurs when syncing on secure connections by using a self-signed certificate and/or missing certificate authority (CA) tag in the respective field.

A quick way to check whether your certificate info gets rosolved properly by the maemo OS is a cli-tool called "cmcli".

Note: This is a system-wide certificate check - not a MfE-specific issue!

Please open terminal and type:

cmcli -T common-ca -v <your-server-dns-name-or-ip-address>:<port-number>

to check with one of the 118 pre-installed certificate authorities or:

cmcli -t ssl-ca -v <your-server-dns-name-or-ip-address>:<port-number>

when the chain of trust ends with a user-installed certificate. To be on the safe side, you can actually use both at the same time:

cmcli -T common-ca -t ssl-ca -v <your-server-dns-name-or-ip-address>:<port-number>

The missing tags have to be replaced with your personal server-address and respective port number (mostly 443 on SSL connections).

For instance: cmcli -T common-ca -v localhost:443

The output should read something like this:
0115e5345e4dd64855ed1e3d44060be25f26c2e6 nixu-jum
trust chain(1):
b5567d6c9eef05f07966d98eb2a85716bff4e80d Maemosec test CA
Verified OK

or

0115e5345e4dd64855ed1e3d44060be25f26c2e6 nixu-jum
Verification failed: self signed certificate

depending whether the verification succeeds or not.

If the verification fails and you want to see why, you can save the certificates the server sends by giving also the -s switch at the command line. Like this:

cmcli -T common-ca -sv <your-servers-dns-name-or-ip-address>:<port-number>

This will make the command to write the server certificates and possibly sent intermediate CA certificates into file(s) with the .pem-extension, where the name of each file is the SHA1 hash of the public key in hexadecimal. You can then study these file for instance with the command

openssl x509 -text -in <certificate-file>

== Miscellaneous ==

=== How can I use my corporate address book (GAL) ? ===

At first, [[#How can I check what version of the software is installed in my N900?|check that you use PR1.1 or later release of the software.]] If you use the release prior to PR1.1.1 check also [[#PR_1.1_3|the known problem of pre-PR1.1.1. Exchange 2003]] implementation.

It is possible to search for a contact in your corporate address book using "Contacts" application.

Follow these steps to add the contact from your corporate address book to the N900 address book:

* Open "Contacts" application
* Select "Get Contacts" option from the menu
* Choose "Import Mail Exch. contacts" option
**# Type parts of the first or last name
**# Press "Search"
**# Select contact from the results. (If the results are not sufficient press outside the window to return in step 1)
**# Press "Import"

=== How can I disable the synchronization of specific folders ? ===

Nokia does not provide the software for selecting the server folders which are synced to device. However, community does. Use [http://mfefolders.garage.maemo.org/ mfefolders] application to disable/enable synchronization of specific folders and assign them the names you wish to see in N900 mail client!

=== How do I synchronize mail for exchange from the command line ? ===

Open xterminal and type the following dbus command (note, I am not sure of the difference between fullSync and sync. I thought sync was safer so that is what I used and it seemed to work.):

dbus-send --print-reply --type=method_call --session --dest=com.nokia.asdbus /com/nokia/asdbus com.nokia.asdbus.<option>

<option> can be:
* <code>fullSync</code>,
* <code>sync</code>,
* <code>syncEmail</code> or
* <code>stopSync</code>

[[Category:HowTo]]
[[Category:Software]]
[[Category:Power users]]

Bugs:Stock answers

2010-04-30T15:52:45Z

82.208.42.129: /* GPRS/3G issues */

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==

To find out what is causing the issue, first check "top" (preferably from SSH console to avoid X etc CPU usage happening when doing this from Xterm) to see which process/es are using most CPU. Provide this information in a corresponding bug with a detailed description on how to trigger the issue.

If others aren't able to reproduce the issue, more information is need. Depending on what is using the CPU, output from different tools may need to be added to the bug:
* If D-BUS server or Tracker is using noticeable amount of CPU, run "dbus-monitor --session" and "dbus-monitor --system" commands.
* If X server is using noticeable amount of CPU, install "xresponse"[1] and run "xresponse -w 0 -a '*'" (this must be done from SSH console) to see which applications are updating their windows.
* Otherwise install "strace"[1] and trace the syscalls from the CPU consuming process with "strace -f -p <PID>".
* If even strace isn't telling enough, install "oprofile"[1] and provide Oprofile data on the issue.

[1] You get these tools from the SDK tools repository, see: http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle).

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there 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/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install ''sp-memusage'' package from the tools repository according to the instructions here: http://wiki.maemo.org/Documentation/devtools/maemo5.

''mem-smaps-private'' script from that package can be used to get most accurate values on process memory usage. ''mem-cpu-monitor'' tool can be used to track system and specified processes memory and CPU usage changes (most relevant values).

To track changes in usage of all device resources (not just memory) over longer period of time, install the ''sp-endurance'' package. The data its ''save-incremental-endurance-stats'' script stores, can be post-processed to a HTML report (with some bar graphs) using the ''parse-endurance-measurements'' script from the sp-endurance-postproc package.

Then attach the information provided by these tools to the corresponding bug.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox on how to analyze memory leaks using the x86 Scratchbox environment.

==Duplicate==
Thanks for reporting this.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

Please feel free to search for existing reports first to avoid filing duplicates.

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
**Short cut: In most cases this command executed as root should give enough information (after running it you can attach the file sip.pcap to the bug).
For WiFi/Wlan:
tcpdump -n -w sip.pcap -s 1500 -i wlan0
For mobile data connections:
tcpdump -n -w sip.pcap -s 1500 -i gprs0
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX PUSH issues===
If you have time it would be useful to also get an HCI log of the issue.

This is done by installing the hcidump package and running "hcidump -XVt" as root when performing the transfer. Please start hcidump before making the Bluetooth connection to get proper parsing of the OBEX packets.

To enable obexd and bluetoothd syslog output execute
"killall -USR2 obexd" and "killall -USR2 bluetoothd" (as root).

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to
wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known issues or any restrictions in place? (Like, traffic shaping of some sort)
* Please provide the SIM status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_sim_status
* Please provide the Network registration status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status

===Operator Setup Wizard===
* In case of missing cellular operators or similar issues, please provide MCC and MNC which are part of the IMSI. To do this, please open the X Terminal, and post the first six digits of the output of "string" after entering the command
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_imsi

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===ICD===
As ICD does not print anything to syslog and in order to get some logging, please manually turn logging on using following command:
icd2-rotate-loglevel.sh DEBUG

===Wifi/WLAN===

====Connection problems====
Could you please post the output of the command "dmesg" (in X Terminal) immediately after a connection failure?

====Misc====

Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:
* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:
* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
Virtual keyboard: When this happens please start X Terminal and provide the output of
gconftool-2 -g /system/osso/af/slide-open

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
<code>run-standalone.sh /usr/bin/hildon-desktop</code>
From [[Terminal|console]] you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Restarting the Desktop (in Fremantle)===
Run "killall hildon-home" if for example the device becomes unresponsive (high memory usage) and you suspect some Desktop widgets to be the root cause of this.

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch -s (in Maemo5) or
/usr/bin/maemo-summoner /usr/bin/modest.launch showui (in Maemo4)
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ (Diablo) or http://wiki.maemo.org/Documentation/devtools/maemo5 and http://wiki.maemo.org/Documentation/devtools/maemo5/strace (Fremantle) for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle). Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===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?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===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?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]
[[Category:Quality Assurance]]

Bugs:Stock answers

2010-04-30T15:52:10Z

82.208.42.129: /* Connectivity */

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==

To find out what is causing the issue, first check "top" (preferably from SSH console to avoid X etc CPU usage happening when doing this from Xterm) to see which process/es are using most CPU. Provide this information in a corresponding bug with a detailed description on how to trigger the issue.

If others aren't able to reproduce the issue, more information is need. Depending on what is using the CPU, output from different tools may need to be added to the bug:
* If D-BUS server or Tracker is using noticeable amount of CPU, run "dbus-monitor --session" and "dbus-monitor --system" commands.
* If X server is using noticeable amount of CPU, install "xresponse"[1] and run "xresponse -w 0 -a '*'" (this must be done from SSH console) to see which applications are updating their windows.
* Otherwise install "strace"[1] and trace the syscalls from the CPU consuming process with "strace -f -p <PID>".
* If even strace isn't telling enough, install "oprofile"[1] and provide Oprofile data on the issue.

[1] You get these tools from the SDK tools repository, see: http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle).

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there 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/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install ''sp-memusage'' package from the tools repository according to the instructions here: http://wiki.maemo.org/Documentation/devtools/maemo5.

''mem-smaps-private'' script from that package can be used to get most accurate values on process memory usage. ''mem-cpu-monitor'' tool can be used to track system and specified processes memory and CPU usage changes (most relevant values).

To track changes in usage of all device resources (not just memory) over longer period of time, install the ''sp-endurance'' package. The data its ''save-incremental-endurance-stats'' script stores, can be post-processed to a HTML report (with some bar graphs) using the ''parse-endurance-measurements'' script from the sp-endurance-postproc package.

Then attach the information provided by these tools to the corresponding bug.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox on how to analyze memory leaks using the x86 Scratchbox environment.

==Duplicate==
Thanks for reporting this.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

Please feel free to search for existing reports first to avoid filing duplicates.

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
**Short cut: In most cases this command executed as root should give enough information (after running it you can attach the file sip.pcap to the bug).
For WiFi/Wlan:
tcpdump -n -w sip.pcap -s 1500 -i wlan0
For mobile data connections:
tcpdump -n -w sip.pcap -s 1500 -i gprs0
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX PUSH issues===
If you have time it would be useful to also get an HCI log of the issue.

This is done by installing the hcidump package and running "hcidump -XVt" as root when performing the transfer. Please start hcidump before making the Bluetooth connection to get proper parsing of the OBEX packets.

To enable obexd and bluetoothd syslog output execute
"killall -USR2 obexd" and "killall -USR2 bluetoothd" (as root).

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to
wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known
issues or any restrictions in place? (Like, traffic shaping of some sort)
* Please provide the SIM status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_sim_status
* Please provide the Network registration status by opening the X Terminal and entering:
dbus-send --system --print-reply --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_registration_status

===Operator Setup Wizard===
* In case of missing cellular operators or similar issues, please provide MCC and MNC which are part of the IMSI. To do this, please open the X Terminal, and post the first six digits of the output of "string" after entering the command
dbus-send --system --print-reply --dest=com.nokia.phone.SIM /com/nokia/phone/SIM Phone.Sim.get_imsi

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===ICD===
As ICD does not print anything to syslog and in order to get some logging, please manually turn logging on using following command:
icd2-rotate-loglevel.sh DEBUG

===Wifi/WLAN===

====Connection problems====
Could you please post the output of the command "dmesg" (in X Terminal) immediately after a connection failure?

====Misc====

Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:
* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:
* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
Virtual keyboard: When this happens please start X Terminal and provide the output of
gconftool-2 -g /system/osso/af/slide-open

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
<code>run-standalone.sh /usr/bin/hildon-desktop</code>
From [[Terminal|console]] you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Restarting the Desktop (in Fremantle)===
Run "killall hildon-home" if for example the device becomes unresponsive (high memory usage) and you suspect some Desktop widgets to be the root cause of this.

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch -s (in Maemo5) or
/usr/bin/maemo-summoner /usr/bin/modest.launch showui (in Maemo4)
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ (Diablo) or http://wiki.maemo.org/Documentation/devtools/maemo5 and http://wiki.maemo.org/Documentation/devtools/maemo5/strace (Fremantle) for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle). Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===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?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===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?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]
[[Category:Quality Assurance]]

Bugs:Stock answers

2010-02-15T20:16:20Z

82.208.42.129: Add "Need a syslog"

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==
Can you please:

* Either install "strace" from the tools repository[1] and "strace" the CPU consuming process, or
* install 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.
* do "kill -6 <PID>" for the process that takes the CPU, and
* attach the resulting .rcore.lzo file from the core-dumps directory here?

[1] http://maemo.org/development/tools/

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Becoming root: http://wiki.maemo.org/Root_access
* Start X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there 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/
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install sp-memusage package from the tools repository according to the instructions here and provide a log: http://wiki.maemo.org/Documentation/devtools/maemo5

The mem-monitor-smaps script can be used to report device free memory and process memory usage accurately enough. Data about shared memory segments (and other system resource) usage changes can be logged with the tools&scripts in the sp-endurance package.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox for how to find memory leaks using the Scratchbox environment.

==Duplicate==
Hi there!

Thanks for the bug report. This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.

Thanks!

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to
wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known
issues or any restrictions in place? (Like, traffic shaping of some sort)

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===Wifi/WLAN===
Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:

* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:

* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
http://maemo.org/development/documentation/how-tos/4-x/extending_hildon_input_methods.html

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
run-standalone.sh /usr/bin/hildon-desktop
From console you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch showui
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ . Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===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?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===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?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]

Mainstream Linux Alignment

2009-07-13T13:02:16Z

82.208.42.129: /* freedesktop.org */ added bug 4766

Let's list here bugs and enhancement requests relating to the Maemo architecture and its proximity/compatibility with mainstream linux standards. The progress on these tasks should bring easier life for application developers and also to platform developers willing to close ties with Debian, Ubuntu, etc.

Useful information:
* [http://maemo.org/maemo_release_documentation/maemo4.1.x/node6.html#SECTION00660000000000000000 Maemo Compared to Desktop Linux Distributions]
* [http://maemo.org/maemo_release_documentation/maemo4.1.x/node6.html#SECTION00635100000000000000 Essential Packages and Delta to Standard Debian Systems]

Proposals:

* [[Maemo_Reconstructed]]

== General upstream ==
{{#bugzilla:id=3826,3827
|columns=id,priority,severity,product,status,resolution,summary
}}

== Debian / GNU / Linux ==
{{#bugzilla:id=752,1621,2896,3825,3951,3989,4008,4078,4248
|columns=id,priority,severity,product,status,resolution,summary
}}

== freedesktop.org ==
{{#bugzilla:id=657,1303,3817,3818,3828,3822,3913,4766
|columns=id,priority,severity,product,status,resolution,summary
}}

== GTK+ ==
{{#bugzilla:id=1464
|columns=id,priority,severity,product,status,resolution,summary
}}

[[Category:Development]]