[Bug 1032569] [NEW] keyboard switching applet does not update /desktop/gnome/peripherals/keyboard/kbd
Public bug reported: Dear all lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.4.2-0ubuntu0.2 Candidate: 3.4.2-0ubuntu0.2 Version table: *** 3.4.2-0ubuntu0.2 0 500 http://ubuntu.ph.tum.de/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.1-0ubuntu1 0 500 http://ubuntu.ph.tum.de/ubuntu/ precise/main amd64 Packages Switching the keyboard layout via system-settings-keyboard-layout updates the file /desktop/gnome/peripherals/keyboard/kbd accordingly: gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us,de] options = [terminate terminate:ctrl_alt_bksp,lv3 lv3:ralt_switch,grp grp:alts_toggle] model = pc105 # switching layouts gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [de,us] options = [terminate terminate:ctrl_alt_bksp,lv3 lv3:ralt_switch,grp grp:alts_toggle] model = pc105 (Note the different order in layouts = [])Switching the keyboard via the keyboard applet in the indicator panel does not update the kbd file gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us,de] options = [terminate terminate:ctrl_alt_bksp,lv3 lv3:ralt_switch,grp grp:alts_toggle] model = pc105 # switching layouts gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [us,de] options = [terminate terminate:ctrl_alt_bksp,lv3 lv3:ralt_switch,grp grp:alts_toggle] model = pc105 although the keyboard layout is changed. This breaks some scripts, which need to determine the current keyboard layout. ** Affects: gnome-settings-daemon (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/1032569 Title: keyboard switching applet does not update /desktop/gnome/peripherals/keyboard/kbd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1032569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 983152] Re: Cancel button not working + providing a wrong password loops
this is still not resolved, I can confirm this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983152 Title: Cancel button not working + providing a wrong password loops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/983152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908905] Re: upstart problems with S20squid script
I dist-upgraded from an ubuntu 10.04.2 LTS. But this problem also occurs with a normal upgrade. sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.2 LTS Release:10.04 Codename: lucid I have a VM-Snapshot of the system before the update and the failure is always reproducable. Since there is now private Data on that Machine (its a testing environment), I could upload the Snapshot, if you like. Thanks for your efforts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/908905 Title: upstart problems with S20squid script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+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 908905] Re: upstart problems with S20squid script
I dist-upgraded from an ubuntu 10.04.2 LTS. But this problem also occurs with a normal upgrade. sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.2 LTS Release:10.04 Codename: lucid I have a VM-Snapshot of the system before the update and the failure is always reproducable. Since there is now private Data on that Machine (its a testing environment), I could upload the Snapshot, if you like. Thanks for your efforts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908905 Title: upstart problems with S20squid script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908905] Re: upstart problems with S20squid script
Thanks for your answer. The output is sudo dpkg -L squid /. /usr /usr/share /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/squid /usr/share/doc /usr/share/doc/squid /usr/share/doc/squid/examples /usr/share/doc/squid/examples/default.squid /usr/share/doc/squid/examples/squid.conf /usr/share/doc/squid/README.Debian.gz /usr/share/doc/squid/copyright /usr/share/doc/squid/NEWS.Debian.gz /usr/share/doc/squid/changelog.Debian.gz /usr/share/doc/squid/changelog.gz /usr/share/man /usr/share/man/man8 /usr/share/man/man8/squid_ldap_group.8.gz /usr/share/man/man8/squid_unix_group.8.gz /usr/share/man/man8/squid_session.8.gz /usr/share/man/man8/squid.8.gz /usr/lib /usr/lib/squid /usr/lib/squid/yp_auth /usr/lib/squid/ldap_auth /usr/lib/squid/msnt_auth /usr/lib/squid/squid_ldap_group /usr/lib/squid/pam_auth /usr/lib/squid/diskd-daemon /usr/lib/squid/logfile-daemon /usr/lib/squid/unlinkd /usr/lib/squid/ntlm_auth /usr/lib/squid/smb_auth /usr/lib/squid/ip_user_check /usr/lib/squid/squid_kerb_auth /usr/lib/squid/wbinfo_group.pl /usr/lib/squid/digest_pw_auth /usr/lib/squid/ncsa_auth /usr/lib/squid/squid_unix_group /usr/lib/squid/getpwnam_auth /usr/lib/squid/smb_auth.sh /usr/lib/squid/squid_session /usr/sbin /usr/sbin/squid /var /var/log /var/log/squid /var/spool /var/spool/squid /etc /etc/resolvconf /etc/resolvconf/update-libc.d /etc/resolvconf/update-libc.d/squid /etc/squid /etc/init.d /etc/init /etc/init/squid.conf /etc/logrotate.d /etc/logrotate.d/squid /etc/init.d/squid As you already suspected the files are not present and I have therefore deleted them, as you suggested. Squid is booting up fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/908905 Title: upstart problems with S20squid script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+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 908905] Re: upstart problems with S20squid script
Thanks for your answer. The output is sudo dpkg -L squid /. /usr /usr/share /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/squid /usr/share/doc /usr/share/doc/squid /usr/share/doc/squid/examples /usr/share/doc/squid/examples/default.squid /usr/share/doc/squid/examples/squid.conf /usr/share/doc/squid/README.Debian.gz /usr/share/doc/squid/copyright /usr/share/doc/squid/NEWS.Debian.gz /usr/share/doc/squid/changelog.Debian.gz /usr/share/doc/squid/changelog.gz /usr/share/man /usr/share/man/man8 /usr/share/man/man8/squid_ldap_group.8.gz /usr/share/man/man8/squid_unix_group.8.gz /usr/share/man/man8/squid_session.8.gz /usr/share/man/man8/squid.8.gz /usr/lib /usr/lib/squid /usr/lib/squid/yp_auth /usr/lib/squid/ldap_auth /usr/lib/squid/msnt_auth /usr/lib/squid/squid_ldap_group /usr/lib/squid/pam_auth /usr/lib/squid/diskd-daemon /usr/lib/squid/logfile-daemon /usr/lib/squid/unlinkd /usr/lib/squid/ntlm_auth /usr/lib/squid/smb_auth /usr/lib/squid/ip_user_check /usr/lib/squid/squid_kerb_auth /usr/lib/squid/wbinfo_group.pl /usr/lib/squid/digest_pw_auth /usr/lib/squid/ncsa_auth /usr/lib/squid/squid_unix_group /usr/lib/squid/getpwnam_auth /usr/lib/squid/smb_auth.sh /usr/lib/squid/squid_session /usr/sbin /usr/sbin/squid /var /var/log /var/log/squid /var/spool /var/spool/squid /etc /etc/resolvconf /etc/resolvconf/update-libc.d /etc/resolvconf/update-libc.d/squid /etc/squid /etc/init.d /etc/init /etc/init/squid.conf /etc/logrotate.d /etc/logrotate.d/squid /etc/init.d/squid As you already suspected the files are not present and I have therefore deleted them, as you suggested. Squid is booting up fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908905 Title: upstart problems with S20squid script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909181] Re: wbinfo_group.pl does not recognize domain names containing spaces
I am sorry for the inconvenience but I just realized that squid replaces all whitespaces with %20 so there is no need to patch anything. Its even the contrary. The above patch does harm if wbinfo_group.pl gets a text- file containing multiple newline seperated groups. So please just close this bug. I am sorry for the inconvenience and I will make more intense testing the next time before I file a bug report. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+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 909181] Re: wbinfo_group.pl does not recognize domain names containing spaces
I am sorry for the inconvenience but I just realized that squid replaces all whitespaces with %20 so there is no need to patch anything. Its even the contrary. The above patch does harm if wbinfo_group.pl gets a text- file containing multiple newline seperated groups. So please just close this bug. I am sorry for the inconvenience and I will make more intense testing the next time before I file a bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909181] Re: wbinfo_group.pl does not recognize domain names containing spaces
** Patch added: wbinfo_group_new.pl.patch https://bugs.launchpad.net/bugs/909181/+attachment/2648641/+files/wbinfo_group_new.pl.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+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 909181] [NEW] wbinfo_group.pl does not recognize domain names containing spaces
Public bug reported: Today I ran into the problem that the wbinfo_group.pl script supplied by squid is incable of handling domain names containing spaces. For example the group name staff is ok, domain admins however is not. I found this great blog post: http://harlekwin.info/2008/12/10/how-to-squid-ad- authentication/ which proposes a fix. I tested the fix and it works. I have created a corresponding patch and have attached it to this bug-report. ATTENTION: The patch was created against a version of wbinfo_group.pl, which has the patch from BugReport: 908908 applied. If you need a patch against the original wbinfo_group.pl, just tell me and I will create one. Thanks for your efforts B. Brandt ** Affects: squid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+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 909016] Re: log file syntax broken due to interpretation of certain encoded chars in urls
** Patch added: HTParse.patch https://bugs.launchpad.net/bugs/909016/+attachment/2648082/+files/HTParse.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909016 Title: log file syntax broken due to interpretation of certain encoded chars in urls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squidguard/+bug/909016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909016] [NEW] log file syntax broken due to interpretation of certain encoded chars in urls
Public bug reported: Squidguard is interpreting encoded chars in urls. So if you have something like %2F in your url this becomes / in your log file. Consequently %0A becomes a new line. This is however not the only dangerous sequence. In example a %09 becomes a tab. This is problematic, since it causes consecuting tools like log-file analyzers to fail, due to incorrect syntax. For example the sarg package isn't producing any output, as long as there is even one malformed log line. As a workaround the issue can be resolved by removing most of the content of the HTUnEscape function in HTParse.c (see appended patch). This stops squidguard entirely from interpreting encoded chars. However a more desireable solution might be to make a list of threatening encoded chars and filter only those. Thanks for your efforts B. Brandt ** Affects: squidguard (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/909016 Title: log file syntax broken due to interpretation of certain encoded chars in urls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squidguard/+bug/909016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909181] [NEW] wbinfo_group.pl does not recognize domain names containing spaces
Public bug reported: Today I ran into the problem that the wbinfo_group.pl script supplied by squid is incable of handling domain names containing spaces. For example the group name staff is ok, domain admins however is not. I found this great blog post: http://harlekwin.info/2008/12/10/how-to-squid-ad- authentication/ which proposes a fix. I tested the fix and it works. I have created a corresponding patch and have attached it to this bug-report. ATTENTION: The patch was created against a version of wbinfo_group.pl, which has the patch from BugReport: 908908 applied. If you need a patch against the original wbinfo_group.pl, just tell me and I will create one. Thanks for your efforts B. Brandt ** Affects: squid (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/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909181] Re: wbinfo_group.pl does not recognize domain names containing spaces
** Patch added: wbinfo_group_new.pl.patch https://bugs.launchpad.net/bugs/909181/+attachment/2648641/+files/wbinfo_group_new.pl.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909181 Title: wbinfo_group.pl does not recognize domain names containing spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/909181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908905] [NEW] upstart problems with S20squid script
Public bug reported:
After performing a dist-upgrade of my lucid installation, I got the
following upstart error in my boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20squid start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20squid
start: Unknown job: S20squid
One can reproduce this bug, by simply issuing sudo
/etc/rc(2-5).d/S20squid start. Since S20squid is simply a symlink to
/etc/init.d/squid this affects all runlevels. However it seems to be non
critical since squid is started anyway (I have no idea why). The issue
can be fixed by modifying line 8 in /etc/init.d/squid from
JOB=${INITSCRIPT%.sh}
to
JOB=squid
So there are two issues here, if I am not mistaken. First the redundancy
since squid is started by two different scripts(?) and secondly the
wrong line in /etc/init.d/squid.
I am running Ubuntu 10.04.3 LTS
My squid version is 2.7.STABLE7
The system is up-to-date (aside from the grub package which is held back)
If you need any more information I am happy to provide it.
Thanks for your efforts
B. Brandt
** Affects: squid (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/908905
Title:
upstart problems with S20squid script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+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 908908] [NEW] uninitialized variable in wbinfo_group.pl causes false authentication results
Public bug reported: I am using squid version 2.7.STABLE7 with users authenticating via an ActiveDirectory (AD). I am using the wbinfo_group.pl helper script for checking group memberships. After a while internet access is denied at random for some users. In the squid log I see Use of uninitialized value in concatenation (.) or string at /usr/lib/squid/wbinfo_group.pl line 67, STDIN line 1. this message repeats from time to time, with line 1 increasing. As described in http://www.linuxquestions.org/questions/linux-server-73 /squid-ntlm-authentication-only-first-logon-is-authenticated-723587/ I explicitly set the variable $ans. After that I get some errors about Character in 'c' format wrapped in pack at /usr/lib/squid/wbinfo_group.pl line 92, STDIN line 1. So I changed the function call pack(c,hex($1)) to pack(C,hex($1)) everywhere in the script. Since then everything is running smoothly. No more random errors. I have attached a diff file with the changes. I am running Ubuntu 10.04.3 LTS squid version 2.7.STABLE7 If you need any more information I am happy to provide it. Thanks for your efforts B. Brandt ** Affects: squid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/908908 Title: uninitialized variable in wbinfo_group.pl causes false authentication results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908908/+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 908908] Re: uninitialized variable in wbinfo_group.pl causes false authentication results
** Patch added: patching unitialized variable and pack function call https://bugs.launchpad.net/bugs/908908/+attachment/2647870/+files/wbinfo_group_new.pl.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/908908 Title: uninitialized variable in wbinfo_group.pl causes false authentication results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908908/+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 908905] Re: upstart problems with S20squid script
** Description changed:
After performing a dist-upgrade of my lucid installation, I got the
following upstart error in my boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20squid start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20squid
start: Unknown job: S20squid
One can reproduce this bug, by simply issuing sudo
/etc/rc(2-5).d/S20squid start. Since S20squid is simply a symlink to
/etc/init.d/squid this affects all runlevels. However it seems to be non
critical since squid is started anyway (I have no idea why). The issue
- can be fixed by modifying line 8 in /etc/init.d/squid from
+ can be fixed by inserting
- JOB=${INITSCRIPT%.sh}
+ if [ $JOB = S20squid ]; then
+ JOB=squid
+ fi
- to
-
- JOB=squid
-
- So there are two issues here, if I am not mistaken. First the redundancy
- since squid is started by two different scripts(?) and secondly the
- wrong line in /etc/init.d/squid.
+ into /etc/init.d/squid, see attached patch. However there are two issues
+ here, if I am not mistaken. First the redundancy since squid is started
+ by two different scripts(?) and secondly the wrong line in
+ /etc/init.d/squid.
I am running Ubuntu 10.04.3 LTS
My squid version is 2.7.STABLE7
The system is up-to-date (aside from the grub package which is held back)
If you need any more information I am happy to provide it.
Thanks for your efforts
B. Brandt
** Patch added: inserting case discrimation in /etc/init.d/squid
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+attachment/2647875/+files/squid_new.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/908905
Title:
upstart problems with S20squid script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+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 908905] [NEW] upstart problems with S20squid script
Public bug reported:
After performing a dist-upgrade of my lucid installation, I got the
following upstart error in my boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20squid start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20squid
start: Unknown job: S20squid
One can reproduce this bug, by simply issuing sudo
/etc/rc(2-5).d/S20squid start. Since S20squid is simply a symlink to
/etc/init.d/squid this affects all runlevels. However it seems to be non
critical since squid is started anyway (I have no idea why). The issue
can be fixed by modifying line 8 in /etc/init.d/squid from
JOB=${INITSCRIPT%.sh}
to
JOB=squid
So there are two issues here, if I am not mistaken. First the redundancy
since squid is started by two different scripts(?) and secondly the
wrong line in /etc/init.d/squid.
I am running Ubuntu 10.04.3 LTS
My squid version is 2.7.STABLE7
The system is up-to-date (aside from the grub package which is held back)
If you need any more information I am happy to provide it.
Thanks for your efforts
B. Brandt
** Affects: squid (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/908905
Title:
upstart problems with S20squid script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908908] [NEW] uninitialized variable in wbinfo_group.pl causes false authentication results
Public bug reported: I am using squid version 2.7.STABLE7 with users authenticating via an ActiveDirectory (AD). I am using the wbinfo_group.pl helper script for checking group memberships. After a while internet access is denied at random for some users. In the squid log I see Use of uninitialized value in concatenation (.) or string at /usr/lib/squid/wbinfo_group.pl line 67, STDIN line 1. this message repeats from time to time, with line 1 increasing. As described in http://www.linuxquestions.org/questions/linux-server-73 /squid-ntlm-authentication-only-first-logon-is-authenticated-723587/ I explicitly set the variable $ans. After that I get some errors about Character in 'c' format wrapped in pack at /usr/lib/squid/wbinfo_group.pl line 92, STDIN line 1. So I changed the function call pack(c,hex($1)) to pack(C,hex($1)) everywhere in the script. Since then everything is running smoothly. No more random errors. I have attached a diff file with the changes. I am running Ubuntu 10.04.3 LTS squid version 2.7.STABLE7 If you need any more information I am happy to provide it. Thanks for your efforts B. Brandt ** Affects: squid (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/908908 Title: uninitialized variable in wbinfo_group.pl causes false authentication results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908908] Re: uninitialized variable in wbinfo_group.pl causes false authentication results
** Patch added: patching unitialized variable and pack function call https://bugs.launchpad.net/bugs/908908/+attachment/2647870/+files/wbinfo_group_new.pl.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908908 Title: uninitialized variable in wbinfo_group.pl causes false authentication results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908905] Re: upstart problems with S20squid script
** Description changed:
After performing a dist-upgrade of my lucid installation, I got the
following upstart error in my boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20squid start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20squid
start: Unknown job: S20squid
One can reproduce this bug, by simply issuing sudo
/etc/rc(2-5).d/S20squid start. Since S20squid is simply a symlink to
/etc/init.d/squid this affects all runlevels. However it seems to be non
critical since squid is started anyway (I have no idea why). The issue
- can be fixed by modifying line 8 in /etc/init.d/squid from
+ can be fixed by inserting
- JOB=${INITSCRIPT%.sh}
+ if [ $JOB = S20squid ]; then
+ JOB=squid
+ fi
- to
-
- JOB=squid
-
- So there are two issues here, if I am not mistaken. First the redundancy
- since squid is started by two different scripts(?) and secondly the
- wrong line in /etc/init.d/squid.
+ into /etc/init.d/squid, see attached patch. However there are two issues
+ here, if I am not mistaken. First the redundancy since squid is started
+ by two different scripts(?) and secondly the wrong line in
+ /etc/init.d/squid.
I am running Ubuntu 10.04.3 LTS
My squid version is 2.7.STABLE7
The system is up-to-date (aside from the grub package which is held back)
If you need any more information I am happy to provide it.
Thanks for your efforts
B. Brandt
** Patch added: inserting case discrimation in /etc/init.d/squid
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+attachment/2647875/+files/squid_new.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908905
Title:
upstart problems with S20squid script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629740] Re: BAM: inconsistant signing key with manual sync (only on 10.04 system, also with backported package)
Thanks so much, this did the trick. Boinc is runnig :-) I had to reattach the project manager, but now things are running smoothly. No problems so far. Good work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629740 Title: BAM: inconsistant signing key with manual sync (only on 10.04 system, also with backported package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/629740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629740] Re: BAM: inconsistant signing key with manual sync (only on 10.04 system, also with backported package)
I can confirm a more sever version of this bug with Oneiric, using 6.12.33 x64. After a fresh install of Oneiric I tried to use BAM as an account manager. However it keeps failing with the error message: 29-Nov-2011 20:56:24 [---] Bad signature for URL http://setiathome.berkeley.edu/ 29-Nov-2011 20:56:24 [---] Bad signature for URL http://lhcathomeclassic.cern.ch/sixtrack/ 29-Nov-2011 20:56:24 [---] Bad signature for URL http://boinc.bakerlab.org/rosetta/ 29-Nov-2011 20:56:24 [---] Bad signature for URL http://www.worldcommunitygrid.org/ I attached the log to this post. ** Attachment added: boinc_stdout https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/629740/+attachment/2612876/+files/boinc_stdout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629740 Title: BAM: inconsistant signing key with manual sync (only on 10.04 system, also with backported package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/629740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
