Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Package: mysql-query-browser Version: 1.2.5beta-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (101, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_ES.UTF-8) Versions of packages mysql-query-browser depends on: ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-01.12.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.14.0-2 Bonobo CORBA interfaces library ii libbonoboui2-0 2.14.0-4 The Bonobo UI library ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.1-2 generic font configuration library ii libgcc11:4.1.1-13GCC support library ii libgconf2-42.16.0-2 GNOME configuration database syste ii libglade2-01:2.6.0-2 library to load .glade files at ru ii libglib2.0-0 2.12.4-1 The GLib library of C routines ii libglibmm-2.4-1c2a 2.12.0-1 C++ wrapper for the GLib toolkit ( ii libgnome-keyring0 0.6.0-2 GNOME keyring services library ii libgnome2-02.16.0-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-2 A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-6 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2+b1 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-2+b1 GNOME virtual file-system (runtime ii libgtk2.0-02.8.20-3 The GTK+ graphical user interface ii libgtkhtml3.8-15 3.12.1-2 HTML rendering/editing library - r ii libgtkmm-2.4-1c2a 1:2.8.8-1 C++ wrappers for GTK+ 2.4 (shared ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libmysqlclient15off5.0.24a-9 mysql database client library ii liborbit2 1:2.14.3-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.14.7-1 Layout and rendering of internatio ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libpopt0 1.10-3lib for parsing cmdline parameters ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-13 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-2 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-4 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-3 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxml22.6.27.dfsg-1 GNOME XML library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii mysql-query-browser-common 1.2.5beta-1 Architecture independent files for ii zlib1g 1:1.2.3-13compression library - runtime mysql-query-browser recommends no packages. -- no debconf information Hi, I'm getting segfaults trying to connect to a remote server. The backtrace is below. Best Regards, manolo -- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1082132832 (LWP 26219)] 0x006071c9 in myx_use_schema () (gdb) bt #0 0x006071c9 in myx_use_schema () Cannot access memory at address 0x8 (gdb) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Hi, Just uploaded -2 version. Please check that one. The -1 had a 32-bit library and mixing 32-bit and 64-bit doesn't work so well. - Adam > Hi, > I'm getting segfaults trying to connect to a remote server. The > backtrace is below. > > Best Regards, > manolo > > -- > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 1082132832 (LWP 26219)] > 0x006071c9 in myx_use_schema () > (gdb) bt > #0 0x006071c9 in myx_use_schema () > Cannot access memory at address 0x8 > (gdb) > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Adam Majer wrote: Hi, Just uploaded -2 version. Please check that one. The -1 had a 32-bit library and mixing 32-bit and 64-bit doesn't work so well. - Adam Hi, Adam Tested 1.2.5beta-2. Just the same. Regards, Manolo Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1082132832 (LWP 23266)] 0x006094f9 in myx_use_schema () (gdb) bt #0 0x006094f9 in myx_use_schema () Cannot access memory at address 0x8 (gdb) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Steve Langasek wrote: > severity 397279 grave > thanks > >> PS. Merging with the important bug. FYI, not RC because >> mysql-query-browser never worked on AMD64... > > That's not an appropriate rationale for downgrading. If the package is > unusable on amd64, the package needs to be fixed so that it doesn't get > *built* on amd64, and the broken binaries removed from the archive. So what about other architectures?? Should I guess that it will not run on ia64 or the s390? Or is it ok to have potentially broken binaries until someone complains? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
On Tue, Nov 07, 2006 at 07:46:36PM -0600, Adam Majer wrote: > >> PS. Merging with the important bug. FYI, not RC because > >> mysql-query-browser never worked on AMD64... > > That's not an appropriate rationale for downgrading. If the package is > > unusable on amd64, the package needs to be fixed so that it doesn't get > > *built* on amd64, and the broken binaries removed from the archive. > So what about other architectures?? Should I guess that it will not run > on ia64 or the s390? Or is it ok to have potentially broken binaries > until someone complains? Ideally, broken packages would be detected at build time. Otherwise, in the absence of feedback telling us that the package is broken, we shouldn't assume that it's broken either. But a known-unusable binary package needs to be addressed for the release. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Steve Langasek wrote: >> So what about other architectures?? Should I guess that it will not run >> on ia64 or the s390? Or is it ok to have potentially broken binaries >> until someone complains? > > Ideally, broken packages would be detected at build time. Otherwise, in the > absence of feedback telling us that the package is broken, we shouldn't > assume that it's broken either. But a known-unusable binary package needs > to be addressed for the release. Ideally, it would have been better to know this a few months ago. What would be even better if we could tag RC bugs against specific architectures so a package that eventually will work on all but doesn't yet could be 1. built in Sid by all arch ALL the time, for testing, etc... 2. a given binary doesn't progress to testing because due to RC bug against that package's architecture. So if there is a potential fix for the problem, the package is built and people can easily check if the program now works on the broken arch. As it is right now, packages have to be built by hand on the broken arch which can be a hustle for people that don't want to install all of the dev packages just to test if a binary runs and report bugs (ie. the non-developers) - Adam PS. Please don't remove this package from testing even though AMD is broken there. I'll try to get either the fix or exclude amd64 from build architectures... I guess I could use a relative's amd64 to see what the problem is and if mysql-admin (another package with some shared connection code) even works. And that one may be affected as well even though upstream says otherwise. I think they may be using 32-bit app on Amd64 32bit/64-bit like Suse and stating it works blah... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397279: mysql-query-browser: crashes when connecting to a remote server
severity 397279 important thanks On Tue, Nov 07, 2006 at 11:46:37PM -0600, Adam Majer wrote: > PS. Please don't remove this package from testing even though AMD is > broken there. I'll try to get either the fix or exclude amd64 from build > architectures... I've just tested the package on my amd64, and it works fine connecting to a remote server. That /is/ an appropriate reason to downgrade the bug, so doing so now. > I guess I could use a relative's amd64 to see what the problem is and if > mysql-admin (another package with some shared connection code) even works. Debian has an amd64 porter system for this reason. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Processing commands for [EMAIL PROTECTED]: > severity 397279 important Bug#397279: mysql-query-browser: crashes when connecting to a remote server Severity set to `important' from `grave' > forwarded 316285 http://bugs.mysql.com/24045 Bug#316285: mysql-query-browser: segfaults on 64bit arches due to unclean 64bit code Forwarded-to-address changed from http://bugs.mysql.com/11751 to http://bugs.mysql.com/24045. > forwarded 397279 http://bugs.mysql.com/24045 Bug#397279: mysql-query-browser: crashes when connecting to a remote server Noted your statement that Bug has been forwarded to http://bugs.mysql.com/24045. > merge 316285 397279 Bug#316285: mysql-query-browser: segfaults on 64bit arches due to unclean 64bit code Bug#397279: mysql-query-browser: crashes when connecting to a remote server Merged 316285 397279. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#397279: mysql-query-browser: crashes when connecting to a remote server
Processing commands for [EMAIL PROTECTED]: > severity 397279 important Bug#397279: mysql-query-browser: crashes when connecting to a remote server Bug#316285: mysql-query-browser: segfaults on 64bit arches due to unclean 64bit code Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
