** Changed in: gnome-disk-utility (Ubuntu)
Status: Triaged => Fix Released
--
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:
palimpsest crash with libg
Solution if you want to fix it permanently yourself without patching
udisks - see Bug #1093901 comment #3 - worked for me.
- Problem was nested extended partition
- Easy check that you are affected - sudo fdisk -l /dev/sda (if problematic
disk is /dev/sda) returns first row "omitting empty partit
** Changed in: gnome-disk-utility
Status: Confirmed => Expired
--
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:
palimpsest crash with libgdu:ERROR:gdu
** Changed in: udisks
Status: Confirmed => Won't Fix
--
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:
palimpsest crash with libgdu:ERROR:gdu-pool.c:23
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
This was also affecting me, but with the help of Mikhail (thank You bro!
can I send U a beer? ;) - comment #46 - my drives are mounting
properly.
Unfortunately I also had a problem with partition table (disk utility
showed a huge - kazillion TB - empty partition with at the end of disk,
GParted s
I'm affected this issue too, but patched udisks worked for me. Can we
have this patch in ubuntu-proposed at least?
--
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
Ti
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
Launchpad has imported 18 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=39603.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
** Changed in: gnome-disk-utility
Status: New => Confirmed
--
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:
palimpsest crash with libgdu:ERROR:gdu-poo
Mikhail, thanks a lot for your help here!
I have tried for an hour to replicate such a nested partition layout,
but haven't succeeded so far. The easiest and safest is to do "sudo
modprobe scsi_debug" and use the new virtual 8 MB device for this. I
used sfdisk and fdisk trying to recreate such a s
** Also affects: udisks via
https://bugs.freedesktop.org/show_bug.cgi?id=39603
Importance: Unknown
Status: Unknown
--
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/bu
** Description changed:
Binary package hint: gnome-disk-utility
gnome-disk-utility 2.30.1-1
- palimpsest
+ palimpsest
**
libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100)
Aborted
+
+ Good stack trace from a duplicate:
+ https
Anyway, thanks for Your effort Mikhail, Ill ty to do my best, to get my
system working, or just reinstall it - clean 11.10, without upgrading
from 11.04.. will see what the future brings..
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
hmm.. It seems You're right.. that's another problem..
I try to follow the topic You suggested..
Anyway, it's still a problem with udisks..
Wondering, if there is a possibility to completely remove udisks package from
the system, not affecting the whole desktop...
Then I would install it again and
@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
I'm talking about Configuration Editor (GConf):
http://imageshack.us/f/40/screenshotat20120307174.png/ (screenshot).
"Are you sure you've installed built and patched udisks?" - Yes.
"Are you running 11.10 with 1.0.4-1 version of udisks?" - That's right.
"Are you able to start palimpsest?" - Yes an
Now to make sure I have Your patched version in the system installed,
apt-get shows me to upgrade "udisks" - so it is good, cause there is no
"hold" now. Ok.. firstly I thought this problem was only in GnomeShell,
which I used recently, but now I know this affects all the system and
the problem is
@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
Hmm.. weird... I did everything as You wrote Mikhail, but it still doesn't
work..
When I run "apt-get upgrade", I get info line as following:
"The following packages have been kept back: udisks"
I think this isa good info, cause Ive installed source version, but.. why it
doesn't work...
In the c
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.
@Mikhail, to be honest, I've just removed the "ommiting.." text :)
All I did was removing the partition created with Paragon software, and
creating it again using gparted.
Now it looks fine, and I think this is ok.
But still having problem with udisks, autmounting.. ehh...
Basically I just downloa
Ok - I understand, this is a problem with the paragon software.
But is there a way to fix my system for me as a basic linux user?
I don't know how to patch it etc. unless I have a step-by-step guide.
So please let me know how to fix this or where I can find the how-to.
Thanks - Helmut
Ubuntu 10
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
Ok, I got it Mikhail, thank You for the info.
I've downloaded the same version of udisks as I have in my ubuntu (it's:
1.0.41).
Then I unpacked the source code and applied with Your patch.
Everything was ok.. Configure - ok. Make - ok. Even make check said everything
is ok.
But make install - fai
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
Hi. I have a similar problem. But with no overlapping and no bad numbering...
Even gparted shows the whole hard drive in a good condition, with all
partitions on it, without any spaces etc..
But my "disk-utility" (palimpsest) doesn't work and shows me this error:
"**
libgdu:ERROR:gdu-pool.c:2369:
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
@ Mikhail Titov
I'm having the same issue with an Ubuntu 10.10 installation.
I did use the Paragon software to do the partitioning.
I'm using a Samsung SSD as boot device.
sudo fdisk -l reports the following:
Platte /dev/sda: 128.0 GByte, 128035676160 Byte
255 Köpfe, 63 Sektoren/Spur, 15566 Zyli
I did a reinstall and it started working again. The odd thing is that I
*did* run into this bug when booted from the same CD I did the install
from.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https:/
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
OK, managed to fix it following this advice:
http://leisurehours.wordpress.com/2010/03/15/partition-table-entries-
are-not-in-disk-order-problem/
That required some repair on the GRUB command line, set root and all
that, then got my system to boot into Ubuntu and had to do both update-
grub and g
Hello,
Just created an account here so I could comment. I just started seeing
this bug.
Don't know if it will still help, but the output of sudo sfdisk -d
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
# partition table o
** Tags added: patch
--
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:
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse:
assertion failed:
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
One more data point, I've confirmed that this problem occurrs on the
same machine when booting from the natty 11.04 cd both i386 and amd64,
while it never happens with the same external drive on another machine
running natty.
--
You received this bug notification because you are a member of Ubunt
I followed Somogyi Ádám's solution and it did work. However I had to
reinstall grub(!) and I'm having all sorts of strange error messages:
sudo gparted
Error informing the kernel about modifications to partition /dev/sda2 -- Device
or resource busy. This means Linux won't know about any changes
Regarding #21, I just did fixparts repair on one of the disks I have and
I'm still getting the palimpsest error and it still won't auto mount.
Also remember that I at least can automount the same disk on a different
ubuntu natty system just fine. So it seems likely that there is some
sort of drive
Regarding #22, "sudo grub-install /dev/sda" did not fix my problem,
still seeing it.
--
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:
palimpsest crash with l
GRUB re installation (caused by something else) solved the problem.
Everything, especially automount and palimpsest, works fine now.
--
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.n
Hi, I was getting this same error, since I've installed natty.
Automounting was not working with partitions, CDROMs and USB keys.
My partition table looked OK to me, only fdisk complained something
about an empty partition being omitted.
I've tried fixparts from the gptfdisk utilities, and it hel
Mike Bell wrote:
"Update: Fixed my partitions and I'm no longer getting an error running
palimpsest."
I would be interested know how the partitions were fixed.
toolman59
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-ut
This affects only one of my two Ubuntu Natty systems. The same
removable drive automounts on one but not the other. With no removable
drive, the broken one gives the following:
$ /usr/lib/gvfs/gvfs-gdu-volume-monitor
**
libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed:
I think the problem here is that the partitions are not in the same
order as they are physically located on the disk. This is also causing
the parted bug (bug #103794). It would be much better if gparted could
fix this problem instead of just showing unallocated disk space. I guess
there is no easy
** Tags added: natty
--
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:
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse:
assertion failed:
After some investigation I don't see any problem with my partition
table. Or maybe it's a problem that the partition are not in the correct
order?
fdisk -l
omitting empty partition (5)
Disk /dev/sda: 300.1 GB, 300090728448 bytes
255 heads, 63 sectors/track, 36483 cylinders
Units = cylinders of 16
I'm having the same problem with Natty-beta. When I start either
palimpsest, update-notifier or gdu-notification-daemon I'm getting the
same error message:
krychek@hostname:~$ /usr/lib/gnome-disk-utility/gdu-notification-daemon
**
libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (de
** Tags added: maverick
--
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:
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed
Same error here.
My fdik -l and gparted are working fine. However I get:
zebu...@ordrealphabetix:/etc$ sudo palimpsest
**
libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion failed: (depth < 100)
Aborted
Nothing is showing up on my system's disk mounter applet apart of the
bootable (root) fi
** Changed in: gnome-disk-utility (Ubuntu)
Status: Triaged => Confirmed
--
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:
palimpsest crash with libgdu:
** Changed in: gnome-disk-utility
Status: Unknown => New
** Changed in: gnome-disk-utility
Importance: Unknown => Medium
--
palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed: (depth < 100)
https://bugs.launchpad.net/bugs/571038
You received this bug n
** Summary changed:
- palimpsest
+ palimpsest crash with libgdu:ERROR:gdu-pool.c:2369:device_recurse: assertion
failed: (depth < 100)
** Changed in: gnome-disk-utility (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-disk-utility (Ubuntu)
Status: Confirmed => Triaged
**
Hi, I am the gentoo user that have this problem. This is my situation:
I have 3 hard disk: WD 320 GB 2.5 Backup (connected directly on mainboard), WD
Raptor 150GB Gentoo (connected through an Enermax Mobil Rack), Seagate 320GB
3.5 Win7(connected through an Enermax Mobil Rack).
Now for high temperat
udisks --dump | awk '{if($1=="type:" || $1=="Showing") print}':
Showing information for /org/freedesktop/UDisks/devices/sda
type:
Showing information for /org/freedesktop/UDisks/devices/sda1
type:ext2
type: 0x83
Showing i
sfdisk -d:
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 2048, size= 190464, Id=83, bootable
/dev/sda2 : start= 195313, size=321475855, Id= f
/dev/sda3 : start=0, size=0, Id= 0
/dev/sda4 : start=0, size=0, Id= 0
/dev/sda5 : start= 195314,
sfdisk -d /dev/sda:
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 63, size=144938367, Id= 7, bootable
/dev/sda2 : start=144938430, size=245762370, Id= f
/dev/sda3 : start=147043008, size= 40965687, Id=83
/dev/sda4 : start=0, size=0, Id= 0
/dev/sda5 : start=14
This is the output from affected user:
sfdisk -d /dev/sda:
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 63, size= 2104452, Id= 6
/dev/sda2 : start= 2104515, size=147460635, Id= c
/dev/sda3 : start=149565150, size= 10249470, Id= c
/dev/sda4 : start=159814620, size=1332321
I seem to overlooked a detail above.
>From Pacho Ramos partition list:
--
# fdisk -l
omitting empty partition (5) <--- HERE
(...)
---
So even fdisk is complaning about error in the partitions.
Combined with your example it seems to further confirm that an error in the
partition tables causes
Update: Fixed my partitions and I'm no longer getting an error running
palimpsest. I imagine that gparted and other disk-oriented programs have
various ways of figuring out the partition structure even w/ slightly
messed-up partition tables, whereas palimpsest's method of enumerating
the partitions
I'm now getting this error as well. nandox7, I think you've got it
pretty much nailed. The code is having trouble reading the partition
table or EBR or ? Not-too-coincidentally, yesterday I installed Paragon
B&R 10 FE on my Win7 partition, and was testing it by backing up and
restoring my Win7 part
The error comes from here:
gdu-pool.c (libgdu0)
--
(...)
static void
device_recurse (GduPool *pool, GduDevice *device, GList **ret, guint depth)
{
gboolean insert_after;
/* cycle "detection" */
g_assert (depth < 100); <--- HERE
insert_after = FALSE;
if (g
This is from affected user in gentoo:
# fdisk -l
omitting empty partition (5)
Disco /dev/sda: 150.0 GB, 150039945216 byte
255 testine, 63 settori/tracce, 18241 cilindri, totale 293046768 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size
Can you get some details from the devices and partitions that you have
on your system?
Something like:
$sudo fdisk -l
--
palimpsest
https://bugs.launchpad.net/bugs/571038
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility
This also affected to a few people at Gentoo:
http://bugs.gentoo.org/show_bug.cgi?id=321971
But we still have no idea about where is the problem :-(
** Bug watch added: Gentoo Bugzilla #321971
http://bugs.gentoo.org/show_bug.cgi?id=321971
--
palimpsest
https://bugs.launchpad.net/bugs/571038
Upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=622066
** Bug watch added: GNOME Bug Tracker #622066
https://bugzilla.gnome.org/show_bug.cgi?id=622066
--
palimpsest
https://bugs.launchpad.net/bugs/571038
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Confirmed
--
palimpsest
https://bugs.launchpad.net/bugs/571038
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu.
--
desktop-bugs mailing list
d
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45848167/Dependencies.txt
--
palimpsest
https://bugs.launchpad.net/bugs/571038
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu.
--
de
76 matches
Mail list logo
