[Bug 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)
Thanks for reporting this The Bright Side, but this issue is much bigger than darktable. The fact that clinfo gives a weird error is a good indicator that this is a very general problem, not related to any user-land programs. The reason I found it (again, thanks) was that I have a problem with boinc- client. As soon as I upgraded to 14.04, boinc-client stopped being able to detect any OpenCL resources. This is an OpenCL driver problem with the nVidia drivers. I think this is link is relevent, which says to install nVidia drivers manually: https://devtalk.nvidia.com/default/topic/734098/linux/-boinc-ubuntu- nvidia-no-usable-gpus-found-/ I'm just trying to figure out if that is worth doing or if Ubuntu folks are going to fix it soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311362 Title: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081831] Re: Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation
Output of commands requested by someone: cat /proc/version_signature Ubuntu 3.0.0-25.41-generic-pae 3.0.40 lspci -vnvn (see attached) ** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1081831/+attachment/3449410/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081831 Title: Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1081831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081831] Re: Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation
Today, we upgraded to 12.04 LTS, which installed kernel 3.2.0.0-34, resolving the issue. As far as I know, however, 11.10 is still affected. To jsalisbury, I didn't try that far upstream, but I think the answer is 'yes', upstream is fixed as 3.2.0.0-34 does not exhibit this issue. To brad-figg, I'm sorry I wasn't able to submit more data using apport. Didn't have my launchpad account with me when I was working on the system. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081831 Title: Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1081831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081831] [NEW] Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation
Public bug reported: Since kernel 3.0.0-26 update was released, the system displays garbled video after switching to graphic mode and X11. I have been hoping subsequent updates would resolve the issue, but after each upgrade, I must boot an older kernel (-25) and reconfigure GRUB menu to boot the older one by default. 3.0.0-25 is now the oldest, last kernel listed and the next upgrade will remove the only kernel that is working on my system. I'm using VMWare Workstation 7.1.4 build-385536 . ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oneiric ** Description changed: Since kernel 3.0.0-26 update was released, the system displays garbled video after switching to graphic mode and X11. I have been hoping subsequent updates would resolve the issue, but after each upgrade, I - must boot and old kernel and reconfigure GRUB menu to boot an older - kernel. 3.0.0-25 is now the oldest, last kernel listed and the next - upgrade will remove the only kernel that works. + must boot an older kernel (-25) and reconfigure GRUB menu to boot the + older one by default. 3.0.0-25 is now the oldest, last kernel listed + and the next upgrade will remove the only kernel that is working on my + system. - I'm using VMWare Workstation 7.1.4 build-385536 + I'm using VMWare Workstation 7.1.4 build-385536 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081831 Title: Video errors on Ubuntu 11.10 Kernels =3.0.0-26 + VMware Workstation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1081831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490154] Re: orage aborts when Today view is selected
Yes, when I originally reported this bug, it happened every time. It no longer occurs, however. I've been avoiding this feature since I reported this problem, so I cannot say when it was fixed. But, it's definitely gone. I can open the Today view reliably, now. -- orage aborts when Today view is selected https://bugs.launchpad.net/bugs/490154 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 493021] [NEW] gnusound crashes immediately on startup: *** buffer overflow detected ***: /usr/bin/gnusound.real terminated
Public bug reported: Binary package hint: gnusound I just installed gnusound, but it immediately fails when started from the command line or menu. It *does not* kill or crash XWindows, however, as reported by several others. I noticed this problem back in Hardy Heron, I think, and it still hasn't been fixed. Unlike before, however, I have to kill the process; it doesn't completely die on it's own. Seems like the problem is getting worse, not better. I'm not sure what happen to crash files, they must be disabled now-a-days, but I would produce one if required. Here is the STDERR data: gnusound sample_init:642: Using plain C minmax module_init:218: collecting modules in path modules module_init:220: expansion 0: modules module_init:218: collecting modules in path ~/.gnusound/modules module_init:220: expansion 0: /home/pdestefa/.gnusound/modules module_init:218: collecting modules in path /usr/lib/gnusound/modules module_init:220: expansion 0: /usr/lib/gnusound/modules file_register_driver:127: registered AudioFile FAIL : src/module.c:module_load:113: no manifest in /usr/lib/gnusound/modules/file_ffmpeg.so FAIL : src/module.c:module_load:113: no manifest in /usr/lib/gnusound/modules/file_flac.so FAIL : src/module.c:module_load:113: no manifest in /usr/lib/gnusound/modules/file_gmerlin_avdec.so FAIL : src/module.c:module_load:113: no manifest in /usr/lib/gnusound/modules/file_lame.so file_register_driver:127: registered sndfile ladspa_init:1420: collecting GLADSPA plugins in path /usr/lib/ladspa/ player_register_driver:1373: registered player driver ALSA player_register_driver:1373: registered player driver JACK player_register_driver:1373: registered player driver OSS player_register_driver:1373: registered player driver Dummy player_init:1402: initializing audio driver OSS dialog_init:138: creating dialog preferencesdialog (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated mixer_buffers_alloc:894: mixer buffers allocated: muxbuf: 65536 by...@0xc3ac00, srcbufs: 2048 bytes (* 32) (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnusound.real:10460): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated *** buffer overflow detected ***: /usr/bin/gnusound.real terminated === Backtrace: = /lib/libc.so.6(__fortify_fail+0x37)[0x7f9163b585f7] /lib/libc.so.6[0x7f9163b575a0] /lib/libc.so.6[0x7f9163b56c9b] /lib/libc.so.6(__snprintf_chk+0x7a)[0x7f9163b56b6a] /usr/bin/gnusound.real(draw_mixer_sliders+0x266)[0x42b006] /usr/bin/gnusound.real(draw_mixercanvas+0xb6)[0x42b8e6] /usr/bin/gnusound.real(view_mixercanvas_expose_event+0x16)[0x4496c6] /usr/lib/libgtk-x11-2.0.so.0[0x7f91651d5728] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f91644c55ae] /usr/lib/libgobject-2.0.so.0[0x7f91644da983] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x68c)[0x7f91644dbbcc] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f91644dc283] /usr/lib/libgtk-x11-2.0.so.0[0x7f91652dc72f] /usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x4b3)[0x7f91651cef63] /usr/lib/libgdk-x11-2.0.so.0[0x7f9164e303da] /usr/lib/libgdk-x11-2.0.so.0[0x7f9164e30387] /usr/lib/libgdk-x11-2.0.so.0[0x7f9164e27be1] /usr/lib/libgdk-x11-2.0.so.0(gdk_window_process_all_updates+0x131)[0x7f9164e299c1] /usr/lib/libgtk-x11-2.0.so.0[0x7f916514dbe1] /usr/lib/libgdk-x11-2.0.so.0[0x7f9164e068c6] /lib/libglib-2.0.so.0(g_main_context_dispatch+0x22e)[0x7f9164027bbe] /lib/libglib-2.0.so.0[0x7f916402b588] /lib/libglib-2.0.so.0(g_main_loop_run+0x1a5)[0x7f916402b9e5] /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7f91651cf177] /usr/bin/gnusound.real(arbiter_run+0x95)[0x44ffd5] /usr/bin/gnusound.real(main+0x2bd)[0x45043d] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f9163a7fabd] /usr/bin/gnusound.real[0x414ff9] === Memory map: 0040-00467000 r-xp fc:01 104653 /usr/bin/gnusound.real 00666000-00667000 r--p 00066000 fc:01 104653 /usr/bin/gnusound.real 00667000-0066b000 rw-p 00067000 fc:01 104653 /usr/bin/gnusound.real 0066b000-0066e000 rw-p 00:00 0 00a0c000-00d93000 rw-p 00:00 0 [heap] 7f913eacb000-7f913eb2b000 rw-s 00:09 986382380 /SYSV (deleted) 7f913eb2b000-7f913ebb7000 r--p fc:01 262277
[Bug 493021] Re: gnusound crashes immediately on startup: *** buffer overflow detected ***: /usr/bin/gnusound.real terminated
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36488194/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/36488195/XsessionErrors.txt -- gnusound crashes immediately on startup: *** buffer overflow detected ***: /usr/bin/gnusound.real terminated https://bugs.launchpad.net/bugs/493021 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 490154] [NEW] orage aborts when Today view is selected
Public bug reported: Binary package hint: orage Right-click on Orage in system tray, choose Today. This causes Orage to crash. This view used to work fine, but I recently upgraded to XUbuntu 9.10 Karmic Koala. The following is the output from orage, including a backtrace: ... ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** (orage:12286): WARNING **: get_alarm_data: Unknown ACTION (10003) i n alarm. Ignoring ALARM. ** Message: Orage **: Build alarm list: Added 21 alarms. Processed 54 events. ** Message: Orage **: Found 142 alarms of which 62 are active. (Sear ched 44 recurring alarms.) *** glibc detected *** orage: free(): invalid pointer: 0x01e04 3b1 *** === Backtrace: = /lib/libc.so.6[0x7f618e55edd6] /lib/libc.so.6(cfree+0x6c)[0x7f618e56370c] orage[0x416f78] /usr/lib/libgtk-x11-2.0.so.0(gtk_tree_view_column_cell_set_cell_data+0 x193)[0x7f618fb7c623] /usr/lib/libgtk-x11-2.0.so.0[0x7f618fb747cb] /usr/lib/libgtk-x11-2.0.so.0[0x7f618fb761f5] /usr/lib/libgtk-x11-2.0.so.0[0x7f618fb762c2] /usr/lib/libgtk-x11-2.0.so.0[0x7f618fb76359] /usr/lib/libgdk-x11-2.0.so.0[0x7f618f4908c6] /lib/libglib-2.0.so.0(g_main_context_dispatch+0x22e)[0x7f618e893bbe] /lib/libglib-2.0.so.0[0x7f618e897588] /lib/libglib-2.0.so.0(g_main_loop_run+0x1a5)[0x7f618e8979e5] /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7f618fa7b177] orage[0x428448] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f618e507abd] orage[0x40b5c9] === Memory map: 0040-0046d000 r-xp fc:01 320224 /usr/bin/orage 0066d000-0066f000 r--p 0006d000 fc:01 320224 /usr/bin/orage 0066f000-0067a000 rw-p 0006f000 fc:01 320224 /usr/bin/orage 0067a000-0067b000 rw-p 00:00 0 01a92000-01e31000 rw-p 00:00 0 [heap] 7f617c00-7f617c021000 rw-p 00:00 0 7f617c021000-7f618000 ---p 00:00 0 7f6183695000-7f61836ab000 r-xp fc:01 335915 /lib/libgcc_s.so.1 7f61836ab000-7f61838aa000 ---p 00016000 fc:01 335915 /lib/libgcc_s.so.1 7f61838aa000-7f61838ab000 r--p 00015000 fc:01 335915 /lib/libgcc_s.so.1 7f61838ab000-7f61838ac000 rw-p 00016000 fc:01 335915 /lib/libgcc_s.so.1 7f61838ac000-7f6183986000 r-xp fc:01 99957 /usr/lib/libasound.so.2.0.0 7f6183986000-7f6183b85000 ---p 000da000 fc:01 99957 /usr/lib/libasound.so.2.0.0 7f6183b85000-7f6183b8b000 r--p 000d9000 fc:01 99957 /usr/lib/libasound.so.2.0.0 7f6183b8b000-7f6183b8c000 rw-p 000df000 fc:01 99957 /usr/lib/libasound.so.2.0.0 7f6183b8c000-7f6183b9 r-xp fc:01 221456 /usr/lib/libcanberra-0.15/libcanberra-alsa.so 7f6183b9-7f6183d8f000 ---p 4000 fc:01 221456 /usr/lib/libcanberra-0.15/libcanberra-alsa.so 7f6183d8f000-7f6183d9 r--p 3000 fc:01 221456 /usr/lib/libcanberra-0.15/libcanberra-alsa.so 7f6183d9-7f6183d91000 rw-p 4000 fc:01 221456 /usr/lib/libcanberra-0.15/libcanberra-alsa.so 7f6183d91000-7f6183da r-xp fc:01 338904 /lib/libbz2.so.1.0.4 7f6183da-7f6183fa ---p f000 fc:01 338904 /lib/libbz2.so.1.0.4 7f6183fa-7f6183fa1000 r--p f000 fc:01 338904 /lib/libbz2.so.1.0.4 7f6183fa1000-7f6183fa2000 rw-p 0001 fc:01 338904 /lib/libbz2.so.1.0.4 7f6183fa2000-7f61840e6000 r-xp fc:01 100281 /usr/lib/libxml2.so.2.7.5 7f61840e6000-7f61842e5000 ---p 00144000 fc:01 100281
[Bug 401588] Re: package libvirt-bin 0.6.1-0ubuntu5.1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
But, in my case, apt-get could not fix the problem. sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up libvirt-bin (0.6.1-0ubuntu5.1) ... addgroup: The group `libvirtd' already exists as a system group. Exiting. * Stopping libvirt management daemon libvirtd [ OK ] * Starting libvirt management daemon libvirtd [fail] invoke-rc.d: initscript libvirt-bin, action start failed. dpkg: error processing libvirt-bin (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: libvirt-bin E: Sub-process /usr/bin/dpkg returned an error code (1) uname -srm Linux 2.6.28-14-generic x86_64 -- package libvirt-bin 0.6.1-0ubuntu5.1 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/401588 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 405081] Re: Long delay between starting to play / stream audio and actual play or disconnect
Okay, thanks for the explanation. -- Long delay between starting to play / stream audio and actual play or disconnect https://bugs.launchpad.net/bugs/405081 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 405081] Re: Long delay between starting to play / stream audio and actual play or disconnect
Look, this is not fixed. My version of Totem and Gstreamer are up-to- date. If you're saying this is a known issue, then mark this as a duplicate of the bug that was fixed and tell me which package version will include the fix. If it's fixed in an upstream build, then the fix needs to be back ported to the stable build. I'm willing to be convinced, but this isn't remotely convincing. What I'm asking for isn't very hard at all. ** Changed in: totem (Ubuntu) Status: Fix Released = New -- Long delay between starting to play / stream audio and actual play or disconnect https://bugs.launchpad.net/bugs/405081 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 405081] Re: Long delay between starting to play / stream audio and actual play or disconnect
I would if I could, but I'm running Jaunty. Did I post this to the wrong place? Why did you test against Karmic? I don't even see a beta release announced. If you need more data, just tell me what to do...in Jaunty. But, it's probably easier to fix if you try it yourself. -- Long delay between starting to play / stream audio and actual play or disconnect https://bugs.launchpad.net/bugs/405081 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 405081] [NEW] Long delay between starting to play / stream audio and actual play or disconnect
Public bug reported: Binary package hint: totem When playing a .wax file with streaming audio content, Totem begins to buffer and then play, but no audio is heard for a long time (in my tests, approximately 2-3 minutes, but read on). I suspect playback isn't really starting until the entire audio clip is buffered, even though the buffering stage has already completed and Totem shows Playing the whole time I am waiting. I discovered this problem when I used the NPR thin web-site (thin.npr.org). Here is an example URL: http://thin.npr.org/dmg.wax?prgCode=MEshowDate=29-Jun-2009mediaPref=WM This URL returns a .wax file: asx version = 3.0 titleNPR's Morning Edition - Monday, June 29, 2009/title abstractmore info at : NPR's Morning Edition Web site/abstract moreinfo href=http://thin.npr.org/templates/rundowns/rundown.php?prgId=3; / PARAM name=ShowPlayList value=true/ entry param name=track value=Array['SEG_NUM'][0] / titleMadoff To Find Out How Long He'll Be In Prison/title authorNPR's Morning Edition - Monday, June 29, 2009/author copyright(c) 2009 NPR/copyright ref href=mms://wm.npr.org/wm.npr.na-central/npr/me/2009/06/20090629_me_01.wma?v1st=F41F264A7616B6D1s_vi=[CS]v1|4A149F86347A-A3A09960BD4[CE]mt=2primaryTopic=1070assignedTopics=1001,1003,1006,1070aggIds=98393250 / ref href=http://wm.npr.org/wm.npr.na-central/npr/me/2009/06/20090629_me_01.wma?v1st=F41F264A7616B6D1s_vi=[CS]v1|4A149F86347A-A3A09960BD4[CE]mt=2primaryTopic=1070assignedTopics=1001,1003,1006,1070aggIds=98393250 / /entry ... Totem loads the URL and the playlist is populated as expected. Then it begins playing the first item in the playlist. There is a short period of buffering and that seem to complete successfully and the buffering progress meter shows as 100% full. Then, Buffering is replaced by Playing, but the audio does *not* begin playing. If one waits about three minutes, the audio will eventually begin playing. It is as if the entire clip is buffered before playback begins. Now, this problem may be connected with other issues. For example, I cannot fast forward these streamed MMS audio clips nor skip ahead in the playlist. If I try to move the Time: slider bar, Totem just goes on to the next playlist item, which fails, eventually, after the long delay described earlier. This time, however, an error is displayed in a dialog box: Disconnected: OK. On STDERR, there is this message: (totem:6572): Gtk-WARNING **: Radio group does not contain an action with value '-2' ** Message: Error: Disconnected: OK pulsesink.c(451): gst_pulsesink_is_dead (): /GstPlayBin:play/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin5/GstAutoAudioSink:autoaudiosink2/GstPulseSink:autoaudiosink2-actual-sink-pulse (This is also what happens if I press the skip button.) This seems like a problem with Totem and Pulseaudio, which is a distinct problem from the one I am reporting. I just wanted to mention it since it occurs coincidentally. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer NonfreeKernelModules: fglrx Package: totem-gstreamer 2.26.1-0ubuntu5 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: totem Uname: Linux 2.6.28-13-generic x86_64 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Long delay between starting to play / stream audio and actual play or disconnect https://bugs.launchpad.net/bugs/405081 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 405081] Re: Long delay between starting to play / stream audio and actual play or disconnect
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/29554845/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/29554846/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/29554847/ProcStatus.txt -- Long delay between starting to play / stream audio and actual play or disconnect https://bugs.launchpad.net/bugs/405081 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 366683] Re: Xubuntu: newly opened windows are no longer placed on front
My apologies. There is, in fact, another recourse. It is possible to use the task bar (which I do not run) or the window list (from the desktop or tray) to locate any window, if you know it's title, already. -- Xubuntu: newly opened windows are no longer placed on front https://bugs.launchpad.net/bugs/366683 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 366683] Re: Xubuntu: newly opened windows are no longer placed on front
Great catch, Matthew. This is the history I was missing on this whole ordeal. Bug 3200 is actually a feature request. In it, the claim is made that new windows popping to the top of of the Z-buffer is a inconvenient and a security risk. Well, obviously, the requester and I disagree on what is inconvenient. But, putting aside this subjective claim, I cannot accept the idea that locating new windows at the bottom of the Z-buffer (window stack) is *more* secure. The bug history show no indication it resulted in a feature change and I see no debate of the validity of this security claim. I don't suppose Z-location has much to do with security, ultimately, since there are probably still ways to hide windows or launch window- less applications. But, if a new window is created, I don't think it placing it below existing windows is a secure option. Isn't it a greater risk to be unable to see newly created windows? Moreover, if a new window goes on top of the stack, you can at least bring your last window to the top immediately with ALT-TAB. Or, you can lower the new window down to the bottom with CTRL-middle-click (or whatever is your hot-key for that action). If new windows go to the bottom, there is no recourse. You have to lower, shade, or minimize all the windows above it to see what happened. Furthermore, there are three Z-buffers, not one. If you want a window to always be on top of new windows that show up on the top of the normal window stack, you can just set the Always above other windows option for that window. I still don't understand the logic of this change in the slightest. I've opened another bug, hoping to have an earnest, open debate. http://bugzilla.xfce.org/show_bug.cgi?id=5581 ** Bug watch added: Xfce Bugzilla #5581 http://bugzilla.xfce.org/show_bug.cgi?id=5581 -- Xubuntu: newly opened windows are no longer placed on front https://bugs.launchpad.net/bugs/366683 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 366683] Re: Xubuntu: newly opened windows are no longer placed on front
Despite the fact this bug was reported (in multiple bug reports), the Xfce team seems to be unmoved. All bugs were closed earlier this week, status: Invalid. Their claim is that this behavior--raise new widows regardless of focus--is incorrect, despite the extremely longstanding nature of this behavior and the fact it was a user configurable behavior. I've been over this many times and I cannot comprehend the unexplained assertion by the Xfce team that the behavior I like is just wrong and was impossible to preserve. This behavior change *might* be a side effect of the following improvement, listed in the 4.6 Changelog: Do not automatically give focus to windows placed on lower layers, but focus those on upper layers at first map. Will the maintainer for this Ubuntu package please help? What are the plans for this bug (in Ubuntu)? -- Xubuntu: newly opened windows are no longer placed on front https://bugs.launchpad.net/bugs/366683 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 316257] Re: [wishlist] merge amd k10 (phemon) support
This request/issue seems old. Didn't a working driver surface about a year ago? Could someone provide more information about when Ubuntu will receive support for the K10 thermal driver? -- [wishlist] merge amd k10 (phemon) support https://bugs.launchpad.net/bugs/316257 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 316257] Re: [wishlist] merge amd k10 (phemon) support
This request/issue seems old. Didn't a working driver surface about a year ago? Could someone provide more information about when Ubuntu will receive support for the K10 thermal driver? -- [wishlist] merge amd k10 (phemon) support https://bugs.launchpad.net/bugs/316257 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 366683] Re: Xubuntu: newly opened windows are no longer placed on front
Second. I find this a serious problem because I use Xfce and XUbuntu mostly for just this feature. I like to be able to click in a window without raising it and I do NOT like pop-up/unexpected windows to steal focus. Xfce makes this possible and I think its perfect. To avoid a religious war, let us all agree that all of these styles are equally valid. Cruncher does a good job explaining why this bug is important, but I just wanted to add that this bug is very new. This behavior is aberrant and I do not think it has anything to do with the settings. New windows should always and have always come to the top of the normal stack space. The meaning of don't-raise-on-focus and don't-focus-new is clear and longstanding. I'd be happy to help if someone could point me in the general direction. -- Xubuntu: newly opened windows are no longer placed on front https://bugs.launchpad.net/bugs/366683 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 356808] Re: Corruption of File Data/Filename w/ Virtual FAT (VFAT)
Granted. I'm sure that's true, but yes, I am using VVFAT for two reasons: (1) it is direct, read/write, host-to-guest file access, and (2) it is the easiest method to transfer files between host and guest. When I first encountered the need to transfer files I had on my host to my VM, I looked for direct methods because it seemed more strait forward. VVFAT worked for small files, which is all I had to move for a long time. Also, I didn't test writes to the VVFAT because I didn't do that much, until recently. After using this feature for a while, I found it to be extremely convenient and useful. Secondly, I found VVFAT much easier to use than the network-based transfer methods. I didn't want to use QEMU's CIFS/SMB/Samba option because it does not allow the use of an alternate Samba configuration file. I didn't want to have to configure /etc/smb.conf just run my VM in user space. (At least, I couldn't figure out how to do it, otherwise.) Similar inconveniences occur using FTP and SSH (which I'm using now, but wouldn't want to at work). Generally speaking, I'm not really using VVFAT as a disk image. I'm using it as a file transfer method. Using an actual disk image would require mounting the disk image in on the host, either via root access, FUSE, or using filesystem editing tools, which are inconvenient. I have created ISO9660 images to import files, which works, but requires creating a new image every time I need to import more files and doesn't support writes, of course. (I don't know how UDF would work on a disk image file. Would that work?) I suppose the next thing I should try is an NTFS-3g filesystem which I could mount with FUSE in my Linux host and natively in my Windows VM. That's still less convenient than VVFAT, however, since I would have to mount/umount the image on the host to get access and the VM would still have to be off. I would still prefer VVFAT to all of these options. I really appreciate your help. Thank you for taking my report seriously. If VVFAT is buggy and cannot be fixed easily, I defer to the judgment of others and ask only that this limitation be well documented in the primary references. But, I'm convinced that a direct, host-to- guest file access scheme is valuable. If there is another solution, I apologize for my ignorance and I would appreciate being pointed in the right direction. -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 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 356808] [NEW] Corruption of File Data/Filename w/ Virtual FAT (VFAT)
Public bug reported: Binary package hint: kvm KVM Version: 1:72+dfsg-1ubuntu6 QEMU Version: 0.9.1-5ubuntu3 Description:Ubuntu 8.10 Release:8.10 File Data and Filename corruption occurs when coping large files to a Virtual FAT (VFAT) drive. I noticed this when copying ISO images between 150MB and 200MB from WindowsXP guest to the Linux host. These ISO images would not boot. Suspecting corruption, I confirmed MD5 hash values of guest and host copies of these ISO images were different. (In fact, the guest OS calculated the correct hashes of the files on the VFAT drive after copying.) Also, filename corruption also occurred. For example, the VFAT directory on the host contained the file pebuilder3110a.zip. After exporting files named pebuilder.iso, pebuilder.log, and pebuilder.log.iso.md5sum.txt from the guest OS to the Linux host, the VFAT directory contained filenames pebuilder.iso86.zip (having the size of the ISO image), and pebuilder.logmd5sum.txt (having the size of the pebuilder.log file). Again, the this corruption was not detectable from the guest OS. Finally, I mounted the guest OS disk image using Linux loop device. Copying the ISO files from the NTFS file system using this method was successful. Using PuTTY's sftp also worked. I hope this report is helpful. I can provided more information if it would be valuable. But, this was frustratingly easy to reproduce. I am willing to help in any way. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 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 356808] Re: Corruption of File Data/Filename w/ Virtual FAT (VFAT)
I forgot to mention this corruption was observed with both QEMU and KVM. -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 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 356808] Re: Corruption of File Data/Filename w/ Virtual FAT (VFAT)
** Description changed: Binary package hint: kvm KVM Version: 1:72+dfsg-1ubuntu6 QEMU Version: 0.9.1-5ubuntu3 Description:Ubuntu 8.10 Release:8.10 - File Data and Filename corruption occurs when coping large files to a + File Data and Filename corruption occur when copying large files to a Virtual FAT (VFAT) drive. I noticed this when copying ISO images between 150MB and 200MB from WindowsXP guest to the Linux host. These ISO images would not boot. Suspecting corruption, I confirmed MD5 hash - values of guest and host copies of these ISO images were different. (In - fact, the guest OS calculated the correct hashes of the files on the - VFAT drive after copying.) + values of guest and host copies of these ISO images were different. + (The guest OS calculated the correct hashes for files on the VFAT drive, + but the files available to the host were corrupted.) Also, filename corruption also occurred. For example, the VFAT directory on the host contained the file pebuilder3110a.zip. After exporting files named pebuilder.iso, pebuilder.log, and pebuilder.log.iso.md5sum.txt from the guest OS to the Linux host, the VFAT directory contained filenames pebuilder.iso86.zip (having the size of the ISO image), and pebuilder.logmd5sum.txt (having the size - of the pebuilder.log file). Again, the this corruption was not - detectable from the guest OS. + of the pebuilder.log file). Again, this corruption was not detectable + from the guest OS. Finally, I mounted the guest OS disk image using Linux loop device. Copying the ISO files from the NTFS file system using this method was successful. Using PuTTY's sftp also worked. + To be clear, this corruption was observed when using both KVM and QEMU. + I hope this report is helpful. I can provided more information if it would be valuable. But, this was frustratingly easy to reproduce. I am willing to help in any way. ** Tags added: kvm qemu virtualfat -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 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 356808] Re: Corruption of File Data/Filename w/ Virtual FAT (VFAT)
Hi Dustin, Excellent questions. I should have included that information. 1) Can you reproduce this on an Ubuntu Jaunty host? I have not tried Jaunty 9.04 beta. Sorry. What version of KVM and QEMU are provided? I checked the main KVM changelog and I don't see anything about it. I thought I read something about a rewrite of the VFAT code but I cannot find that in the Changelog for the life of me. Off topic, is there a way to peek at other APT repositories to, say, get the Changelog of a package in an upcoming release? If you have good reason to believe this is likely to be resolved in Jaunty, let me know. I'll try to move up my upgrade to 9.04 and test for you. My test machine doesn't have the horsepower/RAM for VMs. 2) Does the problem only happen when copying data guest-host? What about host-guest? Yes. I have only detected corruption when exporting data from the guest system to the host (i.e. writes). I have read many small files without any trouble and more convenient than Samba... Well, you'll be interested in this new behavior. I thought I would just test a big file for you really quick. So, I put a new 150MB ISO image in the VFAT directory and started KVM. But, this time, I received this error: kvm: block-vvfat.c:96: array_get: Assertion `index array-next' failed. I created a new directory, moved the ISO image there, and updated the -drive parameter to point to the new directory. KVM started correctly. I performed the test copy, importing the ISO image file without corruption. I believe this problem is isolated to large file exports (i.e. VFAT writes). Now, I'm lost regarding that error. That sounds like the directory file on the host is getting corrupted, in addition to filenames and file data. But, I don't see any bogus data in the directory file, although I don't really know what or how to look for that. The other option is that there is some restriction on the Virtual FAT device that I don't understand. For example, the last time I used this particular VM, WindowsXP was constantly annoying me about the VFAT drive being full and that I should run Disk Cleanup on it. WindowsXP sees the VFAT drive as having a total capacity of 512MB and there was, at that time, more than 512MB used by files in the VFAT directory and its subdirectories on the host. However, the drive was nearly empty when I first noticed this problem and my tests were completed before the drive was full. It filled up as I kept different versions of the same ISO file for comparison. 3) What protocol are you using to do the copy? scp? ftp? rsync? samba? nfs? Something else? The copying that produced the corruption was Windows Explorer copy/paste or drag/drop. I'm sorry I didn't try copy. SFTP network-based export worked perfectly. Mounting the NTFS filesystem within the VM image (after converting to raw with qemu-img convert) and using cp from the host also worked. I assume all TCP/IP or Network based transfers are safe. 4) Also, what type of guest disk? qcow? qcow2? Originally, I was using qcow2 format. But, before I thought of SFTP (doh!) I decided to try to loopback mount the VM disk image, which required converting it to a raw disk image. Corruption was experienced before and after the conversion. Also, to be honest, so my most careful tests were performed using qemu (to remove some of the variables). But, I originally noticed this problem using kvm. 5) And what's the command line you're using to launch this? I use the same command line parameters for QEMU and KVM. (I hope that is correct usage.) Here are all my parameters: -name WinXP -M pc -smp 1 -m 512 -drive file=image.raw,if=ide,index=0,media=disk -drive file=fat:rw:/home/pdestefa/tmp/qemuVVFAT,if=ide,index=3,media=disk -net nic,vlan=0 -net user,vlan=0,hostname=winxp -localtime -usb -S Again, I hope this is helpful. Please let me know if there is anything I can do. -- Corruption of File Data/Filename w/ Virtual FAT (VFAT) https://bugs.launchpad.net/bugs/356808 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 195422] Re: hardy heron 8.04 alpha 5 - flash not installed correctly
I'm not sure if this bug is still affecting Hardy Heron 8.04 with Firefox 3.0. I just wanted to mention that Steve Langasek's post led me to a solution to my problem. My symptoms were similar, but I didn't think creating a link was a good idea. I had a conflict with Gnash, which was the preferred SFW player. The Adobe player was correctly installed. $ update-alternatives --display xulrunner-addons-flashplugin xulrunner-addons-flashplugin - status is auto. link currently points to /usr/lib/gnash/libgnashplugin.so /usr/lib/gnash/libgnashplugin.so - priority 50 /var/lib/flashplugin-nonfree/npwrapper.libflashplayer.so - priority 50 Current `best' version is /usr/lib/gnash/libgnashplugin.so. As soon as I removed Gnash, the non-free player was selected as the 'best'. $ update-alternatives --display xulrunner-addons-flashplugin xulrunner-addons-flashplugin - status is auto. link currently points to /var/lib/flashplugin-nonfree/npwrapper.libflashplayer.so /var/lib/flashplugin-nonfree/npwrapper.libflashplayer.so - priority 50 Current `best' version is /var/lib/flashplugin-nonfree/npwrapper.libflashplayer.so. Thanks Steve. -- hardy heron 8.04 alpha 5 - flash not installed correctly https://bugs.launchpad.net/bugs/195422 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
