| Summary: | New svn revision of skype4pidgin (r699) Requires QA. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Shlomi Fish <shlomif> |
| Component: | RPM Packages | Assignee: | Shlomi Fish <shlomif> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | herman.viaene, qa-bugs |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | NEEDHELP | ||
| Source RPM: | skype4pidgin-0.0-4.svn699.1.mga4.nonfree.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | 14941 | ||
| Bug Blocks: | |||
|
Description
Shlomi Fish
2015-01-21 12:51:56 CET
Suggested advisory: ======================== Updated skype4pidgin packages fix crashes in pidgin when skype4pidgin is installed. A crash in Pidgin was reported in MGA Bug #14941 which is fixed after skype4pidgin is updated to the latest svn revision. References: https://bugs.mageia.org/show_bug.cgi?id=14941 ======================== Updated packages in nonfree/updates_testing: ======================== skype4pidgin-0.0-4.svn699.1.mga4.nonfree Source RPMs: skype4pidgin-0.0-4.svn699.1.mga4.nonfree.src.rpm Oops. This was previously reported here but closed at mga2 EOL. https://bugs.mageia.org/show_bug.cgi?id=8912 sorry wrong bug :\ MGA-64 on HP Probook 6555b No installation issues. I can start pidgin with my AIM account, and open skype with my skype account. CC:
(none) =>
herman.viaene MGA4-32 on Acer D620 No installation issues. I can start pidgin, and connect to skype, but thereafter pidgin bombs out. Repeating the test always has the same result, pidgin starts, the skype connection is made and then pidgin crashes. At the CLI: pidgin Gtk-Message: Failed to load module "canberra-gtk-module" [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pidgin: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted [tester4@mach6 ~]$ pidgin Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Pidgin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. The first line also appears in MGA4-64 (and for a lot of applications), but the rest is typical for my 32-bit installation. (In reply to Herman Viaene from comment #6) > MGA4-32 on Acer D620 > No installation issues. > I can start pidgin, and connect to skype, but thereafter pidgin bombs out. > Repeating the test always has the same result, pidgin starts, the skype > connection is made and then pidgin crashes. > At the CLI: > pidgin > Gtk-Message: Failed to load module "canberra-gtk-module" > [xcb] Unknown sequence number while processing queue > [xcb] Most likely this is a multi-threaded client and XInitThreads has not > been called > [xcb] Aborting, sorry about that. > pidgin: xcb_io.c:274: poll_for_event: Assertion > `!xcb_xlib_threads_sequence_lost' failed. > Aborted > [tester4@mach6 ~]$ pidgin > Gtk-Message: Failed to load module "canberra-gtk-module" > Gtk-Message: Failed to load module "canberra-gtk-module" > Pidgin: Fatal IO error 11 (Resource temporarily unavailable) on X server > :0.0. > > The first line also appears in MGA4-64 (and for a lot of applications), but > the rest is typical for my 32-bit installation. No idea about that. Are you sure you installed skype4pidgin from nonfree/updates_testing ? What does rpm -q skype4pidgin say? Regards, -- Shlomi Fish rpm -q skype4pidgin skype4pidgin-0.0-4.svn699.1.mga4.nonfree Adding feedback marker for now Shlomi Whiteboard:
MGA4-64-OK =>
feedback MGA4-64-OK Assigning back to Shlomi. CC:
(none) =>
qa-bugs
claire robinson
2015-02-27 18:09:04 CET
Depends on:
(none) =>
14941
Shlomi Fish
2015-03-05 07:22:18 CET
Whiteboard:
(none) =>
NEEDHELP
Shlomi Fish
2015-03-21 09:19:04 CET
Status:
NEW =>
ASSIGNED 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/ RESOLVED as OLD, because the new version exists in Mageia 5. Status:
ASSIGNED =>
RESOLVED |