[Bug 1887294] Re: [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB

2020-11-09 Thread Aleksander Demko
Can confirm with 20.04 (not new though, this happened in 18.04 too):

- GTX 1050 Ti, drivers 450.80.02
- Kernel  5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
- dmesg attached
- I have to ssh into the machine and shut it down.

For me, it always seem to happen when I walk away after locking my
screen and turning off my monitor (by turning it off at the power bar -
an old work around for failing-to-sleep-monitor issues, of all things)

Note my keyboard and mice a plugged into the hub, so you'll see usb
disconnects in the dmesg.


** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+attachment/5432773/+files/dmesg2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887294

Title:
  [nvidia] Display freeze and kernel crash on GeForce GTX 1060 6GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl

2008-06-23 Thread Aleksander Demko
I've also tested Bryce's non-xcb libs and  they also fix my Matlab
issues completely. They also fix my Maple issues, which is reasonable as
both packages share a Java foundation in their GUI. I bet this fixes
bugs with many other software packages too.

I hope the non-xcb backed X11 libraries go back into Hardy, especially
as it's a LTS release. Installing Hardy and finding many packages break
is quite disconcerting. I'm not sure how many applications use xcb and
X11 together, but surely sacrificing the stability of older applications
isn't worth it just to run a few xcb+x11 mixed programs.

-- 
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl

2008-06-20 Thread Aleksander Demko
Ok, here's a really ugly and large hack that seems (for me anyways) to
get Matlab back to where it was before Hardy.

Basically, I took the libX11.so (and related) files from a different
machine that didn't have a libxcb-backed libX11:

 scp fedora3machine:/usr/X11R6/lib64/lib*.so.? /opt/oldX11lib

Then I placed this new set of X11 libs in my load path:

 export LD_LIBRARY_PATH=/opt/oldX11lib:$LD_LIBRARY_PATH

Then I ran Matlab with great success, even over TCP.

Note, make sure you use the proper (32-bit or 64-bit) libraries for you
machine/application.

This hack is at best temporary to get you going. Ideally, the libX11-xcb
library should emulate all the issues of the old libX11 for older apps,
or it should be removed and let the old libX11 continue to serve those
applications. Frameworks and applications can then migrate to libxcb at
their own pace.

-- 
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

2008-06-20 Thread Aleksander Demko
Sorry, I meant to say "unusably slow". TCP/X11 transport of Matlab and
other Java applications are unusably slow even with all the hacks and
updates applied.

-- 
xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
https://bugs.launchpad.net/bugs/87947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl

2008-06-20 Thread Aleksander Demko
Sorry, I meant to say "unusably slow". TCP/X11 transport of Matlab and
other Java applications are unusably slow even with all the hacks and
updates applied.

-- 
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

2008-06-20 Thread Aleksander Demko

I still get issues when running MATLAB r2008 under Hard (32-bit and 64-bit). 
I've tried the sed thing, the SLOPPY_LOCK export and have all the updates 
installed as of today.

Basically, matlab over UNIX sockets (the default, DISPLAY=:0.0) seems
fine, but over TCP sockets (DISPLAY=localhost:0) is is usably slow. Even
older versions of matlab have issues. Same applies to Maple and any
other odd Java programs I have. I need the TCP sockets because I'm
deploying (well, stalled until this is sorted) Ubuntu on servers here
which I need X11-over-TCP for.

Why can't we just remove the XCB infection/bridge layer from libX11 and
revert it to the stock libX11 module? Let old libX11 programs use that,
and new ones use XCB.

Thanks!

-- 
xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
https://bugs.launchpad.net/bugs/87947
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl

2008-06-20 Thread Aleksander Demko

I still get issues when running MATLAB r2008 under Hard (32-bit and 64-bit). 
I've tried the sed thing, the SLOPPY_LOCK export and have all the updates 
installed as of today.

Basically, matlab over UNIX sockets (the default, DISPLAY=:0.0) seems
fine, but over TCP sockets (DISPLAY=localhost:0) is is usably slow. Even
older versions of matlab have issues. Same applies to Maple and any
other odd Java programs I have. I need the TCP sockets because I'm
deploying (well, stalled until this is sorted) Ubuntu on servers here
which I need X11-over-TCP for.

Why can't we just remove the XCB infection/bridge layer from libX11 and
revert it to the stock libX11 module? Let old libX11 programs use that,
and new ones use XCB.

Thanks!

-- 
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 25931] Re: Failed to initalize HAL.

2008-05-11 Thread Aleksander Demko
I also get the "failed to initilize hal" error, but ONLY if autologin is
enabled. I guess it logs in too quickly because of an incorrect priority
list?

rc0.d/K01gdm  rc2.d/S13gdm  rc4.d/S13gdm  rc6.d/K01gdm
rc1.d/K01gdm  rc3.d/S13gdm  rc5.d/S13gdm

rc1.d/K88dbus  rc2.d/S12dbus  rc3.d/S12dbus  rc4.d/S12dbus
rc5.d/S12dbus

rc1.d/K16hal  rc2.d/S24hal  rc3.d/S24hal  rc4.d/S24hal  rc5.d/S24hal

rc0.d/K16dhcdbd  rc2.d/S24dhcdbd  rc4.d/S24dhcdbd  rc6.d/K16dhcdbd
rc1.d/K16dhcdbd  rc3.d/S24dhcdbd  rc5.d/S24dhcdbd


This is a Thinkpad X40, running Hardy, which was upgraded from Fiesty.

-- 
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 185755] [NEW] audacious crashes on roll up

2008-01-24 Thread Aleksander Demko
Public bug reported:


Under Gutsy, when I run audacious and double click the title bar (which I've 
configured to "roll up" the window into just a title bar), the application 
crashes with:

 *** stack smashing detected ***: audacious terminated

This seems to happen ONLY when the application is double-sized (ie. I
clicked the little D in audacious to make it larger).

I've tested this on two completely different (but still Gutsy machines),
on both mp3 and ogg files, with only one file loaded at a time. I run
the stock theme only and without any plugins enabled.

** Affects: audacious (Ubuntu)
 Importance: Undecided
 Status: New

-- 
audacious crashes on roll up
https://bugs.launchpad.net/bugs/185755
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs