Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20774 - [tora] segfault
Attached to Project:
Community Packages
Opened by Diederick de Vries (diederick76) - Wednesday, 08 September 2010, 12:10 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 16 December 2010, 16:12 GMT
Opened by Diederick de Vries (diederick76) - Wednesday, 08 September 2010, 12:10 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 16 December 2010, 16:12 GMT
|
DetailsDescription:
Tora segfaults when I open a new connection to a MySQL database. Additional info: * package version: 2.1.2 * stdout: TOra(5381)/ KSharedDataCache::Private::mapSharedMemory: Opening cache "/var/tmp/kdecache-diederick/icon-cache.kcache" page size is 4096 TOra(5381)/ KSharedDataCache::Private::mapSharedMemory: Attached to cache, determining if it must be initialized TOra(5381)/ KSharedDataCache::Private::mapSharedMemory: Cache fully initialized -- attached to memory mapping TOra(5381)/ KSharedDataCache::Private::mapSharedMemory: 4583424 bytes available out of 10485760 TOra(5381)/ KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-diederick/ksycoca4" Segmentation fault Steps to reproduce: - Start tora and MySql. - In the New Connection dialog, select Connection provider: MySQL, enter Username, Password, Host, Port. Optionally enter Database name and deselect pre-selected checkboxes SSL and Compress. - Click OK. |
This task depends upon
Closed by Angel Velasquez (angvp)
Thursday, 16 December 2010, 16:12 GMT
Reason for closing: No response
Additional comments about closing: Re-open in case still failing this
Thursday, 16 December 2010, 16:12 GMT
Reason for closing: No response
Additional comments about closing: Re-open in case still failing this
Are you using i686 or x86_64