[Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 I'm having a similar issue on Ubuntu 20.04. Currently, every time that I reboot I'm unable to login. I just get a black screen after logging in. I have noticed that if I first delete the contents of .config and .local I'm able to log in. However, obviously, all of my configurations and customizations are then gone. My workaround lately has been to clear those directories, login, logout, copy a backup of those directories to the active directories and then log back in. It's a pain, but for some reason it works. Otherwise, 100% of the time after a reboot I can't access the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870779 Title: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442568] Re: Docker causes a segfault when starting containers
OK, I just wondered if there were additional details. I looked at aufs_utils, and it look like the problem is with the AUFin macro (au_util.h)which is #define AuFin(fmt, ...) \ error_at_line(errno, errno, __FILE__, __LINE__, fmt, ##__VA_ARGS__) I think this should be: #define AuFin(fmt, ...) \ error_at_line(1, errno, __FILE__, __LINE__, fmt, ##__VA_ARGS__) The value 1 for the status parameter would always ensure program termination rather than the current situation where it will continue (if errno == 0) and proceed to segfault or some other crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442568 Title: Docker causes a segfault when starting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442568] Re: Docker causes a segfault when starting containers
*** This bug is a duplicate of bug 1441038 *** https://bugs.launchpad.net/bugs/1441038 Also interest to know what happened to bug #1441038 (or is this number incorrect?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442568 Title: Docker causes a segfault when starting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1442568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327104] [NEW] internal error in lint_module
Public bug reported: The current version of Erlang 16B03 cannot compile function parameters and issues a error from the lint module. There was no problem with 16B02. This appears to be caused by a bug in syntax_tools-1.6.12 [OTP-11576] and has been fixed in 16B03-1. An example of the code that fails: the_test() - lists:map(fun double/1, [1,2,3]). double(X) - 2 * x. As a work around I installed 17 from Erlang solutions and the code compiles correctly. OS Version: 14.04 LTS Linux Version: 3.13.0-29-generic x86_64 ** Affects: erlang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327104 Title: internal error in lint_module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1327104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327104] Re: internal error in lint_module
Just to add that the working 16B02 was replaced by broken 16B03 after 12.04 LTS machine was upgraded to 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327104 Title: internal error in lint_module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1327104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929298] [NEW] jetty startup shows grep error
Public bug reported: Just installed jetty, as dependency of : apt-get install --no-install-recommends solr-jetty default-jdk on starting: using service jetty start the following errormessage is output: grep: character class syntax is [[:space:]], not [:space:] $ dpkg-query --show jetty jetty 6.1.24-6 $ uname -a Linux hsw-tp 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 11.10 Release:11.10 Codename: oneiric looks like the fix is to add the missing [] to the grep command in /etc/init.d/jetty ** Affects: jetty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929298 Title: jetty startup shows grep error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/929298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929298] Re: jetty startup shows grep error
** Patch added: patch grep command in /etc/init.d/jetty https://bugs.launchpad.net/bugs/929298/+attachment/2725488/+files/init-jetty.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929298 Title: jetty startup shows grep error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/929298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901525] [NEW] lack of PNG and JPEG support
Public bug reported:
It appears that the python-gd package in Kubuntu 11.10 oneiric was
compiled without PNG or JPEG support
the installed package is:
Package: python-gd
Versions: 0.56+dfsg-2ubuntu1
The error can be seen quite easily by starting a python shell then:
import gd
gd.image('file.png')
unsupported file type (only .gif|.png|.jpeg|.jpg|.gd|.gd2|.xbm|.xpm accepted)
The error is confusing because it implies support, when there is none.
However, there is a simple work-around by just using the _gd.so file
from 11.04 pacakge.
** Affects: python-gd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901525
Title:
lack of PNG and JPEG support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-gd/+bug/901525/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589574] Re: libtidy creates invalid tags
Definitely use after free - tested by remarking the free() call in alloc.c. After this change the invalid tags show as big and /big. Code to do this was introduced in parse.c 1.178 title: inline propagation A work around is to remove this patch; but simply commenting out the call to InlineDup1 on line 1535 is sufficient. This file was at 1.188 at the time of testing this. The code in the InlineDup1 (istack.c) was introduced by the same patch. -- libtidy creates invalid tags https://bugs.launchpad.net/bugs/589574 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 589574] [NEW] libtidy creates invalid tags
Public bug reported: Binary package hint: tidy The following HTML causes libtidy to produce invalid tags: !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; htmlbody pbia href=A bigB/i/bC/a/p /body/html The result of running this through the tidy command line is: $ tidy -w0 t.html !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; html xmlns=http://www.w3.org/1999/xhtml; head meta name=generator content=HTML Tidy for Linux (vers 25 March 2009), see www.w3.org / title/title /head body pbia href=AbigB/big���C/���/a/i/b/p /body /html The invalid tags change on each run, looking like use after free kind of problem. This is running on Ubuntu 10.04 LTS, updated recently. Linux 2.6.32-22-generic #35-Ubuntu SMP Tue Jun 1 14:18:25 UTC 2010 x86_64 GNU/Linux /etc/tidy.conf only contains comments. there are no other tidy configuration files Using LD_PRELOAD I tested the libtidy from earlier distributions; only the version from libtidy-0.99-0_20051018-1_amd64.deb does not show this effect. ** Affects: tidy (Ubuntu) Importance: Undecided Status: New -- libtidy creates invalid tags https://bugs.launchpad.net/bugs/589574 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
