*** 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
Desktop Bu
*** 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 becaus
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 u
*** 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
Desktop B
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
Desktop Bug
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 y
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 entry
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
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/571038
Title
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 sfdisk
@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 th
@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 connecte
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 udisks-1.0.
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 https://help.ubuntu.com/community/UpdatingA
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 place
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.
A
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 reco
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 https://
*** 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
Desktop Bugs, which is subscribed to gnome-di
*** 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
Desktop Bugs, which is subscribed to gnome-di
*** 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 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 duplica
*** 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 duplica
*** 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 duplica
*** 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 duplica
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
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.la
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"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/571038/+attachment/2237798/+files/git_diff_final
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
Desktop Bugs, which
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 bug
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
*
1f0
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.
--
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"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+b
*** 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
32 matches
Mail list logo
