FilingBugs
6032
Comment:
|
6273
Remove link to unity project bug filing as apport hook helps alot
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
Use the standard ubuntu bug reporting tool. From the command line: | Use the standard ubuntu bug reporting tool as it gathers detailed information regarding your systems configuration. From the command line: |
Line 14: | Line 14: |
{{{ubuntu-bug}}} | {{{ubuntu-bug unity}}} |
Line 16: | Line 16: |
You should file bugs against [[http://bugs.launchpad.net/unity|Unity]] in Launchpad. | |
Line 18: | Line 17: |
When a crasher occurs on your system you should automatically see a dialog inviting you to report the issue. If will collect useful information from your system, automatically as well. But here is what you can also add to your bug report to help us confirm the issue more easily: * Provide the result of the command glxinfo. It contains important graphics information that can help us identify your issue. |
When a crasher occurs on your system you should automatically see a dialog inviting you to report the issue. It will collect useful information from your system, automatically as well. But here is what you can also add to your bug report to help us confirm the issue more easily: * Provide the result of the command glxinfo. It contains important graphics information that can help us identify your issue. (glxinfo is provided by the package mesa-utils and is automatically run in Natty) |
Line 32: | Line 31: |
In this case, contact the [[http://design.canonical.com/|Design Team]] first before filing a bug against Unity. You can reach us on the ayatana list or on #ayatana on freenode. If the issue is acknowledged, or if you really want to file a bug, then tag it as 'opinion' or 'whishlist', and link the issue to the 'ayatana-design' project. This will follow a different workflow. | In this case, contact the [[http://design.canonical.com/|Design Team]] first before filing a bug against Unity. You can reach them on the ayatana list or on #ayatana on freenode. If the issue is acknowledged, or if you really want to file a bug, then tag it as 'opinion' or 'wishlist', and link the issue to the 'ayatana-design' project. This will follow a different workflow. |
Line 42: | Line 41: |
To manually create a bug report: | To manually file a bug report using a crash file: |
Line 96: | Line 95: |
|| [[https://launchpad.net/ubuntu/+bugs?field.tag=running-unity|`running-unity`]] || Bugs reported by people who are running Unity || | |
Line 101: | Line 101: |
Sometimes a developer might ask you to test a quick patch he came up with: check the [[https://launchpad.net/~unity/+archive/daily|Daily builds PPA]] to see if an updated version of Unity fixes the bugs you see. Be careful though, as those are daily builds that may break other things, and are to be considered unstable. | Sometimes a developer might ask you to test a quick patch he came up with: check the [[https://launchpad.net/~unity/+archive/daily|Daily builds PPA]] to see if an updated version of Unity fixes the bugs you are experiencing. Be careful though, as those are daily builds that may break other things, and are to be considered unstable. |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Introduction
This page provides guidelines for filing bugs related to Unity, how to provide the debugging information required to analyze the issue, and how to triage Unity bugs.
Filing bugs
Technical issues
Use the standard ubuntu bug reporting tool as it gathers detailed information regarding your systems configuration. From the command line:
ubuntu-bug unity
When a crasher occurs on your system you should automatically see a dialog inviting you to report the issue. It will collect useful information from your system, automatically as well. But here is what you can also add to your bug report to help us confirm the issue more easily:
- Provide the result of the command glxinfo. It contains important graphics information that can help us identify your issue. (glxinfo is provided by the package mesa-utils and is automatically run in Natty)
- Provide the complete description of your GPU and how much video RAM it has. For instance, the market name of your graphics card may be Radeon HD 4650 or NVidia Geforce GTX 280. For embedded Intel GPU, you don't need to provide that information.
- Your monitor resolution and screen setup (single, dual monitor, triple monitor)
If the dialog doesn't appear for some reason, see the "advanced" procedure below.
Even if the issue is actually in Compiz, it's still worth filing the bug against Unity, and we'll triage things to point to compiz as well. We're working very closely with the Compiz project.
Design and usability issues
Because Unity is a user interface, certain problems may be related to usability or design aspects, and not technical aspects.
In this case, contact the Design Team first before filing a bug against Unity. You can reach them on the ayatana list or on #ayatana on freenode. If the issue is acknowledged, or if you really want to file a bug, then tag it as 'opinion' or 'wishlist', and link the issue to the 'ayatana-design' project. This will follow a different workflow.
Advanced debugging procedure
Stale crashers
If apport did not automatically report the issue, you can check that a crasher trace has been collected by looking into the /var/crash directory. You should see a filename containing 'compiz'.
ls -altr /var/crash to list them in chronological order.
To manually file a bug report using a crash file:
- stay in your current X session
add a window manager from a TTY if needed, ie CTRL-ALT-F1, login, DISPLAY=:0 metacity --replace
then, from your X session, do: apport-bug -c /var/crash/<compiz crash file> and follow the procedure in the web page that should open shortly after you invoke this command. Note that focus issues may prevent the page to appear on the top, but look for a new browser window opened in your workspace.
Getting a stack trace
If for some reason apport was not enabled on your system, or if you have a reproducible issue we ask you to investigate, here is how you can generate a stack trace and inspect internal variables.
Ensure that you have the debugging symbols for the compiz, nux and unity packages.
Otherwise, from tty1 (Ctrl + Alt + F1)
$ unity --advanced-debug GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/> ... (gdb) set logging file 'unity.log' (gdb) run [ and when compiz/unity crash, do...] (gdb) bt full [ then CTRL-D or re-run compiz to continue working ] (gdb) run
You can also get a valgrind trace by running valgrind compiz --replace & in a terminal. This is a little bit slower to get because it runs compiz under emulation, but it does produce some output which isn't possible to get from gdb.
In extreme circumstances, we may ask you to use the crashhandler plugin from git and enable that in ccsm.
Triaging instructions
TBD
Bug Tags
These tags allow isolation of bugs into smaller groups, providing an easier and faster way to work on specific issues.
Tag |
Use case |
Compiz bugs which are affecting Unity |
|
Bugs reported by people who are running Unity |
|
... |
... |
Testing a fix
Sometimes a developer might ask you to test a quick patch he came up with: check the Daily builds PPA to see if an updated version of Unity fixes the bugs you are experiencing. Be careful though, as those are daily builds that may break other things, and are to be considered unstable.
Known bugs
Known bugs, or missing features, are tracked in Launchpad and assigned to milestones to indicate when it is planned to be fixed and/or released.
Unity milestones: https://bugs.launchpad.net/unity/+milestones
Also see:
Unity/FilingBugs (last edited 2023-12-04 16:43:22 by jbicha)