Description of problem: I just install Giggle to test out git from a gui instead of the console. As I've opened it and clicked on Project followed by Clone a repository and then added the adress https://github.com/mer-hybris/droid-hal-device.git and then chosen the dir to clone it to it just disappears without a crash-message window. Version-Release number of selected component (if applicable): 0.7 How reproducible: More than once. Steps to Reproduce: 1. Login as root in a terminal-window. 2. Type urpmi giggle and then press Enter/Return/Execute-button. 3. Open Giggle. 4. Click on Project. 5. Click on Clone a repository. 6. Paste https://github.com/mer-hybris/droid-hal-device.git into the window. 7. Choose directory to clone the repository to. 8. Voila! It disappears. Reproducible: Steps to Reproduce:
CC: (none) => kristoffer.grundstrom1983
Severity: critical => major
Created attachment 5487 [details] Here's the backtrace from running Giggle with gdb
I haven't changed the standard Cinnamon theme in case anyone wonders. I'm also NOT using any Testing or Backport-medias.
Attachment 5487 mime type: application/octet-stream => text/plain
Created attachment 5692 [details] giggle backtrace Could be related to https://bugzilla.gnome.org/show_bug.cgi?id=701605 Reproduced here. Click Project -> Clone location -> select the dropdown box next to "Clone in folder" and click on Other... - e.g. to create a new folder. Giggle segfaults. Backtrace is attached.
CC: (none) => doktor5000
Assignee: bugsquad => juan.baptiste
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD