[Bug 1325899] Re: evince is excruciatingly slow on some documents
This appears to have been regressed somewhere. 15.04 with libpoppler 0.30 - a PDF that used to render instantly (and renders instantly using muPDF) now takes on average 10-15s to render a single page using Evince or Atril, or longer if focus is missing. As the behaviour is the same in both Evince and Atril, my assumption is that the issue is in poppler somewhere - PDF renderers that do not use poppler are ultrafast, those that use it are ultra slow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325899 Title: evince is excruciatingly slow on some documents To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1325899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525526] [NEW] evince/atril is excruciatingly slow
Public bug reported: For image-heavy PDF files, both Atril and Evince are extremely slow when rendering the page. 'Slow' being in the region of 5-30s (timed), depending on the page, and depending on focus. Thumbnails take an equally long time to render. The same PDF files opened in muPDF render pages instantly. Currently version of libpoppler is 0.30.0-0ubuntu1. ** Affects: poppler (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/1525526 Title: evince/atril is excruciatingly slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1525526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432171] Re: [udev] Shows starting version 219 boot message even with quiet
Well, I resolved the error - by installing `upstart-sys` (which replaces `systemd` with upstart) So it appears this is an issue where the removal of `upstart` breaks startup of some display managers and prevents the running of login scripts. The workaround is to manually start your chosen display manager from a cli. Reconfiguring (dpkg-reconfigure) doesn't work, and on this basis, `mdm` works, `lightdm` crashes to low-graphics mode and `sddm` (if manually installed) shows a plain white screen. So no, it's not related to `sddm`, it is directly related to the implementation and use of `systemd` as a replacement to `upstart`. It may or may not be cosmetic (the display of the message) but the overall effect of installing systemd in this instance has the net result of causing user systems to fail to boot into a graphical display manager, without a relevant or informative notice. So, if you see starting version 219 and your display manager (login window) doesn't run, but you *can* load it by manually starting it form the console, you most likely have a problem with your display manager startup script(s). Either replace the display manager startup scripts to work with `systemd`, or remove `systemd` and replace it with `upstart- sys`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: [udev] Shows starting version 219 boot message even with quiet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432171] Re: [udev] Shows starting version 219 boot message even with quiet
I get this error as well, and I do NOT have sddm installed, so the provided fixes don't work. I cannot boot to a graphical user interface by waiting, I don't have quiet enabled and I'm using mdm. The only way to boot is to switch to another tty (F1 - the only one available) and execute sudo mdm restart manually. This is a critical error, not a trivial one, as i has completely broken the boot process on my laptop. Failed to start sddm.service: Unit sddm.service failed to load: No such file or directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: [udev] Shows starting version 219 boot message even with quiet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196828] Re: Cannot restart banshee after crash
I'm going to re-open this issue, as it's not solved, and in my case is not a file system issue - as banshee is stuck in a fuse_write stae, writing to the primary disk that everything else is running on quite happily. Banshee will restart once I reboot, which is not a viable option. I've tried every variation of every trick listed in this thread and others (and the noah site) and nothing works. ** Changed in: banshee (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196828 Title: Cannot restart banshee after crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
I disabled tmpfs when I started seeing this issue, however the swapping has continued, albeit with a lesser number of issues - until today, when the swapping issue was so bad that I performed a hard power down after my laptop had been unresponsive for 24 minutes (clock showed 14:32, I forced a power-down at 14:56). I couldn't log into any other TTY (it would time out after 60 seconds, or not respond at all), so I couldn't access top or free or anything to try and debug this issue, or even force-kill firefox (which usually solves the problem). I didn't have many windows open, although I was doing some web development at the time (perhaps 3 or 4 firefox windows, Eclipse, MySQL workbench). I am also seeing instances where swap is using 3Gb, cache is using 1Gb, and there are no processes running (default desktop only - all other processes/applications stopped). The only way to force the system to stop using swap when there is nothing to swap is to do a hard restart. Time to also tune background processes I think - the system uses more than 3Gb of physical RAM when idling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
Ack, and I meant to add: So I don't think this is related to tmpfs, at least in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
I made two changes to my machine yesterday in rc.local: I commented out this: # echo deadline /sys/block/sdb/queue/scheduler I added this: rmmod rts5139 (this is the smart card reader poller) I've not had a swap to death instance since that wasn't directly related to too many embedded objects on a Firefox page. There's been some swapping going on, and some general slowdowns, but nothing like the past few weeks. It may be coincidence though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
An update. The swappiness is still killing my laptop. It seems to be explicitly related to having Firefox running, especially if I have multiple windows open, with lots of content. Killing the Firefox process solves the swap problem and returns control of the desktop and mouse, and allows me to continue working. Here's my 'free' status when kswapd0 is using 100% CPU. In this situation kswapd0 is using between 90 and 120% CPU according to `top`, and everything else is under 5%, including firefox. cro@zen:~$ free -h total used free sharedbuffers cached Mem: 3.8G 3.3G 503M 0B16M 1.4G -/+ buffers/cache: 1.8G 1.9G Swap: 3.9G 274M 3.6G Or, because text formatting is bad, of 4Gb swap, 3.6Gb is free, and I have 500Mb of free RAM. vm_swappiness is set to 0. This happens to me on average more than once an hour when I'm working (multiple windows/tabs open). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
Nope, I'm not using LVM snapshots. I'm thinking it's something to do with embeds or media objects - further attempting to work today showed that whenever the flashplugin was loaded (in either firefox or chrome, showing a video in a page) it would swap to death until those processes were killed. I'm doing more testing/tweaking myself, things like disabling SDD deadline in rc.local to see if that has any effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152736] Re: system swapping itself to death in raring for no good reason
This bug affects my laptop as well, regardless of swap or swappiness settings. The laptop is an Asus UX32A, and has only ever had 13.04 installed (from the RC prior to release) /swap is configured with 4G of space on the internal SSD rather than the HDD. Under normal usage kswapd0 starts using 99%+ of CPU every couple of hours. `killall` on firefox or thunderbird usually fixes things (I generally have a lot of Firefox windows open), as does switching to another TTY and waiting, watching `top` and the HDD light as kswapd0 thrashes the disk. While kswapd0 is using CPU, the UI starts to become unresponsive, with interactions delayed and the mouse movemenets becoming jerky. I've configured this machine with and without swap, with high and low swappiness (it's currently 20, but I originally set it to 0) and nothing affects kswapd0 using up to 100% CPU and making the entire machine unresponsive. In some instances it has become so bad and the disk thrashing so consistent and long-term that only a hard power-off works to recover control of the machine (pressing ctrl-alt-F2 for example will take in excess of 5 minutes to respond, and the password entry in that TTY will timeout before completing login, as will attempts to connect via SSH) An example `free -h` total used free sharedbuffers cached Mem: 3.8G 3.6G 157M 0B 4.3M 1.1G -/+ buffers/cache: 2.5G 1.3G Swap: 3.9G 719M 3.2G I've previously used another laptop also with 4Gb of RAM, configured the same way (except with /swap on a spinning disk rather than an SSD) and I used that laptop with variations from 10.04 up to 12.10 with no swap issues at all. My desktop (Mint14), also with 4Gb of RAM does not suffer this swapping problem either. General information: 3.8.0-19-generic #29-Ubuntu SM desktop: Mate 1.6.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152736 Title: system swapping itself to death in raring for no good reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055534] Re: [regression] since linux 3.4.0, kswapd0 uses 100% cpu when low memory is available
I've started seeing this problem with the most recent kernel(3.8.0-19), even when swap is turned off. For example, when resuming from suspend, kwapd0 will start using 99-100% if CPU according to top, even though the reported swap usage is 0. running swapoff -a has no effect, and the only way to stop kswapd0 from consuming all CPU is to close any process that is currently using a lot of RAM (for example Firefox). It is currently so bad that at times the entire computer is unusable as kswapd0 is thrashing the disk, blocking all other IO (shell, TTY, UI)and I am currently investigating ways to physically prevent the process from ever starting. ** Changed in: linux (Ubuntu) Status: Expired = Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055534 Title: [regression] since linux 3.4.0, kswapd0 uses 100% cpu when low memory is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1055534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055534] Re: [regression] since linux 3.4.0, kswapd0 uses 100% cpu when low memory is available
(also, apologies for changing the status, I wasn't aware I could do that) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055534 Title: [regression] since linux 3.4.0, kswapd0 uses 100% cpu when low memory is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1055534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007976] Re: Windows jump to different workspace when switching workspace
This bug appears to relate to the place windows compiz plugin. I can reliably reproduce this issue by enabling or disabling the plugin. With place windows plugin ENABLED: * rotating the cube to the right will move all maximised windows to workspace 1, once the workspace with a maximised window on it is moved past. With place windows plugin DISABLED * maximised windows remain on their workspace when rotating through cube faces. An associated bug is that when the place windows plugin is DISABLED, new un-maximised windows are placed on the desktop with their title bars behind the top panel. With the place windows plugin ENABLED, new un- maximised windows are placed with their title bar below the top panel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007976 Title: Windows jump to different workspace when switching workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1007976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008399] Re: when shutting down, speakers make loud crackling noise 12.04
In addition to this, I also have the no sound from speakers, but headphones work fine bug (similar to but not exactly #946232) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008399 Title: when shutting down, speakers make loud crackling noise 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1008399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876198] Re: When switching workspaces with rotate/cube previous Ws contents are momentarily displayed
This appears to happen regardless of window manager. I've seen this behaviour in Unity, Gnome classic, XFCE4, LXDE, Lubuntu and MATE (the Gnome2 fork). The focus issue appears in all the above, as well as the moving windows with keyboard shortcuts. A serious regression seems to have been introduced with Ubuntu 11.10 that affects a range of display issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876198 Title: When switching workspaces with rotate/cube previous Ws contents are momentarily displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/876198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764051] Re: Second monitor useless in dual desktop mode
I think the wider issue here is that this is a specific change in functionality, wherever it may be. Under the prior version of Ubuntu, configuring a second monitor/second video card as a seperate X screen would result in the second screen being set up the same as the first when it came to window decorators. Since the upgrade, this functionality has changed, and the X-Server is launched without a default window manager, let alone a clone of the first monitor's window manager setting. Now, there is completely non-obvious behaviour happening, and for the majority of first-time users, the fact that the second monitor *does not work as expected* will cause consternation. Contrary to the low improtance assertion, there are a number of valid use-cases for configuring a second monitor with a seperate X-Server. I use a seperate X-Server on my HDMI-out for general display work when I'm using my laptop for other purposes. I've used it in the past for presentation work, or for displaying server monitoring services and displays in a way that doesn't interfere with my primary workspaces. Not every use case for multiple monitors has them next to each other, or even in close proximity. As I type this I have a monitor being driven by a seperate X Server at the end of a 5 meter HDMI cable - if it was running in Twinview then when I switched workspaces I'd lose what was being displayed in the external monitor. And I'm not the only audience for that second screen. I'd heartily disagree that this is of Low importance, although I wonder if the actual bug is in Compiz, or in the way X (or Ubuntu for that matter) handles the user-selected configuration of multiple X-Servers, especially where a second display is launched without a default window manager (if one is not set for the primary display), and where there is no obvious way to run a display manager for those without comand line knowledge. I struggled myself to resolve this, and I've been using Ubuntu as my only OS (work and home) for the past 5 years or so, so I shudder to think of the reaction of a newcomer to Ubuntu when they run into this kind of issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764051 Title: Second monitor useless in dual desktop mode -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489196] Re: evince cannot print pdf files
Confirmed using the following printers: HP Colour Laserjet 3700n HP Laserjet 4200 Printing documents is possible to both printers using alternate Applications (such as OpenOffice or GIMP), it is only evince that fails to print. Same environment as the original reporter (evince version, processor, kernel version) The Printer propertine page shows the printer state as 'Processing', 'Processing - ready to print', 'Idle - ready to print'. The 'Processing' message is displayed for about the amount of time one would expect the document to process. The 'Processig - ready to print' state lasts less than 1 second, and there is never any data activity at the printer. -- evince cannot print pdf files https://bugs.launchpad.net/bugs/489196 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 447448] [NEW] package human-icon-theme should depend on package tangerine-icon-theme
Public bug reported: Binary package hint: human-icon-theme Since the Human icon theme inherits from the Tangerine icon theme (/usr/share/icons/Human/index.theme), the package human-icon-theme should depend on the package tangerine-icon-theme. The Human icon theme also inherits from the gnome icon theme, so the package should depend on the package gnome-icon-theme as well, regardless of this dependency being provided by the package tangerine- icon-theme. More so since human-icon-theme does not depend on tangerine- icon-theme right now. But the inheritance from the gnome icon theme might be revised, see bug #311249, to which this is related. Exhibited in the Jaunty and Karmic packages. ** Affects: human-icon-theme (Ubuntu) Importance: Undecided Status: New -- package human-icon-theme should depend on package tangerine-icon-theme https://bugs.launchpad.net/bugs/447448 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 284505] Re: 8.543 Crashes on login screen
My apologies - I didn't suggest that the problem was in the vboxdrv driver - I suggested that it was caused by a module compiled and installed for the previous kernel version. It just happened that I had only one module installed for a previous kernel version (the vboxdrv module - after I removed all the old fglrx modules) and my contention was that it was this conflict between modules compiled for different kernel versions that was causing the problem. Whether it was the vboxdrv module, or some other module I don't know. What's your dkms status output? Do you have any dkms-handled driver modules compiled for an earlier version of the kernel? Could they be conflicting with the new version of X? -- 8.543 Crashes on login screen https://bugs.launchpad.net/bugs/284505 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 292441] Re: X crashes with fglrx after upgrade to 8.10
Duplicate of https://bugs.launchpad.net/ubuntu/+source/fglrx- installer/+bug/284505 (I can;t mark as duplicate though) -- X crashes with fglrx after upgrade to 8.10 https://bugs.launchpad.net/bugs/292441 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 284505] Re: 8.543 Crashes on login screen
Here's an update:
I managed to resolve this issue (and will cross-post to the forums as
well) by referencing this against another bug in another package/forum:
http://www.virtualbox.org/ticket/2288
I found that essentially the same X error was being caused by the
vboxdrv under Ubuntu 8.10/2.6.27-7 kernel, which seemed odd - since I
had Virtual box installed, and dkms reported that the vboxdrv module was
assigned against the earlier 2.6.24 kernel.
Disabling vboxdrv ('/etc/init.d/vboxdrv stop' followed by removing the
execute flag from the file itself) caused dkms to fail to load the
module at boot (which I had been seeing before), but 'dkms status' now
says this:
~$ dkms status
vboxdrv, 1.6.2: added
fglrx, 8.543, 2.6.27-7-generic, x86_64: installed
and the fglrx driver works fine.
So it may be (or at least appears to be) an issue with modules loaded
through dkms for older kernels not being disabled properly.
--
8.543 Crashes on login screen
https://bugs.launchpad.net/bugs/284505
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 284505] Re: 8.543 Crashes on login screen
Marcus: Try removing fglrx, 8.543, 2.6.24-21-generic, x86_64: installed (original_module exists) if you get the 'Saw signal 11' error in your Xorg log. It appears (perhaps) to be the conflict between the module built for the old kernel that causes the module for the new kernel to fail. Alejandro: As for reinstalling the vboxdrv driver - setup (/etc/init.d/vboxdrv setup) failed for me with a compile error that's also been seen in some versions of fglrx (although I don't have the references to hand, something about too many parameters on one file), which is what also led me to removing the modules compiled for previous kernels from dkms. It seems, from the previous couple of entries, that it is the 'installed' status of modules for previous kernels that causes the problem. Maarcus' fails because his 2.6.24 is 'installed', but alejandro's works because it's just 'built' not 'installed'. Of course this also means that you can't revert to the old 2.6.24 kernel without backing out of these module changes, and definitely points to a conflict in the way different kernel versions of modules are handled by 2.6.27. -- 8.543 Crashes on login screen https://bugs.launchpad.net/bugs/284505 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 291210] Re: fglrx doesn't work with Mobility Radeon X1600 on 64bit intrepid
This may be related to this bug: https://bugs.launchpad.net/bugs/284505 -- fglrx doesn't work with Mobility Radeon X1600 on 64bit intrepid https://bugs.launchpad.net/bugs/291210 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 284505] Re: 8.543 Crashes on login screen
Error also appears on AMD x86_64, 2.6.27-7-generic SMP, with Radeon 4950HD. Going to try some source compiles today. [snip from Xorg.0.log] (II) Loading /usr/lib/xorg/modules//amdxmm.so (II) Module amdxmm: vendor=X.Org Foundation compiled for 1.4.99.906, module version = 1.0.0 ABI class: X.Org Server Extension, version 1.1 Backtrace: 0: /usr/X11R6/bin/X(xf86SigHandler+0x65) [0x480f35] 1: /lib/libc.so.6 [0x7fd29bf8c060] 2: /usr/X11R6/bin/X(xf86XvMCScreenInit+0xed) [0x49628d] 3: /usr/lib/xorg/modules//amdxmm.so(UvdFwSetup+0xa24) [0x7fd2975e4ef4] 4: /usr/lib/xorg/modules//amdxmm.so(amdxmmInit+0x130) [0x7fd2975dcb00] 5: /usr/lib/xorg/modules/drivers//fglrx_drv.so [0x7fd29ab4003d] 6: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxScreenInit+0x6b9) [0x7fd29ab386f9] 7: /usr/X11R6/bin/X(AddScreen+0x1c9) [0x432d89] 8: /usr/X11R6/bin/X(InitOutput+0x241) [0x469a61] 9: /usr/X11R6/bin/X(main+0x286) [0x433526] 10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7fd29bf77466] 11: /usr/X11R6/bin/X [0x432ad9] Saw signal 11. Server aborting. -- 8.543 Crashes on login screen https://bugs.launchpad.net/bugs/284505 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 292103] Re: Sapphire ATI 3850HD (AGP) does not work with Intrepid
*** This bug is a duplicate of bug 284505 *** https://bugs.launchpad.net/bugs/284505 ** This bug has been marked a duplicate of bug 284505 8.543 Crashes on login screen -- Sapphire ATI 3850HD (AGP) does not work with Intrepid https://bugs.launchpad.net/bugs/292103 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
