Public bug reported:
The following stack trace is presented at least once, often multiple
times, when running arcanist.
ERROR 8192: implode(): Passing glue string after array is deprecated. Swap the
parameters at [/usr/share/libphutil/src/utils/utils.php:1572]
arcanist(), phutil()
#0
Public bug reported:
The pam_tally manpage says filed where it should say field.
** Affects: pam (Ubuntu)
Importance: Undecided
Status: New
** Affects: pam (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Patch added: pam_tally.patch
https://bugs.launchpad.net/bugs/772121/+attachment/2092327/+files/pam_tally.patch
** Also affects: pam (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On Fri, Jun 26, 2009 at 05:37:08PM -, Jonathan Marsden wrote:
| (1) bibledit-bin is explicitly not supposed to be run by hand. Its man
| page says it is an internal command used by bibledit.
I didn't realize that. It was the first command I found when I went
to run bibledit. This is good
You're right -- my situation is not a particularly good way to reproduce
the issue. It was simply what I was doing when I discovered the issue,
and I found this existing report.
As you discovered, the simplest steps are:
1) install bibledit 2.2-2.1
2) install bibledit-data 3.7
I found that SEGV using the 2.2-2.1 package in 9.04. It occurs first
when creating a new project. Then it occurs at every subsequent startup
until I delete ~/.bibledit.
Since that version is so outdated, I built your 3.7 package and don't
see that particular crash.
PS - greetings from ICCM
I just ran into this error.
The solution is to add
Conflicts: bibledit (3.7)
to the bibledit-data control file.
I installed the bibledit (2.2-2.1) package from the 9.04 repository.
Since it is old (and crashed), I then downloaded the source package from
9.10 and compiled it. That one
Public bug reported:
Binary package hint: bibledit
Bibledit will crash (SEGV) when creating a new project if it can't find
the stylesheets.
The partial stack trace is:
#0 0xb705c445 in std::string::assign () from /usr/lib/libstdc++.so.6
#1 0x080ae4b9 in ustring::operator=
** Attachment added: Preliminary patch identifying the problem and avoiding
the SEGV
http://launchpadlibrarian.net/27910128/stylesheetutils.patch
--
SEGV when stylesheet.xml can't be found
https://bugs.launchpad.net/bugs/387141
You received this bug notification because you are a member of
This is particularly braindead behavior:
* ssh automatically defaults to port 22, no need to specify it
* tomboy does not provide a means to specify what port to specify to sshfs
* tomboy does not provide any error information when the connection fails
* my ssh server does not
*** This bug is a duplicate of bug 219518 ***
https://bugs.launchpad.net/bugs/219518
No, this crash was not caused by mount flags on /tmp. It was caused by
removing execute permission from the gksu binary in /usr/bin. (I
removed that permission bit, not some part of the Ubuntu system) The
I saw this problem on my debian/testing system. I fixed my system
yesterday based on Steve Langasek's comment to this bug report.
Steve's analysis appears accurate for my account. I found the WebWizard
references in the old (very old) ~/.openoffice/1.0.1/ directory. The
same reference appears
12 matches
Mail list logo