I also have to mention that the larger the text file the longer the UI
locks up and drops characters which can be a very frustrating problem
for very large text files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've had the same problem since I first started using Gedit regularly. I
have the auto-save function set to every 1 minutes so the UI locking up
can be very irritating.
I've had this problem with Gedit on Ubuntu and Linux Mint. I've also had
this same problem with Xed, so, that implies that this
The corresponding version of Ubuntu also has this same bug.
Here's the launchpad link :
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1389682
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
1) The version and edition of Linux Mint you are using (if you are not
sure, open a terminal and run mintwelcome). :
uname -a :
Linux mint 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a :
No LSB modules are
Filed a bug report under the Linux Mint distribution as well. Also added
bug to package man-db
The lauchpad URL for the Linux Mint bug report is :
https://bugs.launchpad.net/linuxmint/+bug/1443604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same problem here :
man: command exited with status 127: /usr/bin/zsoelim | /usr/lib/man-db/manconv
-f UTF-8:ISO-8859-1 -t ANSI_X3.4-1968//IGNORE | tbl | nroff -mandoc -Tascii |
iconv -c -f ANSI_X3.4-1968 -t UTF-8//TRANSLIT | gzip -c7
catman: man command failed with exit status 3
--
You
similar to the above after
pressing the record button :
jdb2@aleph1 ~/screencap $ xvidcap --fps 3/1001 --sf --auto --file
cap%0.9.ppm --gui yes --window 0x580006c
The program 'xvidcap' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid
** Attachment added: GDB core dump of xvidcap after breaking on
'gdk_x_error()'
https://bugs.launchpad.net/ubuntu/+source/xvidcap/+bug/708332/+attachment/2148811/+files/xvidcap.core.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looks like in this particular case, unlike the previous one involving
the embedded video, xvidcap is crashing because I did not select an area
to be captured.
Here's more extensive debugging information for what it's worth. Note
that I've compiled xvidcap from the source package and run GDB
** Attachment added: GDB core dump of xvidcap debug build after breaking on
'gdk_x_error()'
https://bugs.launchpad.net/ubuntu/+source/xvidcap/+bug/708332/+attachment/2149400/+files/xvidcap_debugbuild.core.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Comment #6 has the wrong text file attached. Here is the correct one.
** Attachment added: gdb-xvidcap_debugbuild.txt
https://bugs.launchpad.net/ubuntu/+source/xvidcap/+bug/708332/+attachment/2149901/+files/gdb-xvidcap_debugbuild.txt
--
You received this bug notification because you are a
you
have attempted to install ) :
jdb2@aleph0:~/tmp/nspluginwrapper-1.2.2$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libjna-java
Public bug reported:
Binary package hint: nspluginwrapper
Attempting a sudo apt-get -f on my system results in the following :
jdb2@aleph0:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were
** Attachment added: GDB debugging output of 'gdb /usr/bin/nspluginwrapper
21 | tee gdb-nspluginwrapper.txt'
https://bugs.launchpad.net/bugs/780678/+attachment/2123119/+files/gdb-nspluginwrapper.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Output of 'catchsegv nspluginwrapper -a -v -u 21
catchsegv-nspluginwrapper.txt'
https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/780678/+attachment/2123121/+files/catchsegv-nspluginwrapper.txt
--
You received this bug notification because you are a member
Public bug reported:
Binary package hint: xvidcap
When trying to record video from a Firefox window which contains an
embedded flash video Xvidcap fails after the Start recording button is
clicked with this error :
The program 'xvidcap' received an X Window System error.
This probably reflects
I forgot to mention the command I used :
xvidcap --fps 3/1001 --audio yes --window 0x665 -v --file
duke.avi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708332
Title:
Xvidcap exits with
** Attachment added: Xvidcap GDB debugging output
https://bugs.launchpad.net/bugs/708332/+attachment/1809251/+files/gdb-xvidcap.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708332
Title:
** Tags added: avi
** Tags removed: mpeg2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708332
Title:
Xvidcap exits with BadMatch error
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've verified that gtk-recordmydesktop works on the above mentioned web
page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708332
Title:
Xvidcap exits with BadMatch error
--
ubuntu-bugs mailing
Similar problem on my Toshiba Satellite T215D-S1150. See my bug report :
https://bugs.launchpad.net/linuxmint/+bug/676740
Unfortunately ubuntu-bug/apport-bug wouldn't let me file a report based
off of the libasound2 package because it wasn't a genuine Linux mint
package.
--
Microphone does not
I don't think so, but I'm running Firefox 3.6.2 from the Ubuntu Mozilla
Daily repo. The above bug was apparently a regression introduced by the
UMD developers ( I was then running 3.5 ) and was subsequently fixed.
The reason it still showed up when I had uninstalled the UMD Firefox 3.5
packages
I can confirm that this bug affects Amarok :
j...@jdb2-kubuntu-temp:~$ gdb amarok
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute
which resulted in a crash. ( ie. System
Settings killed itself )
Upon further inspection with GDB I received this output :
j...@jdb2-kubuntu-temp:~$ gdb systemsettings
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http
functionality broken? ( other distros, such as Knoppix, have no problems
)
Also, why isn't the activated array detected by the device notifier in
KDE 4.3.2? -- On my machine it has to be manually mounted. ( after
having to manually issue dmraid -ay )
jdb2
--
Jaunty not Booting with dmraid Active
*** This bug is a duplicate of bug 376792 ***
https://bugs.launchpad.net/bugs/376792
BTW, I'm running the 1.0.0.rc15-6ubuntu2 version of dmraid .
jdb2
--
Jaunty not Booting with dmraid Active
https://bugs.launchpad.net/bugs/381514
You received this bug notification because you are a member
Yes, it's from a PPA, but the PPA in question is maintained by the
Ubuntu Mozilla Daily Build Team which consists of two of the top
maintainers from the Ubuntu Mozilla Team and which, if I'm not mistaken,
are the people who package the daily builds from the Ubuntu Mozilla Team
:
As a test, I disabled the Ubuntu-Mozilla-Daily PPA, uninstalled all
versions of Firefox, and then installed the official Firefox-3.5
package for Ubuntu. Attempting to launch Firefox-3.5 results in the same
behavior as described above and running it from a terminal results in
the same 'bus error'
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/30904163/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30904164/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/30904165/Disassembly.txt
** Attachment
I just realized that the Ubuntu-Mozilla-Daily pre-release version of
xulrunner-1.9.1 was still installed. After removing it and re-installing
Firefox-3.5 everything seems to work fine. Sorry for any confusion.
So, this is apparently a problem with the pre-release version of
xulrunner-1.9.1
The above behavior was apparently caused by my failure to remove the
Ubuntu-Mozilla-Daily pre-release version of xulrunner-1.9.1 before I
installed the official Firefox-3.5 package.
See bug #419980 for details :
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/419980 .
--
Firefox
-a' :
'
Linux jdb2-Kubuntu-temp 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08
UTC 2009 i686 GNU/Linux
'
'lsb_release -a' :
'
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:cxx-3.0
** Attachment added: gdb-firefox.txt
http://launchpadlibrarian.net/30876674/gdb-firefox.txt
--
Firefox 3.5.4pre dies with bus error
https://bugs.launchpad.net/bugs/419566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've also generated debugging information from an Apport crash/core dump
after having issuing the following commands :
'
sudo force_start=1 /etc/init.d/apport restart
firefox
TMPDIR=$(mktemp -d)
apport-unpack /var/crash/_usr_lib_firefox-3.5.4pre_firefox.1000.crash
$TMPDIR
gdb -nx
I just realized that I had overlooked the './libxul.so' line in debug.log which
means that this build is *not* being compiled/linked against my system libs, or
at least libxul, so the output saved in the attachments may be or probably is
invalid. ( possibly related to this bug :
** Attachment added: The output of issuing 'thread apply all backtrace full'
after the previous command in GDB
http://launchpadlibrarian.net/28378709/thread-apply-all-backtrace-full.log
--
Buffer overflow associated with libxul in latest Firefox-3.0 package on Kubuntu
9.04/Jaunty --
** Attachment added: The output of executing './firefox --debug' and issuing
'run' followed by 'bt full' in GDB
http://launchpadlibrarian.net/28378597/bt-full.log
--
Buffer overflow associated with libxul in latest Firefox-3.0 package on Kubuntu
9.04/Jaunty -- Couldn't load XRE functions.
** Attachment added: The STDOUT/STDERR output of './firefox'
http://launchpadlibrarian.net/28378569/debug.log
--
Buffer overflow associated with libxul in latest Firefox-3.0 package on Kubuntu
9.04/Jaunty -- Couldn't load XRE functions.
https://bugs.launchpad.net/bugs/392268
You received
which then
disappears. Repeated attempts to launch Firefox always results in Plasma
crashing. Attempting to run it from the console produces Couldn't load
XRE functions. and attempting to run GDB with the '--debug' option
produces the following output or similar :
'
j...@jdb2-kubuntu-temp
I can confirm the exact same behavior with Firefox 3.0.11 (
firefox-3.0_3.0.11+build2+nobinonly ) in Kubuntu 9.04/Jaunty .
--
firefox source does not compile on first try
https://bugs.launchpad.net/bugs/385461
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I use Kubuntu and when I upgraded from Hardy to Jaunty the upgrade
script installed the latest Jaunty package for Psi , specifically 0.12 .
I noticed strange behavior as well as lockups when trying to enter text
into a chat window which basically rendered Psi useless.
The solution : Build Psi
I compiled kdebluetooth ( which includes kbluemon ) from the latest svn
snapshot, with all the debugging symbols enabled.
Here's the crash backtrace :
[Thread debugging using libthread_db enabled]
[New Thread 0xb675c6c0 (LWP 26800)]
[KCrash handler]
#6 0x08054c2d in QValueVectorQString::detach
drive : HL-DT-ST CD-RW GCE-8481B
1 DVD-ROM drive : PIONEER DVD-ROM DVD-120
1 floppy drive
Operating System Information :
OS : Kubuntu 8.04 Linux
Kernel : ( uname -a ) Linux jdb2-Kubuntu-temp 2.6.24-21-generic #1 SMP
Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux
lsb_release -rd output
** Attachment added: lspci-vvnn.log.tar.bz2
http://launchpadlibrarian.net/18578236/lspci-vvnn.log.tar.bz2
--
KBlueMon crashes when scanning with service discovery enabled
https://bugs.launchpad.net/bugs/173154
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: lsusb-v.log.tar.bz2
http://launchpadlibrarian.net/18578251/lsusb-v.log.tar.bz2
--
KBlueMon crashes when scanning with service discovery enabled
https://bugs.launchpad.net/bugs/173154
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: uname-a.log.tar.bz2
http://launchpadlibrarian.net/18578261/uname-a.log.tar.bz2
--
KBlueMon crashes when scanning with service discovery enabled
https://bugs.launchpad.net/bugs/173154
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: version.log.tar.bz2
http://launchpadlibrarian.net/18578266/version.log.tar.bz2
--
KBlueMon crashes when scanning with service discovery enabled
https://bugs.launchpad.net/bugs/173154
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Forgot to mention the device being scanned : a Samsung Blackjack II cell
phone.
--
KBlueMon crashes when scanning with service discovery enabled
https://bugs.launchpad.net/bugs/173154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Another note: Similar behavior manifests itself if one clicks on
Hibernate in the shutdown menu. The differences are that the system
turns itself off instead of locking up. Also, upon restoration of the
MBR and subsequent booting of the OS, Kubuntu locks up in the boot-up
progress bar screen upon
One thing I forgot to mention : Note that all the ACPI states supported
by my hardware ( disk, standby, mem ) *work perfectly* under Knoppix
V5.3.1 .
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard and with
the OS installed on an externel USB hard drive results in
** Attachment added: dmesg.log
http://launchpadlibrarian.net/17543424/dmesg.log
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard and with
the OS installed on an externel USB hard drive results in system lock-up and
subsequent failure to boot from external USB hard
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/17543437/lspci-vvnn.log
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard and with
the OS installed on an externel USB hard drive results in system lock-up and
subsequent failure to boot from external
** Attachment added: version.log
http://launchpadlibrarian.net/17543445/version.log
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard and with
the OS installed on an externel USB hard drive results in system lock-up and
subsequent failure to boot from external USB
Kernel : ( uname -a ) jdb2-Kubuntu-temp 2.6.24-19-generic #1 SMP Wed Aug
20 22:56:21 UTC 2008 i686 GNU/Linux
lsb_release -rd output :
Description:Ubuntu 8.04.1
Release:8.04
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard
operating system information follows :
OS : Kubuntu 8.04 Linux
Kernel : ( uname -a ) jdb2-Kubuntu-temp 2.6.24-19-generic #1 SMP Wed Aug
20 22:56:21 UTC 2008 i686 GNU/Linux
lsb_release -rd output :
Description:Ubuntu 8.04.1
Release:8.04
** Affects: linux (Ubuntu
** Attachment added: uname-a.log
http://launchpadlibrarian.net/17543441/uname-a.log
--
Attempting to enter standby in Kubuntu 8.04 on an nforce2 motherboard and with
the OS installed on an externel USB hard drive results in system lock-up and
subsequent failure to boot from external USB
56 matches
Mail list logo
