Bug#681225: tor: Problems with init.d/tor on tmpfs
Package: tor Version: 0.2.3.19-rc-1 Severity: important Dear Maintainer, * What led up to the situation? Running tor with a tmpfs file system. The relevant part of fstab: #temp file settings tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 tmpfs /var/log tmpfs defaults,noatime,mode=0755 0 0 tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0 * What exactly did you do (or not do) that was effective (or ineffective)? Starting tor: # /etc/init.d/tor restart [ ok ] Stopping tor daemon...done (not running - there is no /var/run/tor/tor.pid). [] Starting tor daemon...Jul 11 15:26:25.000 [warn] Couldn't open file for 'Log notice file /var/log/tor/log': No such file or directory Jul 11 15:26:25.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details. Jul 11 15:26:25.000 [err] Reading config failed--see warnings above. failed. If I reinstall tor, then things will work ok until the next reboot: # apt-get install --reinstall tor Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/1,183 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 182816 files and directories currently installed.) Preparing to replace tor 0.2.3.19-rc-1 (using .../tor_0.2.3.19-rc-1_amd64.deb) [ ok ] Stopping tor daemon...done (not running - there is no /var/run/tor/tor.pid). Unpacking replacement tor ... Processing triggers for man-db ... Setting up tor (0.2.3.19-rc-1) ... [ ok ] Starting tor daemon...done. restarting tor then works ok too: # /etc/init.d/tor restart [ ok ] Stopping tor daemon...done. [ ok ] Starting tor daemon...done. However, after a reboot, tor will fail because the files it expects in /var/log are not there or accessible. Thanks for your time in looking in to this. Brendan Murphy. -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tor depends on: ii adduser 3.113+nmu3 ii libc6 2.13-34 ii libevent-2.0-5 2.0.19-stable-3 ii libssl1.0.0 1.0.1c-3 ii lsb-base4.1+Debian7 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages tor recommends: ii logrotate3.8.1-4 ii tor-geoipdb 0.2.3.19-rc-1 ii torsocks 1.2-3 Versions of packages tor suggests: pn apparmor-utils pn mixmaster ii privoxy3.0.19-2 pn socat pn tor-arm pn xul-ext-torbutton -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662251: module-init-tools: Version 6-1 not removable after kmod installed
Package: module-init-tools Version: 6-1 Severity: normal Dear Maintainer, The description for 6-1 on sid says: This dummy package is provided to support the transition from module-init-tools to kmod and should be removed afterwards. However, after installing kmod, trying to remove module-init-tools gives the following: # apt-get -s remove module-init-tools Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: acpi-support-base acpid alsa-base alsa-utils blueman bluetooth bluez bluez-gstreamer dkms gnome-session-bin initramfs-tools linux-image-3.2.0-1-amd64 linux-image-amd64 linux-sound-base module-init-tools nvidia-glx nvidia-kernel-common nvidia-kernel-dkms plymouth plymouth-drm plymouth-themes-all plymouth-themes-fade-in plymouth-themes-glow plymouth-themes-script plymouth-themes-solar plymouth-themes-spinfinity pm-utils powermgmt-base pulseaudio-module-bluetooth upower xfce4-power-manager xfce4-power-manager-plugins 0 upgraded, 0 newly installed, 32 to remove and 0 not upgraded. thanks for your attention Brendan Murphy -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages module-init-tools depends on: ii dpkg 1.16.1.2 ii kmod 6-1 ii libkmod2 6-1 module-init-tools recommends no packages. module-init-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660045: conky-all: background transparency alters the colours of $hr elements
Package: conky-all
Version: 1.8.1-6
Severity: normal
Dear Maintainer,
I've used the following conky script to demonstrate the problem:
**start of conkyrc
# Use Xft?
use_xft yes
xftfont Droid Sans:size=10:style=bold
xftalpha 1.0
text_buffer_size 2048
# Update interval in seconds
update_interval 1
# This is the number of times Conky will update before quitting.
# Set to zero to run forever.
total_run_times 0
# Create own window instead of using desktop (required in nautilus)
own_window yes # create a separate XWindow over the one from Xfdesktop
own_window_type desktop # the window cannot be moved or resized
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager # make it
behave like it belongs to the desktop
own_window_argb_visual yes # true transparency, a compositor has to be active
own_window_argb_value 50 # make the background transparent
own_window_colour black
double_buffer yes # avoid flickering
# Minimum size of text area
minimum_size 320 320
maximum_width 320
max_text_width 0 # don't break lines
# Draw shades?
draw_shades no
# Draw outlines?
draw_outline no
# Draw borders around text
draw_borders no
# Stippled borders?
stippled_borders 0
# border margins
border_inner_margin 5
border_outer_margin 5
# Default colors and also border colors
default_color FF
color1 FF9900 #orange
# Text alignment, other possible values are commented
alignment top_left
# Gap between borders of screen and text
# same thing as passing -x at command line
gap_x 20
gap_y 20
# Subtract file system buffers from used memory?
no_buffers yes
# set to yes if you want all text to be in uppercase
uppercase no
# number of cpu samples to average
# set to 1 to disable averaging
cpu_avg_samples 2
# number of net samples to average
# set to 1 to disable averaging
net_avg_samples 2
# Force UTF8? note that UTF8 support required XFT
override_utf8_locale yes
# Add spaces to keep things from moving about? This only affects certain
objects.
use_spacer none
TEXT
${color1}Text $font${hr 2}$color
**End of conkyrc
When used with conky, the text appears orange as intended but the horizontal
rule appears yellow. Other colours are similarly altered but the orange to
yellow shift is the most visually obvious.
If I remove the background transparency, by setting the argb_visual to 'no',
then the colours of the $hr elements appear as expected.
thanks for time in looking in to this.
Brendan Murphy.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages conky-all depends on:
ii libaudclient2 3.2-1
ii libc6 2.13-26
ii libcairo2 1.10.2-6.2
ii libcurl3-gnutls 7.24.0-1
ii libdbus-glib-1-2 0.98-1
ii libglib2.0-0 2.30.2-6
ii libimlib2 1.4.4-1+b1
ii libiw30 30~pre9-8
ii liblua5.1-0 5.1.4-12
ii libncurses5 5.9-4
ii libtinfo5 5.9-4
ii libx11-6 2:1.4.4-4
ii libxdamage1 1:1.1.3-2
ii libxext6 2:1.3.0-3
ii libxfixes31:5.0-4
ii libxft2 2.2.0-3
ii libxml2 2.7.8.dfsg-7
ii libxmmsclient60.8+dfsg-2
conky-all recommends no packages.
Versions of packages conky-all suggests:
pn apcupsd
pn audacious
pn moc
pn mpd
pn xmms2
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
