apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898911/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898917/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898914/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
Title:
apport information
** Tags added: apport-collected saucy
** Description changed:
Failed to wake up from suspended state. Happened for the first time
after upgrade to Raring. Previously maybe happened twice over several
years on Precise though I'm not sure if it was same reason with
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898912/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
Title:
[ARIMA
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898915/+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/1103492
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898913/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898923/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898920/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898919/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898922/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898916/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898921/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103492
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1103492/+attachment/3898918/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #689312
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689312
** Also affects: auto-complete-el (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689312
Importance: Unknown
Status: Unknown
--
You received this bug notification
Christopher, I'm not sure whether it would be helpful in this case. It
is assembled in Russia something called Bliss 507s. Here you can find
pics and specs of an exact model
Brad, I do try to stay up to date. These kinds of bugs are really rare
for me but I guess it still worth reporting them. When it happened after
your last comment my last upgrade, apport (?) did not recognize an
existing bug but created another one
@suv You are running an outdated libxml2. Looks like it is a regression
bug in 2.9 which is shipped with Ubuntu 13.04. See
https://github.com/lxml/lxml/issues/98
I cannot narrow down the problem to simple reproducible example. You can
build libxml2 from git and test for yourself. Here is the
** Bug watch added: GNOME Bug Tracker #694982
https://bugzilla.gnome.org/show_bug.cgi?id=694982
** Also affects: libxml2 via
https://bugzilla.gnome.org/show_bug.cgi?id=694982
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I set a breakpoint at script.cpp:712 and I can see that it is just that
script fails to produce well formed XML
/opt/inkscape/share/inkscape/extensions/color_morelight.py
/tmp/ink_ext_XX.svgJ80RTW | xmllint -
-:12: parser error : AttValue: ' expected
6vs9RiG3hXUZuZlJhFgd
I can reproduce it with trunk revision 12155. I feel like it might be
something with underlying libraries on Ubuntu 13.04 32 bit. I don't know
how muh time we want to put into investigation... Though it would be
nice if inkscape was more dumb-proof and could withstand non-trivial
menu clicking :-)
It happens only when image is embedded. Something is broken with base 64
representation for that particular photo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130225
Title:
inkscape crashed with
I had a thought that it was not the right menu. Indeed Extension-Raster
does work fine.
It is 100% reproducible with at least one particular file. I tried to
copy the file to /tmp/ and start from there with the same result.
Interestingly enough that it does not crash either with a clean start or
I thought it was something in metadata. But after I stripped it with
exiftool, it still crashes on such action. I attach unstripped version.
I feel like it is something about this particular camera. All other
photos I tried from same camera also crash inkscape.
I failed to attach 344k file here.
Public bug reported:
This happened after upgrade. kernel was upgraded among other things. I
let laptop fall into sleep instead of restarting it. I don't know
whether it is a coincidence or not.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-6-generic 3.8.0-6.13
*** This bug is a duplicate of bug 1061554 ***
https://bugs.launchpad.net/bugs/1061554
** This bug has been marked a duplicate of bug 1061554
assertion failure `trap != NULL' displayed by all GTK3 software
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Same file in both packages.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-4-generic 3.8.0-4.8
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Public bug reported:
I don't know if this is related to previous bug I submitted
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1103492 . Apport
gave it different summary name.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-1-generic 3.8.0-1.5
Public bug reported:
Failed to wake up from suspended state. Happened for the first time
after upgrade to Raring. Previously maybe happened twice over several
years on Precise though I'm not sure if it was same reason with
older kernel.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Public bug reported:
In Raring Ringtail version of Tomboy 1.12.0, it is impossible to delete
a note by right clicking on it and choosing delete. Corresponding option
is greyed out.
See also https://bugzilla.gnome.org/show_bug.cgi?id=634404#c3
** Affects: tomboy (Ubuntu)
Importance:
Note that it is not only about moving but renaming as well (leading dot
removal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068549
Title:
better ~/.fonts.conf deprecation warning
To manage
** Information type changed from Private to Private Security
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100165
Title:
Crash while
*** This bug is a duplicate of bug 1086369 ***
https://bugs.launchpad.net/bugs/1086369
** This bug has been marked a duplicate of bug 1086369
alacarte crashed with ImportError in /usr/share/alacarte/Alacarte/util.py :
cannot import name GError
--
You received this bug notification
Public bug reported:
I was trying to follow OpenDAP example [1] and got the following:
yes? SHADE temp[z=0]
PPL+ error: Unable to read default.spk to set shade and fill colors.
PPL+ error: Unable to read default.spk to set shade and fill colors.
At line 169 of file symbel.f (unit = 10,
*** This bug is a duplicate of bug 738241 ***
https://bugs.launchpad.net/bugs/738241
** This bug has been marked a duplicate of bug 738241
gvfs-gdu-volume-monitor crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It is a possible duplicate of #571038 .
I had gvfs-gdu-volume-monitor crashed after I upgraded to Precise from Oneiric.
Since I'm affected by #571038, I had to patch udisks. After that
gvfs-gdu-volume-monitor did not crush for me.
Does palipmsest tool start okay for you? If not try patching (or
Bartolomiej, sure, you can send me one:-) Though a wheatgrass shot is
preferred.
In case someone has no skills to apply a patch, here is the link to ppa
for oneiric https://launchpad.net/~mtitov/+archive/udisks
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I just realized that I cannot fully test by using palimpsest as I do
have broken partition table myself. However /lib/udev/udisks-part-id
does report incorrectly partition type for scsi_debug device. Thus I
think I reproduced it correctly. Here is how.
1. Create msdos partition table
2. Use
oops. Disregard previous post as I can't delete it. part-id does report
UDISKS_PARTITION_TYPE=0x83 and not 0x05
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571038
Title:
palimpsest crash with
The following should be step 2.5 (i.e. between 2. and 3.)
dd if=/dev/sdb1 of=/dev/sdb1 seek=446 skip=462 count=16 bs=1
dd if=/dev/zero of=/dev/sdb1 seek=462 count=16 bs=1
Explanation:
It turned out that though sfdisk recognized an attempt to write 0-sized
partition, it still writes correct
Here is the screenshot from my terminal showing part-id results on
scsi_debug device before and after my patch. Look at
UDISKS_PARTITION_TYPE . Before it was reported as 0x05 and after I
installed patched version back, it became 0x83 as it is supposed to be.
From what I remember (it was 0.5 year
@elvis_ef I suspect you are having a different issue. Is this relevant
http://ubuntuforums.org/showthread.php?t=1721377 ?
My patch is only for this bug when unpatched palimpsest crashes as
described by original poster. It can't help if you are having problems
with udisks-daemon.
P.S. Generally
@elvis_ef
I have no idea what configuration editor you are talking about. Are you sure
you've installed built and patched udisks? Were there any rejects? Are you
running 11.10 with 1.0.4-1 version of udisks? Are you able to start palimpsest?
Try various combinations. With/out usb device
Once again. It is a fault of neither palimpsest nor libgdu but udisks!
Just get a source package for udisks, apply my patch attached here,
build, and install it. That is it.
It is not the matter of overlapping or wrong numbering, it is an empty
record which
a) should not be there in a first
I'm not sure how you are building the software. Usually you just apt-src
it, patch it, and build using corresponding tools for packages. Try not
to use vanilla source. Make sure you have all dependencies installed
using apt-get build-dep udisks.
Consider
I've uploaded a package to ppa but I don't know how long it would take and if
it is okay it was unsigned.
Here is a step-by-step instruction for 11.10. Make sure you are in sudoers list
(https://help.ubuntu.com/community/Sudoers)
sudo apt-get install apt-src
apt-src install udisks
cd
Glad to hear that my guess was correct. I personally applied patch I
posted here against udisk source package and rebuilt it. It works for me
in 11.10 and I bet it won't be fixed as it is a bug with Paragon's
software. You can also try to fix partition table as Paul R. Potts (?)
explained above.
Just small comment in case someone is having similar issue.
I had to disable AdBlock in firefox :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/196308
Title:
[Hardy] Server can never be reached
I feel like the original issue is likely caused by Paragon software that
creates so called empty partitions. All looks like fdisk can remove
those (I didn't know). It would be nice if you tried fdisk -l first as
fdisk reports empty partitions.
P.S. Empty partition means that extended boot record
What error message do you get when you run palimpsest when hdd is
connected? Could you add strace output? Also I'm curious about fdisk -l
/dev/sda (yes, sda and not sdb) if it mentions something like omitting
empty partition. From XsessionErrors.txt I have a suspicion that it is
related to
I also confirm #34 on 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769866
Title:
tab completion no longer escapes filenames and completes dirnames
incorrectly (space instead of slash)
To
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug has been marked a duplicate of bug 571038
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed: (depth 100)
--
You received this bug notification because you
It would be nice if ubuntu could release patched package first as
crashing update-notifier pissed me off completely.
** Patch added: udisks needs to be patched to close this bug
Just to confirm that this patch solved an issue for me. I got source
with apt-get, patched it, and installed it. palimpsest starts just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571038
*** This bug is a duplicate of bug 450550 ***
https://bugs.launchpad.net/bugs/450550
This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-
disk-utility/+bug/571038
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug is no longer a duplicate of bug 435136
gvfs-gdu-volume-monitor assert failure:
libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth 100)
** This bug has been marked a
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug is no longer a duplicate of bug 435136
gvfs-gdu-volume-monitor assert failure:
libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth 100)
** This bug has been marked a
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug is no longer a duplicate of bug 435136
gvfs-gdu-volume-monitor assert failure:
libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth 100)
** This bug has been marked a
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug is no longer a duplicate of bug 435136
gvfs-gdu-volume-monitor assert failure:
libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth 100)
** This bug has been marked a
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug has been marked a duplicate of bug 571038
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed: (depth 100)
--
You received this bug notification because you
*** This bug is a duplicate of bug 454419 ***
https://bugs.launchpad.net/bugs/454419
A duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-disk-
utility/+bug/571038
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 454419 ***
https://bugs.launchpad.net/bugs/454419
A duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-disk-
utility/+bug/571038
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I conclude that there is a problem (?) with udev that lacks support for
nested partition http://www.ata-atapi.com/hiwtab.html#T4 and probably
only linked extended partitions are properly supported. That explains
that weirdness I saw in my ebr, i.e. no link to another ebr.
--
You received this
This bug is probably related to
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/571038
as both results from incorrect data from udev udisks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the link on bug I submitted with udisks
https://bugs.freedesktop.org/show_bug.cgi?id=39603
** Bug watch added: freedesktop.org Bugzilla #39603
http://bugs.freedesktop.org/show_bug.cgi?id=39603
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
sfdisk shows correct information. However when I look into EBR it
doesn't make any sense to me.
$ dd if=/dev/sda2 count=1 of=ebr
$ hexdump ebr
000
*
1c0 feff 5705 fec8 003e a2ea 052f
1d0
*
*** This bug is a duplicate of bug 571038 ***
https://bugs.launchpad.net/bugs/571038
** This bug has been marked a duplicate of bug 571038
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed: (depth 100)
--
You received this bug notification because you
Here is how it develops from looking from eclipse. Don't have time to
investigate more for now, but I hope it can be useful.
** Attachment added: Debugging session in Eclipse+CDT, showing endless
recursion while working on sda5
Regarding #13, I feel like this is the root of the evil. In my case it
also reports type 0x05 for my root linux partition on /dev/sda5 . This
in turn is interpreted incorrectly by find_extended_partition() in gdu-
pool.c that thinks it is an extended partition and goes into infinite
recursion.
--
*** This bug is a duplicate of bug 574237 ***
https://bugs.launchpad.net/bugs/574237
** This bug has been marked a duplicate of bug 574237
gdecrypt does not start - window appears for a blink, thats it. If I run
gdecrypt in the console it says /usr/bin/env: python2.5: No such file or
I've got this warning on Lucid Lynx with 2.6.34-020634rc7-generic kernel
upon resume from ram-suspend.
--
Corrupted low memory at kernel warning on resume
https://bugs.launchpad.net/bugs/324894
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
71 matches
Mail list logo
