Description of problem: drakconnect Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/libDrakX/mygtk2.pm line 20. The program 'drakconnect' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow'. (Details: serial 8012 error_code 3 request_code 153 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Version-Release number of selected component (if applicable): libdrakx-net-1.4-1.mga2 How reproducible: always Steps to Reproduce: 1.drakconnect 2.click on next 3.crash
maybe you can get a better strace I don't know if it's still valid but we have some info in the triage guide: https://wiki.mageia.org/en/Triage_guide#Drakxtools_Crashes Setting to release_blocker.
Priority: Normal => release_blockerAssignee: bugsquad => mageiaSource RPM: drakx-net-text => drakx-net
Confirming the bug. But the triaging wiki seems not to wotk anymore: ----- [root@prokyon ~]# gdb -q --args perl /usr/bin/drakconnect Reading symbols from /usr/bin/perl...Reading symbols from /usr/lib/debug/usr/bin/perl5.14.2.debug...done. done. (gdb) run Starting program: /usr/bin/perl /usr/bin/drakconnect [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i686/libthread_db.so.1". Unrecognized character \x7F; marked by <-- HERE after <-- HERE near column 1 at /usr/bin/drakconnect line 1. [Inferior 1 (process 31479) exited with code 0377] (gdb) bt No stack. -----
CC: (none) => oliver.bgr
don't know if all bugs are related
CC: (none) => thierry.vignaudSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=4968
CC: (none) => jacques.pronchery
When not trying to use gdb, I get exactly the same error message as Jose reported.
Adding it to the tracker about not or badly working wifi
CC: (none) => marja11Blocks: (none) => 5015
In reply to bug 5005 Tested the new DVD ISO for Mageia 2 Beta 2 x86_64 ,and I have Several problems in the MCC : Mageia release 2 (Cauldron) for x86_64 Kernel 3.3.0-server-0.rc7.1.mga2 on a Dual-processor x86_64 / \l 1.When I want to Set up a new network interface ,I select Wired (Ethernet) and I click on Next , and there the MCC crash. # LC_ALL=C mcc [root@localhost ~]# "/usr/bin/drakmenustyle" is not executable [Menus] at /usr/sbin/drakconf.real line 820. "/usr/sbin/drakbackup" is not executable [Backups] at /usr/sbin/drakconf.real line 820. "/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 820. "/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/sbin/drakconf.real line 820. "/usr/sbin/drakguard" is not executable [Parental Controls] at /usr/sbin/drakconf.real line 820. The program 'drakconnect' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 31254 error_code 3 request_code 153 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 2.When I want to Set up the graphical server ,I choose an X server for my Graphic Card (NVIDIA Geforce 6100 to Geforce 360) and then I click on OK ,and there the same problem MCC crash. The program 'XFdrake' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow'. (Details: serial 65074 error_code 3 request_code 153 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3.When I want to Set up boot system ,I add a new entry and then I click on Finish ,and here again the MCC crash. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522. The program 'drakboot' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 60074 error_code 3 request_code 153 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
CC: (none) => geiger.david68210
oxygen-gtk has been reverted to 1.2.1 and fixes that crash
CC: (none) => ennael1
Tested for the update oxygen-gtk 1.2.1 and for me the problem was not solved ,always the same crash.
did you update both oxygen-gtk and lib ?
I had this bug, too, and for me "down"dating both files to 1.2.1 fixed it
Fixed, thanks.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Ok, really sorry because I did not see the need downgrade version of package oxygen-gtk 1.2.2 to version 1.2.1-3. I can confirm this downgrade fixed this bug. Thanks.
*** Bug 5005 has been marked as a duplicate of this bug. ***