Hmm, your changelog has no reference to this bug-no.
And I would name the Ubuntu package libio-socket-ssl-perl instead of
IO::Socket::SSL.
[ Snip ]
* Revert commit v1.8.5.5~5^2 (send-email: /etc/ssl/certs/ directory may
not be usable as ca_path), which requires IO::Socket::SSL 1.951, and
Without the smtpsslcertpath-line in my local ~/.gitconfig and the new
git-core packages everything works like expected.
[ /etc/apt/sources.list.d/git-core-candidate-precise.list ]
deb http://ppa.launchpad.net/git-core/candidate/ubuntu precise main
deb-src http://ppa.launchpad.net/git-core/c
What is your suggestion?
Fix local/global gitconfig?
Or revert that change?
...
- $smtp_ssl_cert_path = "/etc/ssl/certs";
+ # use the OpenSSL defaults
+ return (SSL_verify_mode => SSL_VERIFY_PEER());
...
I can understand your concerns in case of a higher
Reading and verifying above bug-reports I have here in 'git-send-
email.perl':
[ /usr/lib/git-core/git-send-email ]
...
sub ssl_verify_params {
...
if (!defined $smtp_ssl_cert_path) {
# use the OpenSSL defaults
return (SSL_verify_mode => SSL_VERIFY_PEER());
I am using git (1:1.9.1-0ppa1~precise1) here on Ubuntu/precise AMD64 and
was not able to send a patch to linux-fsdevel via GoogleMail.
The above workaround helped me (for the sake of completeness the snippet
from my dot-gitconfig):
[ ~/.gitconfig]
...
[sendemail]
smtpserver = smtp.gmail.c
On Thu, Mar 28, 2013 at 10:03 AM, Stanislaw Gruszka wrote:
> On Thu, Mar 28, 2013 at 08:18:37AM +, Ali Ustek wrote:
>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>> >> supported by linux-kernel
>
> This device is supported since 3.7 . You most likely compile kernel
> wit
Public bug reported:
After a private conversation with Colin Watson I am doing this BR.
Here, I am on Ubuntu/precise an using a self-compiled v1.8.2.
Colin wanted to keep v1.8.1.x series sn not doing a major-bump.
So, this version-bump request is for latest Ubuntu/raring release.
Unfortunately,
Hi Steve,
Thanks for taking care!
First of all, this was never a "real" bug-report... more an
investigation and understanding how pam_umask is working and how someone
can influence the default UMASK settings.
Can you tell me to which of Ubuntu's MLs I should start such a
discussion next time (op
** Attachment added: "Refreshed /etc/pam.d/login (v4)"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505753/+files/login_pam_umask_so-umask-v4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "Original /etc/pam.d/common-session"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505729/+files/common-session.orig
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "Diff pam_umask man-page (rebuild latest pam (1.1.3-7ubuntu2))"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505731/+files/pam_umask-man8.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "Refreshed /etc/pam.d/login (v3)"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505735/+files/login_pam_umask_so-umask-v3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "Refreshed /etc/pam.d/common-session (v2)"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505730/+files/common-session_pam_umask_so-umask-v2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "Refreshed /etc/pam.d/login (v2)"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505728/+files/login_pam_umask_so-umask-v2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "Original /etc/pam.d/login"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505727/+files/login.orig
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10972
The profiles in LightDM are called "Ubuntu" and "Ubuntu-2d".
NOTE: Check ~/.dmrc file!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344053
Title:
I/O warning : failed to load external entity
To m
I hit the same problem after "ubuntu" (unity-3d) profile was BROKEN here.
To workaround this, I used "unity-2d".
compiz-session-ids are stored at different places.
unity-2d: ~/.compiz/session/
ubuntu (unity-3d): ~/.compiz-1/session/
When switching at the X-login-manager (LightDM) from "unity-2d"
Blueprints "Change the default umask to 0002"
https://blueprints.launchpad.net/ubuntu/+spec/umask-to-0002
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262
Title:
[pam][pam_umask]: Explicitly s
The pam_umask man-page is not up2date.
$ zgrep "influenced by USERGROUPS_ENAB" /usr/share/man/man8/pam_umask.8.gz
[ EMPTY ]
$ dpkg -S /usr/share/man/man8/pam_umask.8.gz
libpam-modules: /usr/share/man/man8/pam_umask.8.gz
$ dpkg -l | grep libpam-modules
ii libpam-modules
Worth reading why UMASK/USERGROUPS_ENAB changes were done.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583971
** Bug watch added: Debian Bug tracker #583971
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583971
--
You received this bug notification because you are a member of Ubuntu
So the root cause seems to be the USERGROUPS_ENAB setting:
--- /etc/login.defs.orig
+++ /etc/login.defs
-USERGROUPS_ENAB yes
+USERGROUPS_ENAB no
This gives a 0022 umask in xterm.
Not sure what side-effects this change will cause.
[ /etc/login.defs ]
...
#
# Login configuration initializations:
# egrep 'umask|libpam-umask' -nr /etc/skel/
/etc/skel/.profile:7:# the default umask is set in /etc/profile; for setting
the umask
/etc/skel/.profile:8:# for ssh logins, install and configure the libpam-umask
package.
/etc/skel/.profile:9:#umask 022
According to [1] /etc/profile should not be us
Another alternative which works here:
root# chfn -o umask=0022 myusername
[ /etc/shadow ]
-myusername:x:1000:1000:WeAreFam,,,:/home/myusername:/bin/bash
+myusername:x:1000:1000:WeAreFamumask=0022:/home/myusername:/bin/bash
root# grep pam_umask.so /etc/pam.d/common-session
session optional
** Attachment added: "Commented /etc/pam.d/login file"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477181/+files/login_pam_umask_so-fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "WorksForMe version of /etc/pam.d/common-session"
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477180/+files/common-session_pam_umask_so-fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
NEVER NEVER NEVER... NEVER EVER REMOVE /etc/pam.d/common-session file
!!!
http://grml.org [saves your admin-day!]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262
Title:
[pam][pam_umask]: Expl
WorksForMe take #2: Side-effects?
$ grep pam_umask.so /etc/pam.d/common-session
#session optional pam_umask.so <--- COMMENTED!
$ grep pam_umask.so /etc/pam.d/login
sessionoptional pam_umask.so umask=0022 <--- UNCOMMENTED - setting has
now an effect!
--
You received
NO changes to pam_umask.so generated by (un)selecting one of these items
(see attached diff):
# pam-auth-update --force
[*] Unix authentication
[*] Register user sessions in the systemd control group hierarchy
[*] GNOME Keyring Daemon - Login keyring management
[*] ConsoleKit Session Management
[
Investigating common-* and where these includes come from...
root# dpkg -S /etc/pam.d/other
libpam-runtime: /etc/pam.d/other
root# cat /etc/pam.d/other
#
# /etc/pam.d/other - specify the PAM fallback behaviour
#
# Note that this file is used for any unspecified service; for example
#if /etc/pam.
OK, 'dpkg-reconfigure libpam-runtime' (not libpam-modules) invokes 'pam-
auth-update' binary which is able to generate/update "...Local
modifications to /etc/pam.d/common-* ...":
# cd /etc/pam.d
# mkdir COMMON
# mv common-* COMMON/
# dpkg-reconfigure libpam-modules
# LC_ALL=C ls -alt /etc/pam.d/
Hmm, looks like these common-* files were generated today.
# LC_ALL=C ls -alt /etc/pam.d/common-*
-rw-r--r-- 1 root root 699 Jan 8 13:23 /etc/pam.d/common-session.diff
-rw-r--r-- 1 root root 1435 Jan 8 12:35
/etc/pam.d/common-session-noninteractive
-rw-r--r-- 1 root root 1515 Jan 8 12:35 /etc
Public bug reported:
[ Resending via 'ubuntu-bug libpam-modules' ]
Hi,
when I am working with the Freetz (a small Linux router project based
on buildroot mainly for MIPS arch) build-system I have this
umask/shell problem described in [1].
NOTE-1: I am using the xterm app from the Unitiy dock.
N
I have placed some informations on how to workaround some known issues
with this experimental systemd package.
Especially, see "Workaround #2: Failures on software-upgrades".
- Sedat -
[1] https://wiki.ubuntu.com/systemd#Workarounds
--
You received this bug notification because you are a membe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039413
Title:
package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
To ma
Public bug reported:
Problem occured when using systemd from Martin Pitt's PPA archive.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cups 1.5.3-0ubuntu4
Uname: Linux 3.6.0-rc2-next20120820-2-iniza-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CupsErrorLog:
Date:
Hi, I have rebuilt 0.9.4.0-0ubuntu5 for quantal on my precise/amd64
system and thus I do not see the errmsgs no more. As usually I tested in
an IPv6 WLAN only environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Thanks, kolya.
See also thread on linux-wireless ML [1] for more details.
[1] http://marc.info/?t=13370042821&r=1&w=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183
Title:
Logs full with
debdiff against network-manager (0.9.4.0-0ubuntu4) from precise-proposed
** Patch added: "network-manager-0.9.4.0-0ubuntu4.1~dileks1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+attachment/3141579/+files/network-manager-0.9.4.0-0ubuntu4.1%7Edileks1.debdiff
-
Hmm, network-manager (0.9.4.0-0ubuntu4) seems not to have the (upstream)
patch from here.
What's status? Especially wireless + wired (with 3.2.0 precise-kernel)?
( OK, Ubuntu developers are visiting UDS, so... :-) )
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have rebuilt a new NM package which includes the upstream fix.
It fixes here WLAN (IPv6) dis-/reconnects and log-files aren't spammed anymore.
Thanks RAOF for vital help in Ubuntu's way of packaging on IRC.
Also RAOF encouraged me to add my debdiff to this BR.
Have fun!
** Patch added: "debdif
I found the upstream commit which points to the RH-Bug:
commit 77de91e5a8b1c1993ae65c54b37e0411e78e6fe6
core: don't fight with the kernel over the default IPv6 route
[1]
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=77de91e5a8b1c1993ae65c54b37e0411e78e6fe6
--
You receive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183
Title:
Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
default route"
To manage notifications about this bug go to:
https://b
Public bug reported:
Hi,
I am observing a lot of "ICMPv6 RA: ndisc_router_discovery() failed to add
default route" in my logs.
After a fresh reboot:
$ dmesg | grep "ICMPv6 RA: ndisc_router_discovery() failed to add default
route." | wc -l
46
First, I thought this is a kernel issue, but than I
43 matches
Mail list logo
