Public bug reported:
During updating via Ubuntu 11.04's update manager after start.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: firefox-trunk 12.0~a1~hg20120131r85707-0ubuntu1~umd2~natty
ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924828
Title:
package firefox-trunk 12.0~a1~hg20120131r85707-0ubuntu1~umd2~natty
failed to install/upgrade: underprocess installerade post-
Dino99, just what does this status change from «Confirmed» to
«Incomplete» mean ?...
Henri
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571893
Title:
Unable to access non-Ubuntu loaders from
Rolf, it's been a long time since I've noticed this problem - running,
for example, Firefox 3.6.12pre on both 64-bit and 32-bit Ubuntu
Maverick, I have no difficulty in using SCIM to import CJK glyphs in a
Gmail compose box
Henri
--
SCIM doesn't work with Gmail on Jaunty beta when running
Thanks, Lionel - that's good to hear !...
Henri
--
package skype 2.1.0.47-0medibuntu2 failed to install/upgrade: trying to
overwrite '/etc/dbus-1/system.d/skype.conf', which is also in package
skype-common 0:2.1.0.47-0medibuntu2
https://bugs.launchpad.net/bugs/584594
You received this bug
Appears as «package skype 2.1.0.47-0medibuntu2 failed to
install/upgrade: försöker skriva över /etc/dbus-1/system.d/skype.conf
som också finns i paketet skype-common 0:2.1.0.47-0medibuntu2» on my
x86_64-bit machine.
Lang : Swedish
Locale : sv_SE
Kernel version : 2.6.32-22.33
I discovered that I
Agree with you dino99 ; that comment is a doozy ! Helpful to the nth
degree !...
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hullo Erick and thanks for posting ! Interesting to see that you also
include a Swedish reference ! I'm hoping that enough people will sign
off on being affected by this problem so that the developers will take
it seriously - if we want, as I do, «every-day users» to consider Ubuntu
as an
Thanks for posting, mgcarley ! It's a pity that this bug, which
certainly affects more than three users (!) has not yet been assigned,
and that the problem and its relatively simple solution (for most of us)
is not mentioned on the Lucid release-notes page
But note, Takkat, that the Sourceforge testdisk app did in fact solve
the problem I describe in this thread, whereas it didn't resolve yours.
Has the latter now been resolved after the update to GRUB2
(1.98-1ubuntu6) ?...
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
Luqe, your problem has nothing to do with the bug described here ; a
more suitable venue for discussing it would have been the Ubuntu fora.
Be that as it may, to resolve the problem you can install the
«StartupManager» from Synaptic, and then edit the timeout via System →
Administration →
Unfortunately, this bug remains unassigned. The affected package would
seem to be grub2 rather than ubiquity, so I have now changed the bug
description accordingly. Hope someone competent will take an interest in
this matter as the bug does not seem to affect only my machines ; for my
part,
To save interested parties from the need to check out the link I
provided in my initial posting above, here below /boot/grub/grub.cfg
from my main box :
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from
Takkat, thank you very much indeed ! The Sourceforge testdisk app did
the trick for me on both my Ubuntu computers - when I came to «Boot», I
was informed that the «Boot sector» was not identical to the «Backup
boot sector». When this anomaly had been corrected and I exited, I found
that I could
Ironic, Takkat, that the procedure you suggested that was so helpful to
Westson and myself, didn't suffice to help you ! In any event, we are
agreed that this is something which the developers would be advised to
look at closely
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu
Napstr, you might want to take a look at the separate bug report
(#571893) I filed ; thanks to Takkat, who posted a link to the Source
Forge testdisk app, you may well be able to find a solution to your
problem there. Ironically enough, the solution posted by Takkat didn't
suffice to resolve his
Hope that all those affected by this bug do indeed click the «This bug
affects you» button, so that developers will realise that this bug
deserves to be taken seriously
Henri
--
Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid
https://bugs.launchpad.net/bugs/571893
You received
Glad that it worked for you, napstr ! You might want to consider logging
in once again to #571893 and clicking the «This bug affects you» button,
so that the developers realise that the problem deserves serious
consideration
Henri
--
[Lucid] no GRUB menu entry for other operating systems
Sonal, your problem *seems* to be the same as mine, i e, an inability to
boot into non-Ubuntu loaders even though they are displayed on the GRUB
menu, something for which, in accordance with a suggestion by Charlie
Kravetz above, I have filed a separate bug notice (#571893). But your
situation
I hope the following won't be interpreted as an attempt to hijack this
thread, but the problem I'm experiencing with multiple-boots and Lucid
is not that the GRUB2 menu doesn't display my other OS-loader - it does
- but rather that the loader cannot be accessed from it. This on my main
Public bug reported:
Binary package hint: ubiquity
After upgrading from 64-bit Ubuntu Karmic to Ubuntu Lucid beta in a
multi-boot environment, I have been unable to access the Windows loader
from the GRUB2 menu, despite the fact that the loader is displayed. I
see this on two machines, both
Thank you, Charlie ; I am fully cognizant of the fact that this «is
really a bug report». Moreover, I regard the problem I described above
as a bug, quite similar to, if not identical with, the one reported by
Jeff Lane two days ago. In any event, I have taken your advice and
reported a new bug,
Thanks for your speedy response, Jeff ! As a matter of fact, on both
machines, Windows was completely shut down before I upgraded from Karmic
to the respective Lucid betas. Both machines have two HDD, on one of
which Windows OS, on the other of which Ubuntu is installed. To provide
an example,
Appeared on my 64-bit Ubuntu Lucid beta 1 setup after updating
Henri
--
npviewer.bin crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/328173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Same thing here on a 64-bit system
Henri
--
backend crashed with ValueError in loads()
https://bugs.launchpad.net/bugs/536645
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
Agree with Neil Wilson's post above - is it really necessary for a
warning of this type to be posted to users whose BIOS doesn't support
EEC ? I am certainly willing to be corrected here, but from what I
understand the problem - if, indeed, it can be considered such - is
hardly so grave as to
Leann, the problem lay elsewhere, and after playing 'round a bit, I
finally managed half an hour ago to discover where. The kernel updates
were indeed being installed, precisely as described above, but my
machines - both of them ! - were trying to boot not from GRUB 1.97, but
from the legacy GRUB
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33312874/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33312875/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33312876/BootDmesg.txt
**
Public bug reported:
I see this on two machines : a HP Pavilion laptop with dual AMD
Turion(tm) 64 X2 Mobile Technology TL-64 CPUs at 2.2 GHz running Gnome
2.28.0 and 4.4.1 (x86_64-linux-gnu) GCC, and a HP Pavilion desktop dual
AMD Athlon 64 X2 CPUs at 2.6 GHz running Gnome 2.28.0 and 4.4.1
ArbitRabbit's workaround did just that for me as well. Presumably, this
bug will shortly be crunched for good !...
Henri
--
package libuniconf4.6 (not installed) failed to install/upgrade: trying to
overwrite '/etc/uniconf.conf', which is also in package libuniconf4.4
0:4.4.1-1.1
Rolf, it's not a problem when running Swiftweasel 3.5 b4/Shiretoko, but
it remains a problem when running Firefox 3.5.1 (Mozilla/5.0 (X11; U;
Linux i686 (x86_64) sv_SE; rev:1.9.1.1) Gecko/20090715 Firefox/3.5.1
GTB5). Interestingly enough, the problem seems to have been fixed in the
latest version
*** This bug is a duplicate of bug 356428 ***
https://bugs.launchpad.net/bugs/356428
Unsubscribe mhenriday
--
hotkey-setup_0.1-23ubuntu11_i386.deb crashes install
https://bugs.launchpad.net/bugs/356454
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unsubscribe mhenriday
--
package hotkey-setup 0.1-23ubuntu10 failed to install/upgrade: subprocess
post-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/356157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Unsubscribe mhenriday
--
package hotkey-setup 0.1-23ubuntu10 failed to install/upgrade: subprocess
post-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/356157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can now be more precise : I have found that SCIM and Gmail work very
well together when running Firefox/Swifteasel 3.0.8 on Jaunty, but I see
the problem described above when running, as I usually do, Firefox 3.1
b3 on this system. The odd thing is that SCIM and Gmail worked fine
together when
** Summary changed:
- SCIM doesn't work with Gmail on Jaunty beta
+ SCIM doesn't work with Gmail on Jaunty beta when running Firefox 3.1 b3
--
SCIM doesn't work with Gmail on Jaunty beta when running Firefox 3.1 b3
https://bugs.launchpad.net/bugs/351770
You received this bug notification
Public bug reported:
Expected behaviour : SCIM (1.4.7-3ubuntu12) can be used to input CJK
text into a Gmail text box, as was the case in (64-bit) Intrepid and its
predecessors.
Observed behaviour : SCIM does not work in Gmail (or, for that matter,
in Launchpad) after upgrading to (64-bit) Jaunty
Agree with nudepenguin about the need for a 64-bit flashplayer. But is
Adobe listnening ?...
Henri
--
npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/192270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
After reading KAA's posting above, I clicked on the link there and
received the following response :
«Sorry, you don't have permission to access this page. »
Intriguing ! What's so secret on that page that my accessing it is not
permitted ? And why is the link publicly exposed in this manner, if
Public bug reported:
I am running Ubuntu 8.04 on an AMD 64 X2 5000+ machine with a Creative
Soundblaster X-Fi audiocard. All relevant updates are installed. Due to
the well-known problem with Creative drivers for Linux, I followed the
instructions on Ubuntu forum thread 571656 to get the audio
In the current version of Hardy, the result of the operation I mentioned
above differs depending upon the SCIM settings ; thus, for example, if
the input editor is set to input in Latin glyphs, entering
«Ctrl+Shift+u» in the gedit text editor results in an underlined «u».
When I continue by
No, Michael, the current stable builds seem to work very well, save that
something - an update yesterday ? - has suddenly made it impossible for
me to print documents on my HP Photosmart 3210 All-in-One machine : when
I click print nothing happens. I get the impression that the printer
isn't
To my great relief, after installing a batch - well over 100 - of Hardy
beta updates a couple of days ago, the Swiftweasel browsers started
loading again. Another problem which then turned up, i e, that the
Google Toolbar failed to install on the Swiftweasel 2.x browser, was
resolved after I
Public bug reported:
After installing the latest batch of Hardy beta updates this morning
(2008-04-18), I suddenly found that neither my Swiftweasel 2.0.0.13-2
nor my Swiftweasel 3.0b4.5 browser (which until then had been working
perfectly) would load. I tried re-installing the former by
How did you install swiftweasel to begin with? I can not find it in the
repositories. ...
Greg, for some reason, Swiftweasel is not found in the repositories, but can
easily be installed from
SourceForgehttp://sourceforge.net/project/showfiles.php?group_id=195473.
Perhaps you could get in touch
Public bug reported:
On my AMD X64 dualcore 5000+ box, where, in addition to Gutsy on one
HDD, I was running XP and Vista on another, I performed an upgrade to
Hardy alpha 6 a couple of weeks ago in such a manner as to get Hardy and
Gutsy running in parallel on my first HDD. Hardy was accessed
Michael, thanks for your speedy reply ! It would be wonderful if you've
found, as it seems, a solution to this problem, but I'm not sure I
understand exactly how to implement it. Just how can I change the toggle
settings for SCIM (if, indeed, this is what I am supposed to do) ; should I
open the
Michael, as you can see from the comment below that I've just posted to
another thread, this problem also occurs in Gutsy - it seems to be
connected to the SCIM update from version 1.4.4 to version 1.4.7. I very
much hope that the developers will be able to provide us with a way to
enter Unicode
I have previously (up to and including Ubuntu 7.04) been able to use
«Ctrl+Shift+u, hex code, space» to enter Unicode glyphs, e g,
«Ctrl+Shift+u,5000, space» resulted in the Chinese glyph «倀». After the
SCIM update to version 1.4.7, however, this is no longer possible ; when
attempting to enter
Public bug reported:
Binary package hint: scim
Bug report : /var/crash/_usr_lib_scim-1.0_scim-launcher.1000.crash
Despite the above report, which I receive almost every time I start my
computer, SCIM does launch when I start FF, and generally speaking works
well
** Affects: scim (Ubuntu)
50 matches
Mail list logo
