[Bug 147551] Re: cups-pdf fails to generate file when user does not print to default ~/PDF (apparmor vs.cups-pdf inconsistency)
My Hardy machine is part of a Windows domain, meaning my home is /home/DOMAIN/user. This throws off AppArmor, and I have to manually add the full path to my ~/PDF directory just to print a PDF. Seems AppArmor is a bit buggy with "non-typical" paths. -- cups-pdf fails to generate file when user does not print to default ~/PDF (apparmor vs.cups-pdf inconsistency) https://bugs.launchpad.net/bugs/147551 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 189441] Re: totem-gstreamer-video-thumbnailer crashed with SIGSEGV in g_object_notify()
I have not had the issue recently, no. -- totem-gstreamer-video-thumbnailer crashed with SIGSEGV in g_object_notify() https://bugs.launchpad.net/bugs/189441 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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
If I understand the original Debian thread correctly, this arises when someone writes sloppy code, no? Sloppy code should be fixed, instead of allowing broken behavior in the libraries...IMHO. Still, the closed- source java annoys me in that only Sun can fix the problem. Is a fix forthcoming in libxcb, or do we wait for broken packages (Java most notably) to be updated? If no fix is in the pipeline, what is the temporary workaround? Just export and run java apps from the CLI every time? -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Found a workaround on the Gentoo forums and adapted it to Ubuntu's locations. NOTE: Newcomers...do NOT run this command. If you don't understand exactly what is going on, NEVER run a command you find online. locate libmawt.so | grep "/usr/lib/jvm/java-6.*/lib/i386/.*libmawt.so" | xargs sudo sed -i 's/XINERAMA/FAKEEXTN/g' -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 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 131444] Re: package mount 2.12r-19ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1
@tmakowka: Quite welcome. Glad it helped! Hopefully there was some condition where one package needed to be updated before mount, and the depends within the mount package simply weren't updated to reflect that. I'm not sure. Either way, hopefully this report helps solve the problem for others. -- package mount 2.12r-19ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/131444 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 131444] Re: package mount 2.12r-19ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1
I got around this by upgrading all packages except mount, then going back to upgrade mount as well. Worked like a charm. -- package mount 2.12r-19ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/131444 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
