Public bug reported:
Binary package hint: molly-guard
molly-guard 0.3-2
molly-guard's SSH detection fails when it is called inside a screen
session.
Example, called over a normal SSH session:
[EMAIL PROTECTED]:~% reboot
W: molly-guard: SSH session detected!
Please type in hostname of the machin
Is this a VMware guest?
--
mlocate package doesn't install /etc/updatedb.conf
https://bugs.launchpad.net/bugs/238062
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.
...and brute forcing has become a more acute problem in light of the
recent OpenSSL vulnerability. Exploitation of weak SSH keys is made much
easier if the attacker knows a valid username on the target system; by
permitting root login, you are making an attacker's job much easier.
(Though [EMAIL P
On reflection, I think it's worth noting...
Although by default the root account on Ubuntu has no password set - so
mitigating the risk of brute-forcing password logins - it is still
possible to login as root given "PermitRootLogin yes" and a valid
private key.
Perhaps rkhunter should warn iff Pe
*** This bug is a duplicate of bug 204868 ***
https://bugs.launchpad.net/bugs/204868
...perhaps I spoke too soon - my "working" NM of this morning is no
longer working. It looks like I got lucky this morning!
I'll keep looking into it and post back if I find a fix.
--
NetworkManager 100% cp
Indeed, and this is done by the bitlbee postinst (using update-inetd,
hence the depend):
update-inetd --group OTHER --add
"$PORT"'\tstream\ttcp\tnowait\tbitlbee\t'"$TCPD"'\t'"$BITLBEE"
--
bitlbee fails to start in feisty (netkit-inetd depend gone awol)
https://bugs.launchpad.net/bugs/108
*** This bug is a duplicate of bug 204868 ***
https://bugs.launchpad.net/bugs/204868
Xubuntu Hardy refused to connect to wifi using NM 0.6.6-0ubuntu5 on
Thinkpad X61s with iwl3945 a/b/g wifi.
Building from source and using Steven Walter's patch (not to include
Ubuntu patches) seems to have fi
** Attachment added: "264aea5efe616901dcf8183d428ae4a43d9b2a5a.txt"
http://launchpadlibrarian.net/12351511/264aea5efe616901dcf8183d428ae4a43d9b2a5a.txt
--
pm-utils incorrectly handles multi-core cpufreq on sleep
https://bugs.launchpad.net/bugs/197646
You received this bug notification becaus
Public bug reported:
Binary package hint: pm-utils
Hardy x86_64
pm-utils-0.99.2-3ubuntu1
When transitioning into S3 or S4, pm-utils saves off current cpufreq
scaling governors in sleep.d/94cpufreq. For each cpufreq-supporting CPU
(identified by $x) in /sys/devices/system/cpu/ it does:
savestate
This seems to have been patched upstream:
commit 264aea5efe616901dcf8183d428ae4a43d9b2a5a
Author: Peter Jones <[EMAIL PROTECTED]>
Date: Wed Mar 14 15:37:04 2007 +
- Fix cpufreq save/restore on multi-core cpus
--
pm-utils incorrectly handles multi-core cpufreq on sleep
https://bugs.lau
This has been patched upstream
** Attachment added: "264aea5efe616901dcf8183d428ae4a43d9b2a5a.txt"
http://launchpadlibrarian.net/12351717/264aea5efe616901dcf8183d428ae4a43d9b2a5a.txt
--
pm-utils changes default cpu policy after resuming from suspend-to-ram
https://bugs.launchpad.net/bugs/162
*** This bug is a duplicate of bug 162652 ***
https://bugs.launchpad.net/bugs/162652
** This bug has been marked a duplicate of bug 162652
pm-utils changes default cpu policy after resuming from suspend-to-ram
--
pm-utils incorrectly handles multi-core cpufreq on sleep
https://bugs.launch
...which made it into debian svn as r5748 (as part of the new upstream
release)
http://svn.debian.org/wsvn/collab-maint/ext-maint/pm-
utils/trunk/pm/hooks/?rev=5748&sc=1
Thanks
Steve
--
pm-utils changes default cpu policy after resuming from suspend-to-ram
https://bugs.launchpad.net/bugs/162652
I have the same problem on my Thinkpad X61s running Hardy.
Even today, having updated all packages and rebooted, the problem
remains. I can't get Fn+Home/End to alter the brightness in any
environment (Gnome, other X, tty[1-6]).
For me this is not fixed.
--
brightness indicator does not work on
...I should mention that the Gnome brightness applet also does not work,
and nor does manually echoing to
/sys/class/backlight/acpi_video0/brightness (the only relevant-looking
thing I could find in /sys).
--
brightness indicator does not work on thinkpad
https://bugs.launchpad.net/bugs/137972
Yo
Kjell - many thanks for the information!
--
brightness indicator does not work on thinkpad
https://bugs.launchpad.net/bugs/137972
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
h
PJ I can confirm that works on my X61s. However when you press
quickly/hold down the keys, things seem to get confused:
1) the popup frequently ends up not displaying spurious brightness settings
2) occasionally pressing "brightness up" turns it down and vice versa
Additionally it doesn't fix e.g
I can confirm that on my Lenovo/IBM Thinkpad X61s laptop the brightness
buttons don't work either. Worse still, however, the brightness doesn't
seem to change *at all* - for example when going from AC to battery.
Pressing the "brightness up" key produces the following log:
[Fri Mar 7 21:15:24 20
Incomplete -> confirmed because issue is repeatable on Lenovo Thinkpads.
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Confirmed
--
Why isn't thinkpad-brightness-down.sh used for Lenovo thinkpads?
https://bugs.launchpad.net/bugs/161745
You received this bug notification becau
Removing that guard changes nothing (and in fact when it is removed,
thinkpad-brightness-{up,down} is functionally equivalent to
video_brightness{up,down}.sh, i.e. doing:
acpi_fakekey $KEY_BRIGHTNESSDOWN
... it doesn't work, with or without video (yes, I too assume this
refers to video.ko).
--
I'm inclined to agree, though it's worth noting that (AFAIK,
https://answers.launchpad.net/ubuntu/+source/pm-utils/+question/23292)
the plan for Hardy is to move to pm-utils, so rather than
/etc/acpi/{battery,start,resume,ac}.d, the script would need to go in
/usr/lib/pm-utils/{power,sleep}.d.
I'm
** Changed in: pm-utils (Ubuntu)
Status: New => Confirmed
--
pm-utils changes default cpu policy after resuming from suspend-to-ram
https://bugs.launchpad.net/bugs/162652
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
changelog.Debian.gz says:
* debian/control: Replace netkit-inetd dependency with a versioned
dependency on netbase. netbase provides the appropriate inetd
dependency. Closes: #382682.
however, unlike Debian's netbase
(http://packages.debian.org/stable/admin/netbase), Ubuntu's netbase
netbase changelog says:
netbase (4.27ubuntu1) feisty; urgency=low
* Merge from debian unstable, remaining changes:
- drop dependency on inet superserver
so suggest (possibly modified to include choice of inetd variant):
--- bitlbee-1.0.3/debian/control2007-04-23 17:21:38.0
Public bug reported:
bitlbee can be started either from inetd (default) or as a stand-alone
daemon (marked upstream as experimental).
It ships in feisty configured to start from inetd, yet - unlike the
version shipped with edgy - it does not depend on netkit-inetd: compare
http://packages.ubuntu.
25 matches
Mail list logo
