[Bug 1881180] Re: drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)

[Mike Gabriel]

Awesome! Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881180

Title:
  drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1881180/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix

[Mike Gabriel via ubuntu-bugs]

@ginggs: What else is needed to get this fix for X2Go Client into Ubuntu
updates?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856795

Title:
  [SRU] X2Go Client broken by libssh CVE-2019-14889 fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856795] Re: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

[Mike Gabriel via ubuntu-bugs]

See Debian bug 947129
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947129

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856795

Title:
  X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1856795] Re: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

[Mike Gabriel via ubuntu-bugs]

I think, this issue needs to be re-assigned and someone needs to provide
updates for x2goclient in all supported Ubuntu releases that have
received the fix for CVE-2019-14889.

This patch needs to be applied on top of X2Go Client:
https://code.x2go.org/gitweb?p=x2goclient.git;a=patch;h=ce559d163a943737fe4160f7233925df2eee1f9a

For Debian, I am currently on this...

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14889

** Bug watch added: Debian Bug tracker #947129
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947129

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856795

Title:
  X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801692] [NEW] dbus-test-runner FTBFS with GLib >= 2.58

[Mike Gabriel]

Public bug reported:

See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908275

Patch is available here:
https://salsa.debian.org/debian/dbus-test-runner/blob/b544b2966ce1819c64b7c7fc09f887b0090e0f11/debian/patches/1002_new-gobject-private-api.patch

Greets,
Mike

** Affects: dbus-test-runner (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch-accepted-debian

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801692

Title:
  dbus-test-runner FTBFS with GLib >= 2.58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/1801692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1791765] Re: Indicator applet just displays "No Indicators" message

[Mike Gabriel]

Hi,

in Debian, we are switching to Ayatana Indicators and m-i-a had already
been built against libayatana-indicator3. Afaik, Martin Wimpress plans
to ship a mate-indicator-applet in Ubuntu that still continues to use
Ubuntu Indicators ( at least in CC).

You could try installing the ayatana-indicator-* packages, that should
soothe some of your woes...

Mike

On Wednesday, September 12, 2018, luca.mg wrote:
> Same here, upgraded from BB as soon as CC became available on a test
> system, never had the pleasure to see the indicators, which were working
> fine on the previous version. Cheers, Luca
> 
> -- 
> You received this bug notification because you are subscribed to Ubuntu.
> https://bugs.launchpad.net/bugs/1791765
> 
> Title:
>   Indicator applet just displays "No Indicators" message
> 
> Status in mate-indicator-applet package in Ubuntu:
>   New
> 
> Bug description:
>   After upgrading to 18.10 the indicator applet no longer shows any
>   icons, just the message "No Indicators".
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: mate-indicator-applet 1.20.1-1
>   ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
>   Uname: Linux 4.18.0-7-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu9
>   Architecture: amd64
>   CurrentDesktop: MATE
>   Date: Mon Sep 10 18:03:06 2018
>   InstallationDate: Installed on 2018-07-04 (68 days ago)
>   InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
> (20180426)
>   SourcePackage: mate-indicator-applet
>   UpgradeStatus: Upgraded to cosmic on 2018-09-10 (0 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mate-indicator-applet/+bug/1791765/+subscriptions
> 
>

-- 
Sent from my Fairphone (powered by SailfishOS)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791765

Title:
  Indicator applet just displays "No Indicators" message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-indicator-applet/+bug/1791765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 150461] Re: smarty-gettext installs plugins to the wrong location

[Mike Gabriel]

This issue has been resolved years back.

Thus, closing.

** Changed in: smarty-gettext (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/150461

Title:
  smarty-gettext installs plugins to the wrong location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smarty-gettext/+bug/150461/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770146] Re: [MIR] libayatana-appindicator

[Mike Gabriel]

A ping from one of the upstream maintainers of Ayatana Indicators.

For Debian I maintain this wiki page that documents the transition
status. There is still a lot of work ahead in Debian:

https://wiki.debian.org/Ayatana/IndicatorsTransition

Anyone chiming in (ideally on the Debian side) is highly welcome. Let's
reduce the Debian/Ubuntu delta...

light+love,
Mike (aka sunweaver)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770146

Title:
  [MIR] libayatana-appindicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1770146/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1760691] Re: Please switch to Ayatana AppIndicator

[Mike Gabriel]

Hi,

did you probably close the wrong bug here?

Mike

On Tuesday, May 29, 2018, Launchpad Bug Tracker wrote:
> This bug was fixed in the package update-notifier - 3.192.5
> 
> ---
> update-notifier (3.192.5) cosmic; urgency=medium
> 
>   * Fix PEP8 errors
> 
> update-notifier (3.192.4) cosmic; urgency=medium
> 
>   * package-data-downloader: Only print processing messages if we
> should download stuff, or if an expected exception occured
> (LP: #1641671)
> 
>  -- Julian Andres Klode   Tue, 29 May 2018 09:38:23
> +0200
> 
> ** Changed in: update-notifier (Ubuntu)
>Status: New => Fix Released
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1760691
> 
> Title:
>   Please switch to Ayatana AppIndicator
> 
> Status in update-notifier package in Ubuntu:
>   Fix Released
> 
> Bug description:
>   There currently is an initiative going on in Debian and Ubuntu to make
>   Indicators globally available, esp. available to non-Ubuntu systemes.
> 
>   For this, we are sending out patches to various applications that
>   build-depend on libappindicator*-dev.
> 
>   Here is a patch against update-notifier 3.189 that brings this change.
> 
>   Thanks,
>   Mike
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1760691/+subscriptions
>

-- 
Sent from my Fairphone (powered by SailfishOS)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760691

Title:
  Please switch to Ayatana AppIndicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1760691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765664] [NEW] Make cmdline option --indicator available again (as no-op)

[Mike Gabriel]

Public bug reported:

This is about this nm-applet patch:
https://bazaar.launchpad.net/~ubuntu-desktop/network-manager-applet/ubuntu/view/head:/debian/patches/Have-the-appindicator-enabled-by-default.patch

In the referenced patch you remove the --indicator option and add --no-
indicator.

This breaks applications launching nm-applet with --indicator option
set. I am esp. interested in arctica-greeter, that needs to launch nm-
applet with --indicator option on all non-Ubuntu platforms (all that
don' have your patch).

Thus, my request is: please keep --indicator and make it a no-op option
in Ubuntu.

Thanks!
Mike

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765664

Title:
  Make cmdline option --indicator available again (as no-op)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1765664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765664] Re: Make cmdline option --indicator available again (as no-op)

[Mike Gabriel]

As I side note... I will submit various Ubuntu patches for nm-applet
upstream in the next couple of days. Also, I submitted an upstream
patch, that enables building nm-applet against Ayatana AppIndicator.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765664

Title:
  Make cmdline option --indicator available again (as no-op)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1765664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1756431] Re: [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

[Mike Gabriel]

Hi,

On  Mi 04 Apr 2018 18:08:15 CEST, Łukasz Zemczak wrote:

> @sunweaver Could you perform a test build in an Ubuntu PPA with armhf
> and arm64 enabled and report back if the package builds correctly in
> Ubuntu on all arches (with logs)? I think once we have certainty that
> the new version does no longer FTBFS, I'd be glad to approve the FFe.

I have now uploaded the source package to:

https://launchpad.net/~sunweaver/+archive/ubuntu/ppa

Builds against all Ubuntu architectures are currently running.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756431

Title:
  [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1756431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1761173] brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.

[Mike Gabriel]

Hi,

On  Mi 04 Apr 2018 15:26:10 CEST, Apport retracing service wrote:

> StacktraceTop:
>  __assert_fail_base (fmt=0x7f9ee9f04b03  at address 0x7f9ee9f04b03>, assertion=assertion@entry=0x7f9ee8f93660  
> "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f9ee8f934cb  
> "../../src/xcb_io.c", line=line@entry=259,  
> function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350>  
> "poll_for_event") at assert.c:92
>  __GI___assert_fail (assertion=assertion@entry=0x7f9ee8f93660  
> "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f9ee8f934cb  
> "../../src/xcb_io.c", line=line@entry=259,  
> function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350>  
> "poll_for_event") at assert.c:101
>  poll_for_event (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:256
>  poll_for_response (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:274
>  _XEventsQueued (dpy=dpy@entry=0x561bc9a54580, mode=mode@entry=2) at  
> ../../src/xcb_io.c:349

I am half sure that I have seen this (or a similar crash) on Debian,  
too, yesterday...

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761173

Title:
  brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259:
  poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non
  riuscita.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1761173/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1760691] Re: Please switch to Ayatana AppIndicator

[Mike Gabriel]

Hi Sebastien,

On  Mi 04 Apr 2018 09:18:22 CEST, Sebastien Bacher wrote:

> Thank you for your bug report, that's late for a such change this cycle.
> Also libayatana-appindicator  is in universe and would need to be
> promoted to main first (https://wiki.ubuntu.com/MainInclusionProcess)
>
> ** Changed in: update-notifier (Ubuntu)
>Importance: Undecided => Wishlist

this is for 18.10 anyway... Long term thing this is...

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760691

Title:
  Please switch to Ayatana AppIndicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1760691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760701] [NEW] Drop gir1.2-appindicator3-0.1 from Depends: field

[Mike Gabriel]

Public bug reported:

The ubiquity package has gir1.2-appindicator3-0.1 int its Depends:
field.

In Ubiquity, the need for gir1.2-appindicator3-0.1 has been removed by
this commit:

```
commit f45b868cfcede304e69720cbbe0f0546292f88d9
Author: Luke Yelavich 
Date:   Wed Feb 17 18:00:56 2016 +1100

Rework the accessibility profile code to use the accessibility profile
manager if available

```

(I checkout the upstream bzr with Git, apologies...).

Please remove gir1.2-appindicator3-0.1 from the Depends: field. Thanks!

Mike

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "No AppIndicator support needed anymore"
   
https://bugs.launchpad.net/bugs/1760701/+attachment/5099193/+files/ubiquity-18.04.4_18.04.4+ayatana.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760701

Title:
  Drop gir1.2-appindicator3-0.1 from Depends: field

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1760701/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760691] [NEW] Please switch to Ayatana AppIndicator

[Mike Gabriel]

Public bug reported:

There currently is an initiative going on in Debian and Ubuntu to make
Indicators globally available, esp. available to non-Ubuntu systemes.

For this, we are sending out patches to various applications that build-
depend on libappindicator*-dev.

Here is a patch against update-notifier 3.189 that brings this change.

Thanks,
Mike

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Switch to Ayatana AppIndicator"
   
https://bugs.launchpad.net/bugs/1760691/+attachment/5099150/+files/update-notifier_3.189_3.189.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760691

Title:
  Please switch to Ayatana AppIndicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1760691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756431] Re: [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

[Mike Gabriel]

1) yes, functionality-wise by Martin Wimpress (local build, I presume),
I myself test-built in a bionic sbuild chroot

2) unfortunately, I see build failures on Debian for 2.0.93-2, as well, but for 
a different reason (something severly broken in /usr/bin/gdbus-codegen, totally 
unrelated to the package it seems):
https://buildd.debian.org/status/package.php?p=ayatana-indicator-power

I have a request pending on #debian-buildds to investigate the cause of
the new FTBFS symptoms.

The previous version in unstable 2.0.93-1 built successfully on all
archs supported by Debian.

3) Esp. the change in 2.0.93-2 (enum id name changes in the gschema file
to allow co-installability with indicator-power) should give good reason
(so that people can start playing with Arctica Greeter that
uses/recommends ayatana-indicator-power.

The FTBFS fixes (due to parallelism problems in the test suite) have
been RC in Debian, so probably that applies to Ubuntu, too.

The rest of the changes (desktop env gnostics) are more for the future
than relevant for the 18.04 release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756431

Title:
  [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1756431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756431] Re: [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

[Mike Gabriel]

Sorry, the correct / new version is 2.0.93-2.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756431

Title:
  [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1756431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756431] Re: [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

[Mike Gabriel]

I (Debian maintainer) just uploaded 2.0.93-1 fixing co-installability of
ayatana-indicator-power and indicator-power.

See https://github.com/AyatanaIndicators/ayatana-indicator-
power/issues/1

** Bug watch added: github.com/AyatanaIndicators/ayatana-indicator-power/issues 
#1
   https://github.com/AyatanaIndicators/ayatana-indicator-power/issues/1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756431

Title:
  [FFe] Please sync ayatana-indicator-power 2.0.93-1 from Debian Sid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-power/+bug/1756431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

On  Mo 04 Jan 2016 21:26:05 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>> Hi Serge,
>>
>> sorry for getting back to this so late.
>>
>> On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:
>>
>> > Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>>
>> >> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> >> 0.7.x (as found in Debian squeeze-lts).
>> >>
>> >> The patch is attached, I am still in the testing-for-regressions phase.
>> >> Can any of the LXC devs take a look at the patch and maybe see if it is
>> >> suitable for Ubuntu 12.04, as well?
>> >
>> > Hi,
>> >
>> > So the thing to look for is any unconverted "mount" calls.  It
>> > looks like the lxc_setup_fs() calls to mount_fs() are not being
>> > protected.  So the contianer admin could attack through a /proc
>> > symlink.
>>
>> Hmmm... ok...
>>
>> I just checked upstream Git and the location you refer to is not using
>> safe_mount either there [1]
>
> Huh, that's odd.  Yes those should be protected, since /proc etc in
> the container could be symlinks.  Do you mind sending a patch?

I will work on the squeeze-lts / precise patch first and test that. If  
that works well, I will forward-port the change to current HEAD.

>> Furthermore, it seems non-trivial to inform safe_mount about the root
>> path from within lxc_init.c.
>>
>> Do you have any input on the following questions?:
>>
>>o Why mount_fs() in latest HEAD still using the mount() call
>> instead of safe_mount()?
>>o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?
>
> You shouldn't need to - it's just '/' because you're already chrooted
> there.
>

Ok. That will make it very easy.

I get back to you with results within the month.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

On  Mo 04 Jan 2016 21:26:05 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>> Hi Serge,
>>
>> sorry for getting back to this so late.
>>
>> On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:
>>
>> > Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>>
>> >> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> >> 0.7.x (as found in Debian squeeze-lts).
>> >>
>> >> The patch is attached, I am still in the testing-for-regressions phase.
>> >> Can any of the LXC devs take a look at the patch and maybe see if it is
>> >> suitable for Ubuntu 12.04, as well?
>> >
>> > Hi,
>> >
>> > So the thing to look for is any unconverted "mount" calls.  It
>> > looks like the lxc_setup_fs() calls to mount_fs() are not being
>> > protected.  So the contianer admin could attack through a /proc
>> > symlink.
>>
>> Hmmm... ok...
>>
>> I just checked upstream Git and the location you refer to is not using
>> safe_mount either there [1]
>
> Huh, that's odd.  Yes those should be protected, since /proc etc in
> the container could be symlinks.  Do you mind sending a patch?

I will work on the squeeze-lts / precise patch first and test that. If  
that works well, I will forward-port the change to current HEAD.

>> Furthermore, it seems non-trivial to inform safe_mount about the root
>> path from within lxc_init.c.
>>
>> Do you have any input on the following questions?:
>>
>>o Why mount_fs() in latest HEAD still using the mount() call
>> instead of safe_mount()?
>>o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?
>
> You shouldn't need to - it's just '/' because you're already chrooted
> there.
>

Ok. That will make it very easy.

I get back to you with results within the month.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

sorry for getting back to this so late.

On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):

>> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> 0.7.x (as found in Debian squeeze-lts).
>>
>> The patch is attached, I am still in the testing-for-regressions phase.
>> Can any of the LXC devs take a look at the patch and maybe see if it is
>> suitable for Ubuntu 12.04, as well?
>
> Hi,
>
> So the thing to look for is any unconverted "mount" calls.  It
> looks like the lxc_setup_fs() calls to mount_fs() are not being
> protected.  So the contianer admin could attack through a /proc
> symlink.

Hmmm... ok...

I just checked upstream Git and the location you refer to is not using  
safe_mount either there [1]

Furthermore, it seems non-trivial to inform safe_mount about the root  
path from within lxc_init.c.

Do you have any input on the following questions?:

   o Why mount_fs() in latest HEAD still using the mount() call  
instead of safe_mount()?
   o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?

Thanks for any input.

Mike

[1] https://github.com/lxc/lxc/blob/master/src/lxc/initutils.c#L35
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi Serge,

sorry for getting back to this so late.

On  Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:

> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):

>> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> 0.7.x (as found in Debian squeeze-lts).
>>
>> The patch is attached, I am still in the testing-for-regressions phase.
>> Can any of the LXC devs take a look at the patch and maybe see if it is
>> suitable for Ubuntu 12.04, as well?
>
> Hi,
>
> So the thing to look for is any unconverted "mount" calls.  It
> looks like the lxc_setup_fs() calls to mount_fs() are not being
> protected.  So the contianer admin could attack through a /proc
> symlink.

Hmmm... ok...

I just checked upstream Git and the location you refer to is not using  
safe_mount either there [1]

Furthermore, it seems non-trivial to inform safe_mount about the root  
path from within lxc_init.c.

Do you have any input on the following questions?:

   o Why mount_fs() in latest HEAD still using the mount() call  
instead of safe_mount()?
   o How could one pipe the rootfs path into lxc_setup_fs() -> mount_fs()?

Thanks for any input.

Mike

[1] https://github.com/lxc/lxc/blob/master/src/lxc/initutils.c#L35
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi all,

today I worked on backporting available fixes for CVE-2015-1335 to LXC
0.7.x (as found in Debian squeeze-lts).

The patch is attached, I am still in the testing-for-regressions phase.
Can any of the LXC devs take a look at the patch and maybe see if it is
suitable for Ubuntu 12.04, as well?

Greets,
Mike (aka sunweaver at debian.org)

** Patch added: "Backport fix for CVE-2015-1335 to LXC 0.7.x (Ubuntu 12.04 / 
Debian squeeze-lts)"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+attachment/4529631/+files/CVE-2015-1335.patch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1476662] Re: lxc-start symlink vulnerabilities may allow guest to read host filesystem, interfere with apparmor

[Mike Gabriel]

Hi all,

today I worked on backporting available fixes for CVE-2015-1335 to LXC
0.7.x (as found in Debian squeeze-lts).

The patch is attached, I am still in the testing-for-regressions phase.
Can any of the LXC devs take a look at the patch and maybe see if it is
suitable for Ubuntu 12.04, as well?

Greets,
Mike (aka sunweaver at debian.org)

** Patch added: "Backport fix for CVE-2015-1335 to LXC 0.7.x (Ubuntu 12.04 / 
Debian squeeze-lts)"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+attachment/4529631/+files/CVE-2015-1335.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476662

Title:
  lxc-start symlink vulnerabilities may allow guest to read host
  filesystem, interfere with apparmor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1170017] Re: nautilus-python fails to load on 64-bit systems: g_module_open libpython failed: No such file or directory

[Mike Gabriel]

I just tested this issue in Debian. The problem does not exist with
python-caja 1.8.0-1 in Debian unstable (and neither with the follow-up
version 1.8.1-1, about to upload).

Mike (aka sunweaver)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170017

Title:
  nautilus-python fails to load on 64-bit systems: g_module_open
  libpython failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus-compare/+bug/1170017/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1270567] Re: package mate-polkit-common not installed failed to install/upgrade: trying to overwrite /usr/share/locale/uk/LC_MESSAGES/mate-polkit.mo , which is also in package mate-polkit 1.6.0-1

[Mike Gabriel]

A fix for this is pending for the Debian mate-polkit package...

http://anonscm.debian.org/gitweb/?p=pkg-mate/mate-
polkit.git;a=commitdiff;h=e00e99d3a11c2e3071ab1f3d77a957dafd4093c5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270567

Title:
  package mate-polkit-common  not installed  failed to install/upgrade:
  trying to overwrite  /usr/share/locale/uk/LC_MESSAGES/mate-polkit.mo ,
  which is also in package mate-polkit 1.6.0-1 raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-polkit/+bug/1270567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1037296] Re: [MIR] remote-login-service

[Mike Gabriel]

Hi,

please note bug #1172318  [1] when looking at remote-login-service.
Currently, only uccs.landscape.canonical.com can be used as UCCS server.
Other UCCS implementations (like [2]) will not be configurable through
/etc/remote-login-service.conf atm.

Thanks for looking at this,
Mike

[1] https://bugs.launchpad.net/remote-login-service/+bug/1172318
[2] http://code.x2go.org/gitweb?p=x2gobroker.git;a=blob;f=x2gobroker/web/uccs.py

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037296

Title:
  [MIR] remote-login-service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remote-login-service/+bug/1037296/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1187450] [NEW] Depends on python3-pycurl

[Mike Gabriel]

Public bug reported:

Please add python3-curl to the package's Depends: field.

Thanks,
Mike

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: thin-client-config-agent 0.7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue Jun  4 17:05:31 2013
InstallationDate: Installed on 2013-06-04 (0 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: thin-client-config-agent
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: thin-client-config-agent (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187450

Title:
  Depends on python3-pycurl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thin-client-config-agent/+bug/1187450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985202] Re: libx11 causes kwin to crash on login (over NX protocol)

[Mike Gabriel]

Hi all,

I just tested the new libxrandr2 package on precise with X2Go and nx-
libs 2:3.5.0.20.

The kwin crashes are gone, indeed. So far so good. However, the NX
capability of resizing a non-fullscreen desktop session window is
completely gone now.

Expected behaviour:

  o Start a (KDE) session with a geometry of 1024x768 in non-full screen mode
  o Resize the NX agent window (i.e. maximize it or drag with the mouse pointer 
on one of the window corners
  o Expectation: the desktop shell inside resizes all its elements and adapts 
to the new desktop size

What happens:

  o the desktop shell stubbornly remains at its initial geometry (1024x768 in 
this example) and refuses to adapt its
 elements to the new desktop session window size

Greets,
Mike (from X2Go upstream)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985202

Title:
  libx11 causes kwin to crash on login (over NX protocol)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/985202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 260136] Re: do not go when click on rigth menu: config, status, etc

[Mike Gabriel]

Issue has been fixed in Debian with version 0.3-3.

** Bug watch added: Debian Bug tracker #655832
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655832

** Also affects: slbackup-php (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655832
   Importance: Unknown
   Status: Unknown

** Changed in: slbackup-php (Ubuntu)
   Status: New = Fix Released

** Changed in: slbackup-php (Ubuntu)
 Assignee: (unassigned) = Mike Gabriel (m-gabriel)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/260136

Title:
  do not go when click on rigth menu: config, status, etc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/slbackup-php/+bug/260136/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 663726] Re: pynotify.set_timeout() ignores timeout

[Mike Gabriel]

Same here: set_timeout is ignored by pynotify...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663726

Title:
  pynotify.set_timeout() ignores timeout

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 663726] Re: pynotify.set_timeout() ignores timeout

[Mike Gabriel]

... that is in Ubuntu lucid, 32bit...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663726

Title:
  pynotify.set_timeout() ignores timeout

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 613568] [NEW] hgimportsvn fails when import svn repos that needs authentication data for reading (checkout)

[Mike Gabriel]

Public bug reported:

Binary package hint: hgsvn

This might well indeed be a subversion bug, but it heavily affects hgsvn
(makes the hgsvn scripts unusable)...

I use an internal subversion repository that needs authentication data
for svn checkout. When importing such a subversion repos to mercurial
with hgimportsvn it allows me to enter my password, but then results in:

-- 8 
m...@host:~$ hgimportsvn http://mysvnsite.local/development/subfolder  .
Password for 'mike': 
Traceback (most recent call last):
  File /usr/bin/hgimportsvn, line 8, in module
load_entry_point('hgsvn==0.1.7', 'console_scripts', 'hgimportsvn')()
  File /usr/lib/pymodules/python2.6/hgsvn/run/hgimportsvn.py, line 51, in main
svn_info = get_svn_info(svn_url, options.svn_rev)
  File /usr/lib/pymodules/python2.6/hgsvn/svnclient.py, line 148, in 
get_svn_info
fail_if_stderr=True)
  File /usr/lib/pymodules/python2.6/hgsvn/common.py, line 231, in run_svn
args=args, bulk_args=bulk_args, fail_if_stderr=fail_if_stderr)
  File /usr/lib/pymodules/python2.6/hgsvn/common.py, line 168, in run_command
return _run_raw_command(cmd, map(_transform_arg, args), fail_if_stderr)
  File /usr/lib/pymodules/python2.6/hgsvn/common.py, line 142, in 
_run_raw_command
% (pipe.returncode, cmd_string, err))
hgsvn.errors.ExternalCommandFailed: External program failed (return code 0): 
svn 'info' '--xml' 'http://mysvnsite.local/development/subfolder'
Authentication realm: http://mysvnsite.local:80 You need a password to access 
this repository:
-8 

When manually calling ,,svn info --xml
http://mysvnsite.local/development/subfolder'' it results in:

-- 8 
m...@host:~$ svn info --xml http://mysvnsite.local/development/subfolder
?xml version=1.0?
info
Authentication realm: http://mysvnsite.local:80 You need a password to access 
this repository:
Password for 'mike': 
entry
   kind=dir
   path=subfolder
   revision=1
urlhttp://mysvnsite.local/development/subfolder/url
repository
roothttp://mysvnsite.local/development/root
uuid5a877c20-035e-4510-8fee-e4c3d4fa362b/uuid
/repository
commit
   revision=1
authormike/author
date2010-08-04T17:47:13.441657Z/date
/commit
/entry
/info
-8 

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: hgsvn (not installed)
ProcVersionSignature: Ubuntu 2.6.32-24.38-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-server x86_64
Architecture: amd64
Date: Wed Aug  4 19:58:26 2010
InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 
(20100427)
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: hgsvn

** Affects: hgsvn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lucid

-- 
hgimportsvn fails when import svn repos that needs authentication data for 
reading (checkout)
https://bugs.launchpad.net/bugs/613568
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608607] [NEW] ng-utils missing as dependency

[Mike Gabriel]

Public bug reported:

Binary package hint: shutdown-at-night

The package ng-utils is missing as a dependency in the package shutdown-
at-night. ng-utils is essential if you want to shutdown the system based
on netgroup information.

** Affects: shutdown-at-night (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ng-utils missing as dependency
https://bugs.launchpad.net/bugs/608607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608616] Re: log output for not-shutting-down reasons

[Mike Gabriel]

** Patch added: shutdown-at-night_logging.patch
   http://launchpadlibrarian.net/52307295/shutdown-at-night_logging.patch

-- 
log output for not-shutting-down reasons 
https://bugs.launchpad.net/bugs/608616
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608616] [NEW] log output for not-shutting-down reasons

[Mike Gabriel]

Public bug reported:

Binary package hint: shutdown-at-night

shutdown-at-night script could be a bit more verbose for not shutting
down a system

reasons for not shutting down, that occurred to me:

  o ethtool not installed
  o ng-utils not installed
  o host in use (see patch)
  o host not in shutdown-at-night-hosts netgroup (see patch)

** Affects: shutdown-at-night (Ubuntu)
 Importance: Undecided
 Status: New

-- 
log output for not-shutting-down reasons 
https://bugs.launchpad.net/bugs/608616
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 607021] [NEW] ethtool missing as dependency

[Mike Gabriel]

Public bug reported:

Binary package hint: shutdown-at-night

For older mainboards (without nvram support) the shutdown-at-night script will 
want to enable the WOL 
feature of the network card. For this the package ethtool is required as a 
dependency.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: shutdown-at-night 0.7
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Jul 19 01:21:50 2010
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: shutdown-at-night

** Affects: shutdown-at-night (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 lucid

-- 
ethtool missing as dependency
https://bugs.launchpad.net/bugs/607021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 607021] Re: ethtool missing as dependency

[Mike Gabriel]

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/52137461/Dependencies.txt

-- 
ethtool missing as dependency
https://bugs.launchpad.net/bugs/607021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 378874] Re: getpwent cannot enumerate users from netgroups with libnss_compat

[Mike Gabriel]

This problem co-exists when using netgroups and pam_access.so...

I have two netgroups (netgroup-staff, netgroup-students), only
,,netgroup-staff'' shall get access to my system...

When tweaking /etc/security/access.conf this _does not_ work, but it
should:

  snippet
  + : root locadm : ALL
  + : @netgroup-staff : ALL

  # All other users should be denied to get access from all sources.
  - : ALL : ALL
  /snippet

However, similar to the issues above, putting the following lines into
/etc/security/access.conf _does_ work:

  snippet
  + : root locadm : ALL
  - : @netgroup-students : ALL

  # All other users can access the system from any source
  + : ALL : ALL
  /snippet

-- 
getpwent cannot enumerate users from netgroups with libnss_compat
https://bugs.launchpad.net/bugs/378874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 378874] Re: getpwent cannot enumerate users from netgroups with libnss_compat

[Mike Gabriel]

Also a bug is the following behaviour:

I have userA, userB and userC, userA+B are in netgroup ,,netgroup-
staff''

My /etc/passwd looks like this:
  snippet
  [...local accounts]
  -...@netgroup-staff:x:
  +:x:
  /snippet

When using the command ,,getent passwd'', the list looks like this
(userA+B are excluded from the passwd list, because their netgroup is
denied access to the system):

  snippet
  [...local accounts]
  userC:x:uidN:gidN:GECOS:/home/userC:/bin/bash
  /snippet

Till here everything looks fine...

However, when I use ,,getent passwd userA'' I expect that nothing will
be returned. But opposed to my expectation the following line is
returned:

  snippet
  userA:x:uidN:gidN:GECOS:/home/userA:/bin/bash
  /snippet

To my understanding using nss_compat and a passwd config as shown above
should hide users that are not members in ,,netgroup-staff'' completely
from the system. Unfortunately, this is not the case...

-- 
getpwent cannot enumerate users from netgroups with libnss_compat
https://bugs.launchpad.net/bugs/378874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 378874] Re: getpwent cannot enumerate users from netgroups with libnss_compat

[Mike Gabriel]

TYPO in the last paragraph, here the correct phrase: To my understanding
using nss_compat and a passwd config as shown above should hide users
that _are_ (here was the typo) members in ,,netgroup-staff'' completely
from the system. Unfortunately, this is not the case...

-- 
getpwent cannot enumerate users from netgroups with libnss_compat
https://bugs.launchpad.net/bugs/378874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 378874] Re: getpwent cannot enumerate users from netgroups with libnss_compat

[Mike Gabriel]

I can confirm the issue for UBUNTU Karmic 9.10 and for Debian Lenny.

But the following works for me (which can be used as a workaround for
some, maybe):

-...@netgroup:x:
+:x::

Means in this context: getpwent will list all LDAP users except those in
@netgroup.

-- 
getpwent cannot enumerate users from netgroups with libnss_compat
https://bugs.launchpad.net/bugs/378874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 378874] Re: getpwent cannot enumerate users from netgroups with libnss_compat

[Mike Gabriel]

The bug also persist if you use

  netgroup: files

in conjunction with a /etc/netgroup file instead of

  netgroup: ldap

in /etc/nsswitch.conf.

-- 
getpwent cannot enumerate users from netgroups with libnss_compat
https://bugs.launchpad.net/bugs/378874
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs