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:
@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
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
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:
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
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
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:
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
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
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
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
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
mobil
.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
--
onProcess)
>
> ** 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: 9BF
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
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
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
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
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
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:
>>
>
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:
>>
>
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).
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).
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
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
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
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.
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]
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
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
: 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
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
... 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
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
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:
** 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
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
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
** 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
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
+
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
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
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
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
44 matches
Mail list logo