Public bug reported:
This package failed to be configured during an upgrade.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: gconf2 3.2.6-3ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture:
Here's some more info:
I ran "dpkg --configure -a" as root, which failed.
Then I ran "sudo dpkg --configure -a" as my user with sudo privileges
and it worked. Now my system is not in an unconfigured state.
--
You received this bug notification because you are a member of Desktop
Packages,
AFAICT, the code doesn't do anything with gids. It only creates the user
ACL.
Also, I understand there are other files that probably need their perms
changed. However, my only point was that udisks is in a position to be
more helpful by either informing the user of what is happening or
rewriting
Sure, changing a uid is not that common, but it is a supported operation
through the usermod tool, and there are valid reasons to do it.
In this specific case, I didn't change the uid while logged in. I logged
out, logged in with a different user on tty1, sudo -i to get a root
shell, then changed
This bug is not invalid. There is a very real UX concern here.
** Changed in: udisks2 (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1335384
Here's some links to code.
Here's the upstream code link:
http://cgit.freedesktop.org/udisks/tree/src/udiskslinuxfilesystem.c#n899
Here's the Utopic code:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/udisks2/utopic/view/head:/src/udiskslinuxfilesystem.c#L891
Here's the trusty
Okay, if I understand this correctly, you're saying that we shouldn't
even tell the user that the directory that udisks would have created has
different permissions than what udisks would have created it with?
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
I am using a just updated copy of 14.04. The version of the udisks2
package is 2.1.3-1.
I changed the UID of a user on my system from 1001 to something else.
After the change, the ACL permissions on /media/username still
reflected the old UID. After I deleted the directory
Similar to bug 1265885. FTR, I tried the blacklist trick and it worked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1273403
Title:
[Dell XPS 13 9333] Touchpad not detected correctly
Public bug reported:
The network-manager service doesn't start automatically after I boot up
a laptop recently upgraded to Quantal.
Here's the /etc/network/interfaces:
auto lo
iface lo inet loopback
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You
Actually, I copied the /etc/network/interfaces from the wrong computer. Here's
the right one:
auto lo
iface lo inet loopback
auto sprint
iface sprint inet ppp
provider sprint
That second interface had no chance to successfully come up as I don't even
have that wifi card anymore. When I
BTW, this is a regression in functionality. I hope it can be fixed
before the final as it's a bad scenario where an improper auto stanza in
a network configuration can stop network-manager from starting. This
could catch people off guard.
Is there anything else I can do to help track this down?
** Description changed:
The network-manager service doesn't start automatically after I boot up
a laptop recently upgraded to Quantal.
- Here's the /etc/network/interfaces:
- auto lo
- iface lo inet loopback
+ == Regression details ==
+ Discovered in version: 0.9.6.0-0ubuntu7 (12.10 beta
13 matches
Mail list logo
