control: -1 severity normal
2013/3/8 Arturo Moral :
>> This config was removed in version 0.79.5 and might not work at all:
>
> I'm currently using 0.79.4, therefore the config change does not affect me,
> right?
You should not use it, 0.79.5 will migrate to testing on the following days.
> Anyw
2013/3/7 g0to :
> -- Configuration Files:
> /etc/apt/apt.conf.d/50unattended-upgrades changed:
> // Automatically upgrade packages from these origin patterns
> Unattended-Upgrade::Origins-Pattern {
> // Codename based matching:
> // This will follow the migration of a release throug
2012/11/6 Michael Tokarev :
> So, can you start it again when libaio1 is NOT installed?
Yes, I was able to start the VMs again after the libaio1 removal. I'm
not sure about the full Xen system -- I can't test now.
Cheers
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
2012/11/6 Michael Tokarev :
> On 06.11.2012 15:40, Teodor wrote:
>> I've just had a system crash a few seconds after I removed 'libaio1
>> package (declared orphan by deborphan).
>
> What kind of crash? Crash of what, exactly? What you were running?
Debian Linux 6.0 (amd64) on top of Xen 4.0 hyp
Didn't you forgot to add "| www-browser" in the Depends: line?
Funny upgrade today with 121 new packages although I have at least two
packages installed that provide www-browser.
Cheers
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
2012/7/3 Tollef Fog Heen :
> Ah, it looks like it never actually got to the configure step of
> systemd. Does that sound correct, and is the diversion correctly
> removed now? If not, could you please try downgrading to 44-2 and then
> upgrading and verifying that the diversion is gone?
1) On pa
2012/7/2 Tollef Fog Heen :
> That's quite odd.
>
> Can you please provide the output of «grep systemd /var/log/dpkg.log»?
See below. I've reinstalled «systemd» this morning on my workstation.
Cheers
--
2012-07-02 10:55:30 upgrade systemd-gui:i386 44-2 44-3
2012-07-02 10:55:30 status half-c
2012/7/2 Tollef Fog Heen :
> Did you upgrade to 44-3 before removing it or not?
Yes, I've upgraded almost all packages (including systemd) and then
reported "Bug#679873: lsb-base: Can't open /lib/lsb/init-functions".
Later I've uninstalled systemd packages to work around the problem,
but I've dis
Diversion is not removed at all on package removal:
| root@frost:~# ls -hl /lib/lsb/
| total 16K
| drwxr-xr-x 2 root root 4.0K Jul 2 11:11 init-functions.d
| -rw-r--r-- 1 root root 12K May 30 17:01 init-functions.systemd
| root@frost:~# dpkg -S /lib/lsb/init-functions.d
| lsb-base: /lib/lsb/init
Attaching the file ...
2012/6/10 Teodor MICU :
> By following the gdb example below I've obtained a (different)
> backtrace by unplugging the power cord from laptop. This is the
> "voluntary" trigger of this bug for me.
Starting program: /usr/bin/gnome-shell --repl
By following the gdb example below I've obtained a (different)
backtrace by unplugging the power cord from laptop. This is the
"voluntary" trigger of this bug for me.
BTW, this is now a problem for those that use systemd as well. Up to
version 0.6.21-1, when using systemd init, gnome-shell did not
Although it appeared that the problem is fixed in version 0.6.21-2,
after several hours the problem reoccurred. Indeed, the crash is not
that frequent and most important I didn't had a full gnome-shell crash
(it restarted automatically).
I can still reproduce the problem by just unplugging the pow
Apparently, using systemd avoids the crash in gnome-shell. This seems
to be a good guess of Michael Biebl in bug#674433, so both problems
appear to have the same root.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact l
severity 673185 grave
stop
This problem affects gnome-shell even more. If I'm on battery the
gnome-shell process is killed but not restarted afterwards. The only
way to obtain a somehow stable X/gnome session was to restart gdm3. I
still get the gnome-shell respawn but I least I'm not forced into
severity 670097 important
stop
I had no other occurrence of this problem for 2-3 weeks. Because there
is a workaround (kill gnome-shell) I downgraded the bug severity.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
I just read [1] that this problem is caused by «cogl», should I reassign?
I've had another occurrence one hour ago (log entries attached). These
are all «ocgl» related packages currently installed:
ii gir1.2-cogl-1.0 1.10.2-3
ii gir1.2-coglpango-1.0 1.10.2-3
ii libcogl-pango0:amd64 1.10.2-
2012/4/30 Michael Biebl :
>>>From time to time the Gnome shell will just freeze/hang and not accept any
>>>input
>
> How often is "from time to time"? Is this related to specific
> actions/circumstances, e.g. running an OpenGL game or something similar.
At least once a week. Usually I run these a
2012/4/24 Michael Vogt :
> This should work with current sid but it will not work with older
> version of python-apt. I added a check into do the code to not crash
> if it runs with older versions of python-apt.
Thanks. I realised after sending the report that severity "grave" was
not justified du
2012/4/20 Michael Vogt :
> Sure, the setsid() call makes the process a session leader and removes
> the controlling tty. The rational is that if you run
> unattended-upgrades in a shell and then shutdown your tty goes away
> and unattended-upgrades gets killed even if its in the middle of a
> opera
2012/4/20 Michael Vogt :
> Thanks for your bugreport. I fixed that now. I guess in your case it
> was already the session-leader for some reason (maybe because of
> systemd?).
Yes, I use «systemd» but I don't know what being session-leader means.
Most times u-a is run automatically by Cron, only w
One important detail: I use «systemd», so this might not be a bug in U-A.
Thaks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2012/4/2 Rene Engelhard :
> On Mon, Apr 02, 2012 at 07:06:26PM +0300, Teodor MICU wrote:
>> I've had this problem on my homestation. I fixed it by setting
>> "LANG=C" and run the upgrade again. [..]
>
> I *think* that this is just by chance. I also get a error w
I've had this problem on my homestation. I fixed it by setting
"LANG=C" and run the upgrade again. On this host I don't have en_US at
all but only ro_RO.UTF-8. Hope this helps as this seemed to be a
locale problem.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
Hi Debian Release team,
The reported problem here appears to be for amd64 only because I was
able to install the package libswt-gtk-3-java on i386. Also, looking
at the build status page [1] I see that the amd64 package was uploaded
directly by the maintainer.
Is there any chance that scheduling
Hi,
> > There is absolutely *no* relation between unattended-upgrades and
> > pm-utils. Any process running at the time of hibernation could consider
> > itself just as important as unattended-upgrades, thereby preventing the
> I'm open for better suggestions but it seems preferable to delay
> h
2011/10/31 Michael Vogt :
> I think I found the issue now and fixed it in trunk. The issue is that
> the init scripts are run on upgrade, but they really should only run
> on actual shutdown. Its a bit confusing why this is happening as the
> header of the init script says that it should not run in
I've forgot to attach the log file.
Thanks
--
2011-10-31 06:15:32,683 INFO Initial blacklisted packages:
2011-10-31 06:15:32,684 INFO Starting unattended upgrades script
2011-10-31 06:15:32,684 INFO Allowed origins are: ['o=Debian,a=testing']
2011-10-31 06:16:18,406 INFO Packages that are au
Hi,
2011/1/31 Julian Andres Klode :
>> Indeed perl-base was corrupted. The question is how since I didn't
>> modified it manually?!
> Filesystem bug, system crash?
That's the most probable cause due to a power failure last night
combined with 'ext4' file systems.
However, this shows more possibl
Hi,
2011/1/31 Adam D. Barratt :
> Looking at the log, it doesn't appear the errors are actually due to
> libc6, however. This section suggests a broken package; it would be
> interesting to narrow down which package caused it, so we can determine
> whether it is a local or mirror issue:
I've red
Hi,
2011/1/31 Julian Andres Klode :
> Definitely not a libc6 bug, and probably not a bug
> at all. It looks like your perl-base installation
> is corrupt.
Indeed perl-base was corrupted. The question is how since I didn't
modified it manually?!
> Does perl -e "require Hash::Util;" work?
It didn
severity 611283 normal
retitle 611283 gnome-commander doesn't start due to broken link on "start_dir_*"
quit
I've found the cause to be a broken link configured for the
"start_dir_right" parameter. Once the broken link was removed it had
no problem to start (with a warning for missing directory).
Package: gnome-commander
Version: 1.2.8.6-3
Justification: renders package unusable
Severity: grave
Hi,
After todays execution of unattended-upgrade for 'dmsetup
libdevmapper1.02.1 libpango1.0-0 libpango1.0-common lvm2' I get
segmentation fault at startup of gnome-commander every time. Yesterday
2011/1/25 Harald Jenny :
> On Tue, Jan 25, 2011 at 04:57:42PM +0200, Teodor MICU wrote:
>> Good catch. Indeed, $USER is defined on interactive sessions and I was
>> only thinking about starting at boot.
>
> Yes therefor I think this change is also necessary do you agree
Hi,
2011/1/24 Harald Jenny :
> On Mon, Jan 24, 2011 at 10:40:06PM +0200, Teodor MICU wrote:
>> I can only spot some cosmetic issues, otherwise I see no problem. The
>> change USER -> SYSTEMUSER only makes the diff larger and not really
>> necessary.
>
> I tend t
2011/1/24 Harald Jenny :
> On Mon, Jan 24, 2011 at 08:59:41PM +0200, Teodor MICU wrote:
>> 2011/1/24 Harald Jenny :
>> > Ok although the PIDFILE line can be removed with the below code.
>>
>> I'm don't see where PIDFILE is removed.
>
> Just take a lo
2011/1/24 Harald Jenny :
> Ok although the PIDFILE line can be removed with the below code.
I'm don't see where PIDFILE is removed.
>> Yes. It should be a valid config if /etc/default/$NAME that doesn't
>> contain anything. Actually it should be the default to have only
>> comments with the defau
Just ignore this. I probably need some coffee.
Having MILTERSOCKET variable empty is also with the case with the
proposed configuration where you set your default
"unix:path/to/socket" value.
Thanks
2011/1/24 Teodor MICU :
> One more important issue I think we missed so f
2011/1/24 Harald Jenny :
> On Mon, Jan 24, 2011 at 06:37:37PM +0200, Teodor MICU wrote:
>> 1) usually you should enclose with "" the full path here:
>> +PIDFILE=/var/run/amavis/"$NAME".pid
>> +[ -r /etc/default/"$NAME" ] && . /etc/de
Hi again,
2011/1/24 Harald Jenny :
> first thanks to everbody for the valuable input, it helped me a lot to improve
> this init script. Please take a look at the third version of my patch and
> comment on it.
Overall it seems fine, just a few observations:
1) usually you should enclose with "" t
2011/1/24 Harald Jenny :
> Well as far as I know Debian currently only supports /bin/bash and /bin/dash
> as
> providers of /bin/sh so I guess it's currently safe to use echo -n in init
> scripts.
It's fine. After some digging I guess I had in mind "echo -e" and
"echo -en" are not working with da
Hi,
2011/1/24 Julien Cristau :
>> Yes, it does cover the case where MILTERSOCKET contains something but
>> not if it is empty. For this I would recommend 'printf' since 'echo
>> -n' is not portable and not working with /bin/dash.
>>
> Eh, what?
>
> Scripts may assume that `/bin/sh' implements
Hi,
2011/1/24 Agustin Martin :
> On Mon, Jan 24, 2011 at 02:17:48PM +0100, Harald Jenny wrote:
>> I will have a to check this - this is meant as a guard against accidently
>> setting $MILTERSOCKET to "".
Good catch on this. I didn't though of this being empty.
> Damm, seems I wrongly understood
Hi,
2011/1/24 Harald Jenny :
>> 7) You should probably add "-q" for all these executions to avoid
>> unwanted strings during start/stop/restart.
>> "`echo $MILTERSOCKET | grep -v ^inet`"
>
> If MILTERSOCKET is checked to contain text too?
Yes, it does cover the case where MILTERSOCKET contains
2011/1/21 Agustin Martin :
> if [ "$MILTERSOCKET" ] && [ "`echo $MILTERSOCKET | grep -v ^inet`" ]; then
>
> but as Teodor points out (just read it), second check seems to be enough.
Only that I realized latter the intention of this construction. My
previous suggestion was to use this construction
[Harald please CC: my address otherwise I could not see your responses]
2011/1/20 Harald Jenny :
> I checked with other init scripts an in order to have a consistent coding
> style
> in the init script I replaced the && with if-clauses - could you take a look
> at
> it and tell me if this looks
Hi Harald,
I looked at your patch and I think those multiple "&&" checks in chain
are prone to mistakes in some conditions.
I've reported the same problem with clamav-milter [1] some time ago
and I believe that is a cleaner and better implementation for checking
SOCKET, SOCKET_TYPE and SOCKET_PATH
severity 602172 normal
tag 602172 + moreinfo unreproducible
stop
Hi,
On Tue, Nov 2, 2010 at 10:50 AM, Matthieu Baechler
wrote:
> Package: openvpn
> Version: 2.1.3-2
> Severity: grave
>
> A freshly installed openvpn package won't start because it needs
> nobody group existence but install script
Hi,
On Thu, Oct 21, 2010 at 2:03 PM, Alberto Gonzalez Iniesta
wrote:
> I've got a new -2 package (same location) with upstream's solution,
> instead of mine. Would you mind testing it? That would probably be the
> one I upload to close this report.
I've just tested this package (built on Oct 21)
Hi,
On Fri, Oct 15, 2010 at 3:39 PM, Alberto Gonzalez Iniesta
wrote:
> Could you try with this package [1]?
> [1] http://etc.inittab.org/~agi/openvpn_2.1.3-2_i386.deb
I've reverted the original config on the oVPN server and with the -2
package it works fine as on v2.1.0.
The weird thing about p
Hi,
On Fri, Oct 15, 2010 at 2:45 PM, Alberto Gonzalez Iniesta
wrote:
> I think I found the bug. But you can help me confirm this (and solve the
> problem for the time being). Could you try this (on the server config):
>
> Change:
> push "route remote_host 255.255.255.255 net_gateway"
> To:
> push
Hi Arnaud,
Since the patch is only a 2 line diff [1], can you upload a targeted
fix with this patch for squeeze? I strongly believe that release team
will not object to this small fix which is also included in the
upstream source. Also, this bug is currently RC.
Thanks
[1] http://boxster.ghz.cc
Hi,
On Thu, Oct 14, 2010 at 11:37 AM, Alberto Gonzalez Iniesta
wrote:
> Hi, could you attach (without sensitive data) the server and client
> configurations?
Sure. The real company addresses and names were replaced with generic names.
Thanks
#== openvpn client options (linux) ==
client
Hi,
On Wed, Sep 22, 2010 at 4:48 PM, Stephane Dudzinski wrote:
> I have just upgraded to 0.8.7g-1, backed up the DB before doing so then
> did the web interface upgrade steps, it said there was no SQL upgrade.
> And it is still happily graphing.
>
> So I am guessing your problem is probably with
Hi,
On Wed, Sep 22, 2010 at 12:00 PM, Stephane Dudzinski
wrote:
> We did upgrade a box from Lenny to Squeeze and it indeed kept all its
> graphs this time, this is what we are currently using:
>
> ii rrdtool 1.4.3-1
> ii cacti 0.8.7e-4
[really attaching the SQL select queries]
mysql> use cacti;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> SELECT id FROM host WHERE disabled = '' ORDER BY id;
++
| id |
++
| 1 |
|
Hi,
On Wed, Sep 22, 2010 at 10:57 AM, Teodor MICU wrote:
> Yes, with 'cmd.php' I get the graphs but still at every 5 minutes
> there are SQL errors reported (see attached).
Ok, the last test reveals that with 'cmd.php' used directly after
upgrade the same SQL errors w
On Wed, Sep 22, 2010 at 10:57 AM, Teodor MICU wrote:
> On Tue, Sep 21, 2010 at 11:56 PM, sean finney wrote:
>> some ideas/questions off the top of my head:
>> * did you get any sql upgrade errors after the package was updated?
>
> There were no sql upgrade scripts from 0.8.
Hi,
On Wed, Sep 22, 2010 at 9:23 AM, sean finney wrote:
> do you get the same problems if you also upgrade spine from the lenny version
> to the squeeze version (0.8.7e-2)? i wouldn't be surprised that the
> poller from lenny is designed for different sql/schema and thus might not
> do the right
Hi,
On Tue, Sep 21, 2010 at 11:56 PM, sean finney wrote:
> some ideas/questions off the top of my head:
> * did you get any sql upgrade errors after the package was updated?
There were no sql upgrade scripts from 0.8.7e-4 to 0.8.7g-1. The
upgrade says clearly that there are no scripts to run. I
Hi again,
On Tue, Sep 21, 2010 at 11:02 PM, Teodor MICU wrote:
> It seems that this old problem has an impact on 'squeeze' too. After
> upgrading from v0.8.7e-4 to 0.8.7g-1 all the graphs were with NaN from
> this point forward.
I've been able to reproduce the problem.
retitle 531546 empty graphs due to 'A DB Exec Failed' Poller[0] ERROR
quit
Hi,
It seems that this old problem has an impact on 'squeeze' too. After
upgrading from v0.8.7e-4 to 0.8.7g-1 all the graphs were with NaN from
this point forward. The error message in cacti.log was like in the
attached fi
On Wed, Aug 18, 2010 at 12:38 AM, Mike Markley wrote:
> On Mon, Aug 16, 2010 at 10:57:35AM +0300, Teodor MICU
> wrote:
> [..]
>> In conclusion, can we downgrade the severity of this bug report so
>> that at least we have the same version from lenny in squeeze too? If
>&
Followup-For: Bug #481072
Package: dk-filter
Version: 1.0.0.dfsg-1+b1
*** Please type your report below this line ***
Hello,
I've been checking the status of 'dk-filter' for squeeze and it is
blocked for inclusion by this RC bug report. As far as I can see this
reliable crash is reproduced only i
Hi,
On Sun, Mar 21, 2010 at 6:43 PM, Nico Golde wrote:
> From what I see it is using /var/cache/ddclient/ddclient.cache. Can you
> elaborate why you think it's using /tmp/?
It doesn't apper to be using that directory. This is what I have on my laptop:
| d...@r2:~$ ls -l /tmp/ddclient.cache /var/
Hello,
On Tue, Mar 2, 2010 at 1:07 AM, Ludovic Claude
wrote:
> The changes were motivated by the fact that jscv is unreliable (see
> #561559) and is hard to use when you need to setup Tomcat with ports <
> 1024. Upstream maintains the catalina.sh script and recommends its use.
> We were kindly as
severity 561477 wishlist
retitle 561477 please improve the debconf question about web server
configuration
thanks
On Thu, Jan 7, 2010 at 11:17 AM, Patrick Schoenfeld
wrote:
> On Wed, Jan 06, 2010 at 05:44:28PM +0200, Teodor MICU wrote:
>> Ok, now I see that this is a way of disab
[please don't use -quiet as I didn't received the responses though I
want to contribute were I can]
2010/1/4 Patrick Schoenfeld :
>> I've noticed in the past that cacti RE-adds the symbolic link
>> conf.d/cacti.conf
>> on every upgrade even if the source file was *manually* removed by the
>> sys
Package: diffutils
Version: 1:2.8.1-18
Severity: serious
Justification: Policy 7.6.1
Hello,
I've added 'unstable' in my sources.list for some *noarch packages and after
the last dist-upgrade the 'diffutils' package was installed due to being
'Essential: yes'. However, I realized that this package
On Thu, Dec 17, 2009 at 5:51 PM, Michael Gilbert
wrote:
> On Thu, 17 Dec 2009 16:13:36 +0200, Teodor wrote:
>> As it can be seen postinstall already has a check for the existence of the
>> config
>> file /etc/cacti/apache.conf. Please add the same check for creating the
>> symlink.
>
> this may
Package: squid
Version: 2.7.STABLE3-1
Followup-For: Bug #505065
I've encountered this problem on both 'etch' and current 'lenny' versions.
This is one reproducable scenario: squid was running just fine and I've
modified this following line by adding 'tproxy'.
http_port 3128 transparent
With t
70 matches
Mail list logo
