Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Olivier Ripoll]

On 20.05.2012 11:14, Rashif Ray Rahman wrote:


So, I finally managed to track down a peculiarity.

On Windows (7), there is no scrolling issue with the keyboard, or the
mouse scroll wheel (or touchpad vertical scroll). However, there is
lag if I use the scroll bar (by dragging with the mouse).

[...]

Hi,

That looks a lot like what I'm seeing since 2.0.2.

www.lyx.org/trac/ticket/8135

Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by 
dragging the scrollbar is working with it ?


Thanks,

Olivier

LyX SEGSEGV crash just after GUI window appears

[Craig]

I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
then it dies.  The strange part is that I can run LyX successfully if I run it 
as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I would 
appreciate any suggestions from the LyX experts about how to diagnose the 
problem.  LyX info and the backtrace are posted below.  If you think it is a 
Gentoo packaging issue, please tell me as much as you can so that I can post a 
good bug report.


LyX info:
LyX 2.0.3 (2012-02-19)
Built on May 21 2012, 11:50:43
Configuration
  Host type:    x86_64-pc-linux-gnu
  Special build flags:  build=release use-hunspell
  C   Compiler: x86_64-pc-linux-gnu-gcc 
  C   Compiler LyX flags:    
  C   Compiler flags:    -O2 -pipe -march=native -msse4
  C++ Compiler: x86_64-pc-linux-gnu-g++ (4.5.3)
  C++ Compiler LyX flags:    
  C++ Compiler flags:    -O2 -pipe -march=native -msse4
  Linker flags: 
  Linker user flags:    -Wl,-O1 -Wl,--as-needed
  Qt 4 Frontend:
  Qt 4 version:        4.8.1
  Packaging:    posix
  LyX binary dir:   /usr/bin
  LyX files dir:    /usr/share/lyx


Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00a397ea in ?? ()
(gdb) backtrace
#0  0x00a397ea in ?? ()
#1  0x00a3a813 in ?? ()
#2  0x00a3af06 in ?? ()
#3  0x00a0a34d in ?? ()
#4  0x0081a526 in ?? ()
#5  0x76a04c5f in ?? () from /usr/lib64/qt4/libQtGui.so.4
#6  0x76a04f29 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#7  0x7498330e in _SmcProcessMessage () from /usr/lib64/libSM.so.6
#8  0x747731f3 in IceProcessMessages () from /usr/lib64/libICE.so.6
#9  0x764673fa in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x764b374e in QSocketNotifier::activated(int) ()
   from /usr/lib64/qt4/libQtCore.so.4
#11 0x7646f29b in QSocketNotifier::event(QEvent*) ()
   from /usr/lib64/qt4/libQtCore.so.4
#12 0x769843a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtGui.so.4
#13 0x76988fef in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/qt4/libQtGui.so.4
#14 0x0081a108 in ?? ()
#15 0x76451b1c in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtCore.so.4
#16 0x76480789 in ?? () from /usr/lib64/qt4/libQtCore.so.4
---Type return to continue, or q return to quit---
#17 0x7509c87f in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#18 0x7509d088 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x7509d261 in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#20 0x76480e2f in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib64/qt4/libQtCore.so.4
#21 0x76a295fe in ?? () from /usr/lib64/qt4/libQtGui.so.4
#22 0x76450b42 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib64/qt4/libQtCore.so.4
#23 0x76450dfd in 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib64/qt4/libQtCore.so.4
#24 0x764555ab in QCoreApplication::exec() ()
   from /usr/lib64/qt4/libQtCore.so.4
#25 0x0052e3e6 in ?? ()
#26 0x00441b6a in ?? ()
#27 0x757c12ad in __libc_start_main () from /lib64/libc.so.6
#28 0x00441a69 in ?? ()
#29 0x7fffdea8 in ?? ()
#30 0x001c in ?? ()
#31 0x0001 in ?? ()
#32 0x7fffe1db in ?? ()
#33 0x in ?? ()

Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Ray Rashif]

On 22 May 2012 23:13, Olivier Ripoll durocortorum73-gm...@yahoo.fr wrote:
 On 20.05.2012 11:14, Rashif Ray Rahman wrote:

 So, I finally managed to track down a peculiarity.

 On Windows (7), there is no scrolling issue with the keyboard, or the
 mouse scroll wheel (or touchpad vertical scroll). However, there is
 lag if I use the scroll bar (by dragging with the mouse).

 [...]

 Hi,

 That looks a lot like what I'm seeing since 2.0.2.

 www.lyx.org/trac/ticket/8135

 Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by
 dragging the scrollbar is working with it ?

I had noticed that bug report before, and I tried my luck on Linux by
installing 2.0.1, but it did not help. I will try it on Windows,
although it does appear to me as if the only problem in Windows is
that of scrolling with the scrollbar. Nothing else is a problem there.


--
GPG/PGP ID: C0711BF1

Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

[John Kane]

Thanks again and thanks for the extra information.  Sorry to take so long to 
reply but I'm on a cycle tour and only the rain has driven me into a library to 
check mail.




- Original Message -
From: stefano franchi stefano.fran...@gmail.com
To: Scott Kostyshak skost...@princeton.edu
Cc: John Kane jrkrid...@yahoo.ca; lyx-users@lists.lyx.org 
lyx-users@lists.lyx.org
Sent: Tuesday, May 15, 2012 5:24:16 PM
Subject: Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

On Tue, May 15, 2012 at 1:47 PM, Scott Kostyshak skost...@princeton.edu wrote:
 From: John Kane [jrkrid...@yahoo.ca]
 Sent: Tuesday, May 15, 2012 12:28 PM

 Glad you got things working.

I then put
export
PATH=/usr/local/texlive/2011/bin/i386-linux:$PATH
in my .profile and
restarted the terminal

 For the future and in case you are curious: .profile is executed when you log 
 in, not on each opening of a terminal. .bashrc is run on each new terminal 
 instance. This is why a reboot fixed it for you.


Well said. In general, it's  s good idea to run

$source .profile

or

$source .bashrc

etc., whenever you modify one of those environment-altering files.
That way you can test your changes immediately without having to
restart the terminal or rebooting the machine. Other things may happen
when you do that, and I'd like to keep variables to a minimum when
setting things up. After a while it becomes a habit, like running
mktexlsr after manually installing a tex package.


Cheers,

Stefano







 Scott



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
 as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
 then it dies.  The strange part is that I can run LyX successfully if I run 
 it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
 would appreciate any suggestions from the LyX experts about how to diagnose 
 the problem.  LyX info and the backtrace are posted below.  If you think it 
 is a Gentoo packaging issue, please tell me as much as you can so that I can 
 post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

Removing ~/.lyx does not change anything.  It still crashes right away (note 
that the window, buttons, etc are fully drawn and the file examples/splash.lyx 
gets loaded before the SIGSEGV dialog box appears).




 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:33 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
 as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
 then it dies.  The strange part is that I can run LyX successfully if I run 
 it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
 would appreciate any suggestions from the LyX experts about how to diagnose 
 the problem.  LyX info and the backtrace are posted below.  If you think it 
 is a Gentoo packaging issue, please tell me as much as you can so that I can 
 post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 Removing ~/.lyx does not change anything.  It still crashes right away (note 
 that the window, buttons, etc are fully drawn and the file 
 examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[William Seager]

On Monday 21 May 2012 10:23:01 Craig wrote:
 The strange part is that I can run LyX successfully if I run it as root. 

That must be a big clue - can you create a brand new user
and see if lyx runs for the new user?

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

I can build LyX with the debug flag, but that will take a little while. In the 
meantime, here is another clue.  When I run the lyx command in a terminal, it 
dumps a lot of text to the terminal when crashing.  First, I get this repeated 
many times:


GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead

Then I get:


Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
When converting from UCS-4LE to UTF-8.
Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 0x0 
0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 
...

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.


It dumps about 20MB of those hex codes to the terminal.  When I run LyX as root 
or do sudo lyx I don't get any errors or warning messages.




 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:50 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 Removing ~/.lyx does not change anything.  It still crashes right away (note 
 that the window, buttons, etc are fully drawn and the file 
 examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 Then I get:
 
 
 Error returned from iconv
 EILSEQ An invalid multibyte sequence has been encountered in the input.
 When converting from UCS-4LE to UTF-8.
 Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running lyx -dbg any and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

lyx -dbg any  a.txt

...

GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead
Menus.cpp(2012): populating menu bar
Menus.cpp(2019): menu bar entries 8
Menus.cpp(2038): menu bar item File is a submenu named file
Menus.cpp(2038): menu bar item Edit is a submenu named edit
Menus.cpp(2038): menu bar item View is a submenu named view
Menus.cpp(2038): menu bar item Insert is a submenu named insert
Menus.cpp(2038): menu bar item Navigate is a submenu named navigate
Menus.cpp(2038): menu bar item Document is a submenu named document
Menus.cpp(2038): menu bar item Tools is a submenu named tools
Menus.cpp(2038): menu bar item Help is a submenu named help
GuiView.cpp(798): Passed Geometry 510x690+50+50
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiApplication.cpp(1055): dispatch msg is
Error: Software exception Detected

LyX has caught an exception, it will now attempt to save all unsaved documents  
and exit.

Exception: std::bad_alloc
GuiSelection.cpp(91): GuiSelection::on_dataChanged
GuiSelection.cpp(91): GuiSelection::on_dataChanged



 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 5:19 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 Then I get:
 
 
 Error returned from iconv
 EILSEQ An invalid multibyte sequence has been encountered in the input.
 When converting from UCS-4LE to UTF-8.
 Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running lyx -dbg any and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel

Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Olivier Ripoll]

On 20.05.2012 11:14, Rashif Ray Rahman wrote:


So, I finally managed to track down a peculiarity.

On Windows (7), there is no scrolling issue with the keyboard, or the
mouse scroll wheel (or touchpad vertical scroll). However, there is
lag if I use the scroll bar (by dragging with the mouse).

[...]

Hi,

That looks a lot like what I'm seeing since 2.0.2.

www.lyx.org/trac/ticket/8135

Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by 
dragging the scrollbar is working with it ?


Thanks,

Olivier

LyX SEGSEGV crash just after GUI window appears

[Craig]

I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
then it dies.  The strange part is that I can run LyX successfully if I run it 
as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I would 
appreciate any suggestions from the LyX experts about how to diagnose the 
problem.  LyX info and the backtrace are posted below.  If you think it is a 
Gentoo packaging issue, please tell me as much as you can so that I can post a 
good bug report.


LyX info:
LyX 2.0.3 (2012-02-19)
Built on May 21 2012, 11:50:43
Configuration
  Host type:    x86_64-pc-linux-gnu
  Special build flags:  build=release use-hunspell
  C   Compiler: x86_64-pc-linux-gnu-gcc 
  C   Compiler LyX flags:    
  C   Compiler flags:    -O2 -pipe -march=native -msse4
  C++ Compiler: x86_64-pc-linux-gnu-g++ (4.5.3)
  C++ Compiler LyX flags:    
  C++ Compiler flags:    -O2 -pipe -march=native -msse4
  Linker flags: 
  Linker user flags:    -Wl,-O1 -Wl,--as-needed
  Qt 4 Frontend:
  Qt 4 version:        4.8.1
  Packaging:    posix
  LyX binary dir:   /usr/bin
  LyX files dir:    /usr/share/lyx


Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00a397ea in ?? ()
(gdb) backtrace
#0  0x00a397ea in ?? ()
#1  0x00a3a813 in ?? ()
#2  0x00a3af06 in ?? ()
#3  0x00a0a34d in ?? ()
#4  0x0081a526 in ?? ()
#5  0x76a04c5f in ?? () from /usr/lib64/qt4/libQtGui.so.4
#6  0x76a04f29 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#7  0x7498330e in _SmcProcessMessage () from /usr/lib64/libSM.so.6
#8  0x747731f3 in IceProcessMessages () from /usr/lib64/libICE.so.6
#9  0x764673fa in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x764b374e in QSocketNotifier::activated(int) ()
   from /usr/lib64/qt4/libQtCore.so.4
#11 0x7646f29b in QSocketNotifier::event(QEvent*) ()
   from /usr/lib64/qt4/libQtCore.so.4
#12 0x769843a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtGui.so.4
#13 0x76988fef in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/qt4/libQtGui.so.4
#14 0x0081a108 in ?? ()
#15 0x76451b1c in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtCore.so.4
#16 0x76480789 in ?? () from /usr/lib64/qt4/libQtCore.so.4
---Type return to continue, or q return to quit---
#17 0x7509c87f in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#18 0x7509d088 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x7509d261 in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#20 0x76480e2f in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib64/qt4/libQtCore.so.4
#21 0x76a295fe in ?? () from /usr/lib64/qt4/libQtGui.so.4
#22 0x76450b42 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib64/qt4/libQtCore.so.4
#23 0x76450dfd in 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib64/qt4/libQtCore.so.4
#24 0x764555ab in QCoreApplication::exec() ()
   from /usr/lib64/qt4/libQtCore.so.4
#25 0x0052e3e6 in ?? ()
#26 0x00441b6a in ?? ()
#27 0x757c12ad in __libc_start_main () from /lib64/libc.so.6
#28 0x00441a69 in ?? ()
#29 0x7fffdea8 in ?? ()
#30 0x001c in ?? ()
#31 0x0001 in ?? ()
#32 0x7fffe1db in ?? ()
#33 0x in ?? ()

Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Ray Rashif]

On 22 May 2012 23:13, Olivier Ripoll durocortorum73-gm...@yahoo.fr wrote:
 On 20.05.2012 11:14, Rashif Ray Rahman wrote:

 So, I finally managed to track down a peculiarity.

 On Windows (7), there is no scrolling issue with the keyboard, or the
 mouse scroll wheel (or touchpad vertical scroll). However, there is
 lag if I use the scroll bar (by dragging with the mouse).

 [...]

 Hi,

 That looks a lot like what I'm seeing since 2.0.2.

 www.lyx.org/trac/ticket/8135

 Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by
 dragging the scrollbar is working with it ?

I had noticed that bug report before, and I tried my luck on Linux by
installing 2.0.1, but it did not help. I will try it on Windows,
although it does appear to me as if the only problem in Windows is
that of scrolling with the scrollbar. Nothing else is a problem there.


--
GPG/PGP ID: C0711BF1

Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

[John Kane]

Thanks again and thanks for the extra information.  Sorry to take so long to 
reply but I'm on a cycle tour and only the rain has driven me into a library to 
check mail.




- Original Message -
From: stefano franchi stefano.fran...@gmail.com
To: Scott Kostyshak skost...@princeton.edu
Cc: John Kane jrkrid...@yahoo.ca; lyx-users@lists.lyx.org 
lyx-users@lists.lyx.org
Sent: Tuesday, May 15, 2012 5:24:16 PM
Subject: Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

On Tue, May 15, 2012 at 1:47 PM, Scott Kostyshak skost...@princeton.edu wrote:
 From: John Kane [jrkrid...@yahoo.ca]
 Sent: Tuesday, May 15, 2012 12:28 PM

 Glad you got things working.

I then put
export
PATH=/usr/local/texlive/2011/bin/i386-linux:$PATH
in my .profile and
restarted the terminal

 For the future and in case you are curious: .profile is executed when you log 
 in, not on each opening of a terminal. .bashrc is run on each new terminal 
 instance. This is why a reboot fixed it for you.


Well said. In general, it's  s good idea to run

$source .profile

or

$source .bashrc

etc., whenever you modify one of those environment-altering files.
That way you can test your changes immediately without having to
restart the terminal or rebooting the machine. Other things may happen
when you do that, and I'd like to keep variables to a minimum when
setting things up. After a while it becomes a habit, like running
mktexlsr after manually installing a tex package.


Cheers,

Stefano







 Scott



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
 as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
 then it dies.  The strange part is that I can run LyX successfully if I run 
 it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
 would appreciate any suggestions from the LyX experts about how to diagnose 
 the problem.  LyX info and the backtrace are posted below.  If you think it 
 is a Gentoo packaging issue, please tell me as much as you can so that I can 
 post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

Removing ~/.lyx does not change anything.  It still crashes right away (note 
that the window, buttons, etc are fully drawn and the file examples/splash.lyx 
gets loaded before the SIGSEGV dialog box appears).




 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:33 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
 as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
 then it dies.  The strange part is that I can run LyX successfully if I run 
 it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
 would appreciate any suggestions from the LyX experts about how to diagnose 
 the problem.  LyX info and the backtrace are posted below.  If you think it 
 is a Gentoo packaging issue, please tell me as much as you can so that I can 
 post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 Removing ~/.lyx does not change anything.  It still crashes right away (note 
 that the window, buttons, etc are fully drawn and the file 
 examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[William Seager]

On Monday 21 May 2012 10:23:01 Craig wrote:
 The strange part is that I can run LyX successfully if I run it as root. 

That must be a big clue - can you create a brand new user
and see if lyx runs for the new user?

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

I can build LyX with the debug flag, but that will take a little while. In the 
meantime, here is another clue.  When I run the lyx command in a terminal, it 
dumps a lot of text to the terminal when crashing.  First, I get this repeated 
many times:


GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead

Then I get:


Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
When converting from UCS-4LE to UTF-8.
Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 0x0 
0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 
...

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help-Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.


It dumps about 20MB of those hex codes to the terminal.  When I run LyX as root 
or do sudo lyx I don't get any errors or warning messages.




 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:50 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 Removing ~/.lyx does not change anything.  It still crashes right away (note 
 that the window, buttons, etc are fully drawn and the file 
 examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
 Then I get:
 
 
 Error returned from iconv
 EILSEQ An invalid multibyte sequence has been encountered in the input.
 When converting from UCS-4LE to UTF-8.
 Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running lyx -dbg any and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

lyx -dbg any  a.txt

...

GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead
Menus.cpp(2012): populating menu bar
Menus.cpp(2019): menu bar entries 8
Menus.cpp(2038): menu bar item File is a submenu named file
Menus.cpp(2038): menu bar item Edit is a submenu named edit
Menus.cpp(2038): menu bar item View is a submenu named view
Menus.cpp(2038): menu bar item Insert is a submenu named insert
Menus.cpp(2038): menu bar item Navigate is a submenu named navigate
Menus.cpp(2038): menu bar item Document is a submenu named document
Menus.cpp(2038): menu bar item Tools is a submenu named tools
Menus.cpp(2038): menu bar item Help is a submenu named help
GuiView.cpp(798): Passed Geometry 510x690+50+50
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiApplication.cpp(1055): dispatch msg is
Error: Software exception Detected

LyX has caught an exception, it will now attempt to save all unsaved documents  
and exit.

Exception: std::bad_alloc
GuiSelection.cpp(91): GuiSelection::on_dataChanged
GuiSelection.cpp(91): GuiSelection::on_dataChanged



 From: Pavel Sanda sa...@lyx.org
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 5:19 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
 Then I get:
 
 
 Error returned from iconv
 EILSEQ An invalid multibyte sequence has been encountered in the input.
 When converting from UCS-4LE to UTF-8.
 Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running lyx -dbg any and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel

Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Olivier Ripoll]

On 20.05.2012 11:14, Rashif Ray Rahman wrote:


So, I finally managed to track down a peculiarity.

On Windows (7), there is no scrolling issue with the keyboard, or the
mouse scroll wheel (or touchpad vertical scroll). However, there is
lag if I use the scroll bar (by dragging with the mouse).

[...]

Hi,

That looks a lot like what I'm seeing since 2.0.2.

www.lyx.org/trac/ticket/8135

Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by 
dragging the scrollbar is working with it ?


Thanks,

Olivier

LyX SEGSEGV crash just after GUI window appears

[Craig]

I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
then it dies.  The strange part is that I can run LyX successfully if I run it 
as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I would 
appreciate any suggestions from the LyX experts about how to diagnose the 
problem.  LyX info and the backtrace are posted below.  If you think it is a 
Gentoo packaging issue, please tell me as much as you can so that I can post a 
good bug report.


LyX info:
LyX 2.0.3 (2012-02-19)
Built on May 21 2012, 11:50:43
Configuration
  Host type:    x86_64-pc-linux-gnu
  Special build flags:  build=release use-hunspell
  C   Compiler: x86_64-pc-linux-gnu-gcc 
  C   Compiler LyX flags:    
  C   Compiler flags:    -O2 -pipe -march=native -msse4
  C++ Compiler: x86_64-pc-linux-gnu-g++ (4.5.3)
  C++ Compiler LyX flags:    
  C++ Compiler flags:    -O2 -pipe -march=native -msse4
  Linker flags: 
  Linker user flags:    -Wl,-O1 -Wl,--as-needed
  Qt 4 Frontend:
  Qt 4 version:        4.8.1
  Packaging:    posix
  LyX binary dir:   /usr/bin
  LyX files dir:    /usr/share/lyx


Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x00a397ea in ?? ()
(gdb) backtrace
#0  0x00a397ea in ?? ()
#1  0x00a3a813 in ?? ()
#2  0x00a3af06 in ?? ()
#3  0x00a0a34d in ?? ()
#4  0x0081a526 in ?? ()
#5  0x76a04c5f in ?? () from /usr/lib64/qt4/libQtGui.so.4
#6  0x76a04f29 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#7  0x7498330e in _SmcProcessMessage () from /usr/lib64/libSM.so.6
#8  0x747731f3 in IceProcessMessages () from /usr/lib64/libICE.so.6
#9  0x764673fa in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x764b374e in QSocketNotifier::activated(int) ()
   from /usr/lib64/qt4/libQtCore.so.4
#11 0x7646f29b in QSocketNotifier::event(QEvent*) ()
   from /usr/lib64/qt4/libQtCore.so.4
#12 0x769843a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtGui.so.4
#13 0x76988fef in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/qt4/libQtGui.so.4
#14 0x0081a108 in ?? ()
#15 0x76451b1c in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib64/qt4/libQtCore.so.4
#16 0x76480789 in ?? () from /usr/lib64/qt4/libQtCore.so.4
---Type  to continue, or q  to quit---
#17 0x7509c87f in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#18 0x7509d088 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x7509d261 in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#20 0x76480e2f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib64/qt4/libQtCore.so.4
#21 0x76a295fe in ?? () from /usr/lib64/qt4/libQtGui.so.4
#22 0x76450b42 in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib64/qt4/libQtCore.so.4
#23 0x76450dfd in 
QEventLoop::exec(QFlags) () from 
/usr/lib64/qt4/libQtCore.so.4
#24 0x764555ab in QCoreApplication::exec() ()
   from /usr/lib64/qt4/libQtCore.so.4
#25 0x0052e3e6 in ?? ()
#26 0x00441b6a in ?? ()
#27 0x757c12ad in __libc_start_main () from /lib64/libc.so.6
#28 0x00441a69 in ?? ()
#29 0x7fffdea8 in ?? ()
#30 0x001c in ?? ()
#31 0x0001 in ?? ()
#32 0x7fffe1db in ?? ()
#33 0x in ?? ()

Re: Scrolling Slowness [Re: keyboard Scrolling Anomaly]

[Ray Rashif]

On 22 May 2012 23:13, Olivier Ripoll  wrote:
> On 20.05.2012 11:14, Rashif Ray Rahman wrote:
>
>> So, I finally managed to track down a peculiarity.
>>
>> On Windows (7), there is no scrolling issue with the keyboard, or the
>> mouse scroll wheel (or touchpad vertical scroll). However, there is
>> lag if I use the scroll bar (by dragging with the mouse).
>
> [...]
>
> Hi,
>
> That looks a lot like what I'm seeing since 2.0.2.
>
> www.lyx.org/trac/ticket/8135
>
> Could you try LyX 2.0.1 on Windows and see if you smooth scrolling by
> dragging the scrollbar is working with it ?

I had noticed that bug report before, and I tried my luck on Linux by
installing 2.0.1, but it did not help. I will try it on Windows,
although it does appear to me as if the only problem in Windows is
that of scrolling with the scrollbar. Nothing else is a problem there.


--
GPG/PGP ID: C0711BF1

Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

[John Kane]

Thanks again and thanks for the extra information.  Sorry to take so long to 
reply but I'm on a cycle tour and only the rain has driven me into a library to 
check mail.




- Original Message -
From: stefano franchi 
To: Scott Kostyshak 
Cc: John Kane ; "lyx-users@lists.lyx.org" 

Sent: Tuesday, May 15, 2012 5:24:16 PM
Subject: Re: OT? upgrading Texlive to work with LyX 2.0.2. Paths problem

On Tue, May 15, 2012 at 1:47 PM, Scott Kostyshak  wrote:
> From: John Kane [jrkrid...@yahoo.ca]
> Sent: Tuesday, May 15, 2012 12:28 PM
>
> Glad you got things working.
>
>>I then put
>>export
>>PATH=/usr/local/texlive/2011/bin/i386-linux:$PATH
>>in my .profile and
>>restarted the terminal
>
> For the future and in case you are curious: .profile is executed when you log 
> in, not on each opening of a terminal. .bashrc is run on each new terminal 
> instance. This is why a reboot fixed it for you.


Well said. In general, it's  s good idea to run

$source .profile

or

$source .bashrc

etc., whenever you modify one of those environment-altering files.
That way you can test your changes immediately without having to
restart the terminal or rebooting the machine. Other things may happen
when you do that, and I'd like to keep variables to a minimum when
setting things up. After a while it becomes a habit, like running
mktexlsr after manually installing a tex package.


Cheers,

Stefano






>
> Scott



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas A University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
> I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
> as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
> then it dies.  The strange part is that I can run LyX successfully if I run 
> it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
> would appreciate any suggestions from the LyX experts about how to diagnose 
> the problem.  LyX info and the backtrace are posted below.  If you think it 
> is a Gentoo packaging issue, please tell me as much as you can so that I can 
> post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

Removing ~/.lyx does not change anything.  It still crashes right away (note 
that the window, buttons, etc are fully drawn and the file examples/splash.lyx 
gets loaded before the SIGSEGV dialog box appears).




 From: Pavel Sanda 
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:33 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
> I just installed LyX 2.0.3 on a Gentoo system and the application is crashing 
> as soon as the window opens.  I get a dialog box with the SIGSEGV message and 
> then it dies.  The strange part is that I can run LyX successfully if I run 
> it as root.  Idon't know if this a LyX bug or a Gentoo packaging issue, so I 
> would appreciate any suggestions from the LyX experts about how to diagnose 
> the problem.  LyX info and the backtrace are posted below.  If you think it 
> is a Gentoo packaging issue, please tell me as much as you can so that I can 
> post a good bug report.

Does (re)moving of ~/.lyx help? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
> Removing ~/.lyx does not change anything.  It still crashes right away (note 
> that the window, buttons, etc are fully drawn and the file 
> examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[William Seager]

On Monday 21 May 2012 10:23:01 Craig wrote:
> The strange part is that I can run LyX successfully if I run it as root. 

That must be a big clue - can you create a brand new user
and see if lyx runs for the new user?

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

I can build LyX with the debug flag, but that will take a little while. In the 
meantime, here is another clue.  When I run the lyx command in a terminal, it 
dumps a lot of text to the terminal when crashing.  First, I get this repeated 
many times:


GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead

Then I get:


Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
When converting from UCS-4LE to UTF-8.
Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 0x0 
0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 
...

lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us  
a bug report, if necessary. Thanks!
Bye.


It dumps about 20MB of those hex codes to the terminal.  When I run LyX as root 
or do "sudo lyx" I don't get any errors or warning messages.




 From: Pavel Sanda 
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 4:50 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
> Removing ~/.lyx does not change anything.  It still crashes right away (note 
> that the window, buttons, etc are fully drawn and the file 
> examples/splash.lyx gets loaded before the SIGSEGV dialog box appears).

Can you post backtrace when lyx is compiled with debug use flag? P

Re: LyX SEGSEGV crash just after GUI window appears

[Pavel Sanda]

Craig wrote:
> Then I get:
> 
> 
> Error returned from iconv
> EILSEQ An invalid multibyte sequence has been encountered in the input.
> When converting from UCS-4LE to UTF-8.
> Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
> 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running "lyx -dbg any" and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel

Re: LyX SEGSEGV crash just after GUI window appears

[Craig]

lyx -dbg any &> a.txt

...

GuiToolbar.cpp(339): Session settings could not be found!. Defaults are used 
instead
Menus.cpp(2012): populating menu bar
Menus.cpp(2019): menu bar entries 8
Menus.cpp(2038): menu bar item File is a submenu named file
Menus.cpp(2038): menu bar item Edit is a submenu named edit
Menus.cpp(2038): menu bar item View is a submenu named view
Menus.cpp(2038): menu bar item Insert is a submenu named insert
Menus.cpp(2038): menu bar item Navigate is a submenu named navigate
Menus.cpp(2038): menu bar item Document is a submenu named document
Menus.cpp(2038): menu bar item Tools is a submenu named tools
Menus.cpp(2038): menu bar item Help is a submenu named help
GuiView.cpp(798): Passed Geometry 510x690+50+50
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiView.cpp(768): GuiView::setFocus()0xffab70
GuiView.cpp(775): GuiView::focusInEvent()0xffab70
GuiApplication.cpp(1055): dispatch msg is
Error: Software exception Detected

LyX has caught an exception, it will now attempt to save all unsaved documents  
and exit.

Exception: std::bad_alloc
GuiSelection.cpp(91): GuiSelection::on_dataChanged
GuiSelection.cpp(91): GuiSelection::on_dataChanged



 From: Pavel Sanda 
To: lyx-users@lists.lyx.org 
Sent: Tuesday, May 22, 2012 5:19 PM
Subject: Re: LyX SEGSEGV crash just after GUI window appears
 
Craig wrote:
> Then I get:
> 
> 
> Error returned from iconv
> EILSEQ An invalid multibyte sequence has been encountered in the input.
> When converting from UCS-4LE to UTF-8.
> Input: 0xd0 0x61 0x16 0x3f 0xc0 0x7f 0x0 0x0 0xe0 0xe5 0xf2 0x0 0x0 0x0 0x0 
> 0x0 0x0 0xaf 0xe9 0x0 0x0 0x0 0x0 0x0 0xc0 

This is the important part.
Can you try running "lyx -dbg any" and look on the console. It will output tons 
of messages
but I suspect that something interesting can be found page or two before this 
line...
Debuging flags won't help here I guess.
Pavel