[Bug 317499] Re: Blank viewport - cannot capture
** Changed in: cheese (Ubuntu) Status: New => Fix Released -- Blank viewport - cannot capture https://bugs.launchpad.net/bugs/317499 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 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)
Okay, today i gave Fedora another try and Cheese also failed there. So it looks like this is a very unfortunate situation with my particular setup. My Webcam always needs a little longer to initialize when it is plugged in and no driver was previously loaded, but other applications have no problem with that. It might be a firmware bug or just the the way my cam is probed by cheese. I don't know. However, it is an issue and i can always reproduce by the following steps: - unplug the cam - sudo rmmod uvcvideo - plug the cam - start cheese 'cheese -v' doesn't show any errors because the probe fails gracefully after the 10 second period. uvcvideo trace logs don't show any errors because the driver is only waiting for the first data to arrive. So everything works as long as the camera initialization isn't interrupted - which is the case with my webcam and it's ridiculous 16 second init time. :) I realize that there is still some error elsewhere - maybe in cheese, gstreamer or the driver - but with no error messages in either the cheese logs, or the uvcvideo traces i am at the moment unable to debug this any further. I will do some more research though. Meanwhile, I would love to see the workaround in the attached patch ( 91_raise_timeout.patch ) included in cheese for karmic. It simply raises the probing timeout from 10 to 30 seconds. This patch should not affect working cameras. However, cameras with a probing time similar to mine ( >10sec. ) will have some more time to initialize and thus get detected correctly by cheese. ** Attachment added: "Raises the probing timeout of cheese to 30 seconds" http://launchpadlibrarian.net/30654339/91_raise_timeout.patch -- cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards) https://bugs.launchpad.net/bugs/290506 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 290506] Re: cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards)
This bug still affects me in Ubuntu Karmic. Compiling the latest driver from http://linuxtv.org/hg/~pinchartl/uvcvideo makes no difference. Basically, every tool (skype, ekiga, luvcview, gst-launch v4l2src ! xvimagesink, ...) except Cheese works fine. Cheese fails to detect the webcam due to extremely long probing times (~16 seconds on my machine for the first access after a freshly loaded uvcvideo module - either through a reboot, or by hand via rmmod/modprobe), and when the cam light finally comes up, cheese already has given up (happens after 10 seconds - this is hardcoded in cheese). When that happens, the state of the webcam/uvcvideo seems to be corrupted somehow. Any access to the webcam with any tool, either cheese or somethig else, fails afterwards. The only fix then is to rmmod/modprobe uvcvideo again. After doing that, the webcam works correct - even in cheese ( ~2-4 seconds probing time ). Raising the hardcoded timeout in src/cheese-webcam.c from 10 to 30 seconds seems to be a good workaround that works most of the time for me, but it is not a real solution to the problem at hand. I tried to reproduce the bug with an Fedora 11 LiveCD, but there everything went fine. Probes to the cam never lasted longer than 2 seconds and the image was always displayed instantly after that. Accessing the cam with other tools after cheese 'initialized' the driver went fine too. So is anyone else still having problems? -- cheese malfunctioning with UVCVIDEO webcams (was cheese doesn't show v4l2 video output and disables output on gstreamer-based apps ran afterwards) https://bugs.launchpad.net/bugs/290506 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 366716] Re: Supertuxkart give me a lot of problems with music using jaunty
*** This bug is a duplicate of bug 192573 *** https://bugs.launchpad.net/bugs/192573 On some hardware configurations, openal-soft doesn't work with the default alsa backend and pulseaudio. A workaround is to switch the backend to oss. To do that, create a file named ".alsoftrc" in your home directory and put "drivers = oss" in it. -- Supertuxkart give me a lot of problems with music using jaunty https://bugs.launchpad.net/bugs/366716 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 115275] Re: Random kernel crash/freeze in Feisty
Sistofe, the system runs stable today! There was no single crash or freeze, which i didn't have for a long time now. I am sure the problem is powernowd. Thank you very much for the tip. If you have any further questions or you want me to do something - shoot! -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 115275] Re: Random kernel crash/freeze in Feisty
Okay. I did the change described above and all i can say for now is that the next boot after the change, the system came up without problems. It is also running stable for more than 30 minutes now. Unfortunately that doesn't mean anything because sometime, after 10 - 20 crashes, if the system ran stable for more than ~30 minutes, it will run stable for the rest of the day. So, to answer your question, it seems to have something to do with powernowd, because today i had only 3 crashes before i did the change. Compared to the usual behaviour, this is a suprising low crash rate! Though i can only provide a correct answer in about 24 hours from now on. It may be interesting to hear the results of other people in here. Thanks for the suggestion. I keep my fingers crossed! -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 115275] Re: Random kernel crash/freeze in Feisty
Hi Sitsofe, the CPU is an Intel P4 3Ghz HT. Motherboard is a Gigabyte 8KNXP Rev. 1. There is no cool 'n quiet function in the BIOS. -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 115275] Re: Random kernel crash/freeze in Feisty
** Changed in: linux-source-2.6.20 (Ubuntu) Status: Unconfirmed => Confirmed -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 76003] Re: Starting Wengophone does produce a Kernel oops entry in Syslog
Newer packages are available for wengophone. This bug doesn't apply anymore. ** Changed in: wengophone (Ubuntu) Status: Unconfirmed => Fix Released -- Starting Wengophone does produce a Kernel oops entry in Syslog https://bugs.launchpad.net/bugs/76003 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 115275] Re: Random kernel crash/freeze in Feisty
The logfiles ** Attachment added: "various info- and logfiles" http://librarian.launchpad.net/7687460/logs.tar.bz2 -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 115275] Random kernel crash/freeze in Feisty
Public bug reported: Binary package hint: linux-source-2.6.20 The current installed kernel freezes/crashes at "random" times. The bug is triggered without any user interaction. There are more people having a similar problem discussing the issue at http://ubuntuforums.org/showthread.php?t=412125 Things i observed while investigating are: - It is definitely a 2.6.20 thing. Edgy doesn't crash on the same machine - Seems to have nothing to do with proprietary NVIDIA drivers because the crash also happens with the "nv" driver enabled. Even a stock Feisty LiveCD crashed. - Disabling every hardware component & feature in the BIOS, one at a time, has no effect. Crashes would still happen - Booting with various kernel flags mentioned in the above thread didn't help ( noapic, assign-busses ... ) - The machine freezes/crashes 10-20 times per day! - Once the machine didn't crash for longer than ~30min, it would run stable for the rest of the day - I noticed that many people on launchpad have problems with their SAMSUNG (TSSTCorp) DVD-Burner, which i also have. One guy posted that he could fix the error with a firmware update of the burner ( https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/64587/comments/16 ). So today i updated my drives firmware to the latest version, but the crash is still there. I even disabled the drive in the BIOS to see if the crash is directly linked to it, but the situation is the same. I managed to get some debug output via ALT+SysRq+1 & ALT+SysRq+T, which i will attach to this report. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Random kernel crash/freeze in Feisty https://bugs.launchpad.net/bugs/115275 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 105907] Re: [needs-packaging]cinelerra
Please note that there are two versions of Cinelerra. The original tree, which can be found at the URL mentioned above ( http://heroinewarrior.com/cinelerra.php3 ), and the community version, which can be found at http://cvs.cinelerra.org The community version has their own repository with packages for ubuntu feisty. See http://cvs.cinelerra.org/getting_cinelerra.php for instructions on how to get these. Getting Cinelerra into the official repositories might be as easy as just taking the existing ones from this site. -- [needs-packaging]cinelerra https://bugs.launchpad.net/bugs/105907 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 104194] [needs-packaging] Linux UVC USB Video Class device driver
Public bug reported: An essential driver to have that supports many Webcams (and later generic video devices) out there. Please have a look at http://linux-uvc.berlios.de for more information. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Tags: needs-packaging -- [needs-packaging] Linux UVC USB Video Class device driver https://bugs.launchpad.net/bugs/104194 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 104191] [needs-packaging] AVM Fritz! WLAN USB Driver
Public bug reported: This is a very popular WLAN USB Stick in Germany and it would be great if it worked OOB for Ubuntu Users. As far as i can tell there is a LGPL-, and a proprietary part of the driver, so it is very much like the nvidia drivers. There are already some restricted drivers for some older hardware components of this manufacturer available in the repositories ( avm-fritz-firmware ). To get a rough overview of the popularity of this hardware, go to http://www.ubuntuusers.de and search the forum for "fritz wlan usb". ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed ** Tags: needs-packaging -- [needs-packaging] AVM Fritz! WLAN USB Driver https://bugs.launchpad.net/bugs/104191 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 76003] Re: Starting Wengophone does produce a Kernel oops entry in Syslog
Adding the syslog entry ** Attachment added: "The syslog entry" http://librarian.launchpad.net/5423703/syslog.txt -- Starting Wengophone does produce a Kernel oops entry in Syslog https://launchpad.net/bugs/76003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76003] Starting Wengophone does produce a Kernel oops entry in Syslog
Public bug reported: Binary package hint: wengophone Wengophone crashes immediately after start and produces some Syslog entrys stating that the Kernel crashed. I get this behaviour everytime i try to start Wengophone. Up to date Ubuntu Feisty i386 (06.12.16) NVIDIA Quadro FX 3000/AGP/SSE2 with the proprietary driver Version 96.29 ** Affects: wengophone (Ubuntu) Importance: Undecided Status: Unconfirmed -- Starting Wengophone does produce a Kernel oops entry in Syslog https://launchpad.net/bugs/76003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71277] Crash when viewing formatted text
Public bug reported: Binary package hint: nvidia-glx The NVIDIA driver crashes when viewing a syntax highlighted text that has very long lines. I am able to reproduce this bug by the following steps: 1) Open Firefox and go to http://maps.google.com 2) press CTRL+U to view the sourcecode of that site 3) grab the horizontal scrollbar and scroll around the sourcecode the same happens with Epiphany, even if epiphany uses Gedit to view the source 1) Open Epiphany and go to http://maps.google.com 2) press CTRL+U Using the newer 9000 series nvidia-glx from albertomilone.com seems to fix this issue. Ubuntu 6.10, Pentium 4, NVIDIA Quadro FX 3000 ** Affects: linux-restricted-modules-2.6.19 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Crash when viewing formatted text https://launchpad.net/bugs/71277 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
