Bug#1019447: [Aptitude-devel] Bug#1019447: aptitude: Wrong "Press Return to continue" after succesful installation
Axel,
On Sat, Sep 10, 2022 at 1:42 AM Axel Beckert wrote:
>
> Control: severity -1 wishlist
> Control: tag -1 + confirmed
>
> Hi Aleksey,
>
> Aleksey Midenkov wrote:
> > > Aleksey Midenkov wrote:
> > > > Since some version aptitude started to behave strangely: it asks user
> > > > interaction after each successful installation.
> > >
> > > I thought that the "Press Return to continue" was always there, just
> > > the "'q' followed by Return to quit" has been added as a feature
> > > somewhen 7 or 8 years ago. But now I'm no more sure if that "Press
> > > Return to continue" was really there before.
> >
> > No, it was not always there. I've been using aptitude for 20 years or
> > so.
>
> Me too, after I discovered that its so much better than dselect. (And
> yes, I initially also was just a user. :-)
Right.
>
> (And JFTR: As of now I'm mostly the packager of aptitude, not its
> "upstream" developer, mostly due to lacking C++ experience.)
>
> > When it started to be nagging it really freaked me out, but had no
> > time nor will to fix until now.
>
> I can relate. UI changes can be very annoying for some people while
> other won't even barely notice that something has changed. E.g. UI
> changes is what drove me away from GNOME many years ago. But which
> change actually annoys someone seems to be a very subjective thing.
Agree. I believe the subjectiveness comes from the amount and variety
of UI experience.
>
> > > > So no obvious reason to use 'q' from the above interaction because 'q'
> > > > also works from the UI.
> > >
> > > No, the reason is that you don't have to wait to reload the database
> > > before being able to press "q" again.
> >
> > But it returns to UI first and hence reloads the database, so you have
> > to wait in any case. Haven't you?
>
> I remember that I once mentioned that I used to press just Ctrl-C
> there. And someone of the aptitude developers back then said that's a
> bad habit because aptitude then can't save back some details.
>
> So as far as I understand there is some database saving part happening
> during that time where it goes back to the TUI to properly quit. And
> it is said to be needed to avoid the loss of some package states in
> aptitude's pkgstate database.
>
> > > > I guess the above pause was added to display
> > > > the errors if any happened
> > >
> > > There is no pause in that sense. The time the UI is displayed is AFAIK
> > > needed to properly write down the current state of aptitude's package
> > > list after the package installation.
> >
> > Pause means do nothing and wait for user interaction. The delay caused
> > by UI reload is not the "pause", is it?
>
> Ok, I might have misunderstood which pause you meant. I initially
> thought that you referred to the waiting time while consolidating and
> writing the database back on disk as "pause".
>
> But now I think you refer to aptitude sitting there and waiting for
> the user to press (at least) Enter as "pause". There it is indeed a
> pause.
>
> > > > I hope you will find the below patch well-suited for stopping
> > > > bugging you with that useless pause.
> > > >
> > > > --- b/src/ui.cc 2020-05-21 06:32:38.0 +0300
> > > > +++ b/src/ui.cc 2022-09-09 13:41:49.752101187 +0300
> > > > @@ -1276,7 +1276,7 @@
> > > > pkgPackageManager::OrderResult rval = f(-1);
> > > >
> > > > bool quit_after_dpkg_run = false;
> > > > -if(rval != pkgPackageManager::Incomplete)
> > > > +if(rval != pkgPackageManager::Completed)
> > > >{
> > > > cout << _("Press Return to continue, 'q' followed by Return to
> > > > quit.") << endl;
> > >
> > > Doesn't make sense to me. But maybe I also still haven't understood
> > > what you're actually trying to achieve.
> >
> > Why it doesn't make sense?
>
> For me it doesn't make sense to show the prompt if something (whatever
> it is) is not completed. It is though unclear to me what is the exact
> semantic of Incomplete and Complete in this case.
If you don't understand the semantics then it doesn't make sense for
sure... But in that case this fact doesn't make sense itself.:)
>
> > When error happens it pauses and shows the reply.
>
> I see. And indeed, I actually prefer to always be able to have a look
> at the console output before returning
Bug#1019447: [Aptitude-devel] Bug#1019447: aptitude: Wrong "Press Return to continue" after succesful installation
Hi Axel,
On Fri, Sep 9, 2022 at 8:58 PM Axel Beckert wrote:
>
> Control: tag -1 + moreinfo
>
> Hi Aleksey,
>
> thanks for the bug report.
>
> Aleksey Midenkov wrote:
> > Since some version aptitude started to behave strangely: it asks user
> > interaction after each successful installation.
>
> I thought that the "Press Return to continue" was always there, just
> the "'q' followed by Return to quit" has been added as a feature
> somewhen 7 or 8 years ago. But now I'm no more sure if that "Press
> Return to continue" was really there before.
No, it was not always there. I've been using aptitude for 20 years or
so. When it started to be nagging it really freaked me out, but had no
time nor will to fix until now.
>
> What definitely has been added around that time (in 0.7.3 from October
> 2015) was this "Perfoming actions" line when switching from TUI to
> installation output. (https://bugs.debian.org/323371)
>
> > Press Return to continue, 'q' followed by Return to quit.
> >
> > That is strange because 'q' returns first into the UI and then
> > quits.
>
> This is correct and is intended.
>
> > So no obvious reason to use 'q' from the above interaction because 'q'
> > also works from the UI.
>
> No, the reason is that you don't have to wait to reload the database
> before being able to press "q" again.
But it returns to UI first and hence reloads the database, so you have
to wait in any case. Haven't you?
>
> > I guess the above pause was added to display
> > the errors if any happened
>
> There is no pause in that sense. The time the UI is displayed is AFAIK
> needed to properly write down the current state of aptitude's package
> list after the package installation.
Pause means do nothing and wait for user interaction. The delay caused
by UI reload is not the "pause", is it?
>
> > but the condition in the code for that was chosen wrongly.
>
> The only thing I remember from discussions back then is that querying
> for a "q" keypress without the following "Enter" press was much more
> work than worth it and would have required a rewrite of the whole
> input handling at that point in the workflow.
>
> > I hope you will find the below patch well-suited for stopping
> > bugging you with that useless pause.
> >
> > --- b/src/ui.cc 2020-05-21 06:32:38.0 +0300
> > +++ b/src/ui.cc 2022-09-09 13:41:49.752101187 +0300
> > @@ -1276,7 +1276,7 @@
> > pkgPackageManager::OrderResult rval = f(-1);
> >
> > bool quit_after_dpkg_run = false;
> > -if(rval != pkgPackageManager::Incomplete)
> > +if(rval != pkgPackageManager::Completed)
> >{
> > cout << _("Press Return to continue, 'q' followed by Return to
> > quit.") << endl;
>
> Doesn't make sense to me. But maybe I also still haven't understood
> what you're actually trying to achieve.
Why it doesn't make sense? When error happens it pauses and shows the reply.
>
> What exactly do you expect aptitude to do when the package
> installation/update/removal run ended?
Return to UI without any interaction. Again, that is stupid: when you
run some lengthy installation you go away from display and when you
return back it asks for Enter then it forces you to wait until UI is
reloaded. That interaction didn't help me in any single case.
>
> Regards, Axel
> --
> ,''`. | Axel Beckert , https://people.debian.org/~abe/
> : :' : | Debian Developer, ftp.ch.debian.org Admin
> `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
> `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
@midenok
Bug#1003186:
Also please note #1019447 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019447 -- @midenok
Bug#1019447: aptitude: Wrong "Press Return to continue" after succesful installation
Package: aptitude
Version: 0.8.13-3
Severity: normal
Tags: patch
Since some version aptitude started to behave strangely: it asks user
interaction after each successful installation.
Press Return to continue, 'q' followed by Return to quit.
That is strange because 'q' returns first into the UI and then quits.
So no obvious reason to use 'q' from the above interaction because 'q'
also works from the UI. I guess the above pause was added to display
the errors if any happened but the condition in the code for that was
chosen wrongly. I hope you will find the below patch well-suited for
stopping bugging you with that useless pause.
--- b/src/ui.cc 2020-05-21 06:32:38.0 +0300
+++ b/src/ui.cc 2022-09-09 13:41:49.752101187 +0300
@@ -1276,7 +1276,7 @@
pkgPackageManager::OrderResult rval = f(-1);
bool quit_after_dpkg_run = false;
-if(rval != pkgPackageManager::Incomplete)
+if(rval != pkgPackageManager::Completed)
{
cout << _("Press Return to continue, 'q' followed by Return to
quit.") << endl;
--
@midenok
Bug#927109: lxdm skips pam_env module or pam at all
Package: lxdm
Version: 0.5.3-2.1
Severity: important
Dear Maintainer,
after logging in to lxdm session I try this:
$ cat ~/.pam_environment
SSH_AUTH_SOCK DEFAULT="${XDG_RUNTIME_DIR}/ssh_auth_sock"
FOO OVERRIDE=a
$ echo $FOO
$ echo $SSH_AUTH_SOCK
It seems that pam_env.so module didn't load ~/.pam_environment. My
installed package has bug with missing user_readenv=1 (which is 0 by
default) which I corrected and nothing happened. I added 'debug', but
nothing from pam_env got into /var/log/syslog.
-- System Information:
Debian Release: buster/sid
APT prefers disco
APT policy: (500, 'disco'), (500, 'cosmic-updates'), (500, 'cosmic'), (100,
'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.0-8-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lxdm depends on:
ii debconf [debconf-2.0] 1.5.69
ii gtk2-engines-pixbuf2.24.32-3ubuntu1
ii iso-codes 3.79-1
ii libc6 2.29-0ubuntu1
ii libcairo2 1.15.12-1
ii libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii libglib2.0-0 2.60.0-1
ii libgtk2.0-02.24.32-3ubuntu1
ii libpam-modules 1.1.8-3.6ubuntu2
ii libpam-runtime 1.1.8-3.6ubuntu2
ii libpam0g 1.1.8-3.6ubuntu2
ii libpango-1.0-0 1.42.4-3ubuntu1
ii libpangocairo-1.0-01.42.4-3ubuntu1
ii librsvg2-common2.40.20-3
ii libx11-6 2:1.6.7-1
ii libxcb11.13.1-2
ii lsb-base 9.20170808ubuntu1
ii x11-utils 7.7+4
Versions of packages lxdm recommends:
pn desktop-base
ii lxde-common 0.99.2-3
lxdm suggests no packages.
-- Configuration Files:
/etc/pam.d/lxdm changed:
authrequisite pam_nologin.so
authrequiredpam_env.so debug readenv=1
authrequiredpam_env.so debug readenv=1 envfile=/etc/default/locale
authrequiredpam_env.so debug readenv=1 user_readenv=1
envfile=/etc/lxdm-environment
@include common-auth
authoptionalpam_gnome_keyring.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so close
session required pam_unix.so# added by klaumi
session requiredpam_limits.so
session required pam_loginuid.so# added by klaumi
@include common-session # added by klaumi
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so open
session optionalpam_gnome_keyring.so auto_start
session optionalpam_systemd.so
@include common-password
-- debconf information excluded
Bug#926504: No hibernate option in shutdown menu
Package: policykit-1 Version: 0.105-4 Desktop envs suffer from lack of hibernation option. The workaround for this is cat > /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.handle-hibernate-key;org.freedesktop.login1;org.freedesktop.login1.hibernate-multiple-sessions;org.freedesktop.login1.hibernate-ignore-inhibit ResultActive=yes As described here: http://ubuntuhandbook.org/index.php/2018/05/add-hibernate-option-ubuntu-18-04/ -- All the best, Aleksey Midenkov @midenok
Bug#922694: lxdm: Continuous restart on start failure
Package: lxdm Version: 0.5.3-2.1 Severity: normal Dear Maintainer, if Xorg fails to start, lxdm service endlessly loops in restart attempts. /lib/systemd/system/lxdm.service has a wrong setting for Restart: Restart=always it must be: Restart=on-success -- System Information: Debian Release: buster/sid APT prefers cosmic-updates APT policy: (500, 'cosmic-updates'), (500, 'cosmic-proposed'), (500, 'cosmic'), (500, 'bionic-updates'), (500, 'bionic'), (500, 'artful'), (100, 'bionic-backports') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-34-generic (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxdm depends on: ii debconf [debconf-2.0] 1.5.69 ii gtk2-engines-pixbuf2.24.32-1ubuntu1 ii iso-codes 3.79-1 ii libc6 2.28-0ubuntu1 ii libcairo2 1.15.10-2 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libglib2.0-0 2.58.1-2 ii libgtk2.0-02.24.32-1ubuntu1 ii libpam-modules 1.1.8-3.6ubuntu2 ii libpam-runtime 1.1.8-3.6ubuntu2 ii libpam0g 1.1.8-3.6ubuntu2 ii libpango-1.0-0 1.40.14-1ubuntu0.1 ii libpangocairo-1.0-01.40.14-1ubuntu0.1 ii librsvg2-common2.40.20-2 ii libx11-6 2:1.6.4-3ubuntu0.1 ii libxcb11.13-1 ii lsb-base 9.20170808ubuntu1 ii x11-utils 7.7+3build1 Versions of packages lxdm recommends: pn desktop-base ii lxde-common 0.99.2-3 lxdm suggests no packages. -- debconf information excluded
Bug#708117: hal segmentation fault after upgrade
Package: hal Version: 0.5.14-8 Severity: important After upgrading from 0.5.14-4 I've got hal failing to start with core dump. Sorry, hadn't saved screen output, but this doesn't matter. I've compiled debug version and found the source of core. But this is not the most important issue. More important is, that user have no clue of what to do with such kind of problem. More useful message should be printed, as done in patch. The source of core was broken fdi cache. I don't know, why it got broken, but I've fixed my with: mkdir /etc/hal/fdi/preprobe rm /var/cache/hald/fdi-cache /usr/lib/hal/hald-generate-fdi-cache The behavior of software is very fragile, because it refuses to work in absence of some directories. Maybe this was the source of broken cache... P.S. I know that HAL is deprecated. But this is not the reason for leaving users sinking in a swamp of inaccuracy. Please, forward this patch to upstream if applicable. 70-core-fix.patch Description: Binary data
Bug#693809: libtimedate-perl: wrong offset for MSK timezone
Package: libtimedate-perl Version: 1.2000-1 Severity: important Tags: patch Please, fix Zone.pm for MSK time zone from +3 to +4: msk = +4*3600, # Moscow -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657327: malloc(): memory corruption
Package: libgstreamer0.10-0 Version: 0.10.35.2-1ubuntu1 Severity: important Start subtitleeditor 0.39.0-2 Run Video - Open Open some AVI. Program should abort with something like backtrace below. Downgrade libgstreamer0.10-0 to version 0.10.35-1 and the bug will go off. The backtrace shows the problem in libgstreamermm-0.10.so.2 but nevertheless the bug is in libgstreamer0.10-0. I had another backtrace with libgstreamer0.10-0 in focus, but then downgraded/upgraded some packages. Downgrading exactly libgstreamer0.10-0 helps. I know I'm on Ubuntu, but you guys probably should forward this bug to upstream anyway. Thanks! --- Backtrace --- subtitleeditor The messenger is now down An IOException occurred at scim_bridge_client_imcontext_set_cursor_location () *** glibc detected *** subtitleeditor: malloc(): memory corruption (fast): 0x014d2bb0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7c8f6)[0x7f3627d998f6] /lib/x86_64-linux-gnu/libc.so.6(+0x7eb2c)[0x7f3627d9bb2c] /lib/x86_64-linux-gnu/libc.so.6(__libc_calloc+0xc2)[0x7f3627d9e8f2] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_malloc0+0x21)[0x7f3628ac3631] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_param_spec_pool_list+0x8d)[0x7f3628f883fd] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x12294)[0x7f3628f80294] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2963b)[0x7f3628f9763b] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_class_ref+0x55c)[0x7f3628f9a61c] /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1(_ZN4Glib15ConstructParamsC2ERKNS_5ClassEPKcz+0xb7)[0x7f3629203a77] /usr/lib/libgstreamermm-0.10.so.2(_ZN3Gst8PlayBin2C1ERKN4Glib7ustringE+0x7c)[0x7f362b3e1b6c] /usr/lib/libgstreamermm-0.10.so.2(_ZN3Gst8PlayBin26createERKN4Glib7ustringE+0x31)[0x7f362b3e23f1] subtitleeditor[0x423e8a] subtitleeditor[0x424459] /usr/lib/subtitleeditor/plugins/actions/libvideoplayermanagement.so(_ZN21VideoPlayerManagement7on_openEv+0x65)[0x7f3615bec995] /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1(_ZN4Glib17SignalProxyNormal19slot0_void_callbackEP8_GObjectPv+0x28)[0x7f36292055f8] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x154)[0x7f3628f7d364] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1f8f3)[0x7f3628f8d8f3] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x60b)[0x7f3628f94feb] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f3628f951b2] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x75213)[0x7f362996e213] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x154)[0x7f3628f7d364] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1f9fa)[0x7f3628f8d9fa] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x60b)[0x7f3628f94feb] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f3628f951b2] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_widget_activate+0x6e)[0x7f3629b48dae] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_menu_shell_activate_item+0xfd)[0x7f3629a43f6d] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x14b305)[0x7f3629a44305] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x136c68)[0x7f3629a2fc68] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x154)[0x7f3628f7d364] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1fbfa)[0x7f3628f8dbfa] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x4ed)[0x7f3628f94ecd] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f3628f951b2] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x250bb1)[0x7f3629b49bb1] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_propagate_event+0xc3)[0x7f3629a2de23] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_main_do_event+0x283)[0x7f3629a2e183] /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5bfac)[0x7f362947efac] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x16a)[0x7f3628abd7da] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x47ba0)[0x7f3628abdba0] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7f3628abdf9a] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_main+0xa7)[0x7f3629a2d1b7] /usr/lib/x86_64-linux-gnu/libgtkmm-2.4.so.1(_ZN3Gtk4Main3runERNS_6WindowE+0x106)[0x7f362a8b5326] subtitleeditor[0x415212] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f3627d3e30d] subtitleeditor[0x415ac5] === Memory map: 0040-0044e000 r-xp 08:05 142368 /usr/bin/subtitleeditor 0064d000-0064e000 r--p 0004d000 08:05 142368 /usr/bin/subtitleeditor 0064e000-0065 rw-p 0004e000 08:05 142368 /usr/bin/subtitleeditor 0065-00651000 rw-p 00:00 0 00ba2000-0151b000 rw-p 00:00 0 [heap] 7f360a7fd000-7f360a7fe000 ---p 00:00 0 7f360a7fe000-7f360affe000 rw-p 00:00 0 7f360affe000-7f360afff000 ---p 00:00 0 7f360afff000-7f360b7ff000 rw-p 00:00 0 7f360b7ff000-7f360b80 ---p 00:00 0 7f360b80-7f360c00 rw-p 00:00 0 7f360c00-7f360c022000 rw-p
Bug#549194: kdevelop: crash when stopping debugger
Package: kdevelop Version: 4:3.5.5-1 Severity: important -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.3-std (PREEMPT) Locale: LANG=POSIX, LC_CTYPE=ru_RU.koi8-r (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages kdevelop depends on: hi kdebase-bin 4:3.5.9.dfsg.1-2+b1 core binaries for the KDE base mod hi kdelibs4c2a 4:3.5.9.dfsg.1-2+b1 core libraries and binaries for al ii kdevelop-data4:3.5.5-1 Data files for the KDevelop IDE hi libapr1 1.2.11-1The Apache Portable Runtime Librar hi libc62.9-25 GNU C Library: Shared libraries ii libdb4.7 4.7.25-6Berkeley v4.7 Database Libraries [ hi libgcc1 1:4.4.1-4 GCC support library hi libqt3-mt3:3.3.8b-4 Qt GUI Library (Threaded runtime v hi libstdc++6 4.4.1-4 The GNU Standard C++ Library v3 ii libsvn1 1.5.1dfsg1-1Shared libraries used by Subversio Versions of packages kdevelop recommends: hi autoconf 2.61-4 automatic configure script builder hi automake 1:1.10+nogfdl-1 A tool for generating GNU Standard hi gdb 6.8-3 The GNU Debugger ii kdevelop-doc 4:3.5.4-1 Documentation for the KDevelop IDE hi libtool 1.5.22-4Generic library support script hi make 3.80+3.81.b4-1 The GNU version of the make util -- no debconf information (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb60949e0 (LWP 26454)] [New Thread 0xb41ebb90 (LWP 26478)] [New Thread 0xb4fcfb90 (LWP 26469)] [KCrash handler] #6 0xb776660a in KProcess::writeStdin () from /usr/lib/libkdecore.so.4 #7 0xb44d98f8 in GDBDebugger::GDBController::slotStopDebugger () from /usr/lib/kde3/libkdevdebugger.so #8 0xb44c74b6 in GDBDebugger::DebuggerPart::slotStopDebugger () from /usr/lib/kde3/libkdevdebugger.so #9 0xb44c7963 in GDBDebugger::DebuggerPart::slotStop () from /usr/lib/kde3/libkdevdebugger.so #10 0xb44d4963 in GDBDebugger::DebuggerPart::qt_invoke () from /usr/lib/kde3/libkdevdebugger.so #11 0xb71e700d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #12 0xb71e7b8d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0xb7a004f9 in KAction::activated () from /usr/lib/libkdeui.so.4 #14 0xb7a3f6a2 in KAction::slotActivated () from /usr/lib/libkdeui.so.4 #15 0xb7b2e6d1 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4 #16 0xb71e700d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0xb71e7b8d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #18 0xb7751c99 in KAccelPrivate::menuItemActivated () from /usr/lib/libkdecore.so.4 #19 0xb77a13a7 in KAccelPrivate::emitActivatedSignal () from /usr/lib/libkdecore.so.4 #20 0xb782f738 in KAccelPrivate::eventFilter () from /usr/lib/libkdecore.so.4 #21 0xb71e682c in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #22 0xb71e689b in QObject::event () from /usr/lib/libqt-mt.so.3 #23 0xb721f4dc in QWidget::event () from /usr/lib/libqt-mt.so.3 #24 0xb72d5d42 in QMainWindow::event () from /usr/lib/libqt-mt.so.3 #25 0xb71891ca in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #26 0xb718a252 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #27 0xb7839ec2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #28 0xb77ad470 in KAccelEventHandler::x11Event () from /usr/lib/libkdecore.so.4 #29 0xb783833a in KApplication::x11EventFilter () from /usr/lib/libkdecore.so.4 #30 0xb7117a05 in ?? () from /usr/lib/libqt-mt.so.3 #31 0xbfd2b49c in ?? () #32 0xbfd2b3a8 in ?? () #33 0xb711decb in QETWidget::translateKeyEventInternal () from /usr/lib/libqt-mt.so.3 #34 0xb712715e in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #35 0xb7138026 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #36 0xb719fbc0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #37 0xb719fa56 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #38 0xb7188d3f in QApplication::exec () from /usr/lib/libqt-mt.so.3 #39 0x0804e4ee in ?? () #40 0xbfd2b49c in ?? () #41 0x0809ca18 in ?? () #42 0xbfd2b618 in ?? () #43 0x0001 in ?? () #44 0x08053315 in ?? () #45 0x0001 in ?? () #46 0x08053400 in ?? () #47 0x080533b9 in ?? () #48 0x08052b7c in ?? () #49 0x08052b68 in _IO_stdin_used () #50 0x0001 in ?? () #51 0x033f in ?? () #52 0xb6096240 in ?? () #53 0x08063698 in ?? () #54 0x0804c007 in ?? () #55 0xb78b00a8 in
Bug#546929: Acknowledgement (binutils: unrecognised emulation mode: elf_x86_64)
I just found out that 'gcc -m64' works ok. But this does not cancel the question about validity of aforementioned usage. The topic is worth to be noted to upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546731: Fwd: Re: Bug#546731: dpkg: 1.15.4 version pulls kde for upgrade
On Tuesday 15 September 2009 17:34:18 Raphael Hertzog wrote: On Tue, 15 Sep 2009, Aleksey Midenkov wrote: Guys! Placing some hints on dpkg about packages that may be broken is wrong. Imagine that count of such packages is infinity, so you will be keep putting all them inside dpkg control info? This is an abstraction and the next is reality. You fixed a lot of good bugs but made an requirement of switching from KDE 3 to KDE 4. Not everyone believe that KDE 4 is better and such requirement is somehow clumsy because the reason of it lies in some insignificant (by the comparison with the topic of KDE version switching) busyness with install-info. Please, be fair! If you managed to put konqueror on hold, you can surely do the same for dpkg. Sid evolves, if you don't want use newer software, then don't use sid (hint: KDE4 replaces KDE3 in sid). It doesn't pull anything new, it just forces the upgrade of what's already installed if you have packages that have not been transitionned to the separate install-info package. So, I required to go to KDE 4 from KDE 3 just because of some obscure install-info that dpkg needs? If you use sid yes, you can also decide to not upgrade dpkg or to rebuild a patched dpkg that doesn't have the breaks relationship. Maybe it will be better to make it to live peacefully with old packages? It does live peacefully with old packages, it tells them when a change breaks them so that the user doesn't experience the breakage. That said, the kind of breakage related to install-info is only of the sort my info page is not listed in the index. I agree it's not an important breakage but I don't see a good reason to revert the change. Wow! The good reason is: you make me and other people set dpkg on hold and be deprived from the features and bugfixes in 1.15.4. For who you made efforts then? For yourself? For who you serve? For people like me or for yourself? You suggest me to make work by fiddling with your dpkg, dragging custom version? For who then you make your job in Debian man? If KDE 4 doesn't suit you, you'd better file bugs on it so that it can be usable for you when squeeze gets out. Do you realize that KDE 3 and 4 are whole different products? Did you used them per chance to suggest me to switch to KDE4 or not use sid? By putting metainfo about KDE in dpkg you proven your sillyness. Cheers, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546885: slap_sasl_init: SASL library version mismatch: expected 2.1.23, got 2.1.22
Package: slapd Version: 2.4.17-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.3-std (PREEMPT) Locale: LANG=POSIX, LC_CTYPE=ru_RU.koi8-r (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages slapd depends on: hi adduser 3.80 Add and remove users and groups hi coreutils 7.4-2 The GNU core utilities hi debconf [debconf-2.0] 1.5.26 Debian configuration management sy hi libc6 2.9-25 GNU C Library: Shared libraries ii libdb4.7 4.7.25-6 Berkeley v4.7 Database Libraries [ ii libgnutls26 2.6.4-2the GNU TLS library - runtime libr ii libldap-2.4-2 2.4.17-1 OpenLDAP libraries ii libltdl7 2.2.6a-4 A system independent dlopen wrappe ii libperl5.10 5.10.0-25 Shared Perl library ii libsasl2-22.1.22.dfsg1-8 Authentication abstraction library hi libslp1 1.2.1-5OpenSLP libraries hi libwrap0 7.6.q-15 Wietse Venema's TCP wrappers libra hi perl [libmime-base64-perl 5.10.0-25 Larry Wall's Practical Extraction hi psmisc21.8-1 Utilities that use the proc filesy hi unixodbc 2.2.11-16 ODBC tools libraries Versions of packages slapd recommends: hi libsasl2-modules2.1.19.dfsg1-0.1 Pluggable Authentication Modules f -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546929: binutils: unrecognised emulation mode: elf_x86_64
Package: binutils Version: 2.19.91.20090910-1 Severity: important Another absurd: gcc -march=x86-64 -Xlinker '-m elf_x86_64' foo.c -o foo-64 /usr/bin/ld: unrecognised emulation mode: elf_x86_64 Supported emulations: elf_i386 i386linux elf_x86_64 elf_l1om Have installed: binutils-multiarch 2.19.91.20090910-1 libc6-amd64 2.9-25 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.3-std (PREEMPT) Locale: LANG=POSIX, LC_CTYPE=ru_RU.koi8-r (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash Versions of packages binutils depends on: hi libc6 2.9-25GNU C Library: Shared libraries hi zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime binutils recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546731: dpkg: 1.15.4 version pulls kde for upgrade
Package: dpkg Version: 1.15.4 Severity: normal Dpkg should know nothing about packages that depend on it. Currently it provides a list of packages it 'breaks'. By the way no info neither in description nor in changelog about how it breaks them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546731: Fwd: Re: Bug#546731: dpkg: 1.15.4 version pulls kde for upgrade
Guys! Placing some hints on dpkg about packages that may be broken is wrong. Imagine that count of such packages is infinity, so you will be keep putting all them inside dpkg control info? This is an abstraction and the next is reality. You fixed a lot of good bugs but made an requirement of switching from KDE 3 to KDE 4. Not everyone believe that KDE 4 is better and such requirement is somehow clumsy because the reason of it lies in some insignificant (by the comparison with the topic of KDE version switching) busyness with install-info. Please, be fair! -- Forwarded Message -- Subject: Re: Bug#546731: dpkg: 1.15.4 version pulls kde for upgrade Date: Tuesday 15 September 2009 From: Aleksey Midenkov a...@uezku.kemsu.ru To: Raphael Hertzog hert...@debian.org On Tuesday 15 September 2009 16:13:10 Raphael Hertzog wrote: Hi, On Tue, 15 Sep 2009, Aleksey Midenkov wrote: Dpkg should know nothing about packages that depend on it. Currently it provides a list of packages it 'breaks'. By the way no info neither in description nor in changelog about how it breaks them. What you saw is the expected behaviour, we want to ensure that you have new enough konqueror so that dpkg can drop install-info without breaking anything. It doesn't pull anything new, it just forces the upgrade of what's already installed if you have packages that have not been transitionned to the separate install-info package. So, I required to go to KDE 4 from KDE 3 just because of some obscure install-info that dpkg needs? Maybe it will be better to make it to live peacefully with old packages? Doesn't it will be more delicate? I think, you should reopen and fix. And the changelog said: * Replace install-info by a wrapper around GNU's install-info. The wrapper will be dropped in squeeze+1. dpkg now Breaks: old versions of info-browsers that do not depend on the new install-info package that provides the real functionality. Closes: #9771, #523980 See http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo for details. So closing this bug. Cheers, --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546210: nvidia-glx: please move init.d script to postinst phase
Package: nvidia-glx Version: 185.18.36-2 Severity: wishlist Per-startup setup of library links seems to be absurd. Please move it to postinst phase. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546215: nvidia-glx: warning from modprobe
Package: nvidia-glx Version: 185.18.36-2 Severity: minor WARNING: All config files need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a future release. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#454350: kernel-package: please add support for KBUILD_OUTPUT
On Sunday 09 December 2007 00:44:59 Ivan Shmakov wrote: Tino Keitel tino.keitel+debb...@tikei.de writes: Package: kernel-package Version: 11.001 Severity: wishlist Hi, it will be nice if KBUILD_OUTPUT is supported. That way, one source tree can be used to build kernels for differend computers with different machines without a clean and messing around with config files. Well, I probably may say that I've some ``initial success'' with building in a separate directory. I'd like to mention a couple of issues that I've stumbled upon: * it seems to me that implementing the support for an autoconf-like style of passing the source and build directories location, e. g.: $ make-kpkg --kernel-source=/where/is/the/source would require less time than a kbuild-like one (assuming using the existing code base, of course); certainly, one'd need to prefix a number of filenames with `$(srctree)/', but it would be even worse to prefix almost everything with `$(KBUILD_OUTPUT)/'; * including build-toplevel Makefile has a little sense, since it contains (almost) no variables, nor `include's (in the separate build directory case); moreover, it defines a rule which may interfere with `debian/rules'. [...] Hi, Ivan, Manoj, anyone! The development time does not matter here, because building the package from the working directory of kernel build tree is inappropriate to the concept of kernel building. make-kpkg must be involved from kernel source tree as it were always before. Though there is no problem with prefixing $(KBUILD_OUTPUT)/ as Ivan mentioned. kernel-package should get everything from kernel source directory and then perform switching to a build directory. It should create this directory if it not exists. The actual build invocation should be done back from source tree. Any checks in kernel source should not taint the source tree as it occurs now with kernel_version.mk. The right method of including kernel Makefile is by setting KBUILD_SRC to avoid spawning fork and override rule warning and overriding dot-config to 0. This will give you VERSION, PATCHLEVEL, SUBLEVEL and EXTRAVERSION. KERNELRELEASE and LOCALVERSION should be acquired after oldconfig was invoked. KERNELRELEASE by the same method as original Makefile does, LOCALVERSION by including .config. Performance question: kernel-package should do as less forks as possible. Current implementation includes original Makefile 6(!) times. There is no need to be afraid of names conflict. Though it is possible to do 1 fork and get all 6 variables by using $(eval). .config may always be included without a fork because it has names prefix. The feature of building in a separate tree is really a treasure. I currently did some symbiotic makefile that builds a package from already built tree (without any changes in kernel-package itself). kernel-package is a great at its flexibility of installation but is clumsy on the building side. I suppose, that it may (and should) be separated from the building process at all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#246621: Anybody will fix this?
Hey! What's going on with this bug? Will it be fixed at last? I need to mention, that along with not releasing leases on ifdown it is a good thing to not renew leases on every ifup. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528532: No tapping on ALPS touchpad
On Wednesday 03 June 2009 17:05:40 Mattia Dongili wrote: On Wed, May 13, 2009 at 09:18:48PM +0800, Aleksey Midenkov wrote: Package: xserver-xorg-input-synaptics Version: 1.1.0-1 Severity: important There were numerous attempts to add varius configuration directives to xorg.conf or use information obtained through HAL. Or to modify settings via synclient. It were noticed that FingerHigh setting is completely ignored by synaptics driver. synclient accepts new FingerHigh value without an error but displays always FingerHigh = 0. The same is observed with other high bound settings like RightEdge, BottomEdge. 'synclient -m' works only when I create explicit section in xorg.conf and set SHMConfig on. Then it shows accurately all the values yes, this is documented changing including z-axis. 'synclient -l' shows always the same and likewise FingerHigh change attempt is ignored. if you use shared memory you should set options using synclient -s. I've already investigated, that I should use 'synclient -s -l'. That were confusing all my tries... The bug should be closed, though some problem with X configuration interface (without -s) may still exist. Thank you! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#427804: Hmmm
So much people spend their time by stumbling upon missing bash documents! I were too unpleasantly surprised when it happened on sid and lost half of hour by investigating what is occured. Now losing my time by dragging bash-doc_3.1-1 everywhere by hand, by writing this letter -- that makes another half-hour. So whole hour on this non-sense!!! Everyone losing their time! It is just so stupid!!! Return back info pages by any means! Quickly! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525828: Fails to install with xinetd
Package: proftpd-basic Version: 1.3.2-3 Severity: important /var/lib/dpkg/info/proftpd-basic.postinst fails with return status 20 The following trace from this postinst script is observed. 'itox' is utility which converts inetd.conf to xinetd.conf. + [ -f /etc/inetd.conf -a 0 -eq 0 ] + update-inetd --group STANDARD --add ftp stream tcp nowait root /usr/sbin/tcpd /usr/sbin/proftpd - IMPORTANT INFORMATION FOR XINETD USERS -- The following line will be added to your /etc/inetd.conf file: ftp stream tcp nowait root/usr/sbin/tcpd /usr/sbin/proftpd If you are indeed using xinetd, you will have to convert the above into /etc/xinetd.conf format, and add it manually. See /usr/share/doc/xinetd/README.Debian for more information. You must use option -daemon_dir if you use tcpd --- + db_get shared/proftpd/inetd_or_standalone + _db_cmd GET shared/proftpd/inetd_or_standalone + IFS= printf %s\n GET shared/proftpd/inetd_or_standalone + IFS= read -r _db_internal_line + RET=20 Unsupported command suggested (full line was Suggested entry (automatically converted using itox):) received from confmodule. + return 20 dpkg: error processing proftpd-basic (--configure): subprocess post-installation script returned error exit status 20 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25.10 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages proftpd-basic depends on: hi adduser 3.105 add and remove users and groups hi debconf 1.5.19 Debian configuration management sy hi debianutils 2.30 Miscellaneous utilities specific t hi libacl1 2.2.45-1 Access control list shared library hi libattr1 1:2.4.41-1 Extended attribute shared library hi libc6 2.9-7 GNU C Library: Shared libraries ii libcap2 1:2.16-5 support for getting/setting POSIX. hi libncurses5 5.6+20080203-1 Shared libraries for terminal hand hi libpam-runtime0.99.7.1-5 Runtime support for the PAM librar hi libpam0g 0.99.7.1-5 Pluggable Authentication Modules l hi libssl0.9.8 0.9.8g-7 SSL shared libraries hi libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra hi netbase 4.30 Basic TCP/IP networking system hi sed 4.1.5-5The GNU sed stream editor hi ucf 3.005 Update Configuration File: preserv hi xinetd [inet-superserver] 1:2.3.14-7 replacement for inetd with many en proftpd-basic recommends no packages. -- debconf information: * shared/proftpd/inetd_or_standalone: from inetd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487589: hibernate: tuxonice does not resume from initrd image
Package: hibernate Version: 1.99-1 Severity: important Tags: patch Well known problem described in http://wiki.tuxonice.net/DistroAndHardwareSetup/DebianInitrd All suggested solutions are not correct with the latest initramfs-tools 0.92b and tuxonice 3.0-rc7. The solution is as simple as this: script_dir=/etc/initramfs-tools/scripts/local-top script_file=$script_dir/000tuxonice cat 'EOF' $script_file #!/bin/sh TUXONICE_DIR=/sys/power/tuxonice [ -d $TUXONICE_DIR ] echo $TUXONICE_DIR/do_resume EOF chmod +x $script_file # this should be done in postinst: update-initramfs -u I suppose 000tuxonice shoud be installed by this package (and not by initramfs-tools eg.) because tuxonice is supposed to be used from hibernate scripts. I do not see any other ways to use it. Aleks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483671: libevent-dev: 1.4.4 available upstream
Package: libevent-dev Version: 1.3e-3 Severity: important 1.3e-3 is kind of too old (2007-09-24). There is 1.4.4 (2008-05-13). Please, consider releasing it. Thank you. http://www.monkey.org/~provos/libevent-1.4.4-stable.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483374: libaudio-dev: should have dependency in libaudio2 version (like = 1.9.1-1)
Package: libaudio-dev Version: 1.9.1-2 Severity: minor I had 1.7 version of libaudio installed and could not compile a program due to link errors like 'undefined reference to `XauDisposeAuth''. After upgrading libaudio2 compilation gone successfully. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477778: kernel-package: add ability to build upgraded kernel version and different package flavors
Package: kernel-package Version: 11.001-0.1 Severity: wishlist Currently debian/control file get built from debian/Control template once on debian/ tree creation. For ability to switch to new upstream version saving current debian/ tree there should be possibility to regenerate debian/control file. It is handy that several kernel configurations to exist in one tree. They should reflect kernel flavours and be selected by --flavour option which should imply --append-to-version option. In this case several debian/control, debian/changelog and .config files should coexist suffixed with flavor name. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475036: Wanted features
According to your plans of redesign please consider #48 as features. Always lacking them since have started using make-kpkg 8 years ago. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474115: aptitude: Got SIGABRT, dying..
On Thursday 10 April 2008 06:10:53 you wrote: To follow up to my last comment, about not knowing why the Section field was empty, it appears that I was confused about the earlier report. I had gotten the impression that the Section field wasn't empty in the package list file, but that's not true: /var/lib/apt/lists/local/_var_local_mirror_..._Packages contains this stanza: Package: gsfonts-other Section: Installed-Size: 1728 (...) This seems to be from deb file:/var/local/mirror/debian/ unknown main contrib non-free in sources-local.list. So in fact apt is not buggy in this case; the Packages file is just unusual and hitting a bad corner case of aptitude's grouping code. (in case you're curious, it looks like the ldso stanza also has an empty Section) This should work in the next upload of aptitude. Thanks for the report. Daniel I mistook the source of this stanza with ftp.debian.de non-free source which also contains gsfonts-other. Sorry for misinformation and thank you for help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474115: aptitude: Got SIGABRT, dying..
On Monday 07 April 2008 20:21:20 you wrote: On Thu, Apr 03, 2008 at 05:06:50PM +0400, Aleksey Midenkov [EMAIL PROTECTED] was heard to say: Package: aptitude Version: 0.4.11.1-1 Severity: grave The program get terminated at very start. I don't think it's grave for aptitude to break when its database is corrupt, so I'm downgrading this. Daniel Neather database nor package cache rebuild does not help. The bug is not only in reading empty Section: field, as I tried to describe. The bug is in losing Section: field. Please, answer to the point. You seem to be the are author of the program. Changing status of the bug back to grave: there is no way to use a program. Aleksey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474115: aptitude: Got SIGABRT, dying..
Have posted aptitude-create-state-bundle output: http://midenkov.narod.ru/aptitude_state.bz2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474115: aptitude: Got SIGABRT, dying..
Package: aptitude
Version: 0.4.11.1-1
Severity: grave
The program get terminated at very start.
The exception std::out_of_range is thrown at pkg_grouppolicy.cc:325
(pkg_grouppolicy_section::add_package):
323section = (sections_remaining.at(0) == '/'
324 ? sections_remaining.substr(1, next_split)
325 : sections_remaining.substr(0, next_split));
due to sections_remaining string emptiness. The string get empty from very
start at 272:
270else
271 {
272section=pkg.VersionList().Section();
273
274// Find the first section divider ('/'); if the split mode is
275// supposed to include only the part of the section preceding it
This is not the first iteration so the pkg (pkgCache) is initialized partly
properly. The problem gets occured when pkg.Name() is gsfonts-other. I
looked into apt list and ascertained that the Section: field is not null for
gsfonts-other (non-free/text). I suspect, that /var/cache/pkgcache.bin get
build somehow wrongly. But to figure where in the code it get build is long
enough task for me. Is there anyone who knows the code enough to give me a
clue where to dig next?
By the way, at 273 the check should be done, that std::string 'section' is not
empty.
Package: apt
Version: 0.7.11
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453856: acpi-support: ipw3945 does not boot properly due to wrong isAnyWirelessPoweredOn
As it was said in 463719, device/power/state is deprecated.
I have no such file on 2.6.24. I use following code for
isAnyWirelessPoweredOn:
isAnyWirelessUp()
{
for DEVICE in /sys/class/net/* ; do
[ -d $DEVICE/wireless ] || continue
[ `cat $DEVICE/operstate` != down ] || continue
[ -r $DEVICE/device/rf_kill ] [ `cat $DEVICE/device/rf_kill` -eq
0 ] || continue
return 0
done
# otherwise return failure
return 1
}
By the way, there is no need in 60-asus-wireless-led.sh at startup for
ipw3945.
The driver sets led state properly. I use this tricky led setting only after
resume from suspend
to ram, because then the led sometimes is not resumed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465283: apache2: ProxySourceAddress directive to select source address of outgoing connections from mod_proxy
Hello Stefan, On Tuesday 19 February 2008 23:27:27 Stefan Fritsch wrote: Hi Aleksey, On Monday 11 February 2008, Aleksey Midenkov wrote: This patch allows to bind to source address of outgoing connections from mod_proxy like this: ProxySourceAddress 192.168.0.1 thanks for your patch. However we try to avoid adding new features (and especially new config options) before upstream adds them. Otherwise, if upstream chooses a different implementation, there might be problems with upgrades. that is wise indeed. Will try to negotiate it on upstream. Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420095: sim: 0.9.4.3 is available
It seems to be that deb package is well maintained by upstream developer and is available at: http://sim-im.org/wiki/Download I think the bug priority should be important, because 0.9.4.3 is a bugfix release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438426: Bug#456007: xserver-xorg-video-intel: solution on resume after suspend to ram
On Tuesday 12 February 2008 21:28:03 Filippo Giunchedi wrote: On Tue, Feb 12, 2008 at 06:48:35PM +0100, Filippo Giunchedi wrote: On Fri, Dec 28, 2007 at 10:37:10AM +0300, Aleksey Midenkov wrote: I have 965GM and in my situation none of suggested workarounds work apart from turning to text mode and back to xorg. It must be noted that text mode is broken after resume. But there is a good news that upstream developers have implemented suspend/resume code in i915 DRM module whish can be downloaded from git repository: $ git-clone git://anongit.freedesktop.org/git/mesa/drm I've tested it, works great on 2.6.23.12! Restores graphic and text modes like a charm! You mean the backlight is turned on after resume both in X and console? Is there any particular setting I should check? I am using 2.6.24-rc7 Confirmed, the backlight is restored on resume with today's mesa/drm git (d63b57749f097b36df04c6beff9b35a1dd859523) Brice: what to do about this bug? For me it is closed, as it shows it is not a intel Xorg driver issue. Ideally, a new package should be created kernel-patch-2.6-drm and this package should suggest it. But I would not close this bug to keep helping people find the solution. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Computer Science is no more about computers than astronomy is about telescopes. -- Edsger Dijkstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465283: apache2: ProxySourceAddress directive to select source address of outgoing connections from mod_proxy
Package: apache2 Version: 2.2.8-1 Severity: wishlist Tags: patch This patch allows to bind to source address of outgoing connections from mod_proxy like this: ProxySourceAddress 192.168.0.1 PR#29404 in apache bugzilla. Aleksey 060_proxy_source_address.dpatch Description: application/shellscript
Bug#461867: spamassassin: spamd.pid should be placed to /var/run/spamd/
Package: spamassassin Version: 3.2.3-1 Severity: minor Apart from .pid file there can be UNIX socket. I think this is Debian-way. Having a lot of directories in /var/run already... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456007: xserver-xorg-video-intel: solution on resume after suspend to ram
I have 965GM and in my situation none of suggested workarounds work apart from turning to text mode and back to xorg. It must be noted that text mode is broken after resume. But there is a good news that upstream developers have implemented suspend/resume code in i915 DRM module whish can be downloaded from git repository: $ git-clone git://anongit.freedesktop.org/git/mesa/drm I've tested it, works great on 2.6.23.12! Restores graphic and text modes like a charm! The mailing thread about this issue can be found at: http://marc.info/?t=11927416254r=1w=2 ([RFC] full suspend/resume support for i915 DRM driver) Aleksey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#456215: kwin-baghira: where is the documentation?
Package: kwin-baghira Version: 0.8-1 Severity: minor Man page says: Complete documentation can be found in docbook format in /usr/share/doc/kde/HTML/lang/kwin-baghira/ on this system. There is no docs. $ dpkg -L kwin-baghira|grep HTML|wc -l 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454557: libc6: before upgrade must uninstall libc6-i686 first
Package: libc6 Version: 2.7-3 Severity: grave The situation I got into was in process of upgrading libc6 and libc6-i686 from version 2.6.1-5 to 2.7-3. New libc6 was already unpacked and libc6-i686 was yet of old version. After that the system became totally unusable. Every exec ended up with sigsegv. Only removing /lib/i686 under another system's boot had helped. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454557: libc6: before upgrade must uninstall libc6-i686 first
On Thursday 06 December 2007 13:42:42 you wrote: Aleksey Midenkov a écrit : Package: libc6 Version: 2.7-3 Severity: grave The situation I got into was in process of upgrading libc6 and libc6-i686 from version 2.6.1-5 to 2.7-3. New libc6 was already unpacked and libc6-i686 was yet of old version. After that the system became totally unusable. Every exec ended up with sigsegv. Only removing /lib/i686 under another system's boot had helped. This is most probably a bug of debian-installer, dpkg or apt. Could you please answer the few questions below to help us understand the problem: - What's the output of dpkg -l libc6-i686? - Do you have a /usr/share/doc/libc6-i686 directory? If yes what is the first entry at the top of /usr/share/doc/libc6-i686/changelog.Debian.gz? - Do you have any mentions of libc6-i686 in /var/log/dpkg.log.*? - When did you installed your system and which install CD did you use? Now I have libc6-i686 of version 2.7-3 installed, because I resumed installation process after removing old /lib/i686 binaries. Anyway, I could not show you 'dpkg -l' in that situation. I was using aptitude for the whole upgrade process. The installation log shows this: log# cat dpkg.log|egrep 'libc6(-i686)? ' 2007-12-06 10:35:58 upgrade libc6 2.6.1-5 2.7-3 2007-12-06 10:35:58 status half-configured libc6 2.6.1-5 2007-12-06 10:35:58 status unpacked libc6 2.6.1-5 2007-12-06 10:35:58 status half-installed libc6 2.6.1-5 2007-12-06 10:36:01 status half-installed libc6 2.6.1-5 2007-12-06 10:36:01 status unpacked libc6 2.7-3 2007-12-06 10:36:01 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status unpacked libc6 2.7-3 2007-12-06 10:36:03 status half-configured libc6 2.7-3 2007-12-06 10:48:23 status half-configured libc6 2.7-3 2007-12-06 10:48:38 status installed libc6 2.7-3 2007-12-06 10:48:55 upgrade libc6-i686 2.6.1-5 2.7-3 2007-12-06 10:48:55 status half-configured libc6-i686 2.6.1-5 2007-12-06 10:48:55 status unpacked libc6-i686 2.6.1-5 2007-12-06 10:48:55 status half-installed libc6-i686 2.6.1-5 2007-12-06 10:48:56 status half-installed libc6-i686 2.6.1-5 2007-12-06 10:48:56 status unpacked libc6-i686 2.7-3 2007-12-06 10:48:56 status unpacked libc6-i686 2.7-3 2007-12-06 10:49:14 status unpacked libc6-i686 2.7-3 2007-12-06 10:49:14 status half-configured libc6-i686 2.7-3 2007-12-06 10:49:15 status installed libc6-i686 2.7-3 Between 10:36 and 10:48 the problem had occured, reboot was made into another system and /lib/i686 removed. log# aptitude --version aptitude 0.4.8 compiled at Nov 15 2007 22:41:47 Compiler: g++ 4.2.3 20071014 (prerelease) (Debian 4.2.2-3) NCurses version: 5.6 libsigc++ version: 2.0.17 log# apt-get --version apt 0.7.9 for i386 compiled on Oct 31 2007 13:40:43 Supported modules: *Ver: Standard .deb *Pkg: Debian dpkg interface (Priority 30) S.L: 'deb' Standard Debian binary tree S.L: 'deb-src' Standard Debian source tree Idx: Debian Source Index Idx: Debian Package Index Idx: Debian Translation Index Idx: Debian dpkg status file log# dpkg --version Debian `dpkg' package management program version 1.14.6 (i386). This is free software; see the GNU General Public License version 2 or later for copying conditions. There is NO warranty. See dpkg --license for copyright and license details.
Bug#434503: nut: /etc/default/nut can not set starting arguments
Package: nut Version: 2.0.5-3+b1 Severity: minor Tags: patch Please, consider attached init.d script. nut Description: application/shellscript
Bug#431777: comments have unfounded offendings
Package: info2man Version: 1.1-3 Severity: minor Please, remove the whole paragraphs of comments from info2pod about 'stupid info' and 'the GNU people are arrogant scum'. It does not carry any sense, but is a stupid rave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427949: kdevelop: GDB cmd prompt (integrated debugger) loses focus after entering a command
Package: kdevelop Version: 4:3.4.0-3 Severity: minor Tags: patch Originally reported to upstream by Christopher Layne (http://bugs.kde.org/show_bug.cgi?id=141320), but not fixed since 2007-02-07. Please, incorporate this patch. It is very annoying bug. Regards, Aleksey --- kdevelop-3.4.0-orig/languages/cpp/debugger/gdboutputwidget.cpp 2007-06-07 18:30:58.0 +0400 +++ kdevelop-3.4.0/languages/cpp/debugger/gdboutputwidget.cpp 2007-03-06 15:33:36.0 +0300 @@ -242,6 +242,7 @@ void GDBOutputWidget::flushPending() m_gdbView-scrollToBottom(); m_gdbView-setUpdatesEnabled(true); m_gdbView-update(); +m_userGDBCmdEditor-setFocus(); } /***/
Bug#424536: apache2.2-common: modules configurations should be carried from apache2.conf into corresponding mods-available/ .conf files
Package: apache2.2-common Version: 2.2.3-3.3 Severity: minor Good day! Subj. Modules configuration make apache2.conf unnecessary huge. The modules I say about are: alias_module mod_autoindex mod_mime mod_negotiation mod_setenvif mod_status mod_info Each of them should have its own .conf file in mods-available/. Thank you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416469: uncrustify: upstream version is 3 more newer than unstable
Package: uncrustify Version: 0.30-1 Severity: minor Please, update the unstable to 0.33. http://uncrustify.sourceforge.net/ChangeLog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415565: astyle: -l switch breaks code (kdevelop is affected too)
Package: astyle
Version: 1.18-1
Severity: important
tmp$ cp /dev/stdin a.cpp
{
//
}
tmp$ astyle -l a.cpp
Artistic Style 1.18
formatted a.cpp
tmp$ cat a.cpp
{
//}
tmp$
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396162: /etc/init.d/apache2 still has wrong logic in PID detection
Package: apache2-common
Version: 2.2.3-2
Severity: important
Tags: patch
In /etc/init.d/apache2 (my comments are after # sign):
pidof_apache() {
...
# This loop returns from procedure with first PID it encounters in
# existing .pid file no matter PidFile is from the right source or not.
# So what if the .pid file is stalled and PidFile source is wrong?
for PFILE in `grep ^PidFile /etc/apache2/* -r | awk '{print $2}'`; do
if [ -e $PFILE ]; then
cat $PFILE
return 0
fi
done
...
for i in $PIDS; do
# $PID is always empty string, it was never used before. This matter
with
# useless REALPID initialization make impression that the file was
published
# in the middle of development process ;)
if [ $i = $PID ]; then
My patch fixes these issues trying to follow the orginal thought. Though
again, it is not the most proper (but rather fastest) way to do the thing. ;)
--- apache2.orig 2006-10-08 12:38:25.0 +0800
+++ apache2 2006-10-30 11:53:50.0 +0700
@@ -36,29 +36,32 @@ pidof_apache() {
# classified as good/unknown feature
PIDS=`pidof apache2` || true
-PID=
-
# let's try to find the pid file
-# apache2 allows more than PidFile entry in the config but only
-# the last found in the config is used
+# apache2 allows more than PidFile entry
+# most simple way is to check all of them
+
+PIDS2=
+
for PFILE in `grep ^PidFile /etc/apache2/* -r | awk '{print $2}'`; do
- if [ -e $PFILE ]; then
-cat $PFILE
-return 0
- fi
+ [ -e $PFILE ] PIDS2=$PIDS2 `cat $PFILE`
done
-REALPID=0
+
# if there is a pid we need to verify that belongs to apache2
# for real
for i in $PIDS; do
-if [ $i = $PID ]; then
+ # may be it is not the right way to make second dimension
+ # for really huge setups with hundreds of apache processes
+ # and tons of garbage in /etc/apache2... or is it?
+ for j in $PIDS2; do
+ if [ $i = $j ]; then
# in this case the pid stored in the
# pidfile matches one of the pidof apache
# so a simple kill will make it
-echo $PID
+ echo $i
return 0
fi
done
+done
return 1
}
Bug#390517: bricolage-cms does not start without libhtml-template-expr-perl
Package: libbric-perl Severity: serious Version: 1.8.9-1 bash_shell# /etc/init.d/bricolage-cms start bric_apachectl start: starting httpd Syntax error on line 81 of /etc/bricolage/httpd.conf: Can't locate HTML/Template/Expr.pm in @INC ... Package libhtml-template-expr-perl should be on Depends list, not on Suggests list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305642: OK, it fixed the problem
Pavel, export HISTCONTROL=ignoreboth did fixed the problem. It would be good if it were a comment on this in bash package. Thank you for the info! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305642: I agree, it is very annoying!
I just enter in the directory in MC panel, for example /usr/src. Then ^O, ^P. I get: 05:52:53 [EMAIL PROTECTED]:usr# 05:53:01 [EMAIL PROTECTED]:src# cd `echo -e '\057usr\057src'` Note the old bash prompt. It have not disappeared. The new bash prompt have appeared right after it. My bash prompt format is: export PS1='\T [EMAIL PROTECTED]:\W\$ ' 05:56:53 [EMAIL PROTECTED]:src# mc --version GNU Midnight Commander 4.6.1 Virtual File System: tarfs, extfs, cpiofs, ftpfs, fish, smbfs With builtin Editor Using system-installed S-Lang library with terminfo database With subshell support as default With support for background operations With mouse support on xterm and Linux console With support for X11 events With internationalization support With multiple codepages support Package: libglib2.0-0 Version: 2.10.2-1 Package: libc6 Version: 2.3.6.ds1-4 Package: libgpmg1 Version: 1.19.6-22 Package: libslang2 Version: 2.0.6-2 05:56:58 [EMAIL PROTECTED]:src# ldd `which mc` linux-gate.so.1 = (0xe000) libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0xb7f8b000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7f87000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0xb7eff000) libgpm.so.1 = /usr/lib/libgpm.so.1 (0xb7ef9000) libslang.so.2 = /lib/libslang.so.2 (0xb7e37000) libnsl.so.1 = /lib/tls/libnsl.so.1 (0xb7e21000) libc.so.6 = /lib/tls/libc.so.6 (0xb7ce9000) /lib/ld-linux.so.2 (0xb7fa2000) libm.so.6 = /lib/tls/libm.so.6 (0xb7cc3000) Note that linux-gate.so.1 doesn't map to any file. Is it normal? On Tuesday 05 September 2006 06:31, you wrote: Weired, since I am using MC all the day, I can not reproduce this bug I use MC from Sarge: GNU Midnight Commander 4.6.1-pre3 Virtual File System: tarfs, extfs, cpiofs, ftpfs, fish, smbfs With builtin Editor Using included S-Lang library with terminfo database With subshell support as default With support for background operations With mouse support on xterm and Linux console With support for X11 events With internationalization support With multiple codepages support What do you do exactly to get this Bug? Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant Am 2006-09-01 09:57:01, schrieb Aleksey Midenkov: Package: mc Version: 1:4.6.1-1 Severity: normal I agree, it is very annoying for me too! I didn't seem to notice this bug before. May be it appeared in recent versions. Or is it may be misconfiguration? - END OF REPLIED MESSAGE - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305642: I agree, it is very annoying!
Package: mc Version: 1:4.6.1-1 Severity: normal I agree, it is very annoying for me too! I didn't seem to notice this bug before. May be it appeared in recent versions. Or is it may be misconfiguration? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381092: Authentication does not work in certain circumstances
Package: gnugk
Version: 2.2.3-2-3
Severity: important
Tags: patch
The bug shows up when both MD5 CryptoToken and CAT Token have arrived and the
CAT Token is wrong. In this case MD5 CryptoToken turns out to be failed even
if it is right. This situation was encountered with Teles iGate hardware
which by some means makes bad Cisco Access Token hash (or maybe gnugk makes
bad CAT hash). Now it works OK.
The fix is contained in attachment:
--- gnugk-2.2.3-2/gkauth.h 2005-02-01 15:28:10.0 +0100
+++ gnugk-2.2.3-2-mod/gkauth.h 2006-07-31 17:15:10.0 +0200
@@ -632,18 +632,13 @@ protected:
{
const RAS req = request;
bool finalResult = false;
- int result;
if (req.HasOptionalField(RAS::e_cryptoTokens)) {
- if ((result = CheckCryptoTokens(req.m_cryptoTokens, aliases,
- request-m_rasPDU)) == e_fail)
-return e_fail;
- finalResult = (result == e_ok);
+ finalResult = (CheckCryptoTokens(req.m_cryptoTokens, aliases,
+ request-m_rasPDU) == e_ok);
}
if (req.HasOptionalField(RAS::e_tokens)) {
- if ((result = CheckTokens(req.m_tokens, aliases)) == e_fail)
-return e_fail;
- finalResult = finalResult || (result == e_ok);
+ finalResult = finalResult || (CheckTokens(req.m_tokens, aliases) == e_ok);
}
return finalResult ? e_ok : GetDefaultStatus();
}
Bug#366378: KDE is not starting on /etc/default/rcS VERBOSE=no (with fix)
Package: x11-common
Version: 1:7.0.15
.xsession-errors contains:
_IceTransmkdir: ERROR: Owner of /tmp/.ICE-unix must be set to root
/etc/init.d/x11-common is not creating /tmp/.ICE-unix when VERBOSE=no
in /etc/default/rcS
Suggested fix in attached patch file:
--- /etc/init.d/x11-common.old 2006-04-28 12:18:58.0 +0800
+++ /etc/init.d/x11-common 2006-05-08 13:51:21.0 +0800
@@ -28,7 +28,7 @@ set_up_socket_dir () {
chown 0:0 $SOCKET_DIR
chmod 1777 $SOCKET_DIR
do_restorecon $SOCKET_DIR
- [ $VERBOSE != no ] log_end_msg 0 || exit 0
+ [ $VERBOSE != no ] log_end_msg 0 || return 0
}
set_up_ice_dir () {
@@ -42,7 +42,7 @@ set_up_ice_dir () {
chown 0:0 $ICE_DIR
chmod 1777 $ICE_DIR
do_restorecon $ICE_DIR
- [ $VERBOSE != no ] log_end_msg 0 || exit 0
+ [ $VERBOSE != no ] log_end_msg 0 || return 0
}
case $1 in
