I fixed this, in 4.10 for sure and also in 4.9, perhaps in 4.9.4
Thanks for reporting !
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1066892
Title:
initial power profiles do not
Still exists in an up-to date 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/218701
Title:
gvfsd-obexftp crashed with SIGSEGV
To manage notifications about this bug go to:
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117
Title:
connect to server doesn't
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130855
Title:
shutdown problem
To manage notifications about this bug go to:
** Changed in: kdebase-workspace
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1066892
Title:
initial power profiles do not use suspend
Public bug reported:
I dont know anything to help sorry i was just downloading updates, im
just learning ubuntu and linux!
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-guest-dkms 4.1.12-dfsg-2ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
We're lining up a call for testing to kick off first thing next week in
anticipation of testing this. I'll report back with the milestone link
so others can track the bugs found during this process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
StacktraceTop:
malloc_consolidate (av=av@entry=0x7f588472c740 main_arena) at malloc.c:4065
_int_malloc (av=0x7f588472c740 main_arena, bytes=1032) at malloc.c:3358
__GI___libc_malloc (bytes=1032) at malloc.c:2859
g_malloc (n_bytes=n_bytes@entry=1032) at
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1153790/+attachment/3576360/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153790
Title:
** Attachment added: StacktraceSource.txt
https://bugs.launchpad.net/bugs/1153790/+attachment/3576361/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153790
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1153790/+attachment/3576362/+files/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/bugs/1153790/+attachment/3568933/+files/CoreDump.gz
** Changed in: evolution-data-server
As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of rsyslog from precise-proposed
was performed and bug 1092936 was found. Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (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/1026410
Title:
*** This bug is a duplicate of bug 1139922 ***
https://bugs.launchpad.net/bugs/1139922
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1139922, so is being marked as such.
** Changed in: oem-priority/quantal
Status: Fix Committed = Fix Released
** Changed in: oem-priority/precise
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This change was made by a bot.
** Changed in: linux (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/1090548
Title:
package linux-image-3.5.0-19-generic
** Changed in: software-center (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126878
Title:
software-center crashed with in install()
To manage
This bug was fixed in the package qemu - 1.4.0+dfsg-1expubuntu4
---
qemu (1.4.0+dfsg-1expubuntu4) raring; urgency=low
* re-add qemu-system-x86.modprobe to set nesting=1 (LP: #1155177)
* qemu-system-x86.qemu-kvm.upstart:
- remove NESTED workarounds from upstart file.
-
This bug was fixed in the package unity-greeter - 13.04.2-0ubuntu1
---
unity-greeter (13.04.2-0ubuntu1) raring; urgency=low
* New upstream release.
- Fix duplicate entries showing for multiple users on the same remote
login service.
- Add custom indicator support for
Stacktrace:
#0 unavailable in ?? ()
PC unavailable, cannot determine locals.
Backtrace stopped: not enough registers or memory available to unwind further
StacktraceSource: #0 unavailable in ?? ()
StacktraceTop: unavailable in ?? ()
ThreadStacktrace:
.
Thread 1 (LWP 13917):
#0 unavailable
*** This bug is a duplicate of bug 1090668 ***
https://bugs.launchpad.net/bugs/1090668
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1090668, so is being marked as such.
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124099
Title:
nautilus crashed with SIGSEGV in gdk_display_get_event()
To manage notifications
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1124099/+attachment/3576365/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124099
Title:
nautilus
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1124099/+attachment/3576366/+files/ThreadStacktrace.txt
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
libgcc1 version
This bug was fixed in the package qemu - 1.4.0+dfsg-1expubuntu4
---
qemu (1.4.0+dfsg-1expubuntu4) raring; urgency=low
* re-add qemu-system-x86.modprobe to set nesting=1 (LP: #1155177)
* qemu-system-x86.qemu-kvm.upstart:
- remove NESTED workarounds from upstart file.
-
I think the problem is bigger because i have downloaded the latest dayly build
and booted off the cd. The installer and also Try Ubuntu don't see any of my
hdds. No devices under /dev/sd*, only the CD Drive.
With kernel 3.5.0.26 i have no such problems!
The MB it is an Asrock 890FX Deluxe 4, AMD
Public bug reported:
(EE) [mi] EQ overflowing. Additional events will be discarded until existin
g events are processed.
471 (EE)
This is a complete freeze including keyboard etc. It is possible to ssh
from a different machine (office) and issue a reboot. Otherwise you must
completly shut
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155756
Title:
virtualbox-guest-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox-guest kernel
module failed to build
To
I think the problem is bigger because i have downloaded the latest dayly build
and booted off the cd. The installer and also Try Ubuntu don't see any of my
hdds. No devices under /dev/sd*, only the CD Drive.
With kernel 3.5.0.26 i have no such problems!
The MB it is an Asrock 890FX Deluxe 4, AMD
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1137419
Title:
gnome-settings-daemon crashed with signal 5
To manage notifications about this bug go
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1137419/+attachment/3576373/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1137419
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1137419/+attachment/3576374/+files/ThreadStacktrace.txt
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
libgcc1 version
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1137418
Title:
colord-sane crashed with SIGSEGV in libusb_get_device_list()
To manage notifications about this bug
Yes! I can confirm too, sec=lanman works but now I'd like to know why
;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1113395
Title:
mount.cifs on 13.04 fails to mount a samba share with 13:
Public bug reported:
I think this is _related to_, but not necessarily the same as #1010131.
Lucid (10.04.4, fully up to date) cannot upgrade to Precise if the ibus-
hangul package is installed.
Steps to reproduce:
- Install 10.04.4 from an ISO (in this case ubuntu-10.04.4-desktop-amd64.iso).
-
Thanks for taking the time to report this issue and make Ubuntu better.
Confirmed. This needs an upstream sync, Debian Sid has a fix for this
issue on a later pre-0.9.26 version, and Debian Experimental has the
final 0.9.26 release.
I'm unsure if this should be backported for Quantal, but it'd
*** This bug is a duplicate of bug 283 ***
https://bugs.launchpad.net/bugs/283
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #283, so is being marked as such.
StacktraceTop:
zeitgeist_engine_insert_event (error=0x7fffa6094528, event=0x7fe62c010b00,
self=0xb0b830) at engine.c:1220
zeitgeist_engine_insert_events (self=0xb0b830, events=events@entry=0xb33920,
sender=sender@entry=0x7fe62c01fe30 :1.64,
result_length1=result_length1@entry=0x7fffa60945a4,
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1150792/+attachment/3576433/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1150792
Title:
** Attachment added: StacktraceSource.txt
https://bugs.launchpad.net/bugs/1150792/+attachment/3576434/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1150792
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1150792/+attachment/3576435/+files/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/bugs/1150792/+attachment/3561309/+files/CoreDump.gz
** Changed in: zeitgeist (Ubuntu)
one can try readlink and fall back to the thing that breaks under unusual
circumstances only if its not there.
But for ubuntu/debian we don't even need to care, we have readlink in coreutils.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same problem here... I'm installing Grizzly from Ubuntu PPA (grizzly-
trunk-testing) and my nova-scheduler.log shows up:
2013-03-15 16:39:11.205 858 CRITICAL nova [-] No module named simple
2013-03-15 16:39:11.205 858 TRACE nova Traceback (most recent call last):
2013-03-15 16:39:11.205 858 TRACE
Comment #5 solves the issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103202
Title:
grizzly scheduler can not start with import error
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129242
Title:
hud-service crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug go
*** This bug is a duplicate of bug 1033262 ***
https://bugs.launchpad.net/bugs/1033262
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1033262, so is being marked as such.
StacktraceTop:
~basic_string (this=0x7fff36c4b210, __in_chrg=optimized out) at
/usr/include/c++/4.7/bits/basic_string.h:536
pkgProblemResolver::DoUpgrade (this=0x7fff36c4b240, Pkg=incomplete type) at
algorithms.cc:730
__GI___libc_malloc (bytes=18321984) at malloc.c:2859
?? ()
?? ()
--
You
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1153819/+attachment/3576445/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153819
Title:
synaptic
** Attachment added: StacktraceSource.txt
https://bugs.launchpad.net/bugs/1153819/+attachment/3576446/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153819
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1153819/+attachment/3576447/+files/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/bugs/1153819/+attachment/3569093/+files/CoreDump.gz
** Changed in: synaptic (Ubuntu)
*** This bug is a duplicate of bug 1142546 ***
https://bugs.launchpad.net/bugs/1142546
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1142546, so is being marked as such.
Stacktrace:
#0 0x7fba3b37f037 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffb9db0de8
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 1 (LWP 18052):
#0 0x7fba3b37f037 in ?? ()
No symbol table info available.
Cannot access memory at address
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
libgcc1 version
I just fixed this in current git. Very stupid mistake this one :(.
Fix can be backported since no strings are involved. I'll try to upload
a *.patch tonight. Even better would be to get the current version
included, but seems unlikely as raring is in feature freeze.
--
You received this bug
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092936
Title:
rate limit cannot be disabled: imuxsock begins to drop messages
To manage notifications about this bug
reviewing bug #1092936 and the diff for this change, they don't appear
to be related; the SRU version just happens to be the verison that bug
#1092936 was reported against, there's not a causal relationship here.
** Tags removed: verification-failed
--
You received this bug notification because
** Bug watch added: GNOME Bug Tracker #695939
https://bugzilla.gnome.org/show_bug.cgi?id=695939
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=695939
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Changed in: oem-priority
Status: New = Confirmed
** Changed in: oem-priority/precise
Status: New = Confirmed
** Changed in: lupin (Ubuntu)
Assignee: (unassigned) = Brian Murray (brian-murray)
** Changed in: lupin (Ubuntu)
Status: Confirmed = Triaged
** Changed in:
Okay, I'll try that. Thanks. I'll report if it helps or not.
I haven't been able to disable it yet. Upon boot now it says the system
network services are not compatible with this version.
On Mar 15, 2013 3:20 PM, Miles Robinson 1155...@bugs.launchpad.net
wrote:
Disabling IPv6 worked for me, but
Public bug reported:
(Apologies for incorrect desktop environment terminology)
Just upgraded to 13.04 on my laptop. terminator seems to be having
issues with the global menu bar. That is, the terminator windows title
bar ends up being managed in the global menu bar, and leaves me no way
of
*** This bug is a duplicate of bug 1138829 ***
https://bugs.launchpad.net/bugs/1138829
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1138829, so is being marked as such.
*** This bug is a duplicate of bug 1054118 ***
https://bugs.launchpad.net/bugs/1054118
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1054118, so is being marked as such.
** Tags added: karmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155699
Title:
INSTALLATION
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1081307 ***
https://bugs.launchpad.net/bugs/1081307
** This bug has been marked a duplicate of bug 1081307
virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to
build [merge request]
--
You received this bug notification because
*** This bug is a duplicate of bug 1058825 ***
https://bugs.launchpad.net/bugs/1058825
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1058825, so is being marked as such.
*** This bug is a duplicate of bug 1152472 ***
https://bugs.launchpad.net/bugs/1152472
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1152472, so is being marked as such.
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097920
Title:
rsyslog SEGFAULT
To manage notifications about this bug go to:
** Package changed: ubuntu = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155658
Title:
desktop improvent that should be done
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1142546 ***
https://bugs.launchpad.net/bugs/1142546
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1142546, so is being marked as such.
*** This bug is a duplicate of bug 1105240 ***
https://bugs.launchpad.net/bugs/1105240
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1105240, so is being marked as such.
StacktraceTop:
g_main_context_wakeup (context=0x) at
/build/buildd/glib2.0-2.35.8/./glib/gmain.c:4315
?? ()
brasero_task_run_loop (error=0x7fff67620f68, self=0xe2a7b0) at burn-task.c:446
brasero_task_start_items (self=self@entry=0xe2a7b0,
error=error@entry=0x7fff67620f68) at
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1118006/+attachment/3576471/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1118006
Title:
brasero
** Attachment added: StacktraceSource.txt
https://bugs.launchpad.net/bugs/1118006/+attachment/3576472/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1118006
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1118006/+attachment/3576473/+files/ThreadStacktrace.txt
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/bugs/1118006/+attachment/3518117/+files/CoreDump.gz
** Changed in: brasero (Ubuntu)
Applying https://projects.kde.org/projects/playground/base/kio-
mtp/repository/revisions/1350841237002357ab5b7bc1ffb9ca139a85dfd2 should
do the trick, however the line numbers may differ greatly. As there have
been lots of other changes that affect stability greatly a complete
reimport would
Thanks for taking the time to report this issue and make Ubuntu better.
This definitely seems like something related to etckeeper first, so I'm
moving it there.
Based on the documentation [1] it looks like once you've setup etckeeper
you should only be using etckeeper itself to commit changes,
** Changed in: eglibc
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967149
Title:
Solution to Nvidia + cairo-gl memory problem proposed by Nvidia
To manage
*** This bug is a duplicate of bug 1132609 ***
https://bugs.launchpad.net/bugs/1132609
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1132609, so is being marked as such.
Today with image:
http://cdimage.ubuntu.com/daily-live/20130315/raring-desktop-armhf+omap4.img
After having my keyboard detected correctly and having clicked on the continue
button, I go to the Personal information window and I could not enter any
personal data there, I could not enter anything
** Summary changed:
- Pull in upstream biosdevname patches for 12.04
+ Upgrade biosdevname to 4.1 in precise
** Changed in: biosdevname (Ubuntu)
Assignee: (unassigned) = Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I ran into the same issue with the latest raring server release.
maas 1.3+bzr1452+df
python-oauth 1.0.1-3build1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005497
Title:
'maas test' fails:
*** This bug is a duplicate of bug 1121836 ***
https://bugs.launchpad.net/bugs/1121836
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1121836, so is being marked as such.
*** This bug is a duplicate of bug 1098451 ***
https://bugs.launchpad.net/bugs/1098451
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1098451, so is being marked as such.
*** This bug is a duplicate of bug 1105417 ***
https://bugs.launchpad.net/bugs/1105417
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1105417, so is being marked as such.
Looks like the typos that caused this were fixed in 0.9.7-0ubuntu7.7.
Marking Fix Released since this only affected -proposed to begin with.
** Changed in: jockey (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The card won't work on other boards since it's just a riser card, part
of the hardware stuff is located on the mobo while the sound chip is on
the riser card. It's exclusive to some Asus x48 Maximus/Rampage boards
with the *dedicated* black PCIe x1 slot for Supreme FXII Card. It will
never work
** Package changed: ubuntu = indicator-sound (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155653
Title:
unity soundvolume mouse bug
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1047143 ***
https://bugs.launchpad.net/bugs/1047143
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1047143, so is being marked as such.
Any thoughts on whether we should go logind for raring or not? I wonder
how much energy I should put into maintaining the logind PPA, and
playing catch-up with normal raring uploads. If we postpone that to
raring+1, then this is rather pointless.
Also, if we don't do logind, but want the D-BUS
*** This bug is a duplicate of bug 1137818 ***
https://bugs.launchpad.net/bugs/1137818
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1137818, so is being marked as such.
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116999
Title:
xfreerdp crashed with SIGSEGV in X509_get_issuer_name()
To manage notifications about this bug go
Is this still an issue for you? This looks like a transient problem
upgrading that may have already been resolved.
** Changed in: procps (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this still an issue for you? This looks like a transient problem
upgrading that may have already been resolved.
** Changed in: procps (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1155775/+attachment/3576517/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155775
Title:
Public bug reported:
Release: Lubuntu 13.04 daily build march 12, 2013
Screen resolution is not detected properly at boot.
xrandr -q shows only one resolution (1024x768), which means I can't change the
resolution once the system is up and running.
I'll attach the files Xorg.0.log (xorg.txt) and
*** This bug is a duplicate of bug 1153342 ***
https://bugs.launchpad.net/bugs/1153342
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1153342, so is being marked as such.
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155601
Title:
Bump to v1.9.1.5
To manage notifications about this bug go to:
801 - 900 of 1191 matches
Mail list logo
