Public bug reported:
Binary package hint: vinagre
happpened during updates
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 245
Package: vinagre 2.24.1-0ubuntu1.1
SourcePackage: vinagre
Title: package
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22984683/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/22984684/DpkgTerminalLog.txt
--
package vinagre 2.24.1-0ubuntu1.1 failed to install/upgrade: subprocess
post-installation
FYI: lyx 1.6.1 has now been released, and the i386 version is already in
debian unstable.
--
Please backport LyX 1.6.0-1 to 8.04 and 8.10
https://bugs.launchpad.net/bugs/297941
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I manually downloaded and installed lyx_1.6.0-1_all.deb and lyx-
common_1.6.0-1_all.deb from Jaunty on an Intrepid system, and no other
jaunty packages were required. I've been using it for 1 few days now,
and it appears to be functioning correctly.
Therefore I believe that backporting lyx 1.6.0
Could this be upgraded from wishlist? It is quite annoying.
Every new window created from an active window (ie not from a menu or
panel button) is started in the background. This include child windows
of active apps. This is happening to me now under both Gnome and KDE
sessions when using compiz.
Forgot to say: I'm running up-to-date Intrepid, with intrepid-updates.
Also, I just tried switching focus-prevention-level to Off, and makes things
seem to work correctly.
It's a useful workaround, but I'd love to this feature working. Focus
prevention is a useful thing, when it works. ;-)
--
There's talk on kde-bugs that they're planning to port the fix back to
4.1. If that happens, could it be included in intrepid-updates or
intrepid-backports.
Perhaps I should make this a separate wishlist bug, no?
--
konsole does not restore session properly (intrepid, kde4)
Sorry, I meant to include the link to kde-bugs:
http://bugs.kde.org/show_bug.cgi?id=152761
--
konsole does not restore session properly (intrepid, kde4)
https://bugs.launchpad.net/bugs/283680
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I get this problem also. The above description is accurate for my
computer, also.
I'm running the i386 Intrepid stream on a dual core 64bit athlon, with
an nvidia 6200-based graphics card.
My compiz version is 1:0.7.8-0ubuntu4, and I've also got fusion, emerald, and
some other plugins
This seems to be by design as a result of this bug report:
https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/114565/comments/3
To avoid this you can load the module manually (sudo modprobe
garmin_gps) or remove the blacklisting by editing
/etc/modprobe.d/blacklist
Look for:
#
The debian 0.3.2 version works fine on my machine (now that google have
fixed the problem with their distributable)
The gutsy 0.2.0 version works fine now too, with only a few differences
to the debian package script.
[EMAIL PROTECTED]:~# diff -u make-googleearth-package.new
Public bug reported:
Binary package hint: googleearth-package
Google has released a new version (4.2), and it seems they've changed
the directory structure of their linux download area.
make-googleearth-package uses
http://dl.google.com/earth/GE4/GoogleEarthLinux.bin, which gives you
version
Sorry, just tested this, and I'm having problem due to a checksum error
in the 4.2 download. I've posted on the googleearth for linux group, and
I'm awaiting a response. I'll post again once it's sorted out.
--
make-googleearth-package doesn't use latest version
Nope. Seems to be gone in my version.
phaedrus$ kget --version
Qt: 3.3.6
KDE: 3.5.5
KGet: v0.8.5
--
kget causes Xorg to use maximum available CPU
https://bugs.launchpad.net/bugs/44491
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber
It should remain open until it is resolved upstream. I think there is a
fix in their svn or cvs, but it is not released.
You can fix it locally by changing /usr/lib/tiger/config line 54 from:
TigerWorkDir=/var/run/tiger/work
to:
TigerWorkDir=/var/lib/tiger/work
and creating the /var/lib/tiger
I have heard from one of the developers that tiger stores status
information in that directory as well, so neither of our solutions will
work properly. That is to say that tiger will resend the same warnings
everything the computer is restarted, instead of only sending warnings
when something
16 matches
Mail list logo
