[Bug 1036985] Re: denial of service of too many headers in response
Fix pushed to upstream and will be released very soon in tinyproxy 1.8.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036985 Title: denial of service of too many headers in response To manage notifications about this bug go to: https://bugs.launchpad.net/tinyproxy/+bug/1036985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
I was not able to confirm yet, but since 12.04 is a LTS release, are there any chances to get this fixed in 12.04? Our virt server is running 12.04, and we would not like to do do an upgrade before 14.04. Thanks - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998435] Re: qemu-kvm-spice doesn't support spice/qxl installs
Sorry, I meant to say: I was not yet able to confirm that it is fixed in raring. I am able to confirm that the bug persists in 12.04: kvm-spice won't work with any other graphics card than cirrus. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998435 Title: qemu-kvm-spice doesn't support spice/qxl installs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/998435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036985]
Hi. Thanks for the report and the patch! And sorry for the long delay. I have made minor modifications to the patches. (will attach next). I have to admit though, that I did not quite understand the problem though. The seeding of the hash seems reasonabe in any case, but for, the loading of your hashes page takes approximately the same time - without a proxy - with unpatched tinyproxy - with patched tinyproxy. Maybe it is simply too late here and I am doing something wrong, but could you please explain some more what you are experiencing with and without the patches? Thanks - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036985 Title: denial of service of too many headers in response To manage notifications about this bug go to: https://bugs.launchpad.net/tinyproxy/+bug/1036985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036985]
Created attachment 63 updated version of the header limiting patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036985 Title: denial of service of too many headers in response To manage notifications about this bug go to: https://bugs.launchpad.net/tinyproxy/+bug/1036985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036985]
To be quite clear: I see the danger of hash collisions and also understand the risk of higher CPU consumption when the hashes collide since behind a hash, we have a linear list in the bucket. But since the hashofheaders is currently only built of 32 buckets, (i.e. a 5 bit hash), with a big number of headers, we will have many many collisions anyway. So I dont't quite see the point. What am I thinking wrong? Maybe we should use a tree implementation, e.g. an rbtree. That would give us really quick searching. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036985 Title: denial of service of too many headers in response To manage notifications about this bug go to: https://bugs.launchpad.net/tinyproxy/+bug/1036985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036985]
Created attachment 62 updated version of the hash seeding patch slightly polished version of the seeding patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036985 Title: denial of service of too many headers in response To manage notifications about this bug go to: https://bugs.launchpad.net/tinyproxy/+bug/1036985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154502] Re: Multiple open vulnerabilities in tinyproxy
indeed. I have added updated patches to the upstream bug report: https://banu.com/bugzilla/show_bug.cgi?id=110 Those adhere to coding guidelines and also add configure check for the newly used functions (time, rand, srand). These could go upstream. I need to really understand the problem though (i.e I am not certain that I understand the phenomenon. the bug report does not contain a precise desciption. or I am not able to reproduce.) Thanks for any details! Michael ** Bug watch added: Banu Bugzilla #110 https://banu.com/bugzilla/show_bug.cgi?id=110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154502 Title: Multiple open vulnerabilities in tinyproxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinyproxy/+bug/1154502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584862] Re: libvirt launches dnsmasq for non-dhcp networks.
I am also currently struggeling with this behaviour: I would like to configure bridges with libvirt but start my own universal dnsmasq separately. iirc, earlier versions of libvirt did not launch dnsmasq (not even for serving dns), when the dhcp section was not present in the network xml file. I am running libvirt Version: 0.9.2-4ubuntu15.2 on oneric (11.10). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584862 Title: libvirt launches dnsmasq for non-dhcp networks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/584862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, Could you explain why use of --path can lead to X crashing where lxc-create without --path is not? My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc. I need the stuff to be stored elsewhere. I thought that the --path option in the template was made exactly for this purpose. Also notice that --path is specified as parameter for the ubuntu template and not for the lxc-create command: it is specified after -- in the command line. So I think it is really the plymouthd doing something with my framebuffer (which I assume my X server is also using), somehow eventually killing my X session. Does that make sense? I just noticed that I should probably have called lxc-ubuntu with the --trim option. The description of the option is somewhat misleading: Looking at the trim() function in the script itself, it in particular disables a couple of upstart services: quoting from the script: ~~ chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls tty[2-9].conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls plymouth*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls hwclock*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf); do mv $f $f.orig; done' ~~ This also explains why another container (lucid) that was created with the --trim option works without problems. I will re-test the oneiric container with --trim... Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925513] Re: plymouth should not run in container
Confirmed: running the same lxc-create command with --trim creates a directly usable container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, thanks for your comments. I have experimented a little more. And I found that --path is indead at the very least misleading: If I don't use --path, then the config (snippet) given to lxc-create by -f is merged with the config that the template creates. If i do use paht, then the -f file is put under /var/lib/lxc while the template creates is stored under the --path. So at least this is bad and confusing. I also came up with the idea of linking or bind-mounting /var/lib/lxc to some other place. It seems safer ... :-) As for plymouth: I still have to experiment whether the behaviour is different when not using --path. But one of the main purposes for me to use is to get network virtualization, so it is not an option to _not_ configure network for my containers. :-) I usually use veth and one of the bridge devices created by libvirt. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, I might have misready your statement about network config. I do add nettwork config (veth0, dev=virbr0, etc) manually. There is no /etc/lxc/lxc.conf in my system. The reason I used a config file snipped for lxc-create was exactly to get this network virtualization layer into the container config. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, Could you explain why use of --path can lead to X crashing where lxc-create without --path is not? My motivation was: I don't want lxc-create to create the rootfs under /var/lib/lxc. I need the stuff to be stored elsewhere. I thought that the --path option in the template was made exactly for this purpose. Also notice that --path is specified as parameter for the ubuntu template and not for the lxc-create command: it is specified after -- in the command line. So I think it is really the plymouthd doing something with my framebuffer (which I assume my X server is also using), somehow eventually killing my X session. Does that make sense? I just noticed that I should probably have called lxc-ubuntu with the --trim option. The description of the option is somewhat misleading: Looking at the trim() function in the script itself, it in particular disables a couple of upstart services: quoting from the script: ~~ chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls u*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls tty[2-9].conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls plymouth*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls hwclock*.conf); do mv $f $f.orig; done' chroot $rootfs /bin/bash -c 'cd /etc/init; for f in $(ls module*.conf); do mv $f $f.orig; done' ~~ This also explains why another container (lucid) that was created with the --trim option works without problems. I will re-test the oneiric container with --trim... Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925513] Re: plymouth should not run in container
Confirmed: running the same lxc-create command with --trim creates a directly usable container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, thanks for your comments. I have experimented a little more. And I found that --path is indead at the very least misleading: If I don't use --path, then the config (snippet) given to lxc-create by -f is merged with the config that the template creates. If i do use paht, then the -f file is put under /var/lib/lxc while the template creates is stored under the --path. So at least this is bad and confusing. I also came up with the idea of linking or bind-mounting /var/lib/lxc to some other place. It seems safer ... :-) As for plymouth: I still have to experiment whether the behaviour is different when not using --path. But one of the main purposes for me to use is to get network virtualization, so it is not an option to _not_ configure network for my containers. :-) I usually use veth and one of the bridge devices created by libvirt. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925513] Re: plymouth should not run in container
@Serge, I might have misready your statement about network config. I do add nettwork config (veth0, dev=virbr0, etc) manually. There is no /etc/lxc/lxc.conf in my system. The reason I used a config file snipped for lxc-create was exactly to get this network virtualization layer into the container config. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925513] Re: plymouth should not run in container
Hi, plymouth running in the container prevents me from using the container at all, it kills my X instead: I created a 11.10 container with the following lxc-create command on freshly installed 11.10: sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu -- --release=oneiric --path=/data/lxc/ubuntu1 here ubuntu1-template.conf contains this: ~ lxc.network.type = veth lxc.network.flags = up lxc.network.link = virbr0 ~ (virbr0 being the bridge created by libvirt) Now when I later start the container with sudo lxc-start -n ubuntu1 (after sudo lxc-create -n ubuntu1 -f /data/lxc/ubuntu1/config), then there is no output but after a couple of seconds, my X session is killed placing me in the login manager. When I do lxc-ps -n ubuntu1, I see only plymouthd is running except for init. After disabling plymouth in the container by mv /etc/init/plymouth.conf /etc/init/plymouth.conf.gone, I was able to start the container successfully. So maybe plymouth should really be disabled in the container. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 925513] Re: plymouth should not run in container
Hi, plymouth running in the container prevents me from using the container at all, it kills my X instead: I created a 11.10 container with the following lxc-create command on freshly installed 11.10: sudo lxc-create -n ubuntu1 -f ./ubuntu1-template.conf -t ubuntu -- --release=oneiric --path=/data/lxc/ubuntu1 here ubuntu1-template.conf contains this: ~ lxc.network.type = veth lxc.network.flags = up lxc.network.link = virbr0 ~ (virbr0 being the bridge created by libvirt) Now when I later start the container with sudo lxc-start -n ubuntu1 (after sudo lxc-create -n ubuntu1 -f /data/lxc/ubuntu1/config), then there is no output but after a couple of seconds, my X session is killed placing me in the login manager. When I do lxc-ps -n ubuntu1, I see only plymouthd is running except for init. After disabling plymouth in the container by mv /etc/init/plymouth.conf /etc/init/plymouth.conf.gone, I was able to start the container successfully. So maybe plymouth should really be disabled in the container. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925513 Title: plymouth should not run in container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890887] Re: socksify try to LD_PRELOAD a missing library
I think this is a duplicate of bug #857598 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890887 Title: socksify try to LD_PRELOAD a missing library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/890887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857598] Re: socksify fails to run
With the attached patch (on x86_64), socksify does not complain any more about the missing library. ** Patch added: patch to socksify for 64bit https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+attachment/2701883/+files/socksify.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857598 Title: socksify fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857598] Re: socksify fails to run
bug #890887 seems to be a duplicate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857598 Title: socksify fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857598] Re: socksify fails to run
Please ignore the set -x in the patch. I added it only for debugging. The patch quietens socksify's ERROR: ld.so: ... message. But it does not finally fix the problem for me: At least on 11.10, socksify still does not work: output of socksify bash with set -x in socksify: $ socksify bash + SOCKSIFY_PRELOAD_LIBS=/lib/x86_64-linux-gnu/libdl.so.2 + LIBDIR=/usr/lib + LIBRARY=/usr/lib/libdsocksd.so.0 + PRELOAD_SEPERATOR= + PRELOAD_POSTFIX= + LD_PRELOAD=/usr/lib/libdsocksd.so.0 /lib/x86_64-linux-gnu/libdl.so.2 + export LD_PRELOAD + LD_LIBRARY_PATH=/usr/lib + export LD_LIBRARY_PATH + exec bash $ echo $? 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857598 Title: socksify fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857598] Re: socksify fails to run
** Attachment added: patch to socksify for 64bit without set -x https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+attachment/2701912/+files/socksify.patch2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857598 Title: socksify fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857598] Re: socksify fails to run
This also seems to be a duplicate -- at partially -- of what is described in bug #767085. As described in that bug report, placing a symlink fixes socksify for me: $ sudo ln -s libc-2.13.so /lib/x86_64-linux-gnu/libc.so What to do here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857598 Title: socksify fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/857598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890887] Re: socksify try to LD_PRELOAD a missing library
also see bug #767085 -- it contains a workaround -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890887 Title: socksify try to LD_PRELOAD a missing library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/890887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920702] [NEW] cups-config --ldflags lists a default -L searchpath
Public bug reported: On my 11.10 64bit box, I get this: $ cups-config --ldflags -L/usr/lib/x86_64-linux-gnu This library search path is default on the 64-bit system anyways. The negative effect is that this leads to my software build system (for samba) pulling in the libs that reside in /usr/lib/x86_64-linux-gnu too early. Specifically libtevent: current samba build has (and needs) a newer version of that library. Consequently, the symtem tevent library is linked (giving and error) instead of the built-in one. Arguably, this is also a bug in the samba-build system (that we will fix), in that the order of the -L... arguments to the gcc calls should be changed, but I still consider this listing of the default lib search path with -L wrong. Cheers - Michael ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920702 Title: cups-config --ldflags lists a default -L searchpath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/920702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631864] Re: shotwell doesn't find facebook existing albums
Hi Lucas, thank you for your opinion / estimation! I don't want to waste anyone's time. So I just added the yorba ppa to my sources and updated to 0.10. This works fine - thanks. Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631864 Title: shotwell doesn't find facebook existing albums To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/631864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631864] Re: shotwell doesn't find facebook existing albums
In the 10.10 shotwell package, this is _not_ fixed (for me): The patch that is missing from the ubuntu package is describet in comment #27 of yorba bug 2370: http://trac.yorba.org/ticket/2370#comment:27 The fix consists in requesting the user_photos permission in the authorization request (src/FacebookConnector.vala, line 667) It would be great to fix this in the 10.10 ubuntu package! How can I reopen a bug? Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631864 Title: shotwell doesn't find facebook existing albums To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/631864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631864] Re: shotwell doesn't find facebook existing albums
Thanks Shahar for the hint, I am not quite sure how / whether this allows me to mark the bug as open for the maverick version (0.7.2) while keeping it fixed for other versions. I don't seem to be able add a specific version of ubuntu or the shotwell package to the also affects list. I guess I just need to read throught the launchpad docs more carefully... Cheers - Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631864 Title: shotwell doesn't find facebook existing albums To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/631864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631864] Re: shotwell doesn't find facebook existing albums
Hi Alex, thank you for the explanations! I don't think that it would be useful to backport newer packages to maverick. I personally would like request a SRU, since firstly, it potentially affects every user publishing to facebook (when the user has not yet authorized the shotwell connector and lets shotwell do the authorization request, which I assume is standard), and secondly, the patch documented in the upstream bug is minimal (one addition in one line) and has no sideeffect other than requesting one additional authorization. I am adding the patch as an attachment. According to the shotwell upstream bug, the patch has been added to the upstream trunk, but the bug does not tell into which bugfix release the patch had been added (if any). Cheers - Michael ** Patch added: patch for 0.7.2, based on shotwell but 2370, comment #27 https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/631864/+attachment/2175895/+files/shotwell-facebook.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/631864 Title: shotwell doesn't find facebook existing albums To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/631864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605960] Re: [Maverick] Error starting domain: internal error Process exited while reading console log output: libvir: Security Labeling error : internal error error calling aa_change_profile()
*** This bug is a duplicate of bug 599450 ***
https://bugs.launchpad.net/bugs/599450
Hi, I have just installed maveric on 64bit.
Kernel is this:
# uname -a
Linux nirvana 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011
x86_64 GNU/Linux
I have copied xml config of a qemu-kvm virtural machine and the corresponding
disk image file from a
ubuntu 9.10 install, and now I get the same error as above:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 814, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 1296, in startup
self._backend.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 333, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log output:
libvir: Security Labeling error : internal error error calling
aa_change_profile()
Any hints would be greatly appreciated!
Cheers - Michael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605960
Title:
[Maverick] Error starting domain: internal error Process exited while
reading console log output: libvir: Security Labeling error : internal
error error calling aa_change_profile()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440015] Re: Error starting domain: Unable to deny all devices for vm0: No such file or director
I just updated my ubuntu 9.10 after a couple of days today.
The update consisted of a kernel update and a libc update.
Since the update, I can not start my libvirt/kvm virtual machines
any more with virt-manager, nor create new ones.
When I try to start a vm with virt-manager, I get the error message:
Error starting domain: Unable to deny all devices for foobar: No such
file or directory
and the traceback reads like this:
~~~
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 493, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 558, in startup
self.vm.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to deny all devices for foobar: No such file or directory
~~~
I am putting the bug status to confirmed, since it seems I have confirmed the
bug.
Is that how it's meant to be used?
What details do you need?
Cheers - Michael
** Changed in: virt-manager (Ubuntu)
Status: Invalid = Confirmed
--
Error starting domain: Unable to deny all devices for vm0: No such file or
director
https://bugs.launchpad.net/bugs/440015
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 440015] Re: Error starting domain: Unable to deny all devices for vm0: No such file or director
Oops, I just found this in the debian bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550845 And by chance, the same problem has occurred in my case: I had installed the cgroups-bin package for testing purposes today, too. And this made my vms fail. I uninstalled the package and now they work again. Sorry for the noise! But maybe the coincidence is interesting? ** Bug watch added: Debian Bug tracker #550845 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550845 ** Changed in: virt-manager (Ubuntu) Status: Confirmed = Invalid -- Error starting domain: Unable to deny all devices for vm0: No such file or director https://bugs.launchpad.net/bugs/440015 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 440015] Re: Error starting domain: Unable to deny all devices for vm0: No such file or director
(putting to invalid again) -- Error starting domain: Unable to deny all devices for vm0: No such file or director https://bugs.launchpad.net/bugs/440015 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 529877] Re: Tinyproxy is outdated in Ubuntu Lucid - please include v1.8 (sync from Debian)
dardack: The Listen 0.0.0.0 issue is this: 0.0.0.0 is the ipv4 wild card address that means listen to all. This was the default when there was no explicit Listen statement in the config file. But it does of course also work when you explicitly state Listen 0.0.0.0 in the config. But the introduction of IPv6 support in 1.8.0 apparently has introduced a bug in tinyproxy, that removes the 0.0.0.0 default when there is no Listen statement. This is why it does not work without explicit Listen. I will fix this upstream for 1.8.1 Cheers - Michael -- Tinyproxy is outdated in Ubuntu Lucid - please include v1.8 (sync from Debian) https://bugs.launchpad.net/bugs/529877 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 271922] Re: Default ACL not applied on files created through CIFS filesystem (mount.cifs)
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set? So the nifty posix acl extensions can never be used with stock kernel. Should we open a new enhancement bug report for this or was I just not clever enough searching... Michael -- Default ACL not applied on files created through CIFS filesystem (mount.cifs) https://bugs.launchpad.net/bugs/271922 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 271922] Re: Default ACL not applied on files created through CIFS filesystem (mount.cifs)
I was looking for a reason why Ubuntu kernels dont have CIFS_POSIX_XATTR set? So the nifty posix acl extensions can never be used with stock kernel. Should we open a new enhancement bug report for this or was I just not clever enough searching... Michael -- Default ACL not applied on files created through CIFS filesystem (mount.cifs) https://bugs.launchpad.net/bugs/271922 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
