Package: acidlab
Version: 0.9.6b20-10.1
Severity: important
If I select one or more alerts from the 5 Most Frequent Alerts
screen, select Delete alert(s) from the Action dropdown box, and
then hit the Selected button, the alerts are not deleted. Instead, I
get an error message that says
No
Package: acidbase
Version: 1.2.1-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I try to delete alerts from the 5 most frequent alerts page (by
selecting the checkbox next to the alerts, selecting delete alerts
from the dropdown box under ACTION, and then hitting the
Package: libssl0.9.8
Version: 0.9.8a-2
Severity: normal
After the libssl upgrade to 0.9.8a-2 yesterday, the ssh client
segfaults. Confusingly, it doesn't do it all the time, just most of
the time. Usually, I can get it to work by repeating the command until
it works.
Here's a gdb session, with
Package: xinetd
Version: 1:2.3.13-3
Severity: wishlist
Tags: patch
Debian turns off entries in inetd.conf by putting #off# at the
beginning of the line. It would be nice if xconv.pl processed those
lines as well, adding a disable = yes line to the xinetd.conf entry.
The attached patch does
Kurt Roeckx wrote:
On Sat, Nov 12, 2005 at 08:57:17PM +0100, Kurt Roeckx wrote:
Hi,
Can you try the patch available at:
http://cvs.openssl.org/chngview?cn=14621
Hi Ron,
Can you please give more details about the hardware you're using?
Upstream seems to think this might be related to
Package: installation-reports
Version: 2.17
Severity: normal
-- Package-specific info:
Boot method: CD
Image version: etch beta 3
(http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso)
Date: September 17, 2006, some time in the morning
Machine: Compaq
Package: powertweak
Version: 0.99.5-18+b1
Followup-For: Bug #417589
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Found powertweak to segfault on my i386 box, caused by bad bounds
checking in src/backends/DMI/dmi.c/dmi_port_type(). My system entered
here with a code of 0xa1 for its floppy:
Mark Brown wrote:
On Sun, Jan 20, 2008 at 02:45:08PM -0500, Ron Murray wrote:
I think the following code should fix it (at least, it protects
against out-of-array-bounds problems):
Thanks.
Could you please resend this patch as a unified diff (ie: 'diff -u orig
new')? patch cannot apply
Package: powertweak
Version: 0.99.5-18+b1
Followup-For: Bug #417589
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems I made a minor error in the bounds checking code. I've
attached a patch to apply against the patched dmi.c. Sorry I didn't
find it before you released the update.
This is,
Package: libcdk5
Version: 5.0.20060507-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The calendar widget segfaults when you call activateCDKCalendar().
Found the problem to be caused by a classic buffer overflow: in line
462 of calendar.c, the temp[] buffer is
Package: brasero
Version: 0.6.1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This appears to be the same problem as bug #441451, which is now
closed. When I try to write a data disc (haven't tried any others), I
get an error message saying that the CD is not writable
Package: acidlab
Version: 0.9.6b20-10
Followup-For: Bug #247730
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
acidlab version now in sarge still has this problem, which exists in
three files:
acid_graph_main.php
acid_stat_time.php
acid_state_citems.inc
It looks like there's been a new
?
.Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4
D86C 74DE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: bluez-firmware
Version: 1.0-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When plugging my BT3030 Bluetooth dongle into a USB slot:
Apr 3 17:33:27 khufu kernel: usb 1-1: new full speed USB device using
uhci_hcd and address 2
Apr 3 17:33:28 khufu
Christian Perrier wrote:
tags 199079 unreproducible moreinfo
retitle 199079 [TO CLOSE] passwd: groupadd/groupdel abort on signal 13
thanks
Despite my efforts (including installation of nagios and mysql stuff
which I don't need), I haven't been able to reproduce this bug, which
is very
Package: krb5-clients
Version: 1.6.dfsg.1-7
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When running ftp (linked via /etc/alternatives/ftp to
/usr/bin/krb5-ftp):
$ ftp elsewhere
../../../../src/appl/gssftp/ftp/cmds.c: at line 175
Connected to elsewhere.rjmx.net.
220
Package: hobbit
Version: 4.2.0.dfsg-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package bb (see http://packages.debian.org/lenny/bb) also has a
/usr/share/man/man1/bb.1.gz file. This causes a conflict when you try
to install one of these packages if the other is already
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patch for both switch and switch2 attached to fix hash table pointer
problems.
- -- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500,
Package: libpam-tmpdir
Version: 0.07-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I installed libpam-tmpdir on three of my machines. It worked fine on
two of them, but on the third I was unable to log in until I disabled
it. I found that pam-tmpdir-helper was
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure whether all of this applies to bug #229384, but some of
it does, so here goes.
switch (i.e. switch for gtk 1.x) wouldn't change themes for me at
all. (Actually, it's more complex than
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After looking at the switch(1) code further, it seems that my comments
about the 'dirname' variable were not quite correct. The usage of that
variable does work as originally written, although using
Package: xcdroast
Version: 0.98+0alpha15-2rjmx1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With the new xcdroast package compiled with gtk 2, drag and drop (at
least in the Create CD/Write Tracks screen) doesn't work. The only way
I can add tracks to the list is to use the
This bug was fixed several months ago by a new upstream version, I
believe. It should probably be closed.
.Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4
D86C 74DE
--
To UNSUBSCRIBE, email to [EMAIL
I don't have access to an alpha box any longer, so I can't test lshw on
one. The current version seems to work ok on powerpc, however. I thhink
we can close this bug.
.Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C
Package: hplip-base
Version: 0.9.3-3
Severity: normal
When starting hplip:
~# /etc/init.d/hplip start
Starting HP Linux Printing and Imaging System: hpiod, hpssd
my syslog shows:
Sep 12 19:11:58 rjmx hpiod: 0.9.3 accepting connections at 1031...
Sep 12 19:12:12 rjmx python: hpssd [ERROR]
Package: util-linux
Version: 2.12r-6
Severity: normal
Since the recent util-linux upgrade, all five of my Debian machines
(running etch) boot up with their clocks five hours slow (i.e. the
difference between my timezone and UTC). All have UTC=no in
/etc/default/rcS, but the system clock is not
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: normal
X worked fine until I rebooted after running today's etch upgrade,
and now it won't start. The Xorg.0.log gives details, but basically
we get an INVALID MEM ALLOCATION warning, and later a message to the
effect that
Package: cupsys
Version: 1.2.1-2
Severity: wishlist
After upgrading to the latest cupsys package in testing, the CUPS
printer no longer appeared as a samba share (not visible from a
Windows machine nor a Linux box running smbclient).
After spending several hours trying to track the problem down,
Perhaps a warning that long filenames don't work well with samba would
^
be appropriate.
Sorry, that should be printer names. I probably shouldn't file these
things at 1:30 am.
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key
Package: php5
Version: 5.1.4-0.1
Severity: serious
Justification: no longer builds from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While trying to build php5_5.1.4-0.1 locally (to track down a segfault
bug, similar to #347642), discovered that the php5 package is currently
unbuildable
Package: sshfs
Version: 1.6-1
Severity: normal
When I try to run sshfs on my Sun Enterprise 250 (2 x 400 MHz
Ultrasparc II processors), I get a bus error:
[EMAIL PROTECTED]:~/tmp$ mkdir mnt
[EMAIL PROTECTED]:~/tmp$ ll
total 64
drwxr-xr-x 3 ron ron 126 May 17 11:42 ./
drwxr-xr-x 190
Package: gdb
Version: 6.4-1
Severity: important
I'm trying to help track down a problem with sshfs, which is a
threaded program. Here's what happens:
(gdb) set args -s -d -osshfs_debug bb: ./mnt
(gdb) r
Starting program: /home/ron/Debian/sshfs/sshfs-fuse-1.6/sshfs -s -d
-osshfs_debug bb:
out, and
log in again. (There's probably a better way than logging out/in, but I
haven't looked yet).
If hal isn't mostly necessary any more, it might have been an idea to
state that in the changelog.
(forgot to copy to bugs.debian.org earlier)
--
Ron Murray (r...@rjmx.net)
http://www.rjmx.net
Package: manpages-dev
Version: 3.05-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The basename (3) man page says that there are two different versions
of basename(): the POSIX one and the GNU version. This is
correct. However, it goes on to say that you get the GNU version
Package: grub-pc
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As of the last grub-pc update, this problem seems to have been
resolved (at least as far as I'm concerned: the original submitter may
differ).
Thanks for your work on this.
.Ron
- -- Package-specific info:
, let me know what you think. Wouldn't surprise me if I'd
missed something obvious.
Thanks for you work on this,
.Ron
--
Ron Murray (r...@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint:
0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D 0D4A
Random access is the optimum
Package: gnome-keyring
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I unmount my NTFS partition, I keep getting errors (in auth.log, no
less!) like this:
Feb 15 10:42:53 khufu gnome-keyring-daemon[17623]:
removing removable location: /win
Feb 15 10:42:53 khufu
Package: ninja
Version: 0.1.3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On first installation of ninja, it flat-out refuses to create its log
file:
Starting ninja: log: reading configuration file: /etc/ninja/ninja.conf
log: ninja version 0.1.3 initializing
log: magic
Package: spamassassin
Version: 3.3.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the recent spamassassin upgrade, I'm starting to get log entries
like this:
Feb 9 10:41:04 tinkerbell mimedefang-multiplexor[2743]: Slave 2
stderr: plugin: failed to parse plugin (from
Package: shorewall6
Version: 4.2.9-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's a typo in the example two-interface config file in
/usr/share/doc/shorewall6/examples/two-interfaces/shorewall6.conf
which, when copied to /etc/shorewall6, renders the ipv6 firewall
Package: opendnssec-enforcer, opendnssec-signer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Version: 1.0.0-6
Severity: normal
There's a bug in the init.d scripts of both the opendnssec-enforcer
and opendnssec-signer packages which causes the PID file to be created
in a newly-created
Looks like one of the recent samba/winbind updates made winbind
authentication required (seems a silly thing to do, but what do I
know?).
Try running pam-auth-update and switch off winbind authentication.
.Ron
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: selinux-policy-default
Version: 2:0.2.20100524-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When trying to start avahi-daemon after today's update, it fails. My
syslog has:
Jul 23 21:36:29 tinkerbell avahi-daemon[21370]: Found user 'avahi'
(UID 135) and group
Package: fetch-crl
Version: 2.8.5-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Installing this package does not create the
/etc/grid-security/certificates directory. This could be the reason we
get the
'/etc/grid-security/certificates' is not a directory
or cannot be
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have three boxes running testing. They all exhibit the same problem,
and have been doing so for a couple of months now.
They're all set up in much the same way:
- - root partition is a
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah, thanks for clearing that up. Again, sorry for the confusion.
The problem, then, seems to be that grub is going into rescue mode
when it first comes up. On my machines, at least, it looks
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like I should file bug reports soon after doing the research,
not several weeks later. The root device is apparently chosen
(incorrectly, IMHO) by a line in /etc/grub.d/00_header:
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that, on my system at least (don't know about the original
submitter), grub is going directly into rescue mode. I do not know why
it should do such a thing, although one possibility is
Florent's init.d script doesn't work if more than one interface is
specified in /etc/default/isc-dhcp-server. The attached script fixes
that problem.
.Ron
--
Ron Murray (r...@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint:
0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D
Package: libclutter-1.0-0
Version: 1.6.10-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Programs using clutter have recently started to fail. geeqie, for
example:
(geeqie:9963): Clutter-CRITICAL **: Unable to initialize Clutter:
Unable to find suitable fbconfig for the GLX
for annoying you.
Thanks,
.ROn
--
Ron Murray (r...@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint:
0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D 0D4A
Stand on the toilet, get high on pot.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Package: strongswan-ikev2
Version: 4.5.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The charon daemon in strongswan 4.5.0 respawns after less than a
minute:
Feb 19 11:13:16 cheops charon: 10[DMN] thread 10 received 11
Feb 19 11:13:16 cheops charon: 10[DMN] killing
Not sure if this is related or not, but since the upgrade to 5.7.3 in
testing, I've been getting lots of mail from logcheck that look like this:
This email is sent by logcheck. If you wish to no-longer receive it,
you can either deinstall the logcheck package or modify its
configuration file
Package: hal
Version: 0.5.14-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the recent hal upgrade and the change to d-bus activation, hald
is not starting on bootup on at least three of my Debian
machines. Running 'lshal' as root starts it up just fine, and it works
Package: calendarserver
Version: 3.2+dfsg-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After the upgrade from v2.x, calendarserver no longer listens on the
SSL port as it did before. Nothing obvious in the access or error
logs, even in debug mode.
- -- System Information:
Package: spamass-milter
Version: 0.3.1-10
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With the move of /var/run to /run (and associated use of volatile
memory), the permissions on /run/spamass are not set correctly on
reboot:
drwxr-xr-x. 2 root root100
I second the motion. I do not need xul-ext-adblock-plus. Especially
since it forces installation of iceweasel, which I most emphatically do
_not_ need. I'll stick with manually installing the *real* firefox,
thank you very much.
As the original submitter says, please move the dependency to
On 08/28/12 13:00, Laurent Bigonville wrote:
Hi,
Could you please check if you have the selinux-policy-default package
installed?
Also, what is the semanage login -l command giving you?
Cheers
Laurent Bigonville
selinux-policy-default package is installed.
semanage login -l gets me:
Package: selinux-policy-default
Version: 2:2.20110726-9
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the last selinux update (around July 6), running selinux in
permissive mode stops gdm3 and X from working for me (haven't tried
enforced mode).
Bootup proceeds normally
Package: selinux-policy-default
Version: 2:2.20110726-9
Followup-For: Bug #683756
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running gdm3 in debug mode, I get this in the gdm slave log:
-
gdm-welcome][4275]: DEBUG(+): GdmSessionWorker: received pam message of type 2
On 08/14/12 12:10, Rahul Amaram wrote:
On Friday 13 July 2012 12:53 PM, Rahul Amaram wrote:
I am able to reproduce this issue. I will have to follow up with
upstream reg. this.
The problem is that the configuration option EnableSSL is set to
false. Kindly set the below option in
On 08/14/12 05:03, Laurent Bigonville wrote:
I'm running selinux in permissive mode and using GDM3 as DM and I've no
problem with it.
Could you look in /etc/pam.d/ and see and see what are call to
pam_selinux module in the gdm3 related services?
Also what is the version of gdm3 package?
Package: calendarserver
Version: 2.4.dfsg-7.1
Severity: important
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the upgrade to 2.4.dfsg-7.1, calendarserver would not start:
[] Starting calendarserver: caldavdinvoke-rc.d: initscript
calendarserver, action start failed.
Hi.
I was just going through old submitted bugs, and I came across this
one. I must have missed the reply, and I'm sorry about that, but the
problem certainly doesn't exist in current versions of brasero.
You can close this bug if you want.
.Ron
--
To UNSUBSCRIBE, email to
Package: usbmount
Version: 0.0.22
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For some time, I've noticed that, when I plug a flash drive into my
wheezy boxes, it's been mounted twice (usually at /media/usb0 and
/media/usb1). Access is ok at either mount point, but I've had to
Package: evolution
Version: 3.2.2-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just installed evolution on my desktop and laptop, and both have
the same problem: no root CA certicates in the certificate store
(Edit/Preferences/Certificates/Authorities is empty). This
.
.Ron
--
Ron Murray (r...@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint:
0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D 0D4A
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: earcandy
Version: 0.9+bzr12-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Starting earcandy doesn't result in a GUI. It just hangs until I
interrupt it with ctl-C:
- ---
ron@khufu:~$ earcandy
** (process:16963):
Package: krb5-auth-dialog
Version: 3.8.0-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sometime recently, krb5-auth-dialog lost its 'preferences' function,
leaving no way to set the login primcipal (among other things). It
used to be in the context menu, but it's no longer
On 08/29/12 06:27, Laurent Bigonville wrote:
Hello,
Alright, I got it.
/usr/sbin/gdm3 is not labeled with the right context.
On my machine here it's labeled:
-rwxr-xr-x. 1 root root system_u:object_r:xdm_exec_t:SystemLow 160296 jun 25
20:29 /usr/sbin/gdm3
And by default in wheezy it's
Package: selinux-policy-default
Version: 2:2.20110726-9
Followup-For: Bug #683756
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did some work on the remaining machine today. First I enabled
debugging on the gdm3 daemon, set up an strace, and started gdm. As
before, gdm3 respawned multiple
On Sep 5, 2012, at 5:11, deb...@mikapflueger.de wrote:
Hi Ron
Are you absolutely sure the context for gdm3 is correct at the machine where
it doesn't work? You wrote that you relabeled and rebooted and that would
restore the (wrong) context. Unfortunately (I'm not sure if this is a bug -
I downloaded the source package and checked debian/spamass-milter.init.
Seems to be the same size and md5sum as my /etc/init.d/spamass-milter:
# md5sum ./debian/spamass-milter.init /etc/init.d/spamass-milter
f59a570b2c630a540e2471350f7050ec ./debian/spamass-milter.init
On 05/08/12 21:24, Don Armstrong wrote:
On Tue, 08 May 2012, Ron Murray wrote:
I downloaded the source package and checked
debian/spamass-milter.init. Seems to be the same size and md5sum as
my /etc/init.d/spamass-milter:
# md5sum ./debian/spamass-milter.init /etc/init.d/spamass-milter
This is probably caused by Debian bug #662990 (in policycoreutils),
assuming you're running selinux. Unfortunately, while they fixed that
bug a couple of months ago, the upgraded package hasn't made it into
testing yet.
As a workaround, comment out line 32 of
Package: gnome-online-accounts
Version: 3.4.2-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For some time now, whenever I log in to Gnome, the display locks up
solid for around 30 seconds. The mouse cursor is visible and moveable,
but anything on the display (like gkrellm's
Package: krb5-auth-dialog
Followup-For: Bug #714815
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah yes. I must admit that I hadn't realised there were menu items
under those. Sorry for taking up your time.
You may close this bug if you want.
Thanks,
.Ron
- -- System Information:
Package: udev
Version: 204-5
Followup-For: Bug #655924
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have the same kind of problem. I have four Debian machines, and on
three of them the only symlink created is /dev/cdrom (linked to sr0).
The fourth machine (the one I'm submitting this on, and
Package: calendarserver
Version: 3.2+dfsg-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When trying to start calendarserver:
# /etc/init.d/calendarserver start
Traceback (most recent call last):
File /usr/bin/twistd, line 14, in module
run()
File
Package: grub2-common
Version: 2.00-22
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the last grub update in testing, update-grub appears to fail
during 30_init-select and doesn't include Windows partitions in
grub.cfg, although it sees them:
khufu:~# update-grub
Package: init-select
Version: 1.20140301
Followup-For: Bug #739581
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
H. Close, but no banana.
* Problem still exists in version 1.20140301. grub.cfg cuts off
immediately after the ### BEGIN /etc/grub.d/30_init-select ###
line.
*
character set: us-ascii
Please change your locale if this is incorrect.
- -- Package-specific info:
** Environment settings:
EDITOR=emacs
EMAIL=r...@rjmx.net
INTERFACE=text
** /home/ron/.reportbugrc:
reportbug_version 2.10.1
mode expert
ui text
realname Ron Murray
email r...@rjmx.net
no-ldap
query
.
--
Ron Murray r...@rjmx.net
PGP Fingerprint: 0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D 0D4A
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: cairo-dock-core
Version: 3.3.2-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have cairo-dock set to start with my xfce4 session (with no xfce4
panels). It will quite often crash noiselessly after a few minutes
running; the cairo-dock process is still running,
Package: gqrx-sdr
Version: 2.3.1-2
Severity: minor
Dear Maintainer,
URL given in man page (in SEE ALSO section) is
http://www.oz9aec.net/index.php/gnu-radio/gqrx-sdr
Project's home page has moved to
http://gqrx.dk/
-- System Information:
Debian Release: stretch/sid
APT prefers testing
Package: python-paramiko
Version: 1.15.2-1
Severity: normal
I'm using paramiko as the SSH backend for duply. Recently, after
looking more closely at the current SSH man page, I found that
newer types of SSH keys, ECDSA and ED25519, existed. So I created
new keypairs of that nature, and all seemed
I neglected to mention that authentication for my backups is normally
in the form of passwords (contained in duply's config file). I don't
use public-key authentication for my backups, although I do use it for
all other SSH purposes.
.Ron
--
Ron Murray <r...@rjmx.net>
PGP Finge
Package: initramfs-tools-core
Version: 0.123
Severity: normal
Dear Maintainer,
When using lsinitramfs to check the contents of an initrd:
> root:~# lsinitramfs /boot/initrd.img-4.4.2
> /boot/initrd.img-4.4.2-curly-0
> kernel
> kernel/x86
> kernel/x86/microcode
>
ot; option in the rescue disc returned "ok", even though the above
error messages appeared.
I've marked this "important" even though it's probably close to the "grave"
category. Feel free to change it.
.Ron Murray
-- Package-specific info:
***
value from efibootmgr is tested, as I noted in the original
bug report.
.Ron
--
Ron Murray <r...@rjmx.net>
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
signature.asc
Description: OpenPGP digital signature
Corrected patch attached (fixes gtk-3.0 as well as gtk-3.20 branch).
.Ron
--
Ron Murray <murr...@dor.state.ma.us>
PGP Fingerprint:
5A26 A211 68D9 E5AA 176A 1AA3 7A89 5E0B 040A 7431
diff -uNr xfce4-notifyd-0.3.3/themes/gtk-3.0/Bright/gtk.css xfce4-notifyd-0.3.3-fixed/themes/gtk-3.0/
k
properly (on my box, at least) without correcting this issue.
,Ron Murray
--
Ron Murray <murr...@dor.state.ma.us>
PGP Fingerprint:
5A26 A211 68D9 E5AA 176A 1AA3 7A89 5E0B 040A 7431
**
This email and any f
and gcc-6, I have no idea whether it'll work for previous or
future gcc versions. It depends on whether gcc, cc and other executables
are symlinked to gcc-5, cc-6 and so on.
Hope it helps.
.Ron
--
Ron Murray <r...@rjmx.net>
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E86
I've just checked, and the problem doesn't happen here any longer either
(using xfce4).
Thanks,
.Ron
--
Ron Murray <r...@rjmx.net>
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
signature.asc
Description: OpenPGP digital signature
logins from :0, but there weren’t,
apparently because of this bug. (I am not usually in the habit of repeatedly
rebooting a machine just to watch it come up).
Thanks,
.Ron
--
Ron Murray <r...@rjmx.net>
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
Package: sddm
Version: 0.15.0-1
Severity: normal
Dear Maintainer,
sddm doesn't seem to update /run/utmp or /var/log/wtmp. Logging in with it, the
'w' command gives me:
> ron@khufu:~$ w
> 21:09:47 up 36 min, 0 users, load average: 0.10, 0.08, 0.20
> USER TTY FROM LOGIN@
essary).
>
> I actually think it is a feature of the headphones and not triggered
> from your Linux system.
>
>
Could be my headphones, but it doesn't happen with the Windows 10 box. I'll try
your suggestion when I get a chance, and let you know how it goes.
Thanks,
.Ron
-
Package: blueman
Version: 2.0.5-1+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
I have a set of Bluetooth headphones which I use on multiple computers. I also
have a Bluetooth keyboard attached to my Linux box.
If I have the headphones connected to the
After "and then right-clicking on the appropriate device.", I should have
written "then select 'Disconnect'".
Apologies for the error.
.Ron
--
Ron Murray
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761
On 06/09/2018 03:12 PM, Ron Murray wrote:
> On Fri, 8 Jun 2018 07:48:30 +0200 Christopher Schramm wrote:
> > Hi Ron,
> >
> > there should not be any such auto-connect feature in blueman. You can
> > easily confirm that by stopping blueman-applet and check if it sti
1 - 100 of 140 matches
Mail list logo
