Public bug reported:
dpkg: error: parsing file '/var/lib/dpkg/status' near line 5900 package
'libswscale-extra-2':
`Depends' field, reference to `libavutil-extra-51': version contains ` '
E: Sub-process /usr/bin/dpkg returned an error code (2)
A package failed to install.
deb cdrom:[Ubuntu-Studio 12.04.2 _Precise Pangolin_ - Release i386 (20130213)]/
precise main multiverse restricted universe
deb-src http://archive.ubuntu.com/ubuntu precise main multiverse restricted
universe #Added by software-properties
# See http://help.ubuntu.com/community/UpgradeNotes for
I think i experienced this bug too. My workaround was to go into
Assistive Technologies program and turn off the 'Slow Keys' feature
which had apparently been activated by the function and volume key
combo.
--
gnome-settings-daemon X keyboard grab
https://bugs.launchpad.net/bugs/618700
You
the computer i had this on is a Dell Inspiron 2200 running Lucid.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
gnome-settings-daemon X keyboard grab
https://bugs.launchpad.net/bugs/618700
You received this bug notification because you are a member of Ubuntu
Hi Daniel, indeed the CL is how i solved my problem, but that is completely
beside the point. We're talking about the User Experience bug on Jockey.
Jockey is often ineffective in installing wifi, there's a bug written
against it. end of story
On Wed, Oct 6, 2010 at 7:28 AM, Daniel Stone
@Sebastian Bacher wrote:
How about the Lucid users? Backport? PPA?
What protocol do you have the issue with? Let's try to see how the fix
work in maverick then consider lucid but it seems non trivial change for
a stable update
For an LTS there *needs to be a way* for people to upgrade to a
** Description changed:
Binary package hint: firefox
Version: Ubuntu 10.04 LTS
- SB X-Fi Go! sound output level is broken as right channel output level
- is 50% higher than left one. Problem doesn't depends on specific
- application (tested on firefox, audacious2, totem).
+ SB X-Fi Go!
Thank you for raising the importance of this bug. I hope it will be
included in 10.04.2 since it is important to new users that the capability
to reach irc support channels be available from the start.
On Fri, Sep 10, 2010 at 4:24 PM, Bug Watch Updater
433...@bugs.launchpad.net wrote:
**
Thank you for the good news Omer. I hope we will put it into 10.04.2 as
well.
On Thu, Aug 26, 2010 at 7:03 AM, Omer Akram om2...@ubuntu.com wrote:
this bug is now fixed upstream. the fix for it will be in empathy
2.31.91 in Maverick
** Changed in: empathy (Ubuntu)
Status: Triaged =
Please see bug #626503 for response to Orrin Zirbel's question. While
both bugs have the Grub Update in common, the effect is different. In
this one the machine is completely unbootable while in bug #626503, the
Wubi install doesn't boot, but the Windows installation still boots
okay.
--
** Summary changed:
- error message and stopping booting
+ error message and stopping booting; Kernel panic - not syncing: Attempted to
kill init!
--
error message and stopping booting; Kernel panic - not syncing: Attempted to
kill init!
https://bugs.launchpad.net/bugs/617426
You received
** Summary changed:
- linux-image-2.6.19-5-generic kernel panic
+ linux-image-2.6.19-5-generic Kernel panic -- not syncing: Attempted to kill
init!
** Description changed:
Binary package hint: linux-image-2.6.19-5-generic
Kernel panic while booting linux-image-2.6.19-5-generic.
Feisty
** Changed in: network-manager (Ubuntu)
Status: Invalid = Incomplete
--
[feisty] kernel panic on upgrade
https://bugs.launchpad.net/bugs/80555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 70874 ***
https://bugs.launchpad.net/bugs/70874
** Summary changed:
- Kernel Panic with Feisty Fawn - Herd 1 in VMware
+ Kernel Panic with Feisty Fawn - Herd 1 in VMware; Kernel panic -- not
syncing: Attempted to kill init!
** Description changed:
1.
** Description changed:
Kernel Panic - agp_amd64_init with 2.6.17-9-amd64-k8
Attaching photo of messages, attaching lspci -vv as well.
+
+ Kernel panic -- not syncing: Attempted to kill init!
** Summary changed:
- Kernel Panic - agp_amd64_init
+ Kernel Panic - agp_amd64_init; Kernel
** Summary changed:
- Kernel Panic only with 64-bit after update to 2.6.27-2 kernel
+ On 64 bit after update to 2.6.27-2; Kernel Panic - not syncing: Aiee, killing
interrupt handler!
--
On 64 bit after update to 2.6.27-2; Kernel Panic - not syncing: Aiee, killing
interrupt handler!
** Summary changed:
- Kernel stops booting on HP EliteBook 8530w
+ On HP EliteBook 8530w; Kernel stops booting at ACPI: Thermal Zone [DTSZ]
--
On HP EliteBook 8530w; Kernel stops booting at ACPI: Thermal Zone [DTSZ]
https://bugs.launchpad.net/bugs/288385
You received this bug notification
** Summary changed:
- Kernel panic after update to 2.6.24-23 on Acer Aspire One netbook
+ After update to 2.6.24-23 on Acer Aspire One netbook; Kernel panic - not
syncing - attempted to kill init!
--
After update to 2.6.24-23 on Acer Aspire One netbook; Kernel panic - not
syncing - attempted
any news?
On Wed, Aug 18, 2010 at 11:53 AM, xiss burg
609...@bugs.launchpad.netwrote:
@ bcbc: I just posted a new thread a href=
http://ubuntuforums.org/showthread.php?p=9735896;here/a.
--
Fresh Wubi 10.04 install + grub update renders system unbootable
@Sebastien Bacher i implore you to change your mind on this. Please
hear me out.
Can we not only emulate, but can we blow right past Apple? Mark
Shuttleworth, July 22 2008.
The answer is definitely yes! if we take care of these vital user
experience details.
Bear in mind that Rythmbox = iTunes
@Alberto Milone wrote: Also you mention workarounds for the Jockey
bug(s), such as the need to connect to the Internet some other way and
run the script to work b43-fwcutter package or ndiswrapper or bmcwl
sources. I would be glad if you could describe the exact steps that you
followed to get your
@ Jeff how about we fix it and push it upstream to GNOME instead of
waiting for them? Lately that's what we (Ubuntu and Canonical) been
criticized for failing to do. If it is trivial then we can 1) solve our
problem and 2) be heroes to GNOME and good FLOSS community members
simultaneously.
Yeah! Thank you
nUboon2Age
On Mon, Aug 16, 2010 at 1:54 AM, Matthew East m...@mdke.org wrote:
The fix is now released on the site.
** Changed in: ubuntu-docs (Ubuntu)
Status: Fix Committed = Fix Released
--
Broken link: Switching from Windows
https://bugs.launchpad.net/bugs
I think this fix needs to be put into 10.04.1 . As i wrote above, this
is a serious problem for supporting new users and since 10.04 is an LTS
we could be faced with this issue for a long time unless the fix is
added to the LiveCD. I continue to believe this should be raised from
'low'
** Summary changed:
- Fresh Wubi 10.04 install + grub update render system unbootable
+ Fresh Wubi 10.04 install + grub update renders system unbootable
--
Fresh Wubi 10.04 install + grub update renders system unbootable
https://bugs.launchpad.net/bugs/609815
You received this bug notification
bcbc: This bug may relate to #604417, but in the instance i observed
with xissburg wubi was installed on the same partition as Win 7. In
xissburg's system there was an original XP partition, then a second Win
7 partition. Wubi was installed on the Win 7 partition. Then a Wubi
Ubuntu install was
The log of most everything that we tried with xissburg is at:
http://irclogs.ubuntu.com/2010/08/14/%23ubuntu.txt
http://irclogs.ubuntu.com/2010/08/15/%23ubuntu.txt
http://pastebin.com/cPqzHj7p
http://pastebin.com/U1VjZEBp
xissburg e-mailed this followup:
I got that wubi log in temp folder.
Question for BCBD: what if the bug is not about whether its the same
partition as windows is on (because in xissburg's case it was the same
partition as Windows 7) but whether it is on the first partition created
or not? Because in xissburg's case Wubi was installed on a partition
with the
sorry, the above question in comment #9 was directed to bcbc. ^^^
--
Fresh Wubi 10.04 install + grub update renders system unbootable
https://bugs.launchpad.net/bugs/609815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@xiss burg, @bcbc, okay xissburg clarified something i'd not known: that
on xiss burg's system Wubi was installed not on the Windows 7 partition,
but on another partition that didn't have a windows system on it. So
this seems to reinforce bcbc's theory that the key is installing Wubi on
a non
** Changed in: wubi
Status: New = Confirmed
--
Fresh wubi 10.04 install + package update can brick the system
https://bugs.launchpad.net/bugs/609815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On 8/14/10 in #ubuntu a number of us supported xissburg for something
like 15 hours as this bug was preventing booting. Finally xissburg
solved it by using a Windows7 recovery CD, but we left it before
xissburg had been able to reestablish the 2nd entry in the bootloader
for Win XP or their wubi
This may be a duplicate of Bug #610898.
--
Fresh wubi 10.04 install + package update can brick the system
https://bugs.launchpad.net/bugs/609815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- Fresh wubi 10.04 install + package update can brick the system
+ Fresh Wubi 10.04 install + grub update render system unbootable
--
Fresh Wubi 10.04 install + grub update render system unbootable
https://bugs.launchpad.net/bugs/609815
You received this bug notification
Note that I succesfully ran some of the funcions of Ubuntu One gnome
client on Portable Ubuntu and my discussion about it is located at
http://ubuntuforums.org/showpost.php?p=9540784postcount=2
--
ubuntu everywhere
https://bugs.launchpad.net/bugs/376807
You received this bug notification because
Bug is not really fixed and not invalid -- original reporter chewit just
found a workaround and then marked it invalid. Returned to 'confirmed'
as it was previously realizing that unless someone else runs into the
bug and provides further testing information there may be no more work
done on it.
Correction: changed back to incomplete as Jeremy Foshee had set it.
--
Screen goes Out of Range when boot into live cd and first time ubuntu boot up
https://bugs.launchpad.net/bugs/529387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
alexanderpas wrote on 2010-05-10
The correct link should be https://help.ubuntu.com/10.04/switching/C/index.html
Could someone with the permission please fix this? Thanks!
--
Broken link: Switching from Windows
https://bugs.launchpad.net/bugs/575627
You received this bug notification because
** Changed in: wicd (Ubuntu)
Status: New = Confirmed
--
package wicd-daemon 1.7.0 ds1-2 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/596151
You received this bug notification because you are a member
Based on Pedro Villavicencio's comment's actions it sounds like this bug
should be narrowed to be more specific, so I'll narrow it to being
Rhythmbox Sync Feature Missing on Lucid. It needs to be included in
Lucid (and hopefully when the Lucid liveCD is remade since it is such a
fundamental
** Description changed:
- I'm using Ubuntu 10.04 with Rhythmbox 1.12.8 and an iPod Nano 5th
- Generation. I can't figure out how to sync music and podcasts (in both
- directions like iTunes does) between RB and the iPod. Can Rhythmbox
- even do it? I think I have all the codecs necessary and
I was able to get both ubuntuone-gnome-client and ubuntuone-kde working
on Kubuntu 10.04 Lucid Lynx. Here's the full report:
http://ubuntuforums.org/showthread.php?t=1522137. Post #1 describes
installation for ubuntuone-kde, and post #2 ubuntuone-gnome-kde
--
ubuntuone not usable in default
** Description changed:
This is a requests to add a wireless network selection screen to oem-
- config if wirless is avaliable.
+ config if wireless is avaliable.
- This would set the wireless settings for the newly created user that is
created during the use of oem-config. It would also
-
** Description changed:
This is a requests to add a wireless network selection screen to oem-
config if wireless is avaliable.
This would set the wireless settings for the newly created user that is
- created during the use of oem-config. f no wireless is available then
+ created during
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
--
Searching within a notebook should inform the user that no results were found
within that notebook
https://bugs.launchpad.net/bugs/386893
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
--
[time-admin] We need a GUI to enable/disable utc
https://bugs.launchpad.net/bugs/53132
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
--
Send To... should become Send To sub-menu
https://bugs.launchpad.net/bugs/390193
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
--
gvfs does not report correct ownership group and file permissions
https://bugs.launchpad.net/bugs/308299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
I'm using Ubuntu 10.04 with Rhythmbox 1.12.8 and an iPod Nano 5th
Generation. I can't figure out how to sync music and podcasts (in both
directions like iTunes does) between RB and the iPod. Can Rhythmbox
even do it? I think I have all the codecs necessary and Rythmbox has
** Also affects: ayatana-ubuntu
Importance: Undecided
Status: New
** Summary changed:
- Rhythmbox missing normal iPod/iPhone/mp3Player syncronization
+ Rhythmbox missing normal iPod/iPhone/mp3Player synchronization feature
** Package changed: ubuntu = rhythmbox (Ubuntu)
** Summary
I completely disagree with this bug being labeled of 'Low' importance.
Note that this is important enough that it will need to be included in
the liveCD of Ubuntu 10.04, Lucid Lynx when it gets updated. Otherwise
since Empathy is the default IRC client new users of Lucid may
mistakenly think IRC
** Summary changed:
- Unplug, replug AC on laptop, screen pulses, battery indicator not reliable,
power statistics and preferences screens unavailable
+ Unplug, replug AC on laptop, screen pulses, battery discharges, indicator not
reliable, power statistics and preferences screens unavailable
Okay, Steve could certainly be correct to point to the gnome-power-
manger, but as far as my research showed, acpid and acpi-support does
indeed cover AC power being unpluged, replugged, battery on/off and
other related power events.
** Description changed:
Binary package hint: acpi-support
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: acpi-support
Steps to reproduce:
Laptop (Dell Inspiron 2200 with an after-market AC adapter)
1) unplug AC power
2) replug AC power
Resulting symptoms: Frequently (probably 70% of
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52007304/CurrentDmesg.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52007306/Dependencies.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/52007307/DevkitPower.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/52007308/GConfNonDefault.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/52007311/Lspci.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You received this bug
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/52007312/ProcCpuinfo.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/52007313/ProcInterrupts.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/52007314/ProcModules.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/52007315/UdevDb.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You received this
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/52007316/UdevLog.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
https://bugs.launchpad.net/bugs/605290
You received this
apport information
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/52007319/gnome-power-bugreport.txt
--
Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
The above apport update was collected while this sydrome is taking
place. Currently upower --dump reports the battery is discharging even
though the AC is plugged in and the battery indicator shows charging,
but the battery indicator detail screens are inaccessible and a little
rectangle pops up
** Summary changed:
- Unplug, replug AC on laptop, screen pulses, battery indicator not updated,
power statistics and preferences screens unavailable
+ Unplug, replug AC on laptop, screen pulses, battery indicator not reliable,
power statistics and preferences screens unavailable
--
Unplug,
Public bug reported:
Binary package hint: acpi-support
Steps to reproduce:
Laptop (Dell Inspiron 2200 with an after-market AC adapter)
1) unplug AC power
2) replug AC power
Resulting symptoms: Frequently (probably 70% of the time)
1) Pulsing, Flashing, beating, flickering display (looks like
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51907405/Dependencies.txt
** Description changed:
Binary package hint: acpi-support
- Steps to reproduce:
- Laptop (Dell Inspiron 2200)
- 1) unplug AC power
- 2) replug AC power
+ Steps to reproduce:
+ Laptop (Dell
** Changed in: software-center (Ubuntu)
Status: Incomplete = Confirmed
--
Install Button not Working - nothing happens
https://bugs.launchpad.net/bugs/591129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
THE ESSENCE OF THIS USC BUG is that USC fails silently and inexplicably leaving
the new user (the target audience for Ubuntu Software Center) in the dark as to
what to do next. Below are listed least three slightly different circumstances
that result in this bug.
.
FIXES: 1) Minimally the
PROBLEM: with Lucid and a Palm 700p with a USB cradle using the visor
module if I pressed the hotsync button the palm would be continously
reseting indefinitely (had to unplug). The key to fixing this problem
seemed to be purging modemmanager. I also removed the visor module.
FIX: Hotsync
Also I was getting the same kind of dmesg entries as the original bug report
when undergoing these continous resets:
such as:
visor 1-3:1.0: Handspring Visor / Palm OS converter detected
usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB0
Followed shortly thereafter by:
** Changed in: seahorse (Ubuntu)
Status: Incomplete = New
--
Seahorse will not generate a key
https://bugs.launchpad.net/bugs/321287
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirm this on Lucid 10.04 i686
Above is requested:
please do a 'ls -l ~/.gnupg/*.gpg'. This will will list (among other
things) which user and group owns the files.
There should be 3 files, pubring.gpg, secring.gpg, and trustdb.gpg.
These 3 files -- in fact, *all* under ~/.gnupg -- should be
Update and RESOLUTION:
What it boils down to is that previously I'd run the command line gpg
tool with sudo. Like the original gug reporter, my .gnupg directory was
therefore owned by root. To fix it I deleted the directory and ran
Seahorse again in normal user mode (ie. w/o sudo).
Here's my
Suggested Fix:
1) inform the operator that the .gnupg directory is owned by root and therefore
cannot be used to generate a key
2) either (preferred) a) give operator option to delete the directory b)
authenticate their sudo password, delete the directory and then c) ask if they
wish to try
key
- // General error. To get Seahorse working again the ~/.gnupg/ directory
+ Bug Summary (by nUboon2Age): When the ~/.gnupg/ directory and its
+ contents are owned by root Seahorse gives: Couldn't generate PGP key //
+ General error. To get Seahorse working again the ~/.gnupg/ directory
must
I think the comments by Jimbo and Dominic above are probably a different
bug (possibly bug #321287) which then would need to be written up
separately.
Note: looking at the gpg documentation, my guess is that
http://www.gnupg.org/gph/en/manual.html#AEN26 gives General error for
several different
C de-Avillez, yes that is a good point about potentially unintentionally
destroying other data. I wonder if Seahorse just changed the
permissions to be controlled by userid if that would solve the problem.
I think it probably would. The thing is that if you give new to
intermediate users with
New Suggested Fix (taking into account C de-Avillez's input above):
1) inform the operator that the ~/.gnupg/ directory and all the files in it are
owned by root and therefore cannot be used to generate a key.
2) either
(my strong preference)
2.1.1) give operator option to change the ownership
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 585929
This will help us to find and resolve the problem. Bear in mind that you
may need
** Changed in: bughugger (Ubuntu)
Status: Incomplete = Confirmed
--
bughugger freezes authorizing with launchpad
https://bugs.launchpad.net/bugs/585929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
Package: bughugger 10.04
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Tags: lucid
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
- Architecture: amd64
+ Architecture: amd64 (or i686 -- see apport data below from nUboon2Age)
Date: Wed May 26 16:49:59 2010
InstallationMedia: Ubuntu 10.04 LTS Lucid
The Apport retracing service mechanically asks me to upgrade my system
to the latest system, however it misses the whole point. This was the
10.04 liveCD. You can't upgrade it. Nevertheless it should be easy to
replicate. I'm re-marking this new.
** Changed in: telepathy-haze (Ubuntu)
Since this incorrect URL doc bug is rated High Importance and the
correct link is already available could someone please change the URL?
I'd do it myself if I could.
alexanderpas wrote on 2010-05-10:
The correct link should be https://help.ubuntu.com/10.04/switching/C/index.html
--
Broken
** Changed in: gwibber (Ubuntu)
Status: Incomplete = Confirmed
--
gwibber crashed with CancelledError in __init__()
https://bugs.launchpad.net/bugs/542761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Still present in released 10.04 liveCD (64 bit). Started Gwibber from
the Applications-Internet menu, and canceled at the first New Keyring
Password dialog box. Reproducible seemingly at will.
--
gwibber crashed with CancelledError in __init__()
https://bugs.launchpad.net/bugs/542761
You
** Changed in: gwibber (Ubuntu)
Status: Fix Released = Confirmed
--
gwibber-accounts crashed with CancelledError in __init__()
https://bugs.launchpad.net/bugs/532524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 532524
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 532524
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 532524
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 556626
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 556626
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 556626
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in __init__()
--
gwibber-accounts crashed with CancelledError in __init__()
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 556626
gwibber-accounts crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug is no longer a duplicate of bug 542220
gwibber-preferences crashed with CancelledError in __init__()
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError
*** This bug is a duplicate of bug 542761 ***
https://bugs.launchpad.net/bugs/542761
** This bug has been marked a duplicate of bug 542761
gwibber crashed with CancelledError in __init__()
--
gwibber-accounts crashed with CancelledError in __init__()
1 - 100 of 233 matches
Mail list logo
