As I ran into this today as well, I might add that I managed to see the very
first line in the kernel.log:
> BUG: unable to handle kernel NULL pointer dereference at [very low address]
Going back to 4.4.0-138 solved the problem here as well.
--
You received this bug notification because you
Public bug reported:
When trying to run docker-compose from the 1.17.1-1 package from Bionic
(https://launchpad.net/ubuntu/+archive/primary/+files/docker-compose_1.17.1-1_all.deb)
under Xenial (I know, stupid idea; was just trying...) the following traceback
is generated suggesting that
Workaround, tested on 14.04: Meta + W to show all windows and pick the
Mumble window.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326903
Title:
remmina and mumble windows get lost
To manage
This bug has been fixed with kernel 3.2.0-41. Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157878
Title:
No X with
This seems to be true. Starting the newer kernels will not automatically
turn off the computer when shutting down, I have to do it manually after
the 'System halted' message appeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I found the following solution to this problem:
* BIOS - PCI / Plug and Play Setup
* Allocate IRQ to PCI VGA: Yes (before: No)
Kernels 3.2.0-39, 3.2.0-40, 3.5.0-26 work without problems. Kernel
3.9.0-030900rc3 fails again in uvesafb, so I do not see anything during booting:
kernel: [
Since there has not been any reply for the past week(s), I wanted to say
that, if somebody could prepare intermediate kernel packages from
3.2.0-38 to 3.2.0-39 I would like to help find the commit which
introduced the problem.
--
You received this bug notification because you are a member of
I downloaded the following files:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/linux-headers-3.9.0-030900rc3-generic_3.9.0-030900rc3.201303171935_i386.deb
** Attachment added: Typical Xorg.log with kernel 3.9.0_rc3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+attachment/3588087/+files/Xorg.log_3.9.0-rc3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Running in low graphics mode for this session. ;) No output, not even
the console (?) output I normally see during booting. With 3.2.0-39 and
3.5.0-26 I saw something, but not in the native resolution of the
screen, with 3.9rc3 the screen remains black until bulletproof X asks
what to do. When I
** Attachment added: Typical output for lspci -k -n -vv for kernel 3.9.0_rc3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+attachment/3588088/+files/lspci_knvv_3.9.0_rc3.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added:
** Attachment added: Typical dmesg with kernel 3.2.0-39
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586135/+files/dmesg_3.2.0-39.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Typical Xorg.log with kernel 3.2.0-39
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586130/+files/Xorg.log_3.2.0-39.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Typical output for lspci -k -n -vv for kernel 3.5.0-26
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586133/+files/lspci_knvv_3.5.0-26_generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Output for nvidia-settings --glxinfo (kernel 3.2.0-38)
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586139/+files/nvidia-settings-glxinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Typical dmesg with kernel 3.2.0-38
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586134/+files/dmesg_3.2.0-38.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Typical output for lspci -k -n -vv for kernel 3.2.0-38
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586131/+files/lspci_knvv_3.2.0-38_generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Typical output for lspci -k -n -vv for kernel 3.2.0-39
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+attachment/3586132/+files/lspci_knvv_3.2.0-39_generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
lsb_release -rd
Description:Ubuntu 12.04.2 LTS
Release:12.04
uname -a
Linux samus 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:20:02 UTC 2013 i686
athlon i386 GNU/Linux
After I upgraded from 3.2.0-38 to 3.2.0-39 upon restart X failed to start. The
nvidia
Public bug reported:
X refuses to start on 32 bit PAE Ubuntu after todays kernel and nvidia
updates.
When starting the PAE kernel, I get the following message in Xorg.0.log:
[42.536] (II) LoadModule: nvidia
[42.536] (II) Loading /usr/lib/xorg/extra-modules/nvidia_drv.so
[42.536] (II)
** Attachment added: Complete Xorg log trying PAE + latest nvidia-current
https://bugs.launchpad.net/bugs/979839/+attachment/3052310/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Erm... fixed by removing nvidia-current and reinstalling while running
PAE kernel.
What I did in more detail:
Remove nvidia-current while running non-PAE kernel.
Restart with PAE kernel.
Log in without X.
Delete xorg.conf.
Start gdm and login.
Reinstall nvidia-current.
Restart with PAE kernel.
Sorry for the spam. Driver removal and reinstallation were done via
Additional drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979839
Title:
No X with nvidia-current 270.41.06-0ubuntu1.1
To
If possible, please try to verify this with the latest version (2.2.4)
as with every release new crash bugs are fixed. On the other hand you
could probably try 2.3.0 Beta 4 the latest beta release of the upcoming
2.3 branch. The choice is up to you, but I doubt that there will be
another 2.2.x
Jens, we have a dedicated wiki page for 3rd party packages, please see
http://developer.wz2100.net/wiki/3rdPartyPackages . Perhaps somebody
should add a link to that wiki page on the downloads page xD *hint*
*hint*
--
warzone2100 crashed with SIGSEGV in aiChooseTarget()
Filed as Bug #105394, see
http://www.openoffice.org/issues/show_bug.cgi?id=105394
** Bug watch added: OpenOffice.org Issue Tracker #105394
http://qa.openoffice.org/issues/show_bug.cgi?id=105394
--
Bibliography has problem with comma in character style's name
Reproducible with OpenOffice.org 3.1.1 OOO310m19 (Build:9420).
--
Bibliography has problem with comma in character style's name
https://bugs.launchpad.net/bugs/423572
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'll try my best.
--
Bibliography has problem with comma in character style's name
https://bugs.launchpad.net/bugs/423572
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
Public bug reported:
Binary package hint: openoffice.org
Version: 1:3.0.1-9ubuntu3
How to reproduce:
1. Create a new text document in Writer.
2. Add some references into the document.
3. Add a bibliography to the document.
4. Go to the Entries tab.
5. In Structure select Au.
6. Select the
** Description changed:
+ EDIT: I just noticed that it's perfectly working with the predefined
+ character styles, but not with the one that I've created. I have just
+ redone everything for the third time and now it's working. I have no
+ idea why, but I am sorry to have wasted your time.
+
** Summary changed:
- Character style not working in bibliography
+ Bibliography has problem with comma in character style's name
** Description changed:
EDIT: I just noticed that it's perfectly working with the predefined
character styles, but not with the one that I've created. I have
Funny bug. But it is not recommended to use the outdated version that
comes with Ubuntu. Instead you should consider using latest stable
release 2.0.10 or latest beta (2.1 Beta 2). See the homepage for further
information.
Try to reproduce this bug in a current (not 2.0.10!) version and the
Selecting previously deselected package warzone2100-data.
Unpacking warzone2100-data (from
.../warzone2100-data_2.1.0~0.svn3595.dfsg.1-1_all.deb) ...
Selecting previously deselected package warzone2100.
Unpacking warzone2100 (from .../warzone2100_2.1.0~0.svn3595.dfsg.1-1_i386.deb)
...
Setting up
I still have this bug in Hardy (xchat 2.8.4).
--
Leave message does not like and
https://bugs.launchpad.net/bugs/159940
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
This version is horribly outdated and never was published as an
official stable version. Currently svn is at revision 4773, so I think
that chances are little that this problem gets ever fixed.
And the savegame-format has changed since then so old save-games may not
be loaded with a current
** Summary changed:
- Leave message does not like
+ Leave message does not like and
** Description changed:
Binary package hint: gnome-screensaver
Entering leave-messages containing a (without quotes) results in an
empty leave-message.
Example texts (without quotes):
Hey,
I found out that at least in x-chat and gnome-screen-saver the is
affected, too. Open new bug-report?
--
Leave message does not like
https://bugs.launchpad.net/bugs/159940
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Make sure to have checked Show tray ballons on: (in my case: channel-
message) in your options. First balloon has a message containing a ,
second balloon's message is displayed correctly/as expected.
Hope this helps ^^
** Attachment added: xchat balloon with inside
** Also affects: xchat (Ubuntu)
Importance: Undecided
Status: New
--
Leave message does not like
https://bugs.launchpad.net/bugs/159940
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
It does not have to do much with gnome-screensaver as further testing
showed. E. g. x-chat popups containing behave the same way: Popup
appears, but empty.
--
Leave message does not like
https://bugs.launchpad.net/bugs/159940
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: gnome-screensaver
Entering leave-messages containing a (without quotes) results in an
empty leave-message.
Example texts (without quotes):
Hey, where are you? .
RandomNick RandomChatMessage
Please respond to this when you are back!
Have checked
41 matches
Mail list logo
