[Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803929 Title: Summary: Kernel bug (unhandled paging request) on "udisksctl power- off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743606] [NEW] docker-compose 1.17.1-1 requires python-backports.ssl-match-hostname>=3.5
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 python-backports.ssl-match-hostname>=3.5 (and not just python-backports.ssl-match-hostname) is required: Traceback (most recent call last): File "/usr/bin/docker-compose", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2927, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2913, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2940, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 637, in _build_master return cls._build_from_requirements(__requires__) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 650, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 829, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'backports.ssl_match_hostname>=3.5' distribution was not found and is required by docker-compose The .deb installed just fine, so IMHO the dependencies need to be fixed. ** Affects: docker-compose (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/1743606 Title: docker-compose 1.17.1-1 requires python-backports.ssl-match- hostname>=3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1743606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326903] Re: remmina and mumble windows get lost
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1326903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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: [2.438172] uvesafb: Getting VBE info block failed (eax=0x4f00, err=0) kernel: [2.438222] uvesafb: vbe_init() failed with -22 kernel: [2.438254] uvesafb: probe of uvesafb.0 failed with error -22 The Xorg.log is attached. Some more information regarding my system: * Mainboard: Elitegroup K7S5A * BIOS: AMIBIOS 1.21.06 * Graphics card: GeForce FX 5200 in an AGP slot While I can use the latest kernel without problems again, it would probably still be interesting to find out the reason why I have to change a BIOS setting with kernels younger than 3.2.0-38. ** Attachment added: Xorg.log when booting 3.9.0-rc3 with 'Allocate IRQ to PCI VGA' set to 'Yes' https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+attachment/3643764/+files/3.9_rc3_Xorg.txt -- 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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/linux-headers-3.9.0-030900rc3_3.9.0-030900rc3.201303171935_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/linux-image-3.9.0-030900rc3-generic_3.9.0-030900rc3.201303171935_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/linux-image-extra-3.9.0-030900rc3-generic_3.9.0-030900rc3.201303171935_i386.deb I used gdebi-gtk to install the packages one by one (headers all, headers generic, image, image extra). During installation of the generic headers package I saw the following in the terminal: run-parts: executing /etc/kernel/header_postinst.d/dkms 3.9.0-030900rc3-generic /boot/vmlinuz-3.9.0-030900rc3-generic Error! Bad return status for module build on kernel: 3.9.0-030900rc3-generic (i686) Consult /var/lib/dkms/nvidia-173/173.14.35/build/make.log for more information. Since the nvidia kernel module did not build I expect to get into trouble, but I will try and reply again in a few minutes. I attached the log (exactly the same output in both cases except for a timestamp). ** Attachment added: make.log during installation of 3.9rc3 generic headers/image extra for nvidia 173.14.35 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+attachment/3588039/+files/3.9_rc3_headers_generic_make.log -- 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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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 want to log in using the console, the screen stays black. Fortunately, I was able to log in, 'beep' and shutdown blindly. That fits to 'uvesafb: vbe_init() failed with -22'. I will attach dmesg, Xorg.log and the output of lspci -k -n -vv again. I will also add the tag 'kernel-unable-to-test-upstream' and mark this bug as 'Confirmed'. ** Attachment added: Typical dmesg with kernel 3.9.0_rc3 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+attachment/3588054/+files/dmesg_3.9.0_rc3.txt -- 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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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: kernel-unable-to-test-upstream -- 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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] Re: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157878 Title: No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157878] [NEW] No X with nvidia after upgrade from 3.2.0-38 to 3.2.0-39
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 module does not work anymore. I also tried the quantal kernel 3.5.0-26: same behaviour. The (imho) interesting messages in dmesg are the following: [ 28.302848] nvidia :01:00.0: can't find IRQ for PCI INT A; please try using pci=biosirq [ 28.302866] NVRM: Can't find an IRQ for your NVIDIA card! [ 28.302871] NVRM: Please check your BIOS settings. [ 28.302876] NVRM: [Plug Play OS] should be set to NO [ 28.302881] NVRM: [Assign IRQ to VGA] should be set to YES [ 28.302900] nvidia: probe of :01:00.0 failed with error -1 [ 28.319027] PCI: setting IRQ 12 as level-triggered [ 28.319046] snd_ens1371 :00:0d.0: found PCI INT A - IRQ 12 [ 28.319462] NVRM: The NVIDIA probe routine failed for 1 device(s). [ 28.319473] NVRM: None of the NVIDIA graphics adapters were initialized! I attached an Xorg.log for 3.2.0-38 and 3.2.0-39, lspci output for 3.2.0-38, 3.2.0-39 and 3.5.0-26, the output of dmesg for 3.2.0-38 and 3.2.0-39 and the output of glxinfo of nvidia-settings. If you need anything else, please tell me. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: kernel nvidia xserver ** Attachment added: Typical Xorg.log with kernel 3.2.0-38 https://bugs.launchpad.net/bugs/1157878/+attachment/3586129/+files/Xorg.log_3.2.0-38.txt -- 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 nvidia after upgrade from 3.2.0-38 to 3.2.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1157878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979839] [NEW] No X with nvidia-current 270.41.06-0ubuntu1.1
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) Module nvidia: vendor=NVIDIA Corporation [42.536]compiled for 4.0.2, module version = 1.0.0 [42.536]Module class: X.Org Video Driver [42.539] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your [42.539] (EE) NVIDIA: system's kernel log for additional error messages. [42.540] (II) UnloadModule: nvidia [42.540] (II) Unloading nvidia [42.540] (EE) Failed to load module nvidia (module-specific error, 0) [42.540] (EE) No drivers available. [42.540] Fatal server error: [42.540] no screens found I had the same symptoms when I started using the PAE kernel with nvidia drivers installed using the non-PAE kernel (long time ago). Starting the non-PAE kernel gives me a working X, but unused nvidia driver since the driver was installed while running the PAE kernel. lsb_release -rd: Description:Ubuntu 11.04 Release:11.04 apt-cache policy nvidia-current: 270.41.06-0ubuntu1.1 What I expected to happen: X and gdm starting up and allowing me to graphically log in as usual. What happened instead: No GUI since X refused to start. What I have not tried so far: Reinstall nvidia-current while running the non-PAE kernel. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: nvidia xorg -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/979839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979839] Re: No X with nvidia-current 270.41.06-0ubuntu1.1
** 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. https://bugs.launchpad.net/bugs/979839 Title: No X with nvidia-current 270.41.06-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/979839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979839] Re: No X with nvidia-current 270.41.06-0ubuntu1.1
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. Works. I have no idea why it did not work from the beginning like that. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/979839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979839] Re: No X with nvidia-current 270.41.06-0ubuntu1.1
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/979839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500843] Re: Warzone freezes during single mission
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 release, so the invested time probably is better invested in trying the Beta 4. I hope this helps. And do you have a savegame just before that crash? If so, try starting WZ with sound disabled (--nosound) and see if that helps. BTW: Official bug-tracker (more devs review bugs there) is located at http://developer.wz2100.net/ -- Warzone freezes during single mission https://bugs.launchpad.net/bugs/500843 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 399327] Re: warzone2100 crashed with SIGSEGV in aiChooseTarget()
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() https://bugs.launchpad.net/bugs/399327 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 423572] Re: Bibliography has problem with comma in character style's name
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423572] Re: 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423572] Re: Bibliography has problem with comma in character style's name
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423572] [NEW] Character style not working in bibliography
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 character style Emphasis (should make text appear in italics). 7. Hit the OK button. The author should appear in italics now, but it doesn't, stays the same as before. Going back to the Entries tab and selecting Au under Structure shows that there is no character style. I tried removing the structure and re-adding things with character style already selected, but it didn't work as well. Probably I misunderstand something, but this appears like a bug to me. If it's no bug, then please tell me how to make those character styles work, although I Google didn't give me any relevant answers when searching for open office writer bibliography character style. Output of lsb_release -rd: Description:Ubuntu 9.04 Release:9.04 ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New ** Tags: bibliography character style -- Character style not working in bibliography 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423572] Re: Character style not working in bibliography
** 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. + 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 character style Emphasis (should make text appear in italics). 7. Hit the OK button. The author should appear in italics now, but it doesn't, stays the same as before. Going back to the Entries tab and selecting Au under Structure shows that there is no character style. I tried removing the structure and re-adding things with character style already selected, but it didn't work as well. Probably I misunderstand something, but this appears like a bug to me. If it's no bug, then please tell me how to make those character styles work, although I Google didn't give me any relevant answers when searching for open office writer bibliography character style. Output of lsb_release -rd: Description: Ubuntu 9.04 Release: 9.04 -- Character style not working in bibliography 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423572] Re: Bibliography has problem with comma in character style's name
** 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 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. + redone everything for the third time and now it's working. + + 2nd EDIT: I found the reason for the defunct behaviour and updated this + report accordingly. Sorry for the inconvenience ;_; 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 character style Emphasis (should make text appear in italics). - 7. Hit the OK button. + 3. Create a new character style called Literaturverzeichnis, Artikel, Band and let it make the text appear in italics. + 4. Add a bibliography to the document. + 5. Go to the Entries tab. + 6. In Structure select Au. + 7. Select the character style Literaturverzeichnis, Artikel, Band. + 8. Hit the OK button. The author should appear in italics now, but it doesn't, stays the same as before. Going back to the Entries tab and selecting Au under Structure shows that there is no character style. I tried removing the structure and re-adding things with character style already selected, but it didn't work as well. - Probably I misunderstand something, but this appears like a bug to me. - If it's no bug, then please tell me how to make those character styles - work, although I Google didn't give me any relevant answers when - searching for open office writer bibliography character style. + Trying to manually apply the style (by selecting the text and then + double-clicking the style in the stylist) works. Output of lsb_release -rd: Description: Ubuntu 9.04 Release: 9.04 ** Tags added: comma -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244015] Re: when i run warzone its give me this (underline words )
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 developers surely will take care of it. -- when i run warzone its give me this (underline words ) https://bugs.launchpad.net/bugs/244015 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 239871] Re: package warzone2100-data None [modified: /var/lib/dpkg/info/warzone2100-data.list] failed to install/upgrade: trying to overwrite `/usr/share/games/warzone2100/mods/global/grim.wz', w
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 warzone2100-data (2.1.0~0.svn3595.dfsg.1-1) ... Setting up warzone2100 (2.1.0~0.svn3595.dfsg.1-1) ... Removing warzone2100 ... Removing warzone2100-data ... Selecting previously deselected package warzone2100-data. Unpacking warzone2100-data (from .../warzone2100-data_2.1.0~0.svn3595.dfsg.1-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/warzone2100-data_2.1.0~0.svn3595.dfsg.1-1_all.deb (--unpack): trying to overwrite `/usr/share/games/warzone2100/mods/global/grim.wz', which is also in package warzone2100 Description of what I think happened: You installed/tried to install the Warzone 2100 version included in Hardy Heron (warzone2100_2.1.0~0.svn3595.dfsg.1-1_i386.deb). Additionally you installed/tried to install the corresponding data-package. The data-package has at least one file that is also included in the warzone2100-package. Both files (grim.wz) should be exactly the same, so overwriting should not be a problem. How you could work around this problem: I have not checked those two packages and do not use them at all. Instead I am using the latest stable version (2.0.10) which is also available as a .deb-package at the Gna! project site (http://download.gna.org/warzone/releases/2.0/). It is working with Ubuntu 8.04 Hardy Heron (i386). I recommend to not use the more or less randomly chosen outdated svn- versions included in the Ubuntu repositories as reporting bugs for those versions is almost no use (one would have to verify the existance of the bug in the current svn-version). Possible source of the bug: This could be a bug in the packages, but the package-maintainer could tell you more about it. -- package warzone2100-data None [modified: /var/lib/dpkg/info/warzone2100-data.list] failed to install/upgrade: trying to overwrite `/usr/share/games/warzone2100/mods/global/grim.wz', which is also in package warzone2100 https://bugs.launchpad.net/bugs/239871 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 159940] Re: Leave message does not like and
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176095] Re: warzone2100 crashed with SIGSEGV
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 version of Warzone 2100. -- warzone2100 crashed with SIGSEGV https://bugs.launchpad.net/bugs/176095 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 159940] Re: Leave message does not like and
** 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, where are you? . RandomNick RandomChatMessage Please respond to this when you are back! Have checked as well without any problems. + + Added later: Also doesn't like unescaped. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159940] Leave message does not like AND
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159940] Re: Leave message does not like
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 http://launchpadlibrarian.net/10292790/xchat_tray_balloon.png -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159940] Re: Leave message does not like
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159940] Re: Leave message does not like
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 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
[Bug 159940] Leave message does not like
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 as well without any problems. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: Confirmed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
