** Patch added: "on top of 1:1.7.7.3-1 for precise"
https://bugs.launchpad.net/bugs/906631/+attachment/2640476/+files/git-instaweb.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906631
Title:
Public bug reported:
Patch against 1:1.7.7.3-1 attached.
Description: If I edit the .git/gitweb/gitweb_config.perl file and then
restart a git-instaweb instance, my modifications to the config file
will be overwritten by the default config. This is because there is a
call to gitweb_conf() without
** Patch added: "git log completion config with support for --oneline option"
https://bugs.launchpad.net/bugs/845194/+attachment/2374240/+files/zshgitlog.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
The attached patch against lucid zsh 4.3.10-5ubuntu3 completion config
for git log adds support for --oneline option.
** Affects: zsh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Package changed: make (Ubuntu) => make-dfsg (Ubuntu)
--
Incorrect per-target ?= variable affectations
https://bugs.launchpad.net/bugs/483086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35718303/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/35718304/XsessionErrors.txt
--
Incorrect per-target ?= variable affectations
https://bugs.launchpad.net/bugs/483086
You r
Public bug reported:
Binary package hint: make
I am running 9.10 on x86_64 (updated yesterday), make 3.81-6.
The following Makefile:
-
target1: OPTVAR?=/usr/local
target1:
echo "Value for $@ '$(OPTVAR)'."
target2:
echo "Value for $
FYI, Filed bug report https://bugs.freedesktop.org/show_bug.cgi?id=25097
** Bug watch added: freedesktop.org Bugzilla #25097
https://bugs.freedesktop.org/show_bug.cgi?id=25097
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
https://bugs.launchpad.net/bugs/478274
You rec
Reopening this issue. I am afraid there is a real problem here...
As I understand by looking at the code (mainly
ck-manager.c:load_seats_from_dir()), the fact that there is an invalid regular
file in /etc/ConsoleKit/seats.d/ has only the following impacts:
- the first correct seat created will
Chris: sorry, we changed the status in parellel with my former comment.
Restoring to "Confirmed" as you set it.
** Changed in: consolekit (Ubuntu)
Status: In Progress => Confirmed
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
https://bugs.launchpad.net/bugs/478274
Yes, Paul, you were right: my problem was different; it was a local
configuration issue. It only had similar symptoms.
For your startx problem, I don't see any way other than adding a new part
source script (eg. 99custom) in /etc/X11/Xsession.d, with some custom test to
overload the STARTUP vari
Bingo ! Thank you very much Chris ! You were right: it was a local
configuration issue. But I'd say consolekit seems overly sensitive and I'm not
sure its behavior is really legitimate.
Here is what /usr/sbin/console-kit-daemon --debug tells me (in
/var/log/daemon.log):
Nov 15 10:50:07 xyz conso
Thanks for the feedback. Here is the contents of
/etc/ConsoleKit/seats.d/00-primary.seat:
--
[Seat Entry]
Version=1.0
Name=Primary seat
Hidden=false
Devices=
--
Is there anything wrong with it ?
--
cannot mount usb v
Bug seems to lie somewhere between consolekit and policykit. It is
apparently not related to gdm (happens with console logins as well).
** Changed in: policykit-1 (Ubuntu)
Status: Incomplete => New
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
https://bugs.launchp
I can just confirm this, and add that it seems close to issue #478274.
In Karmic, apparently this active flag is not expected to be set by
pam_ck_connector. I just don't know what is supposed to set it to TRUE,
and I know that something does it (it's working on a fresh karmic
installation, and not
Some info relevant to my problem: see issue #363568
I looked at the consolekit sources and it appears that the only flags
that are set are:
res = ck_connector_open_session_with_parameters (ckc,
&error,
Digging somewhat more, it appears that none of the seats allow to
activate sessions (CanActivateSession) except one. The strange thing is
that that one seat doesn't contain any session. The other strange thing
is that none of the seats are associated with any device (GetDevices).
Anyway, here is w
Well, the "dbus" trick didn't make it either.
I tried with the following script:
---
import dbus, traceback
bus = dbus.SystemBus()
mgr = bus.get_object('org.freedesktop.ConsoleKit',
'/org/freedesktop/ConsoleKit/Manager')
for seat_name
Just FYI... I tried to force /usr/bin/ck-launch-session to run in
/etc/X11/Xsession.d/90consolekit because it was not enabled at STARTUP
as XDG_SESSION_COOKIE is defined. This doesn't make things better: it
just created another parallel inactive session. Both sessions were still
marked "active = FA
If it can help, here is what /var/log/ConsoleKit/history tells me since I last
rebooted:
1258028674.109 type=SEAT_ADDED : seat-id='Seat2' seat-kind=0
1258028721.681 type=SEAT_ADDED : seat-id='Seat3' seat-kind=1
1258028721.931 type=SEAT_SESSION_ADDED : seat-id='Seat3' session-id='Session1'
session
Well, I just chose my login name from the gdm login screen, typed my
password and that's it. I'm physically on the machine. How is that
'active' flag determined ?
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
https://bugs.launchpad.net/bugs/478274
You received this bug no
Some further information coming from the beginning of my ~/.xsession-errors:
(polkit-gnome-authentication-agent-1:2658): GLib-GObject-WARNING **: cannot
register existing type `_PolkitError'
(polkit-gnome-authentication-agent-1:2658): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization
Thank you for your support. The following is the output from ck-list-sessions:
Session2:
unix-user = '1000'
realname = 'david'
seat = 'Seat4'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device =
mark it related to policykit
** Package changed: yelp (Ubuntu) => policykit (Ubuntu)
** Summary changed:
- cannot mount usb volumes: "Not authorized"
+ cannot mount usb volumes: "Not authorized", after upgrade to Karmic
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
htt
Well, I used 'yelp' to file this bug report, so this bug report appears
related to yelp. Of course it doesn't have anything to do with yelp.
IMHO, it's probably more related to devkit pour policykit.
--
cannot mount usb volumes: "Not authorized", after upgrade to Karmic
https://bugs.launchpad.net
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35362079/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/35362080/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/35362081/ProcStatus.txt
--
cannot
Public bug reported:
Binary package hint: yelp
My machine (amd64) was running fine under jaunty (amd64) until
yesterday, when I upgraded to Karmic. Things seem to run well, except
for (at least) a devkit/policykit problem.
When I plug a USB memory stick, a window shows up telling me that the
vol
Same problem for me: intrepid x86_64 (up-to-date from today) after 2
days up. Never happened before, even with longer uptimes. I confirm the
problem seems to be related to this funky poll() on thousands of files.
And, err, well, I don't have thousands of windows showing up on my
desktop.
Looking a
Thank you !
You're perfectly right, any recent mainline > 2.6.28 already contains the fix.
I tried with http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.5/ and our
ftdi is fine again. How do you manage this kind of issue at Canonical ? You
patch the current 2.6.28 ? Or you jump directly to
Looking at the git, I noticed this changeset:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=commit;h=4a90f09b20f4622dcbff1f0e1e6bae1704f8ad8c
This adds a few reference counting tweaks. Most notably, in ftdi_process_read,
there reference acquires and release in the form of "goto out" (w
We are using ftdi_sio with a 232M chip.
On intrepid and with jaunty's 2.6.27 kernel, ftdi_sio works like a charm
on different setups (x86 IA32 and x86_64).
On 2.6.28-10 and -13, we have the following regression (x86 IA32): one
program opens the device, sends/receives data, then closes it. This
wo
31 matches
Mail list logo
