** Branch linked: lp:debian/parted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
to Default of []
To manage
** Branch linked: lp:ubuntu/saucy-proposed/parted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
to Default of
This bug was fixed in the package parted - 2.3-14
---
parted (2.3-14) unstable; urgency=low
* Merge fix-head-size-assertion.patch from Ubuntu: change an
assert so it correctly recovers instead of aborting the program
(closes: #620273).
* Merge dm_p_separator.patch from
** Changed in: unity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
Oops, I've uploaded a fixed version now, please update and try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set
On 06/19/2013 12:43 PM, Phillip Susi wrote:
Oops, I've uploaded a fixed version now, please update and try again.
Now that's much better. No launcjer blacklist nonsesnse app works
correctly with no warnings, reported errors, ect.
--
You received this bug notification because you are a member
The script that invokes GParted uses hal-lock, udisks, devkit-disks, and
most recently systemctl to exclusively lock or otherwise prevent
automounting on disk devices.
The history of these tools being installed by default in Ubuntu appears
to be:
- Uses HAL (Hardware Abstraction Layer) at least
Oops, sentence referring to fedora should read:
Hovever systemd is NOT installed by default in Ubuntu.
See https://en.wikipedia.org/wiki/Systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 18 June 2013 17:43, Curtis Gedak ged...@gmail.com wrote:
The script that invokes GParted uses hal-lock, udisks, devkit-disks, and
most recently systemctl to exclusively lock or otherwise prevent
automounting on disk devices.
The history of these tools being installed by default in Ubuntu
The actual mounting or not mounting isn't related to this issue. Simply
having the device (re)appear causes Unity to show it, even though it is
not mounted until you try to open it, thus inhibiting udisks doesn't
help.
--
You received this bug notification because you are a member of Ubuntu
Dmitrijs,
Thank you for pointing out the udisks2-inhibit command.
Phillip,
Have you tested using udisks2-inhibit to see if it helps?
For example:
sudo /usr/lib/udisks2/udisks2-inhibit /usr/sbin/gpartedbin
--
You received this bug notification because you are a member of Ubuntu
Bugs,
No, and for some reason I am currently unable to reproduce the problem
with gparted, but I'm pretty sure it has been around since before
udisks2 as I have always been bit by this when building parted, whose
test suite creates a lot of temporary devices/filesystems to use for
testing, and udisks
For reference - Bug 1053704
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
to Default of []
To manage
The only difference between disks gparted is the syncing/refreshing occurs
when gparted is opened, disk's only does so once some action (partitioning) has
occurred.
At the end of the day unity will clear the blacklist if any partitioning takes
place so 'solving' this has limited benefit
The only difference between disks gparted is the syncing/refreshing occurs
when
gparted is opened, disk's only does so once some action (partitioning) has
occurred.
When gparted starts up, it makes a call to the libparted library
function ped_disk_commit_to_os(). This checks to see if the
or
C) Remove this check, and let resize/move operations fail later.
Note that based on Doug's comment #41, it appears that the blacklist will
be cleared whenever the partition table is actually changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Can you run sudo apt-add-repository ppa:psusi/ppa, then apt-get update
and apt-get upgrade and see if that fixes it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
On 06/18/2013 09:05 PM, Phillip Susi wrote:
Can you run sudo apt-add-repository ppa:psusi/ppa, then apt-get update
and apt-get upgrade and see if that fixes it?
As far as, do partitions show up in the launcher?, no, the ppa
package(s) fix that the blacklist remains as is.
Though the gparted
So I figured out why this is happening. It seems that gparted syncs the
partition table on startup, just to make sure that it can. To do this,
libparted removes all existing partitions, and then re-adds them. It
seems that unity decides to un-blacklist a drive if you unplug it and
plug it back
Hi Phillip,
Would it make sense for libparted to re-blacklist the partitions that
were blacklisted before Unity un-blacklisted them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
No, since libparted has no idea what unity is or where it stores its
blacklist, nor should it. I think Unity should not be un-blacklisting
the drive just because you yank it and reinsert, but I'm working on
patching libparted to avoid removing and re-adding partitions that
haven't changed, so it
Well now I can't seem to reproduce the problem under 13.04, can you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set
Yes,
I can reproduce 100% of the time using either 1304 3.8.0-25-generic #37-Ubuntu
SMP Thu Jun 6 20:47:07 UTC 2013 or
1310 3.9.0-6-generic #13-Ubuntu SMP Fri Jun 14 15:47:09 UTC 2013 builds.
Although it is probably not significant, each OS was installed in a free
logical partition.
--
You
Just to make sure, you unlock the drive from the launcher, fire up
gparted, and it reappears?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
The same behavior is still seen in 13.04 13.10. The blacklist will be reset
to [] after running gparted.
(If one has any 'orphaned' blacklist entries then it won't be reset to []
though after opening gparted the result will still be the same, persistent
icon(s) returned to launcher.
And
In either OS, I just unlock the partitions from the launcher, fire up
gparted, and they reappears. ALL partitions on the hard drive that
contains the OS being run except that OS and the swap. Partitions on
other disks do not show up.
Grub2 lives on /dev/sda but none of the sda partitions get
The bug is still open; you don't need to comment every week or two to
make that clear. Doing so only adds clutter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
This CLUTTER-BUG still exists in 13.04 Gparted 0.12.1 and 13.10dev
Gparted 0.14.1
Locking every partition on the disk containing the currently running OS
except for the swap partition results in CLUTTER. Please provide a way
for this unwanted behavior to be disabled.
--
You received this bug
In addition to 12.10 and 13.04, this bug also manifests in 64-bit 1310
3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013
How can I disable this behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Except for dependency upon Nvidia drivers, I would be quite satisfied with
12,04.
I really would like to put Nvidia drivers in the trash where they belong.
The list of 13.xx BUGs preventing the switch from 12.04 is getting shorter.
Please shorten the list by fixing this BUG promptly. Thanks.
In addition to 12.10 and 13.04, this bug also manifests in 64-bit 1310
3.9.0-0-generic #4-Ubuntu SMP Thu May 2 21:43:59 UTC 2013
How can I disable this behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using 64-bit RELEASED 13.04 Desktop, Gparted still locks almost ALL
partitions that exist on the same drive as the OS to the launcher. The
swap partition and the partition containing the running OS do not get
locked to the launcher.
--
You received this bug notification because you are a
That's how Unity works Ernie. It shows you your drives until you tell
it not to. This bug is about it forgetting you asked it not to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
Phillip,
Thanks for clarifying that the Unity behavior in 1166996 is by design.
Since it changed significantly from 12.04 the design change was
interpreted as a bug.
As for 1060484 and 1167002, Gparted exhibits similar behavior which is a
real pain.
--
You received this bug notification
When either 12.10 or 13.04 gets launched after installation, ALL
partitions on the drive containing the OS except the OS partition and
the swap partition get locked to the launcher and will stay that way
following a reboot. If all locked partitions on that drive are
individually unlocked, they
This bug also occurs in 64-bit 1304 (Raring) 3.8.0-18-generic #28-Ubuntu
SMP Thu Apr 11 19:38:55 UTC 2013
When Gparted is executed, does it run any of the same code that Raring
does when Raring is initially started?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Assume a desktop system with multiple hard drives where each hard drive
contains several ext4 partitions.
Mounting a single one of those partitions under 12.04 will result in ONLY the
icon for the newly mounted partition to be temporarily added to the launcher
icons. When that partition is
This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-6-generic.
Tested Friday 2013-02_16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
There are also other instances where the blacklist is reverted, nothing to do
with gparted.
Right now have 2 out of 3 previously blacklisted drives showing in the launcher
9haven't yet found the trigger, if any thing specific
(seen on both raring quantal
--
You received this bug notification
This bug also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-3-generic.
Tested Friday 2013-02_01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
Another data point. 12.10 and 13.04 exhibit the SAME behavior when
initially started.
This bug STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-2-generic.
Downloaded and tested today 2013-01_27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: unity (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gparted (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/1060484
Title:
Andrea, the problem is not in gparted. I'm not sure exactly what unity
is seeing from udisks, and whether udisks is doing the right thing, but
the bug is either in udisks not telling unity the right thing, or in
unity removing the blacklist when it shouldn't.
** Project changed: gparted =
** Changed in: unity
Milestone: None = 7.0.0
** Changed in: unity
Status: Confirmed = Triaged
** Changed in: unity
Assignee: (unassigned) = Andrea Azzarone (andyrock)
** Changed in: unity (Ubuntu)
Assignee: (unassigned) = Andrea Azzarone (andyrock)
--
You received this
For what I see the problem is in GParted that removes (remove !=
unmount) all the volumes.
** Also affects: gparted
Importance: Undecided
Status: New
** Changed in: unity
Status: Triaged = Invalid
** Changed in: unity (Ubuntu)
Status: Confirmed = Invalid
** Changed in:
This bug STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-0-generic.
Downloaded and tested today 2013-01_14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted
Another confirmation for quantal amd64 with kernel 3.5.0-21-generic,
with gnome-tweak-tool installed, plus xubuntu-desktop and lubuntu-
desktop installed alongside. Can right clickunlock from launcher, and
disable 'show mounted drives' in gnome-tweak-tool, but all mounted
drives return when
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is set back
to Default of []
To manage notifications
** Also affects: unity
Importance: Undecided
Status: New
** Changed in: unity
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/1060484
Title:
When using
This bug STILL occurs in 64 bit 1210 (Quantal) with kernel
3.5.0-21-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices blacklist is
Will this BUG be fixed before 13.04 or should I AVOID 12.10 and continue
to use 12.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060484
Title:
When using gparted com.canonical.Unity.Devices
This annoying and cluster-producing BUG is NOT present in 12.04
If the powers that be deem this changed functionality important, so be
it, as long as they also provide a way to configure Gparted in such a
manner as to disable this new behavior.
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** 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.
https://bugs.launchpad.net/bugs/1060484
Title:
When
** Summary changed:
- gparted resets com.canonical.Unity.Devices blacklist back to Default of []
whenever it starts
+ When using gparted com.canonical.Unity.Devices blacklist is set back to
Default of []
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
55 matches
Mail list logo
