low: trivial typo
** Changed in: exiv2 (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272731
Title:
Typo in Exiv2 package (string 3033)
To manage
*** This bug is a duplicate of bug 1265509 ***
https://bugs.launchpad.net/bugs/1265509
Multiarch problem; possibly same as 1122120
** Changed in: tk8.6 (Ubuntu)
Importance: Undecided = Medium
** This bug has been marked a duplicate of bug 1265509
package libtk8.6 (not installed)
Triaged: Points to upstream fixes
Low: Timeouts after annoying but not geological time.
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks Tim; seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690431
Title:
lspci crashed with SIGSEGV in pci_load_name_list() (with invalid
parameter to -i)
To manage notifications
Setting to medium as per the related bug.
Lets collect the log files and see where we go.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lightweight/nocobrainless: Hmm given that the fix in this bug fixes
something for some group of people, but you're still having issues,
please open separate bugs for them.
Add a comment here with the new bug number, and in your new bug add a
comment saying you think it might be related to this
Triaging Low: Machine useable, possible workaround
Anyone who has this please try following the instructions in
https://wiki.ubuntu.com/Kernel/Debugging/Backlight
** Summary changed:
- Hardware buttons doesn't adjust monitor brightness
+ Lenovo E530: Hardware buttons doesn't adjust monitor
3.2.1-1 is in Jessie, so if we sinked that we should fix this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690431
Title:
lspci crashed with SIGSEGV in pci_load_name_list() (with invalid
Yeh, it seems to work in Trusty with the 2.3.0-1 which Trusty seems to
have now (with 3.12.0-7-generic #15). Marking fixed-released
** Changed in: trace-cmd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi ALl,
I was looking back through my list of bugs and noticed this had been closed
in an odd way.
Jorge you reported this a while back; is it still a problem for you? Have you
tried more recent updates?
** Changed in: xorg (Ubuntu)
Status: Fix Committed = Incomplete
--
You received
OK, fair enough - I'll leave it as incomplete and it should close itself
in a couple of months; leaves time for anyone else woh was affected at
the same time to jump in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are you sure this isn't some type of time screwup? i.e. your date has gone
backwards since you rebooted?
You are running ntp?
(My other guess would be a timezone issue?)
** Changed in: mailgraph (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a
** Changed in: debsecan (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: debsecan (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264342
Title:
I don't currently have Ubuntu on the system that triggered that so can't really.
However, I think Olivier is onto something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717870
Title:
1002:954f
So there are approximately 3 possibilities:
1) Some library it's linked with has been fixed/changed
2) Some compiler change has made it go away
3) Perhaps the bug is still there but only triggered if unlucky due to data
alignment etc - so you got lucky this
time.
bit tricky to track
I'd like to suggest something;
It should be possible to build a ppa'd kernel with just that change
reverted, then that kernel could be used to see if other apparently similar
bugs (like bug 1243904) are actually the same issue without other users having
to do the same bisect (especially if
I don't recall ever seeing an ISO respin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241871
Title:
8086:0166 [ASUS ZENBOOK UX32VD] 13.10 kernels (3.11.x) Fail to light
To manage notifications
Joonas: Thanks for doing that, technically by the ubuntu lp rules we
should have a separate bug for your separate failure on different
hardware - but I agree it's probably the same problem, so create the bug
anyway, and add a comment giving this bug number, and also add a comment
here giving the
Hi Frank,
Can you confirm the version of perl and the version of each of the broken
packages that you're seeing?
And confirm that this is on a trusty box? My understanding is that Saucy is
still on 5.14.x, and it's just trusty that's
moved to 5.18.1.
I seem to have libdbi-perl installed
As per Frank's comment #2 this is a PPA problem.
** Changed in: perl (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254180
Title:
Numerous
Confirm that the version in Saucy proposed, 0.9.5-1ubuntu1.1 fixes this.
Thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marc:
I think the answer for Trusty is to just update to virt-manager 0.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217524
Title:
Error refreshing hardware page: unsupported operand type(s)
Luc: I can confirm the crash with 'wri' on Saucy, but not on Trusty.
The backtrace on saucy looks similar to me to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239381
Title:
Unity
This has 'gone away' on trusty but not saucy; I think it's the X server update,
but can't be sure.
Looking at the debug I sent upstream I'm wondering if the problem is the X
server stopping the VT change happening
as the 1st problem, and then things going down hill from there.
--
You received
High: Uninstallable package
Triaged: This looks like a python3 ism - the syntax for except changed to be
except typename as var
rather than
except typename, var
the change happened mid 2.x but they finally banned the old one in
Python 3.something.
** Changed in: screen-resolution-extra
Nougieryann: if this fix has fixed it then no, you don't need to submit
a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241822
Title:
RAID 5 not available after upgrade from 13.04 to
Today's drm-next kernel also fails; linux-
headers-3.12.0-996_3.12.0-996.201311070425_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247906
Title:
Repeatable oops qxl_enc_commit
To manage
Also fails in set I built from drm-next, so I've reported it upstream in
the spice/qxl bug tracker and added the link here
** Bug watch added: freedesktop.org Bugzilla #71365
https://bugs.freedesktop.org/show_bug.cgi?id=71365
** Also affects: linux via
Linux trusty 3.12.0-1-generic #3-Ubuntu SMP Tue Oct 29 18:41:32 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
corrupted console on 1st c-a-f1, oops on c-a-f3 (even via grub menu)
Linux trusty 3.10.0-031000-generic #201306301935 SMP Sun Jun 30 23:36:16 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
got
High: Problem with essential hardware component (touchpad) - although
the work around of the mouse is tempting to set a little lower.
Hamilton please confirm:
1) which model computer you're using
2) Does 13.10 help?
3) When you say you reverted to 12.04, which 12.04?
On current trusty (i.e. hasn't changed much) it still does it:
(gdb) where
#0 __strcmp_sse2 () at ../sysdeps/x86_64/multiarch/../strcmp.S:212
#1 0x7faafc8a320a in rccGetDefaultLanguage (ctx=0x198d700) at lng.c:115
for (i=0;ctx-languages[i];i++) {
115 if
Public bug reported:
I've got an Ubuntu Trusty guest running under a Fedora 20-pre-beta, the
guest oops reliably.
To repeat:
Setup KVM with the guest configured with QXL graphics,
Install openssh-server in the guest
Boot it and then send a ctrl-alt-f1
Problem 1 : Corrupt graphics
Hi,
OK, I've flipped this to 'linux' - I think it's much more likely than it
being ibus.
You'll be asked to do some commands to report some more logs.
Set to importance High: Important device (internal keyboard) doesn't
work.
** Package changed: ibus (Ubuntu) = linux (Ubuntu)
** Changed in:
Answer to 1st question 1st;
I've got this on both a saucy and a trusty guest, so not new in Trusty, but
Raring doesn't seem to exhibit it
Linux saucy 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
still oopsing - slightly different backtrace
Hi Gabriel,
I'm just putting this back to Confirmed/Medium.
Lets ignore your comment #13 - this bug isn't about other problems;
but can you confirm the current kernel-ppa fixes this bug.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Christopher:
Please carefully read the upstream bug that Gabriel has referenced, it
includes a fix that he references in #10
I don't see how this bug with a specified upstream fix is an 'unhelpful catch
all', given it's got an upstream fix I'd say it's pretty
close to triaged if Gabriel
Tested in Tahr, seems to start up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925005
Title:
moria fails to start with Abort error
To manage notifications about this bug go to:
Hi Gabriel,
SO hopefully you should mainline builds pick this up in the kernel-ppa; it
would be good to know.
I don't think it's possible to fix the install ISO?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
racb: Given the easy work around I'd say it doesn't need it's own SRU
unless it turns out to be causing knock on effects for a lot of people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242383
*** This bug is a duplicate of bug 689593 ***
https://bugs.launchpad.net/bugs/689593
** This bug has been marked a duplicate of bug 689593
2x100% CPU and memory usage growth when performing partition modifications
via udisks
--
You received this bug notification because you are a member
1) hmm ok; so how many of you still have this old bug
2) and can any of you trigger it either on 13.10 or 12.04 ?
3) Does it only happen with some thumb drives or does it happen to any drive
you try this with?
Dave
** Also affects: udisks (Ubuntu)
Importance: Undecided
Status:
Flipped to the ubuntu udisks package since that's what's hanging.
** Changed in: udisks (Ubuntu)
Importance: Undecided = Medium
** Changed in: udisks (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Triaged: Trivial reproduce
High: Prevents the application from functioning correctly at all (for idle)
** Changed in: python-defaults (Ubuntu)
Status: Confirmed = Triaged
** Changed in: python-defaults (Ubuntu)
Importance: Undecided = High
--
You received this bug notification
Triaged: (as stated but didn't press the button) pointer to upstream fix
Medium: Rare to hit it, but it's procps so it's core, and if it's going to
affect lots of things it's going to be a pain
** Changed in: procps (Ubuntu)
Importance: Undecided = Medium
** Changed in: procps (Ubuntu)
This isn't minicom's problem - most likely kernel (or possibly udev?)
** Package changed: minicom (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in Ubuntu.
https://bugs.launchpad.net/bugs/1243607
hi,
does anything work - e.g. mouse move? Does an external usb keyboard work?
** Changed in: ibus (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243904
This isn't minicom's problem - most likely kernel (or possibly udev?)
** Package changed: minicom (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243607
Title:
Ubuntu
Triaged: Pointer to upstream fix
John-Mark: How often does this trigger, is this something that causes
regular pain or a rare issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242746
Title:
13.10 still uses kernel 3.11
The upstream comment says they believe it's fixed in kernel 3.12-rc2, so can
some of you try the latest kernel by using the
instructions in comment #27 from Christopher.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Siddu: Hmm your description on there seems to be different; my
understanding of the bug reported here was that it happened every/most
times during boot, your comment on the upstream bug talks about
occasional infinite loops - are we talking about the same bug here?
--
You received this bug
Triaged: Trivial to reproduce
Low: Easy work around (install python-yaml).
** Changed in: uvtool (Ubuntu)
Importance: Undecided = Low
** Changed in: uvtool (Ubuntu)
Status: New = Triaged
** Tags added: bitesize packaging
--
You received this bug notification because you are a member
Low: Just docs
Triaged: Trivially repeatable, can tell they aren't there just by dpkg -L on
all the zsg packages as well.
** Changed in: zsh (Ubuntu)
Importance: Undecided = Low
** Changed in: zsh (Ubuntu)
Status: Confirmed = Triaged
** Tags added: packaging
--
You received this
Please:
1) File the bug against the right packages
2) File separate bugs against each issue
3) And be nice about it even if it's hopelessly broken (see code of conduct)
Dave (just a triager)
** Changed in: ubuntu
Status: New = Invalid
--
You received this bug notification
High: Crashes making application unusable
Triaged: Trivially repeatable
Start kazam:
Click capture
Wait a few seconds
Seg faults.
** Changed in: kazam (Ubuntu)
Importance: Undecided = High
** Changed in: kazam (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug
Gabriel: Can you give us log files from your system, if you can't do it
with current then go with the previous working version and include at
least a dmesg and /var/log/Xorg.0.log so at least we have something to
reference and please state full details of the hardware you see htis on.
--
You
Maarten: Do you have a pointer to some discussion about that patch? Is
this really a gcc optimisation bug or is vlc doing something that's not
legal/safe but didn't happen to trigger on older gcc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can see in the new kernels there is a config called CONFIG_MD_RAID456
- is this a case tha t the 6 got added somewhere?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241822
Title:
RAID 5 not
** Summary changed:
- crash on install :(
+ crash on install :( [plugininstall.py too many open files]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241728
Title:
crash on install :(
Triaged: Upstream fix found
High: Affecting multiple common packages making them unusable.
** Changed in: x264 (Ubuntu)
Importance: Undecided = High
** Changed in: x264 (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
High: A problem with an essential hardware component / Has a severe
impact on a small portion of Ubuntu users
this looks the same as bug 102973 which is duped to bug 220493 but I'm
not entirely sure it's the same.
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received
Nouguieryann: Can you please submit a separate bug which will capture
your logs, put a comment on it mentioning this bug number, and put a
comment on here mentioning the new bug number you get.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hontvari: Yeh I think you're right, it looks like thats's fixed in the
main stuff but not backported, and unfortunately the variable names have
all changed so the git change won't apply; but I'll fix it up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just attached a patch that seems to do the trick, it's just a backport
of the upstream change.
** Changed in: virt-manager (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: Backport of upstream 61369d25
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1217524/+attachment/3885604/+files/customize_disk_details_lp_1217524.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trivially repeatable here on a 64bit Saucy install
** Changed in: unity (Ubuntu)
Importance: Undecided = Medium
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
backtrace shows a 'free(): invalid next size (fast)' somewhere below
libpango called from unity::dash::ResultRendererTile::LoadText
#3 0x7f7a095a9996 in malloc_printerr (ptr=0x54ab030, str=0x7f7a096b08e0
free(): invalid next size (fast), action=3)
at malloc.c:4923
buf =
here with some dbgsym's installed - not sure I believe some of the
values though, and anyway if it's an allocation problem might not help
anyway, but still might be useful to someone
(gdb) bt full
#0 0x7f7a0955ff77 in __GI_raise (sig=sig@entry=6) at
Public bug reported:
It looks like /dev/disk/by-path isn't getting populated with my SATA
drives:
dg@major:/dev/disk$ ls -l by-path
total 0
lrwxrwxrwx 1 root root 9 Oct 13 12:05
pci-:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:0 - ../../sdc
lrwxrwxrwx 1 root root 10 Oct 13 12:05
Still seems to do it on Saucy host, and guest. (Guest up to date as of
2013-10-12, host a few days older).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176920
Title:
lots of warnings during run
David Balažic :
Can you just confirm the latest stuff you tried - does this bug happen on an
installed system?
Alberto: IMHO this isn't a hundredpapercut job unless it can be nailed
down more as to how to repeat it
--
You received this bug notification because you are a member of Ubuntu
David: Please run
sudo dbus-monitor --system
in a shell on the machine in the live environment and paste the output when you
insert a cd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/658042
Title:
It looks like this was already fixed in the virt-manager git a few
months back:
https://git.fedorahosted.org/cgit/virt-
manager.git/commit/virtinst/osdict.py?id=fb76c4e550006cf3948106852228198255f1983e
** Changed in: virt-manager
Status: New = Fix Committed
--
You received this bug
Triaged: Just a config change and reporter states what they want, seems
reasonable if it works
Low: It's just something new, not apparently a regression
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You
OK, let me ask:
1) What makes people think it's a kernel bug? The kernel is detecting the CD
drives in the bootdmesg, and if I read the bug correctly it mounts them if told
to.
2) Does this issue happen in an installed system; i.e. if you install (I think
you could probably install to a thumb
fehwalker said on irc that he accidentally set it as fix-released, so undoing.
Triaged seems reasonable since the upstream fix is known.
Hmm low/medium - Medium because it's going to make the printer not work
and a lot of people aren't going to be able to figure out the sequence
of power off/on
Triaged: User supplied set of how to trigger and the upstream bug/patch
that fixes it.
** Bug watch added: freedesktop.org Bugzilla #60182
https://bugs.freedesktop.org/show_bug.cgi?id=60182
** Also affects: xserver-xorg-driver-ati via
https://bugs.freedesktop.org/show_bug.cgi?id=60182
TJ: Plus can you confirm where you got that kernel from - the current
version on my just-updated saucy box is 3.11.0-8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Regression: USB
Hi TJ,
Could you file a separate bug on this (so that we can catch all your hardware
info etc) and add a comment here stating the bug number.
Thanks, Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, I don't think it's gcc-multilib directly; I think it's something it
depends on libc6-dev-i386 that it pulls in.
I just tried this in a saucy (13.10) 64 bit vm, and it failed.
sudo apt-get install gcc-multilib
and it works
But sudo dpkg --purge gcc-multilib gcc-4.8-multilib
and it still
Public bug reported:
The trace-cmd in ubuntu ( 1.0.3-0ubuntu2 on saucy 3.11.0-4-generic )gives
'interrupted system call' errors on the
example uses I could find.
Note that this also happens with the trace-cmd from Eric Miao's ppa referenced
in bug 1068464,
but it all works fine if I build
Triaged: Has the upstream patch to fix it.
** Changed in: openldap (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1216650
Title:
slapd
Marking Fix released because original description said that it's already fixed:
'which is fixed in later versions of Ubuntu (it was fixed in OpenLDAP 2.4.30),
but not in precise.'
** Changed in: openldap (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
Triaged: Has the upstream patch to fix it.
** Changed in: openldap (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1216650
Title:
slapd crashed with
Marking Fix released because original description said that it's already fixed:
'which is fixed in later versions of Ubuntu (it was fixed in OpenLDAP 2.4.30),
but not in precise.'
** Changed in: openldap (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
Yeh same here on Kubuntu (shows as a styalised X).
(Set to Low importance since only cosmetic).
Dave
** Changed in: gedit (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, the question is, is it still there; on Saucy (3.11.0-4-generic #9):
# grep -i taint /var/log/kern.log
Aug 26 11:34:52 major vmunix: [0.903410] crc_itu_t: module verification
failed: signature and/or required key missing - tainting kernel
Aug 27 11:55:01 major vmunix: [0.903210]
Adnan:
Hmm, still not quite happy; what were you trying to fix with:
# Ubuntu checker | added to fix Ubuntu font problem
if [ $(lsb_release -i | grep -i Ubuntu) ]; then
ubuntu=, ia32-libs-multiarch
fi
ia32-libs-multiarch doesn't exist any more; do you know which libs are needed
and
Public bug reported:
This happens if you do the customise VM before install and click on the Disk
section.
It sounds very similar to https://bugzilla.redhat.com/show_bug.cgi?id=978264
ii virt-manager 0.9.5-1ubuntu1all desktop
application for managing virtual
It is now (as is 13.10) - in 0.9.5-1ubuntu1
** Changed in: virt-manager (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169351
Title:
virt-manager doesn't
Still happens on Saucy's 0.7.0 googleearth-package; it's still
generating a package dependent on ia32-libs-gtk.
It's possibly a little tricky, since it's not necessarily googleearth-
package that needs to have the dependency, but the package it generates.
** Changed in: googleearth-package
Trying this on Saucy's 0.7.0 package it works without /etc/mailname; it seems
to use
the hostname if it can't read /etc/mailname.
** Changed in: googleearth-package (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
9.10 went end of life in 2011; please try again on a newer Ubuntu.
I've got Google earth working on Saucy and have had it working for the last few
releases
** Changed in: googleearth-package (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
Hi,
You reported this bug quite some time ago; I've checked on google Earth
6.0.3.2197 (running on Saucy)
and the distances on the ruler seem consistent for me; please reopen this bug
if you can
still trigger it on something newer.
** Changed in: googleearth-package (Ubuntu)
Status:
Public bug reported:
Please sync googleearth-package 1.0.0 (multiverse) from Debian unstable
(contrib)
Changelog entries since current saucy version 0.7.0:
googleearth-package (1.0.0) unstable; urgency=low
* Update for MultiArch (Closes: #695957)
* Fix Google Earth not being properly
In particular this should help bug 336611
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217077
Title:
Sync googleearth-package 1.0.0 (multiverse) from Debian unstable
(contrib)
To manage
Hmm I think you're right; in most other parts of that text it says
'bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist.'
but that section does have ~/.bashrc twice.
It doesn't seem to be upstream bash, but seems to be in the
debian/ubuntu
Hi Adnan,
Thanks for doing that, and we spotted it and bug 121707 has caused a sync of
that fix into ubuntu, so it should
land in Ubuntu anytime soon.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, but I didn't have many other ideas how to track it down except to
leave it to the compiz/X devs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205633
Title:
Xorg stalls out the whole system
All good - thanks!
Linux major 3.11.0-2-generic #5-Ubuntu SMP Mon Aug 12 16:09:51 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Works in 3.11.0-2generic #5
** Changed in: linux (Ubuntu Saucy)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205827
Title:
Regression: USB storage
101 - 200 of 2987 matches
Mail list logo
