[Bug 579653] Re: 10.04 - Xorg Crash: Video device settings could not be detected correctly
I have the same problem with a Viglen P4 desktop. It crashed every time I started VirtualBox. I tried the ppa, and things are slightly better now (I can run VirtualBox), but I still get a crash or freeze every once in a while. -- 10.04 - Xorg Crash: Video device settings could not be detected correctly https://bugs.launchpad.net/bugs/579653 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 455969] Re: reading database slow since upgrading to karmic
@Matthew: Yes, I think something more general is wrong. I noticed that a number of the larger files used by aptitude, apt and dpkg have extreme fragmentation on my disk (hundreds of fragments). And I have no idea why that is - do they grow by a little bit every time, for example? Or are concurrent processing writing files the problem? I have Dropbox installed, and use KDE, but that is the only thing that all my systems really have in common. -- reading database slow since upgrading to karmic https://bugs.launchpad.net/bugs/455969 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 478611] Re: amsn 0.98 looking for farsight2, freeze
Hi there I can confirm this bug, and I would propose to upgrade it from "low" - because it really limits the usefulness of this package on a 64bit system. The problems seems to be pretty simple: the architecture independent package amsn-data contains a number of libraries for tcl. These are x86 libraries, so they do not work on any other architecture. Recompiling the program on amd64 fixes the problem for me (running an amd64 system). I would think that moving the libraries (such as /usr/share/amsn/utils/farsight/tcl_farsight.so) from amsn-data to amsn should fix the issue for everybody. They may also get installed in the wrong location (/usr/share should be architecture independent as far as I understand), but that should not be a problem for most users (unless it is the reason for the wrong packaging in the first place). I am sure that amsn should generate an error message when trying to load the wrong libraries, but I have no idea how to find it. Certainly the man page is not very helpful. -- amsn 0.98 looking for farsight2, freeze https://bugs.launchpad.net/bugs/478611 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 364319] Re: pstoedit cannot convert to SVG any more
I anything happening concerning this bug? It has been confirmed, it is a packaging bug, it is easy to fix... what else do we need? -- pstoedit cannot convert to SVG any more https://bugs.launchpad.net/bugs/364319 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 326583] Re: Freezes with K8M890 and openchrome driver
> have you attempted to push this patch upstream at all? Yes, I did. The response was two-fold negative: on one hand, the existing (kernel) driver is not supposed to support the Chrome9 anyway, and it is just a coincidence that it works. On the other hand, a rewrite is underway by Jon, which should then support Chrome9. But he is busy at the moment, and I was not able to test it. So I think the upstream situation for OpenChrome is still a bit chaotic. I am not sure whether it is worthwhile to try to get it into the main line kernel. I am surprised that it is in there at all. -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
Sorry this took a while, but the graphics card does not like 2.6.29 - I will have to figure that out at some point. For the remote, the patch works great. There is only one key not working, the ENTER key, and that may be a problem with the device rather than the driver. Great work! Is there anything else I can do? I will add a list of key codes and the corresponding keys soon, although that may be specific to this remote rather than the receiver. -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326674] Re: Logitech Quickcam E2500 not supported
Hi Manoj Sorry, I had trouble compiling my own kernel - it is not easy with linux-source... Anyway, the kernel from http://people.ubuntu.com/~manjo/lp326674-jaunty/ works in so far as the camera is detected, and I can get a picture with cheese. The quality in 640x480 is horrible (way to dark), but 320x240 is alright, very responsive, if a bit noisy. I do get a lot of error message on the console like libv4lconvert: Error decompressing JPEG: unknown huffman code: (and similar numbers), so the support does not seem perfect yet. But it is much better than nothing. ekiga crashes, whether I use the webcam or not, so I cannot test that. -- Logitech Quickcam E2500 not supported https://bugs.launchpad.net/bugs/326674 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 364319] Re: pstoedit cannot convert to SVG any more
Hi Andrew No, actually a rebuild does not change anything for me. I have to install libplot-dev (which is not a build dependency), and then a rebuild will include the plot-* filters. So I think the dependencies need to be changed, probably to include libplot-dev as build dependency, and libplot2c2 as run time dependency, but I may be missing something. -- pstoedit cannot convert to SVG any more https://bugs.launchpad.net/bugs/364319 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 364319] [NEW] pstoedit cannot convert to SVG any more
Public bug reported: Binary package hint: pstoedit pstoedit used to be able to convert to the SVG format with libplot. Now it no longer links against libplot, and so all output formats only available via libplot do not work any more. Example: $ pstoedit -f svg fig.eps pstoedit: version 3.45 / DLL interface 108 (build Jan 21 2009 - release build - g++ 4.3.3 20090119 (prerelease)) : Copyright (C) 1993 - 2007 Wolfgang Glunz Unsupported output format svg Available formats : ... This causes the SVG import in inkscape to fail, so it is a serious problem. This bug may be related to https://bugs.launchpad.net/ubuntu/+source/pstoedit/+bug/343369 . Debian (upstream?) does not have the same problem: http://packages.debian.org/sid/libpstoedit0c2a . About me: I am using an up to date (not quite released) Jaunty installation on AMD64. $ apt-cache policy pstoedit pstoedit: Installed: 3.45-5 Candidate: 3.45-5 Version table: *** 3.45-5 0 500 http://uk.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status $ uname -a Linux nvidia 2.6.28.4 #3 SMP Fri Feb 13 13:27:27 GMT 2009 x86_64 GNU/Linux ** Affects: pstoedit (Ubuntu) Importance: Undecided Status: New -- pstoedit cannot convert to SVG any more https://bugs.launchpad.net/bugs/364319 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 238580] Re: LyX should recommend epstopdf for EPS support
I had more trouble with eps images in the pdflatex backend, and that is despite using epstopdf. So I think there is more to this bug than meets the eye. It is probably an upstream issue with LyX 1.6. -- LyX should recommend epstopdf for EPS support https://bugs.launchpad.net/bugs/238580 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
Thanks for the patch, I will try that once I have some time for it. And I hope I can answer at least some of the questions: > - Precisely, which device was this? Excellent question, but it is part of a media TV branded "optronix" (but made by amazepc, at least the board), so I am not quite sure. The remote says "optronix", and the chip inside is marked "EM78P447SAM-G", which seems like Samsung. I may be able to disassemble the receiver, and see whether anything is printed on the board or the controller chip. I thought it was Samsung, but I admit this may not be the case. > - Can you please also please provide "lsusb -v" without connected daemon? I tried it without X server and without any kernel module, but I get the same result. I think there is a syntactical error in the descriptor, and the kernel seems to be able to work around it (see the kernel log), but lsusb -v just ignores that part. > please doublecheck whether usage code 0224 is really contained twice in the report descriptor That is what the kernel says, and it also appears twice in the hex dump. > do the supported remote keys match exactly with the kernel mapping No, not quite. I have to check the exact matching, but it seemed to be made for a remote control with different labels: the keys would make sense the way the kernel interprets them, but it is not how the control is labeled. > One of these points might explain why 3 keys are missing. Yes, I am still puzzled by these. I have heard reports that Windows has the same problem, but I did not really manage to get it to work, so I cannot confirm that. Is there a way to trace the USB data stream, instead of using the raw hid device? -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 238580] Re: LyX should recommend epstopdf for EPS support
> Probably reporting it to upstream (Debian) would help getting this into Ubuntu. I checked Debian sid / unstable, and lyx does pull in epstopdf. So I think this bug does not apply to Debian. This is why: [code] $ aptitude why texlive-extra-utils i lyx Recommends texlive-latex-recommended i A texlive-latex-recommended Recommends prosper (>= 1.00.4+cvs.2006.10.22-1) i A prosper Dependstexlive-pstricks i A texlive-pstricks Recommends texlive-extra-utils [/code] Now in Ubuntu jaunty, the texlive-latex-recommended does not depend on prosper, and I think therefore texlive-pstricks is not pulled in. Ok, arguable lyx should depend on texlive-extra-utils directly, but there is no reason to change it in Debian. Of course there is another bug involved here: why does ps2pdf not work properly? And should it? -- LyX should recommend epstopdf for EPS support https://bugs.launchpad.net/bugs/238580 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 238580] Re: LyX should recommend epstopdf for EPS support
I have just been bitten by this bug, and I think it deserves more attention. I would argue that this should be fixed, and installing lyx should pull in epstopdf automatically (require it). The reason is simple: EPS is the standard format for including graphics, PDF is the standard output format for LyX (using pdflatex as a backend), and I guess we all agree that including graphics is an important function of LyX. Without epstopdf, it just does not work correctly, so much so that it is essentially useless. In my book, that ticks all the boxes for being a requirement. I also have to say that even after installing it, I had to fiddle with LyX for a while to get it right. A simple reconfigure did not do the job for some reason (even after I deleted an old manual conversion entry). All the more reason to get it right from the beginning. -- LyX should recommend epstopdf for EPS support https://bugs.launchpad.net/bugs/238580 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 343548] Re: [sync] lyx_1.6.2-1/unstable into jaunty
Thanks a lot! It solves the freezing problem that Reinhard describes for me. -- [sync] lyx_1.6.2-1/unstable into jaunty https://bugs.launchpad.net/bugs/343548 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 326583] Re: Freezes with K8M890 and openchrome driver
Hi Bartosz Yes, I just tried it (I think I did it before, but I may not have installed the DRM LKM). Anyway, the effect is very much the same, which is not surprising given that the same offending statement is in via_dma.c. Are you using AMD64 (or x86_64 in new speak)? That may be part of the problem, although I fail to see how it would make a difference. Did you try XV? I think the problem is very much related to an application opening an XV port, although it could be another part of mythtv. And I am not sure whether there are different versions of the K8M890. lspci says about mine: 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 01) Subsystem: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16 Memory at c000 (32-bit, prefetchable) [size=256M] Memory at dd00 (32-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at de00 [disabled] [size=64K] Capabilities: [60] Power Management version 2 Capabilities: [70] AGP version 3.0 or numeric: 01:00.0 0300: 1106:3230 (rev 01) Subsystem: 1106:3230 -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "xinput query-state when the key is stuck" http://launchpadlibrarian.net/22301318/xinput-query-state-3.log.gz -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "lsusb" http://launchpadlibrarian.net/22301307/lsusb-v.log -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "kernel log: HID descriptor" http://launchpadlibrarian.net/22301280/kern.log.gz -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "modprobe options (disable some of the quirks)" http://launchpadlibrarian.net/22301298/options -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "sanitized/cooked HID stream (with patch)" http://launchpadlibrarian.net/22301276/hiddev-after.dump -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "sanitized/cooked HID stream (without patch)" http://launchpadlibrarian.net/22301275/hiddev-before.dump -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "raw HID stream" http://launchpadlibrarian.net/22301257/hidraw.dump -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] Re: Key stuck with Samsung IR remote (USB 0419:0001)
** Attachment added: "fixing patch?" http://launchpadlibrarian.net/22301251/hid-core.patch -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326986] [NEW] Key stuck with Samsung IR remote (USB 0419:0001)
Public bug reported: I have a Samsung IR remote that should work as a USB HID device. I need to do some tweaking with modprobe options in /etc/modprobe.d/options to get it recognised (see options), and then it mostly works. However, once I press one of the upper keys, the X server becomes unresponsive. Unloading and reloading the LKM hiddev solves the issue, until one of the offending keys is pressed. Using xinput from a remote system, I was able to figure out that X becomes unresponsive because it thinks that key 123 is still pressed (see xinput-query-state-3.log.gz). I looked further into this, and I found that the HID input layer creates this effect. For one key press, the trace from the device looks normal (see rawhid.dump), but the "sanitized" version (see hiddev-before.dump) shows a key press event for e9 at the end. I am no expert of the HID spec, but it seems that the device uses a seriously broken definition. I turned on HID debugging to get this definition (see kern.log.gz). Field 4 has an offset of 0, so the first key becomes indistinguishable from no key press - and the kernel gets confused by this. I had a go at this problem, and the patch (see hid-core.patch) fixes the problem for me. The new output does not have the spurious key press event (see hiddev-after.dump). Now I am not sure that this is a best fix, or that it has no side effect, but it works for me. Maybe it would be better to raise the minimum? And even with this fix, there are three buttons that I cannot get to works. But I have been tracing the USB connection, and I cannot figure out how they could possibly work, so I will leave that for now. My system is an up to date Ubuntu 8.10 AMD64, running kernels from 2.6.27-7 down to -11 (with the same problem). The Samsung remote must be a different model from the one the kernel quirk refers to, because the definition looks very different from what the quirk is dealing with. Maybe Samsung tried to fix the earlier issues, but they introduced a new one. Of course it is a shame that the USB ID is still the same. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- Key stuck with Samsung IR remote (USB 0419:0001) https://bugs.launchpad.net/bugs/326986 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 326674] Re: Logitech Quickcam E2500 not supported
** Description changed: I recent bought the Logitech Quickcam E2500, which is budget webcam. It is not supported under Ubuntu 8.10 (AMD64). The fix is trivial, and the risk is essentially zero. So I propose that the patch is applied as an update. The patch is already applied upstream: http://www.mail-archive.com/linuxtv-comm...@linuxtv.org/msg02282.html lsusb says: Bus 001 Device 004: ID 046d:089d Logitech, Inc. and uname -a: Linux mythtv 2.6.27-11-generic #1 SMP Fri Feb 6 15:47:26 GMT 2009 x86_64 GNU/Linux (this is my modified version, with the patch) + + There is a related bug, but it is concerned with the old (V4L1 ?) + driver: https://bugs.launchpad.net/ubuntu/+source/gspca/+bug/273727 . -- Logitech Quickcam E2500 not supported https://bugs.launchpad.net/bugs/326674 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 326674] [NEW] Logitech Quickcam E2500 not supported
Public bug reported: I recent bought the Logitech Quickcam E2500, which is budget webcam. It is not supported under Ubuntu 8.10 (AMD64). The fix is trivial, and the risk is essentially zero. So I propose that the patch is applied as an update. The patch is already applied upstream: http://www.mail-archive.com/linuxtv-comm...@linuxtv.org/msg02282.html lsusb says: Bus 001 Device 004: ID 046d:089d Logitech, Inc. and uname -a: Linux mythtv 2.6.27-11-generic #1 SMP Fri Feb 6 15:47:26 GMT 2009 x86_64 GNU/Linux (this is my modified version, with the patch) ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- Logitech Quickcam E2500 not supported https://bugs.launchpad.net/bugs/326674 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 310824] Re: opreport crashes with "error: basic_string::erase"
I am using the AMD64 version of Ubuntu 8.10, and I have run into exactly the same problem. The patch fixes it for me, although I have no idea whether there are any side effects. Another strange issue that I observed is that I cannot compile the version for 8.10 (oprofile_0.9.3-1.1ubuntu2.dsc) on 8.10. I get bfd_support.cpp:86: error: 'strlen' was not declared in this scope which according to google is an issue with gcc 4.3. The source package from 9.04 to be (oprofile_0.9.3-2ubuntu1.dsc) compiles fine. -- opreport crashes with "error: basic_string::erase" https://bugs.launchpad.net/bugs/310824 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 158999] Re: openchrome driver unable to find video mode
Since I have been digging in the VIA driver, I have a few suggestions. Is there any chance to get a stack trace? Can you enable debug=1 for the drm kernel module? (as root: /etc/init.d/gdm stop ; rmmod via ; rmmod drm ; insmod /lib/module/linux-2.6.27-11-generic/drivers/gpu/drm/drm.o debug=1; modprobe via ; /etc/init.d/gdm start) Can you try the patch attached to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326583 ? Can you try with a 64bit installation (Ubuntu 8.10/amd64)? I found that it magically nearly works under 64bit. -- openchrome driver unable to find video mode https://bugs.launchpad.net/bugs/158999 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 326583] Re: Freezes with K8M890 and openchrome driver
** Description changed: I am using Ubuntu 8.10 AMD64 with openchrome on a VIA K8M890 board, using the on board graphics VIA Chrome9 HC. This is working fine, except that during the startup of graphical applications, the system would freeze for about 5 seconds at a time. I have now found the cause of these freezes, and I think I have a fix. The bug is in via_wait_idle(), in the DRM module via.ko. This function (I assume) is supposed to wait until the GPU is idle. First it waits for the GPU to become busy, but this may never happen. It then times out, but that causes the observed freeze of the system. The statement to wait for the GPU to become busy was introduced in 2.6.22, http://www.linuxhq.com/kernel/v2.6/21-git13/drivers/char/drm/via_dma.c to be precise. I assume that there is a reason for this change (maybe the routine is sometimes called before the GPU is marked as busy), but even then it is not the correct solution. Now one of the problems is that this first bug interacts with a second one: the timeout of via_wait_idle() is ignored in via_driver_dma_quiescent(). The return value indication a timetout is -1, but the check assumes it would be 0. The combination of both bugs means that we do not want to handle timeouts caused by the GPU being already idle. And I am not even sure whether we want to handle timeouts at all: it would be a good idea, but the code so far does not. Anyway, I have a patch below that fixes the two bugs, explains what is going on, and most of all works for me. I would be interested to here how it works for other people. (To be honest I could not get openchrome to work under i386 on my system, but maybe somebody has more luck.) One of the annoying aspects of this bug is that there is no error message anywhere. I think this is because DRM does not usually log error messages, and because the return code of via_wait_idle() is handled incorrectly. If I enable debugging with insmod drm.ko debug=1, I get the lines attached as dmesg.log, indicating that the patch is working as intended. + + This bug may be related to https://bugs.launchpad.net/ubuntu/+source + /xserver-xorg-video-openchrome/+bug/158999, because that is probably + caused by the same patch set in linux 2.6.22. This may even be the + solution, but I cannot test that. -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] Re: Freezes with K8M890 and openchrome driver
** Attachment added: "version.log" http://launchpadlibrarian.net/22079081/version.log -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] Re: Freezes with K8M890 and openchrome driver
** Attachment added: "uname-a.log" http://launchpadlibrarian.net/22079074/uname-a.log -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] Re: Freezes with K8M890 and openchrome driver
** Attachment added: "dmesg.log.gz" http://launchpadlibrarian.net/22079070/dmesg.log.gz -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] Re: Freezes with K8M890 and openchrome driver
** Attachment added: "lspci-vvnn.log.gz" http://launchpadlibrarian.net/22079071/lspci-vvnn.log.gz -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] Re: Freezes with K8M890 and openchrome driver
** Attachment added: "proposed fix" http://launchpadlibrarian.net/22079064/via_dma.patch -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 326583] [NEW] Freezes with K8M890 and openchrome driver
Public bug reported: I am using Ubuntu 8.10 AMD64 with openchrome on a VIA K8M890 board, using the on board graphics VIA Chrome9 HC. This is working fine, except that during the startup of graphical applications, the system would freeze for about 5 seconds at a time. I have now found the cause of these freezes, and I think I have a fix. The bug is in via_wait_idle(), in the DRM module via.ko. This function (I assume) is supposed to wait until the GPU is idle. First it waits for the GPU to become busy, but this may never happen. It then times out, but that causes the observed freeze of the system. The statement to wait for the GPU to become busy was introduced in 2.6.22, http://www.linuxhq.com/kernel/v2.6/21-git13/drivers/char/drm/via_dma.c to be precise. I assume that there is a reason for this change (maybe the routine is sometimes called before the GPU is marked as busy), but even then it is not the correct solution. Now one of the problems is that this first bug interacts with a second one: the timeout of via_wait_idle() is ignored in via_driver_dma_quiescent(). The return value indication a timetout is -1, but the check assumes it would be 0. The combination of both bugs means that we do not want to handle timeouts caused by the GPU being already idle. And I am not even sure whether we want to handle timeouts at all: it would be a good idea, but the code so far does not. Anyway, I have a patch below that fixes the two bugs, explains what is going on, and most of all works for me. I would be interested to here how it works for other people. (To be honest I could not get openchrome to work under i386 on my system, but maybe somebody has more luck.) One of the annoying aspects of this bug is that there is no error message anywhere. I think this is because DRM does not usually log error messages, and because the return code of via_wait_idle() is handled incorrectly. If I enable debugging with insmod drm.ko debug=1, I get the lines attached as dmesg.log, indicating that the patch is working as intended. This bug may be related to https://bugs.launchpad.net/ubuntu/+source /xserver-xorg-video-openchrome/+bug/158999, because that is probably caused by the same patch set in linux 2.6.22. This may even be the solution, but I cannot test that. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Freezes with K8M890 and openchrome driver https://bugs.launchpad.net/bugs/326583 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 81567] Re: [apport] skencil.py crashed with SIGSEGV in free()
Hi I have been rather annoyed with this bug for a while, because sketch/skencil is my favorite drawing program for more complex things. And it seems that I have found a work around short of recompiling, although it is certainly not for anyone faint of heart. 1. Remove skencil. 2. Install python2.4. 3. Download skencil_0.6.17-7_i386.deb from Ubuntu 6.10 and install it with dpkg. This shows a conflict in the python version. 4. Edit /var/lib/dpkg/status to delete the conflict: just remove the entry "python (<< 2.5), " in skencil. 5. Edit /usr/bin/skencil to start /usr/bin/python2.4 instead of /usr/bin/python. (skencil should now work!) 6. Use dselect to put a hold on skencil. (is there an easier way to do this?) Note that this does make changes to your packaging system. If you make a mistake, you may have to reinstall your system. When the workaround is no longer needed, the changes should go away once you remove the hold flag and upgrade. -- [apport] skencil.py crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/81567 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
