Bug#1021685: upgrading from 40.1-1 to 43.0-2 breaks xfce

[Brent S. Elmer Ph.D.]

Is this bug going to be looked into?  This is still a problem
preventing me from upgrading the package.  If there is additional
information that could be collected let me know the steps to collect
the information.

Brent

On Wed, 12 Oct 2022 17:33:53 -0500 "Brent S. Elmer" 
wrote:
> Package: libwnck3
> Version: libwnck-3-0
> Severity: normal
> X-Debbugs-Cc: webe...@aim.com
> 
> When I upgrade from 40.1-1 to 43.0-2 on a debian testing system, xfce
breaks.
> I see no xfce items at all on the screen(i.e. top bar, application
menu, bottom
> bar, desktop icons)
> I am accessing the machine through x2go.  I am not near the machine
to see if
> xfce works directly on the machine.  When I downgrade to 40.1-1 then
xfce works
> again.
> 
> I see these lines over and over in syslog.
> 
> Oct 12 16:58:49 mj04lv70 x2gogetstatus: db_getstatus called, session
ID:
> bselme-50-1665611527_stDXFCE_dp32, return value: R
> Oct 12 16:58:51 mj04lv70 x2gocleansessions: executing external
command
> ,,/usr/lib/x2go/x2golistsessions_sql'' with args: mj04lv70.ds.xxx.com
> Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external
command
> ,,x2gopath'' with args: libexec
> Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external
command
> ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
> listsessionsroot,mj04lv70.ds.xxx.com
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> 

Bug#860317: upgrade to latest stretch version breaks

[Brent S. Elmer Ph.D.]

On Thu, 2017-04-20 at 17:20 +0200, Andreas Metzler wrote:
> 
> 
> 
> Ok, suspicion confirmed. Run dpkg-reconfigure exim4-config and drop
> ::1
> from the listening interfaces.
> 
> cu Andreas

Yes, that fixed it.

Thanks

Bug#860317: upgrade to latest stretch version breaks

[Brent S. Elmer Ph.D.]

On Wed, 2017-04-19 at 18:45 +0200, Andreas Metzler wrote:
> On 2017-04-17 "Brent S. Elmer Ph.D." <webe...@aim.com> wrote:
> [...]
> > paniclog and mainlog contains this:
> > 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
> > supported by protocol
> 
> This looks like 610918, i.e. having changed Debian's default default
> setup to disable IPv6 without adapting exim4 configuration
> accordingly.
> 
> Are you able to manually start a daemon instance?
> update-exim4.conf && exim4 -bd -d
> 
> cu Andreas

No, here is the output.

# update-exim4.conf && exim4 -bd -d
Exim version 4.89 uid=0 gid=0 pid=3468 D=fbb95cfd
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM
DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm
dbmjz dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Compiler: GCC [6.3.0 20170221]
Library version: Glibc: Compile: 2.24
Runtime: 2.24
Library version: GnuTLS: Compile: 3.5.8
 Runtime: 3.5.8
Library version: PCRE: Compile: 8.39
   Runtime: 8.39 2016-06-14
Total 13 lookups
WHITELIST_D_MACROS: "OUTGOING"
TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs"
changed uid/gid: forcing real = effective
  uid=0 gid=0 pid=3468
  auxiliary group list: 
seeking password data for user "uucp": cache not available
getpwnam() succeeded uid=10 gid=10
configuration file is /var/lib/exim4/config.autogenerated
log selectors = cffc 0e320202
cwd=/home/brente 3 args: exim4 -bd -d
trusted user
admin user
seeking password data for user "mail": cache not available
getpwnam() succeeded uid=8 gid=8
DSN: hubbed_hosts propagating DSN
DSN: nonlocal propagating DSN
DSN: real_local propagating DSN
DSN: system_aliases propagating DSN
DSN: userforward propagating DSN
DSN: procmail propagating DSN
DSN: maildrop propagating DSN
DSN: lowuid_aliases propagating DSN
DSN: local_user propagating DSN
DSN: mail4root propagating DSN
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
 3468 listening on 127.0.0.1 port 25
 3468 LOG: MAIN
 3468   IPv6 socket creation failed: Address family not supported by
protocol
 3468 LOG: PANIC DIE
 3468   IPv6 socket creation failed: Address family not supported by
protocol
 3468 search_tidyup called
 3468 >>>>>>>>>>>>>>>> Exim pid=3468 terminating with rc=1
>>>>>>>>>>>>>>>>

Bug#860317: upgrade to latest stretch version breaks

[Brent S. Elmer Ph.D.]

On Tue, 2017-04-18 at 18:50 +0200, Andreas Metzler wrote:
> On 2017-04-17 "Brent S. Elmer Ph.D." <webe...@aim.com> wrote:
> > On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote:
> > > On 2017-04-14 "Brent S. Elmer" <webe...@aim.com> wrote:
> 
> [...]
> > > > Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail
> > > > Transport Agent...
> > > > Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
> > > > Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
> > > > /var/log/exim4/pa…oken
> > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
> > > > /run/exim4/exim.…tory
> > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never
> > > > wrote its
> > > > PI…ing.
> > > > Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim
> > > > Mail
> > > > Transport…ent.
> 
> Hello,
> 
> you have set
> QUEUERUNNER='nodaemon'
> in /etc/default/exim4, haven't you?
> 
> cu Andreas

No, it is 'combined'.  I don't think I have ever done anything to
change it.

Bug#860317: upgrade to latest stretch version breaks

[Brent S. Elmer Ph.D.]

On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote:
> On 2017-04-14 "Brent S. Elmer"  wrote:
> > Package: exim4
> > Version: 4.89-1
> > Severity: normal
> > I upgraded packages in stretch and there was a problem upgrading
> > exim4.  When I
> > try to do a reinstall of exim4 to try to fix it using synaptic, I
> > get:
> 
> [...]
> > Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail
> > Transport Agent...
> > Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
> > Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
> > /var/log/exim4/pa…oken
> > Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
> > /run/exim4/exim.…tory
> > Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never
> > wrote its
> > PI…ing.
> > Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
> > Transport…ent.
> 
> Anything in the exim logfiles?
> 
> cu Andreas
> 

paniclog and mainlog contains this:

2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
supported by protocol

Bug#851321: Found the problem

[Brent S. Elmer Ph.D.]

I found the problem.  I had LD_LIBRARY_PATH set and it was picking up
some libkrb5* libraries from there.  After I removed that directory
from LD_LIBRARY_PATH, import cv2 worked fine.

Bug#845216: fails to upgrade/install

[Brent S. Elmer Ph.D.]

On Mon, 2016-11-21 at 14:51 -0500, Peter S Galbraith wrote:
> > 

> Hi,
> 
> A log file is generated that would show the exact error.  Can you
> include it please?
> 
> 
> This file... /tmp/elc_xITXzf.log
> 

Here it is.emacs23 -batch --no-site-file --multibyte --eval (setq load-path (cons "." load-path)) -l autoload --eval (setq generated-autoload-file (expand-file-name "emacs-goodies-loaddefs.el")) --eval (setq make-backup-files nil) -f batch-update-autoloads .
Generating autoloads for align-string.el...
Generating autoloads for align-string.el...done
Generating autoloads for all.el...
Generating autoloads for all.el...done
Generating autoloads for apache-mode.el...
Generating autoloads for apache-mode.el...done
Generating autoloads for ascii.el...
Generating autoloads for ascii.el...done
Generating autoloads for auto-fill-inhibit.el...
Generating autoloads for auto-fill-inhibit.el...done
Generating autoloads for bar-cursor.el...
Generating autoloads for bar-cursor.el...done
Generating autoloads for bm.el...
Generating autoloads for bm.el...done
Generating autoloads for boxquote.el...
Generating autoloads for boxquote.el...done
Generating autoloads for browse-huge-tar.el...
Generating autoloads for browse-huge-tar.el...done
Generating autoloads for browse-kill-ring.el...
Generating autoloads for browse-kill-ring.el...done
Generating autoloads for button-lock.el...
Generating autoloads for button-lock.el...done
Generating autoloads for clipper.el...
Generating autoloads for clipper.el...done
Generating autoloads for coffee.el...
Generating autoloads for coffee.el...done
Generating autoloads for color-theme-library.el...
Generating autoloads for color-theme-library.el...done
Generating autoloads for color-theme.el...
Generating autoloads for color-theme.el...done
Generating autoloads for color-theme_seldefcustom.el...
Generating autoloads for color-theme_seldefcustom.el...done
Generating autoloads for csv-mode.el...
Generating autoloads for csv-mode.el...done
Generating autoloads for ctypes.el...
Generating autoloads for ctypes.el...done
Generating autoloads for dedicated.el...
Generating autoloads for dedicated.el...done
Generating autoloads for df.el...
Generating autoloads for df.el...done
Generating autoloads for diminish.el...
Generating autoloads for diminish.el...done
Generating autoloads for dir-locals.el...
Generating autoloads for dir-locals.el...done
Generating autoloads for edit-env.el...
Generating autoloads for edit-env.el...done
Generating autoloads for egocentric.el...
Generating autoloads for egocentric.el...done
Generating autoloads for emacs-goodies-custom.el...
Generating autoloads for emacs-goodies-custom.el...done
Generating autoloads for emacs-goodies-el.el...
Generating autoloads for emacs-goodies-el.el...done
Generating autoloads for eproject-extras.el...
Generating autoloads for eproject-extras.el...done
Generating autoloads for eproject.el...
Generating autoloads for eproject.el...done
Generating autoloads for ff-paths.el...
Generating autoloads for ff-paths.el...done
Generating autoloads for filladapt.el...
Generating autoloads for filladapt.el...done
Generating autoloads for floatbg.el...
Generating autoloads for floatbg.el...done
Generating autoloads for folding.el...
Generating autoloads for folding.el...done
Generating autoloads for framepop.el...
Generating autoloads for framepop.el...done
Generating autoloads for graphviz-dot-mode.el...
Generating autoloads for graphviz-dot-mode.el...done
Generating autoloads for highlight-beyond-fill-column.el...
Generating autoloads for highlight-beyond-fill-column.el...done
Generating autoloads for highlight-completion.el...
Generating autoloads for highlight-completion.el...done
Generating autoloads for highlight-current-line.el...
Generating autoloads for highlight-current-line.el...done
Generating autoloads for home-end.el...
Generating autoloads for home-end.el...done
Generating autoloads for htmlize.el...
Generating autoloads for htmlize.el...done
Generating autoloads for initsplit.el...
Generating autoloads for initsplit.el...done
Generating autoloads for joc-toggle-buffer.el...
Generating autoloads for joc-toggle-buffer.el...done
Generating autoloads for joc-toggle-case.el...
Generating autoloads for joc-toggle-case.el...done
Generating autoloads for keydef.el...
Generating autoloads for keydef.el...done
Generating autoloads for keywiz.el...
Generating autoloads for keywiz.el...done
Generating autoloads for lcomp.el...
Generating autoloads for lcomp.el...done
Generating autoloads for map-lines.el...
Generating autoloads for map-lines.el...done
Generating autoloads for maplev.el...
Generating autoloads for maplev.el...done
Generating autoloads for marker-visit.el...
Generating autoloads for marker-visit.el...done
Generating autoloads for matlab.el...
Generating autoloads for matlab.el...done
Generating autoloads for minibuf-electric.el...
Generating autoloads for minibuf-electric.el...done
Generating autoloads for 

Bug#842403: jetty8 install fails on stretch

[Brent S. Elmer Ph.D.]

On Tue, 2016-11-15 at 11:29 +0100, Emmanuel Bourg wrote:
> Hi,
> 
> Thank you for the report. jetty8 has been removed from stretch and
> replaced by jetty9. The jetty9 package is quite similar, could you
> give
> it a try and see if it's affected by the same issue please?
> 
> Thank you,
> 
> Emmanuel Bourg
> 
Yes, jetty9 is the same.

Selecting previously unselected package jetty9.
(Reading database ... 477197 files and directories currently
installed.)
Preparing to unpack .../jetty9_9.2.19-2_all.deb ...
Unpacking jetty9 (9.2.19-2) ...
Setting up jetty9 (9.2.19-2) ...
Adding system user `jetty' (UID 131) ...
Adding new group `jetty' (GID 142) ...
Adding new user `jetty' (UID 131) with group `jetty' ...
Not creating home directory `/usr/share/jetty9'.
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and
overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and
overrides
Job for jetty9.service failed because the control process exited with
error code.
See "systemctl status jetty9.service" and "journalctl -xe" for details.
invoke-rc.d: initscript jetty9, action "start" failed.
● jetty9.service - LSB: Start Jetty
   Loaded: loaded (/etc/init.d/jetty9; generated; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Thu 2016-11-17 11:52:26
CST; 5ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 13934 ExecStart=/etc/init.d/jetty9 start (code=exited,
status=1/FAILURE)
  CPU: 1.537s

Nov 17 11:52:21 brente systemd[1]: Starting LSB: Start Jetty...
Nov 17 11:52:21 brente jetty9[13934]: Starting Jetty 9 Servlet Engine:
jett…ng).
Nov 17 11:52:26 brente jetty9[13934]:  failed!
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Control process
exited, …us=1
Nov 17 11:52:26 brente systemd[1]: Failed to start LSB: Start Jetty.
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Unit entered failed
state.
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Failed with result
'exit…de'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package jetty9 (--configure):
 subprocess installed post-installation script returned error exit
status 1
Processing triggers for systemd (232-3) ...
Errors were encountered while processing:
 jetty9

Not all changes and updates succeeded. For further details of the
failure, please expand the 'Details' panel below.

Brent

Bug#842195: patch

[Brent S. Elmer Ph.D.]

I have found a fix thanks to Tibor Boesze.  He fixed an older version
of Ubuntu so I applied the fix to debian.  The only change is in 
/auth-dialog/main.c.

@@ -997,6 +997,7 @@ static int get_config (GHashTable *optio
    if (csd_wrapper && !csd_wrapper[0])
    csd_wrapper = NULL;

+   openconnect_set_xmlpost(vpninfo, 0);
    openconnect_setup_csd(vpninfo, getuid(), 1, OC3DUP
(csd_wrapper));
    }


His comments were 
* Do not attempt to post XML authentication requests when a cds
 wrapper is configured.

I have never made a patch before but I tried.  I will attach my attempt
at a patch.

Once I make the small change, network-manager-openconnect connects to
my vpn.

I am guessing that the change above is doing what 
--no-xmlpost is doing in the openconnect command line connection that
works.Description: 
 network-manager-openconnect (1.2.2+nxp1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Do not attempt to post XML authentication requests when a cds
 wrapper is configured.
Author: Tibor Bősze 

 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 network-manager-openconnect (1.2.2-1) unstable; urgency=medium
 .
   [ Aron Xu ]
   * New upstream release.
 .
   [ Mike Miller ]
   * Add dependency on network-manager (>= 1.2) to ensure non-absolute
 plugin paths are handled.
   * No longer need to build with configure option --enable-absolute-
 paths.
Author: Mike Miller 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 2016-11-04

--- network-manager-openconnect-1.2.2.orig/auth-dialog/main.c
+++ network-manager-openconnect-1.2.2/auth-dialog/main.c
@@ -418,7 +418,7 @@ static gboolean ui_add_select (ui_fragme
if (g_queue_peek_tail(ui_data->form_entries) == data)
gtk_widget_grab_focus (combo);
g_signal_connect(G_OBJECT(combo), "changed", G_CALLBACK(combo_changed), 
data);
-   /* Hook up the 'show' signal to ensure that we override prompts on
+   /* Hook up the 'show' signal to ensure that we override prompts on
   UI elements which may be coming later. */
g_signal_connect(G_OBJECT(combo), "show", G_CALLBACK(combo_changed), 
data);

@@ -524,7 +524,7 @@ static gboolean ui_form (struct oc_auth_
data = g_slice_new0 (ui_fragment_data);
data->ui_data = ui_data;
data->opt = opt;
-
+
if (opt->type == OC_FORM_OPT_PASSWORD ||
opt->type == OC_FORM_OPT_TEXT) {
g_mutex_lock (_data->form_mutex);
@@ -567,7 +567,7 @@ static gboolean ui_form (struct oc_auth_
} else
g_slice_free (ui_fragment_data, data);
}
-
+
return ui_show(ui_data);
 }

@@ -981,7 +981,7 @@ static int get_config (GHashTable *optio

openconnect_set_xmlsha1 (vpninfo, (char *)sha1_text, 
strlen(sha1_text) + 1);
g_checksum_free(sha1);
-
+
parse_xmlconfig (config_str);
}

@@ -997,6 +997,7 @@ static int get_config (GHashTable *optio
if (csd_wrapper && !csd_wrapper[0])
csd_wrapper = NULL;

+   openconnect_set_xmlpost(vpninfo, 0);
openconnect_setup_csd(vpninfo, getuid(), 1, OC3DUP 
(csd_wrapper));
}

@@ -1528,7 +1529,7 @@ static auth_ui_data *init_ui_data (char

 #if OPENCONNECT_CHECK_VER(1,4)
openconnect_set_cancel_fd (ui_data->vpninfo, ui_data->cancel_pipes[0]);
-#endif
+#endif

 #if 0
ui_data->vpninfo->proxy_factory = px_proxy_factory_new();

Bug#822964: Have to click connect twice before login dialogue opens

[Brent S. Elmer Ph.D.]

On Fri, 2016-04-29 at 15:08 -0400, Mike Miller wrote:
> On Fri, Apr 29, 2016 at 11:23:52 -0500, Brent S. Elmer Ph.D. wrote:
> > 
> > gnome-shell current stretch version 3.18.1-1
> Do you have another desktop environment (e.g. xfce) you can try?
> 
> > 
> > yes, nmcli has the same behavior:
> > 
> > $ nmcli con up 'IBM openconnect'
> > Error: Connection activation failed: no valid VPN secrets.
> Since gnome-shell is the registered "secret agent" for NetworkManager
> when working in a Gnome desktop environment, this still sounds like a
> gnome-shell bug.
> 
> In fact it sounds like https://bugzilla.gnome.org/show_bug.cgi?id=760
> 999
> 
> If you don't have a different desktop environment, can you try
> upgrading
> to gnome-shell 3.20 from unstable? That may be what fixed the issue
> for
> me, and I am unable to downgrade to verify that now.
> 

There were a few new packages today in stretch that I upgraded.  After
the upgrade today, I have tried rebooting twice and openconnect vpn now
works on the first try.  There were a few network-manager packages in
today's upgrade.  Here is what is in the log for the upgrade:

Upgraded the following packages:
apt (1.2.10) to 1.2.11
apt-utils (1.2.10) to 1.2.11
console-setup (1.141) to 1.142
console-setup-linux (1.141) to 1.142
daemonize (1.7.6-2) to 1.7.7-1
debian-keyring (2016.03.22) to 2016.04.22
gir1.2-networkmanager-1.0 (1.1.94-1) to 1.2.0-1
gstreamer1.0-plugins-bad (1.8.0-1+b1) to 1.8.1-1
gstreamer1.0-vaapi (1.8.0-1) to 1.8.1-1
keyboard-configuration (1.141) to 1.142
libapt-inst2.0 (1.2.10) to 1.2.11
libapt-pkg5.0 (1.2.10) to 1.2.11
libbsd0 (0.8.2-1) to 0.8.3-1
libbsd0:i386 (0.8.2-1) to 0.8.3-1
libgif7 (5.1.2-0.3) to 5.1.4-0.1
libgpg-error0 (1.21-2) to 1.22-1
libgpg-error0:i386 (1.21-2) to 1.22-1
libgstreamer-plugins-bad1.0-0 (1.8.0-1+b1) to 1.8.1-1
libiw30 (30~pre9-9) to 30~pre9-10
libmetacity-private3a (1:3.18.3-1) to 1:3.18.4-1
libnm-glib-vpn1 (1.1.94-1) to 1.2.0-1
libnm-glib4 (1.1.94-1) to 1.2.0-1
libnm-util2 (1.1.94-1) to 1.2.0-1
libnm0 (1.1.94-1) to 1.2.0-1
libnss-myhostname (229-4) to 229-5
libpam-systemd (229-4) to 229-5
libpath-tiny-perl (0.086-1) to 0.088-1
libpoppler-glib8 (0.38.0-2+b1) to 0.38.0-3
libpoppler-qt4-4 (0.38.0-2+b1) to 0.38.0-3
libpoppler57 (0.38.0-2+b1) to 0.38.0-3
libselinux1 (2.4-3+b1) to 2.5-1
libselinux1:i386 (2.4-3+b1) to 2.5-1
libsemanage-common (2.4-3) to 2.5-1
libsemanage1 (2.4-3+b1) to 2.5-1
libsepol1 (2.4-2) to 2.5-1
libsqlite3-0 (3.12.1-1) to 3.12.2-1
libsystemd0 (229-4) to 229-5
libsystemd0:i386 (229-4) to 229-5
libteamdctl0 (1.23-1) to 1.24-1
libudev1 (229-4) to 229-5
libudev1:i386 (229-4) to 229-5
metacity (1:3.18.3-1) to 1:3.18.4-1
metacity-common (1:3.18.3-1) to 1:3.18.4-1
network-manager (1.1.94-1) to 1.2.0-1
ntfs-3g (1:2015.3.14AR.1-1+b1) to 1:2016.2.22AR.1-3
openjdk-8-jre (8u77-b03-3+b1) to 8u91-b14-2
openjdk-8-jre-headless (8u77-b03-3+b1) to 8u91-b14-2
poppler-utils (0.38.0-2+b1) to 0.38.0-3
printer-driver-brlaser (3-4) to 3-5
printer-driver-foo2zjs (20151024dfsg0-2) to 20160313dfsg0-1
printer-driver-foo2zjs-common (20151024dfsg0-2) to 20160313dfsg0-1
pylint (1.5.2-1) to 1.5.5-1
pylint3 (1.5.2-1) to 1.5.5-1
python-libvirt (1.3.1-1+b1) to 1.3.3-1
python-pkg-resources (20.7.0-1) to 20.10.1-1
python-selinux (2.4-3+b1) to 2.5-1
python-setuptools (20.7.0-1) to 20.10.1-1
python3-pkg-resources (20.7.0-1) to 20.10.1-1
python3-requests-cache (0.4.10-1) to 0.4.12-1
python3-setuptools (20.7.0-1) to 20.10.1-1
systemd (229-4) to 229-5
systemd-sysv (229-4) to 229-5
tex4ht (20090611-1.1+b1) to 20090611-3
tex4ht-common (20090611-1.1) to 20090611-3
udev (229-4) to 229-5
virt-viewer (1.0-1) to 3.1-1
wireless-tools (30~pre9-9) to 30~pre9-10

Installed the following packages:
libntfs-3g871 (1:2016.2.22AR.1-3)

Bug#822964: Have to click connect twice before login dialogue opens

[Brent S. Elmer Ph.D.]

On Fri, 2016-04-29 at 11:37 -0400, Mike Miller wrote:
> 
> Can you say which graphical tool you are using to connect to the VPN?
> If
> gnome-shell or gnome-control-center network, which version? Does the
> same behavior occur with "nmcli con up VPN-NAME"? When it does occur,
> do
> you see a stray nm-openconnect-service process running after the
> failure?
> 
> This sounds like a symptom I used to see with both OpenConnect and
> OpenVPN connections, but has recently disappeared since upgrading to
> Gnome 3.20 and NetworkManager 1.2.0.
> 

gnome-shell current stretch version 3.18.1-1

yes, nmcli has the same behavior:

$ nmcli con up 'IBM openconnect'
Error: Connection activation failed: no valid VPN secrets.
brente@brente:~$ nmcli con up 'IBM openconnect'
A password is required to connect to 'IBM openconnect'.
Warning: password for 'vpn.secrets.gateway' not given in 'passwd-file'
and nmcli cannot ask without '--ask' option.



The first time I run nmlci I get an immediate prompt back after the
Error.  The second time I get the Warning but the login dialog shows
and I can click login.

Here is what ps shows after the failure:

root  3394 1  0 10:46 ?00:00:00
/usr/lib/NetworkManager/nm-openconnect-service --bus-name
org.freedesktop.NetworkManager.openconnect.Connection_2


When the "connect to VPN" dialog shows up for me to login, I have
"Automatically start connecting next time" checked and "Save passwords"
checked and the password is there.  However, it has never automatically
connected.  I have always had to click "Login" to be connected.  It
seems like with those two boxes checked and a password in the field, it
should just connect automatically.  Shouldn't it?  What is
vpn.secrets.gateway and passwd-file?

I did some experimenting and found that if I disconnect from the vpn
that reconnecting always brings up the connect dialog box.  Also, if I
log out and back in the first time clicking on connect to vpn always
brings up the connect dialog box.  I also tried waiting 5 or 10 minutes
after I log in to gnome to see if that makes any difference.  It
appears that no matter how long I wait, the first attempt after a boot
fails.

I hope this helps to figure out what the problem is.

Bug#804183: upgrade to 1.10.4-1 creates circular inclusion

[Brent S. Elmer Ph.D.]

I just installed 1.10.4-1 and the circular inclusion came back.

Setting up dbus (1.10.4-1) ...
A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
Error org.freedesktop.DBus.Error.Failed: Circular inclusion of file
'/etc/dbus-1/system.conf.dpkg-bak'
Setting up dbus-x11 (1.10.4-1) ...

My system may have been in an odd state due to this bug causing the
1.10.4-1 upgrade to perpetuate the circular dependency.  How do I get
my system to a good state again?  Just upgrading to 1.10.4-1 does not
fix the circular dependency for me.

Help please.

Bug#804183: upgrade to 1.10.4-1 creates circular inclusion

[Brent S. Elmer Ph.D.]

On Tue, 2015-11-24 at 01:13 +, Simon McVittie wrote:
> On 23/11/15 20:11, Brent S. Elmer Ph.D. wrote:
> > My system may have been in an odd state due to this bug causing the
> > 1.10.4-1 upgrade to perpetuate the circular dependency.  How do I
> > get
> > my system to a good state again?
> 
> Before doing anything to try to solve it, please show me the output
> of:
> 
> ls -la /etc/dbus-1/
> 
> Ideally, what you want (with uninteresting date/ownership/size
> columns
> removed to avoid linewrapping) is something like this:
> 
> drwxr-xr-x [...] .
> drwxr-xr-x [...] ..
> lrwxrwxrwx [...] session.conf -> /usr/share/dbus-1/session.conf
> drwxr-xr-x [...] session.d
> lrwxrwxrwx [...] system.conf -> /usr/share/dbus-1/system.conf
> drwxr-xr-x [...] system.d
> 
> *.dpkg-{dist,old,new} files are also OK. *.dpkg-bak are OK but only
> if
> they are real files, not if they are symlinks into /usr/share/dbus-
> 1/;
> if in doubt, rename them out of the way.
> 
> If /etc/dbus-1/s*.conf.bak is a symlink into /usr/share/dbus-1/,
> delete
> that symlink.
> 
> For completeness, also check that /usr/share/dbus-1/session.conf and
> /usr/share/dbus-1/system.conf are real files, not symlinks. If not,
> move
> them out of the way, then reinstall dbus (something like "sudo dpkg
> -i
> /var/cache/apt/archives/dbus_1.10.4-1_*.deb" should work).
> 
> Having reached a stable state, "sudo service dbus reload" should
> work.
> Please substitute your favourite way of running things as root if
> that
> isn't sudo.
> 
> I'm reluctant to add any additional workarounds in the dbus package
> to
> try to sort out your system automatically, because the bad situation
> could only be hit by downgrading (which is unsupported anyway), and
> the
> more special-case code I add to the maintainer scripts, the more
> likely
> it is that I'll accidentally cause some regression for someone else.
> 
> S
> 

$ ls -la /etc/dbus-1/
total 32
drwxr-xr-x   4 root root  4096 Nov 23 13:56 .
drwxr-xr-x 163 root root 12288 Nov 23 13:57 ..
lrwxrwxrwx   1 root root30 Nov 23 13:56 session.conf ->
/usr/share/dbus-1/session.conf
lrwxrwxrwx   1 root root30 Nov  3 13:23 session.conf.dpkg-bak ->
/usr/share/dbus-1/session.conf
-rw-r--r--   1 root root   828 Sep 15 17:09 session.conf.dpkg-new
drwxr-xr-x   2 root root  4096 May 27 17:12 session.d
lrwxrwxrwx   1 root root29 Nov 23 13:56 system.conf ->
/usr/share/dbus-1/system.conf
lrwxrwxrwx   1 root root29 Nov  3 13:23 system.conf.dpkg-bak ->
/usr/share/dbus-1/system.conf
-rw-r--r--   1 root root   823 Sep 15 17:09 system.conf.dpkg-new
drwxr-xr-x   2 root root  4096 Nov 23 13:57 system.d

Bug#804183: dbus fails to start, circular inclusion of *.dpkg-bak

[Brent S. Elmer Ph.D.]

On Sat, 2015-11-07 at 15:09 +0100, Simon McVittie wrote:
> Control: retitle 804183 downgrading dbus from 1.10.2-1 leads to
> circular inclusion of s*.conf.dpkg-bak
> 

> Before upgrading to 1.10.2, had you modified /etc/dbus-1/s*.conf?
> 

No.

> Please show me anything relevant to dbus from /var/log/dpkg.log* and
> /var/log/apt/*, going back to before you first attempted to install
> dbus 1.10.2-1? I'm particularly interested in whether the package
> went
> via some unusual state (maybe a failed or partially-failed upgrade)
> before you did the problematic downgrade, and in any messages that it
> emitted in /var/log/apt/term.log* during the upgrade and downgrade.
> 


> (reference:
>  -mscriptsinstact>)
> 
> S

I attached the greps for dbus below.

Brent
grep --color -nH -e dbus /var/log/dpkg.log*
/var/log/dpkg.log:246:2015-11-03 13:22:09 upgrade dbus-x11:amd64 1.10.0-3 1.10.2-1
/var/log/dpkg.log:247:2015-11-03 13:22:09 status half-configured dbus-x11:amd64 1.10.0-3
/var/log/dpkg.log:248:2015-11-03 13:22:09 status unpacked dbus-x11:amd64 1.10.0-3
/var/log/dpkg.log:249:2015-11-03 13:22:09 status half-installed dbus-x11:amd64 1.10.0-3
/var/log/dpkg.log:250:2015-11-03 13:22:09 status half-installed dbus-x11:amd64 1.10.0-3
/var/log/dpkg.log:251:2015-11-03 13:22:10 status unpacked dbus-x11:amd64 1.10.2-1
/var/log/dpkg.log:252:2015-11-03 13:22:10 status unpacked dbus-x11:amd64 1.10.2-1
/var/log/dpkg.log:253:2015-11-03 13:22:10 upgrade libdbus-1-3:i386 1.10.0-3 1.10.2-1
/var/log/dpkg.log:254:2015-11-03 13:22:10 status half-configured libdbus-1-3:i386 1.10.0-3
/var/log/dpkg.log:255:2015-11-03 13:22:10 status unpacked libdbus-1-3:i386 1.10.0-3
/var/log/dpkg.log:256:2015-11-03 13:22:10 status half-configured libdbus-1-3:amd64 1.10.0-3
/var/log/dpkg.log:257:2015-11-03 13:22:10 status half-installed libdbus-1-3:i386 1.10.0-3
/var/log/dpkg.log:258:2015-11-03 13:22:10 status half-installed libdbus-1-3:i386 1.10.0-3
/var/log/dpkg.log:259:2015-11-03 13:22:10 status unpacked libdbus-1-3:i386 1.10.2-1
/var/log/dpkg.log:260:2015-11-03 13:22:10 status unpacked libdbus-1-3:i386 1.10.2-1
/var/log/dpkg.log:261:2015-11-03 13:22:11 upgrade libdbus-1-3:amd64 1.10.0-3 1.10.2-1
/var/log/dpkg.log:262:2015-11-03 13:22:11 status half-configured libdbus-1-3:amd64 1.10.0-3
/var/log/dpkg.log:263:2015-11-03 13:22:11 status unpacked libdbus-1-3:amd64 1.10.0-3
/var/log/dpkg.log:264:2015-11-03 13:22:11 status half-installed libdbus-1-3:amd64 1.10.0-3
/var/log/dpkg.log:265:2015-11-03 13:22:11 status half-installed libdbus-1-3:amd64 1.10.0-3
/var/log/dpkg.log:266:2015-11-03 13:22:11 status unpacked libdbus-1-3:amd64 1.10.2-1
/var/log/dpkg.log:267:2015-11-03 13:22:11 status unpacked libdbus-1-3:amd64 1.10.2-1
/var/log/dpkg.log:268:2015-11-03 13:22:11 upgrade dbus:amd64 1.10.0-3 1.10.2-1
/var/log/dpkg.log:269:2015-11-03 13:22:11 status half-configured dbus:amd64 1.10.0-3
/var/log/dpkg.log:270:2015-11-03 13:22:12 status unpacked dbus:amd64 1.10.0-3
/var/log/dpkg.log:271:2015-11-03 13:22:12 status half-installed dbus:amd64 1.10.0-3
/var/log/dpkg.log:273:2015-11-03 13:22:12 status half-installed dbus:amd64 1.10.0-3
/var/log/dpkg.log:274:2015-11-03 13:22:12 status unpacked dbus:amd64 1.10.2-1
/var/log/dpkg.log:275:2015-11-03 13:22:13 status unpacked dbus:amd64 1.10.2-1
/var/log/dpkg.log:579:2015-11-03 13:23:16 upgrade cairo-dock-dbus-plug-in:amd64 3.4.0-1+b2 3.4.0-1.1
/var/log/dpkg.log:580:2015-11-03 13:23:16 status half-configured cairo-dock-dbus-plug-in:amd64 3.4.0-1+b2
/var/log/dpkg.log:581:2015-11-03 13:23:16 status unpacked cairo-dock-dbus-plug-in:amd64 3.4.0-1+b2
/var/log/dpkg.log:582:2015-11-03 13:23:17 status half-installed cairo-dock-dbus-plug-in:amd64 3.4.0-1+b2
/var/log/dpkg.log:583:2015-11-03 13:23:17 status half-installed cairo-dock-dbus-plug-in:amd64 3.4.0-1+b2
/var/log/dpkg.log:584:2015-11-03 13:23:17 status unpacked cairo-dock-dbus-plug-in:amd64 3.4.0-1.1
/var/log/dpkg.log:585:2015-11-03 13:23:17 status unpacked cairo-dock-dbus-plug-in:amd64 3.4.0-1.1
/var/log/dpkg.log:777:2015-11-03 13:23:33 configure libdbus-1-3:amd64 1.10.2-1 
/var/log/dpkg.log:778:2015-11-03 13:23:33 status unpacked libdbus-1-3:amd64 1.10.2-1
/var/log/dpkg.log:779:2015-11-03 13:23:33 status half-configured libdbus-1-3:amd64 1.10.2-1
/var/log/dpkg.log:780:2015-11-03 13:23:33 status installed libdbus-1-3:amd64 1.10.2-1
/var/log/dpkg.log:781:2015-11-03 13:23:33 configure libdbus-1-3:i386 1.10.2-1 
/var/log/dpkg.log:782:2015-11-03 13:23:33 status unpacked libdbus-1-3:i386 1.10.2-1
/var/log/dpkg.log:783:2015-11-03 13:23:33 status half-configured libdbus-1-3:i386 1.10.2-1
/var/log/dpkg.log:784:2015-11-03 13:23:33 status installed libdbus-1-3:i386 1.10.2-1
/var/log/dpkg.log:785:2015-11-03 13:23:33 configure dbus:amd64 1.10.2-1 
/var/log/dpkg.log:786:2015-11-03 13:23:33 status unpacked dbus:amd64 1.10.2-1
/var/log/dpkg.log:787:2015-11-03 13:23:33 status unpacked dbus:amd64 1.10.2-1

Bug#803112: same problem on integrated Intel graphics

[Brent S. Elmer Ph.D.]

I have the same problem on a machine with integrated Intel graphics.  I
have no xorg.conf on that machine.
I only have one monitor connected but I get the black screen with mouse
cursor in the middle which is unresponsive.  cntl alt f* also does not
work.  This only started when upgrading to gdm3 3.18.0-2.  Reverting
gdm3 to 3.14 fixes the problem.

Bug#803256: downgrading to 3.14.2-2 fixes the problem

[Brent S. Elmer Ph.D.]

I downgraded gdm3, gir1.2-gdm3, and libgdm1 to 3.14.2-2 and the problem
went away.  Gnome starts after logging in without putting the laptop to
sleep.

Bug#769942: almost always happens with import pdb;pdb.set_trace()

[Brent S. Elmer Ph.D.]

I have noticed the bad behavior of loosing the gud window happens
almost all of the time on inline debugging breaks.  Because setting
breaks in python code really slows the running down, I place inline
breaks like the following:

import pdb;pdb.set_trace()

When debugging in emacs24, the window that had the gud in it gets
replaced by the source for where the break is and thus I lose my gud
window and have to go hunting for it in the buffers in order to enter
any commands.

On emacs23 this does not happen.  My gud window is always there during
the debugging no matter how many other source files have to be opened
during the debugging.  I have noticed under emacs23 that a lot of the
times, the gud window will be bounced back and forth between the 2
split windows(one with the current source and gud in the other). That
is also kind of annoying but still usable.

Bug#769942: problem still exists in 24.5+1-2

[Brent S. Elmer Ph.D.]

I just tried 24.5+1-2 for kicks.  The problem still occurs.  Going back
to emacs23.

Bug#794237: nm upgrade from 9.10.0 to 1.0.6.0-2 breaks my openconnect vpn also

[Brent S. Elmer Ph.D.]

When upgrading my computer, my openconnect vpn broke.  I finally
narrowed it down to upgrading network-manager from the version in
jessie to the version in stretch.  It is network-manager that is
causing the trouble.  When network-manager only is upgraded, when I
connect to my openconnect vpn, the newer broken version sets the mtu on
vpn0 to 1500.  The previous version that worked, set the mtu to 1406.

Bug#766900: [Pkg-utopia-maintainers] Bug#766900: network-manager: postinst fails to restart NM

[Brent S. Elmer Ph.D.]

 54d80f8e.4000...@debian.org
In-Reply-To: 54d80f8e.4000...@debian.org
Content-Type: text/plain; charset=UTF-8
X-Mailer: Evolution 3.12.9-1+b1 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Mon, 09 Feb 2015 02:38:22 +0100 Michael Biebl bi...@debian.org wrote:

 
 Is this problem reproducible?
 What's the output of systemctl status NetworkManager.service?
 The output of journalctl -u NetworkManager.service might help as well
 
 
 
 -- 

I am having the same problem on a system that I haven't upgraded for a
while.  I tried to upgrade today and I get the problem.

Here is the information you asked for:


profitwiki:/home/brente# dpkg --configure -a
Setting up network-manager (0.9.10.0-7) ...
Job for NetworkManager.service failed. See 'systemctl status
NetworkManager.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript network-manager, action restart failed.
dpkg: error processing package network-manager (--configure):
 subprocess installed post-installation script returned error exit
status 1
Errors were encountered while processing:
 network-manager
profitwiki:/home/brente# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
   Active: failed (Result: start-limit) since Thu 2015-04-30 11:27:16
EDT; 4min 21s ago
  Process: 1969 ExecStart=/usr/sbin/NetworkManager --no-daemon
(code=exited, status=1/FAILURE)
 Main PID: 1969 (code=exited, status=1/FAILURE)

Apr 30 11:27:16 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 11:27:16 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 11:27:16 profitwiki systemd[1]: NetworkManager.service start
request repeated too quickly, refusing to start.
Apr 30 11:27:16 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 11:27:16 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
profitwiki:/home/brente# journalctl -u NetworkManager.service
-- Logs begin at Thu 2015-04-30 09:33:05 EDT, end at Thu 2015-04-30
11:27:16 EDT. --
Apr 30 09:33:30 profitwiki NetworkManager[23609]: NetworkManager is
already running (pid 6009)
Apr 30 09:33:30 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 09:33:30 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:30 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 09:33:30 profitwiki NetworkManager[23694]: NetworkManager is
already running (pid 6009)
Apr 30 09:33:30 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 09:33:30 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:30 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 09:33:30 profitwiki NetworkManager[23696]: NetworkManager is
already running (pid 6009)
Apr 30 09:33:30 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 09:33:30 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:30 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 09:33:30 profitwiki NetworkManager[23708]: NetworkManager is
already running (pid 6009)
Apr 30 09:33:30 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 09:33:30 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:30 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 09:33:30 profitwiki NetworkManager[23712]: NetworkManager is
already running (pid 6009)
Apr 30 09:33:30 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 09:33:30 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:30 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 09:33:31 profitwiki systemd[1]: NetworkManager.service start
request repeated too quickly, refusing to start.
Apr 30 09:33:31 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 09:33:31 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 10:26:16 profitwiki NetworkManager[1696]: NetworkManager is
already running (pid 6009)
Apr 30 10:26:16 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 10:26:16 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 10:26:16 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 10:26:16 profitwiki NetworkManager[1699]: NetworkManager is
already running (pid 6009)
Apr 30 10:26:16 profitwiki systemd[1]: NetworkManager.service: main
process exited, code=exited, status=1/FAILURE
Apr 30 10:26:16 profitwiki systemd[1]: Failed to start Network Manager.
Apr 30 10:26:16 profitwiki systemd[1]: Unit NetworkManager.service
entered failed state.
Apr 30 10:26:16 profitwiki 

Bug#776018: filling log directory

[Brent S. Elmer Ph.D.]

This bug is causing me a lot of grief as it is filling my /var/log
directory and bringing my system down.  Is there some way to set the
logging level so that these messages don't show up?  I think the bug
level needs to be increased because it can bring a system down.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774790: setting security.tls.version.min does not stick between restarts

[Brent S. Elmer Ph.D.]

 2015021135.ga30...@x201s.cruise.homelinux.net

 1421024217.721.11.ca...@aim.com
In-Reply-To: 1421024217.721.11.ca...@aim.com
Content-Type: text/plain; charset=UTF-8
X-Mailer: Evolution 3.12.9-1+b1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sun, 11 Jan 2015 18:56:57 -0600 Brent S. Elmer Ph.D. webe...@aim.com 
wrote:

 
 Aha, when I start in safe-mode, security.tls.version.min does show as 0
 in the icedove config.  I guess I need to see what plugins I have and
 try to figure out which one is causing the problem.
 
 Brent 
 
 
 

It is the plugin HTTPS-Everywhere 4.0.2 that is causing the behavior.
When I disable the plugin, the security.tls.version.min setting sticks
between restarts.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774790: setting security.tls.version.min does not stick between restarts

[Brent S. Elmer Ph.D.]

On Sun, 2015-01-11 at 13:11 +0100, Carsten Schoenert wrote:
 Hello Brent,
 
 On Wed, Jan 07, 2015 at 10:53:09AM -0600, Brent S. Elmer wrote:
  In the README.Debian it tells how to set security.tls.version.min to 0.  
  This
  works fine until icedove is stopped.  Upon restart of icedove,
  security.tls.version.min is set back to 1 again.  Is this the expected
  behavior?  If so, a note in the readme would be good.  If not, then there 
  is a
  bug.  Is there a way to make it stick between restarts?
 
 I've rechecked this behavior here with version 31.3.0-1
 I can't reproduce your issue here. The setting is stored in your
 local profile in $HOME/.icedove/$PROFILE_NAME/prefs.js
 
 Do you have a mountpoint with a local filesystem for the home
 directories? Or you working with a network filesystem? What about the
 permissions of your profile?
 Do you have tried to work in safe-mode with disabled plugins?
 
 Regards
 Carsten

It is behaving very strange.  When I change security.tls.version.min to
0 then icedove works to read my forum.  I exit out of icedove.  I can
see the setting in prefs.js.  When I restart icedove and I go into
edit- preferences-advanced-config, the value shows up as 1 instead of
0.  So, it looks like icedove will set the value and use it and write it
back to prefs.js.  But, on a restart of icedove, even if the value is 0
instead of 1 in prefs.js, icedove loads a 1 for the setting.

I am not on a network filesystem.  prefs.js is owned by me and the group
is me and the permissions are 644.

Aha, when I start in safe-mode, security.tls.version.min does show as 0
in the icedove config.  I guess I need to see what plugins I have and
try to figure out which one is causing the problem.

Brent 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772851: hp5550c scanner that used to work now fails

[Brent S. Elmer Ph.D.]

The scanner does not show up in scanimage -L unless I unplug it and plug it 
back in.
When I do get it to show up in scanimage -L and then start simple-scan and go 
into preferences to make sure it uses the hp,
I get the USB-in-USB errors and scanning does not work.  After I kill simple 
scan with ^-C, the scanner no longer shows up in scanimage -L until I unplug 
and plug in the scanner again.


brente@belmer:~$ scanimage -L
device `v4l:/dev/video0' is a Noname UVC Camera (17ef:4807) virtual
device
device `hp5590:libusb:008:004' is a HP 4500C/5550C Workgroup scanner
brente@belmer:~$ simple-scan
[hp5590] hp5590_control_msg: USB-in-USB: error reading data
^C
brente@belmer:~$ scanimage -L
device `v4l:/dev/video0' is a Noname UVC Camera (17ef:4807) virtual
device
brente@belmer:~$ 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729750: emacs24: GUD mode doesn't show prompt in several situations it should

[Brent S. Elmer Ph.D.]

On Fri, 2014-11-14 at 16:43 -0600, Rob Browning wrote:
 Brent S. Elmer Ph.D. webe...@aim.com writes:
 
  GUD is also giving me problems in emacs24 that I never had in emacs23.
 
  I am debugging Python code using pdb and gud in emacs24.  GUD usually
  opens by splitting the window with a pdb) debugger prompt/gud buffer in
  one half and the source code in the other half.  Commands can be entered
  at the pdb) prompt and the source will be tracked in the other window.
  Since emacs24, when I step into a function that requires opening another
  source file, the prompt window gets replaced with the new source file.
  The gud buffer still exists but it isn't showing anymore.  This action
  makes debugging in gud nearly useless under emacs24.  In fact, because
  of this I am changing my default emacs back to emacs23.
 
 This sounds like a new bug.  If so, please submit a new bug report, and
 please include the relevant Emacs version, step-by-step instructions to
 reproduce the problem, and check to see if any customizations in your
 ~/.emacs file might affect the relevant behavior.
 
 Also, if you have time, please let us know if the original bug that this
 report refers to is fixed in emacs24 -- or if you might have any further
 information about how we can reproduce the problem.
 
 Thanks

I submitted bug report 769942 for this.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729750: emacs24: GUD mode doesn't show prompt in several situations it should

[Brent S. Elmer Ph.D.]

 87siix4423@trouble.defaultvalue.org
In-Reply-To: 87siix4423@trouble.defaultvalue.org
Content-Type: text/plain; charset=UTF-8
X-Mailer: Evolution 3.12.7-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

GUD is also giving me problems in emacs24 that I never had in emacs23.

I am debugging Python code using pdb and gud in emacs24.  GUD usually
opens by splitting the window with a pdb) debugger prompt/gud buffer in
one half and the source code in the other half.  Commands can be entered
at the pdb) prompt and the source will be tracked in the other window.
Since emacs24, when I step into a function that requires opening another
source file, the prompt window gets replaced with the new source file.
The gud buffer still exists but it isn't showing anymore.  This action
makes debugging in gud nearly useless under emacs24.  In fact, because
of this I am changing my default emacs back to emacs23.

I also noticed some of the gud commands changed between emacs 23 and 24.
In emacs 23 the set break command was C-x space in emacs 24 it is C-x
C-a C-b.

emacs 23 has its own quirks wrt gud.  In the scenario above, emacs 23
bounces the gud window to the other window when opening new source.  So,
when stepping through source in different files, the gud half of the
window bounces back and forth.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766007: similar issues

[Brent S. Elmer Ph.D.]

I have recently started getting similar issues.  On sites that used to
work, I am now getting this error:

Secure Connection Failed

An error occurred during a connection to secure.marketwatch.com

Cannot communicate securely with peer: no common encryption
algorithm(s).

(Error code:ssl_error_no_cypher_overlap)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754407: error installing on 32bit jessie

[Brent S. Elmer Ph.D.]

On Thu, 2014-08-28 at 11:24 +0300, Christos Trochalakis wrote:

 Sorry for that, I meant:
 
 $ netstat -ntpl|grep :80 (as root)
 
 Also make sure that nginx is purged before installing it:
 
 $ apt-get purge nginx nginx-common nginx-full

Yes, apache2 is already bound to port 80.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757330: libvirt-daemon-system: fails to install

[Brent S. Elmer Ph.D.]

I am also getting an error with installing.  I have an up to date jessie
i386 system and I am getting the error E: Internal Error, No file name
for libvirt-daemon-system:i386


I have not done anything at all with libvirt on my system other than let
it upgrade when new versions come out.  If I try to just remove all
libvirt packages, it also wants to remove gnome-boxes.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754407: error installing on 32bit jessie

[Brent S. Elmer Ph.D.]

On Wed, 2014-08-27 at 13:26 +0300, Christos Trochalakis wrote:
 Hello,
 
 nginx seems to install correctly for me. Based on your logs, it seems
 that another process has already binded port 80 when you are trying to
 install nginx.
 
 nginx-full postinst script can't start nginx since the port is binded
 and fails. This is expected behaviour.
 
 Could check that nobody has binded :80 with `netcat -ntpl` and try to
 install nginx again?
 
 
 
I am not familiar with netcat but here is what I get:

# netcat -ntpl
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
  [-P proxy_username] [-p source_port] [-q seconds] [-s source]
  [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
  [-x proxy_address[:port]] [destination] [port]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758148: similar old bug

[Brent S. Elmer Ph.D.]

On Fri, 15 Aug 2014 11:38:02 -0400 Brent S. Elmer Ph.D. webe...@aim.com 
wrote:

  
 I'm guessing that mutter would be a better place for this bug report.
 On my system, the following were updated on July 23, 2014 which would be
 the right time frame for when I started seeing the problem.
 
 gir1.2-mutter-3.0
 libmutter0d
 mutter-common
 
 Brent
 
 
 
I have integrated and discrete graphics on my laptop.  I normally use
the discrete Radeon graphics with the xserver-xorg-video-radeon driver.
When I switched to using the integrated Intel graphics, it looks like
the refresh problem went away in the xterm as well as emacs.  It looks
like the problem may be in the radeon driver.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758148: similar old bug

[Brent S. Elmer Ph.D.]

I found this old bug report and it looks very similar to what I am
seeing.

https://bugzilla.redhat.com/show_bug.cgi?id=720605

In the report, in comment #36, it says to add 

export CLUTTER_PAINT=disable-clipped-redraws:disable-culling

to /etc/gdm/Xsession

On my Debian jessie computer, I do not see /etc/gdm/Xsession.  Any ideas
on where I should add the export to try it?

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758148: similar old bug

[Brent S. Elmer Ph.D.]

On Fri, 15 Aug 2014 10:40:00 -0400 Brent S. Elmer Ph.D. webe...@aim.com 
wrote:
 I found this old bug report and it looks very similar to what I am
 seeing.
 
 https://bugzilla.redhat.com/show_bug.cgi?id=720605
 
 In the report, in comment #36, it says to add 
 
 export CLUTTER_PAINT=disable-clipped-redraws:disable-culling
 
 to /etc/gdm/Xsession
 
 On my Debian jessie computer, I do not see /etc/gdm/Xsession.  Any ideas
 on where I should add the export to try it?
 
 Brent
 
 
 

I created a file with the export and put it in /etc/X11/Xsession.d.
Unfortunately, it did not help at all and sent both cores of my CPU to
be continuously  95%.  This is probably not the right package for this
bug report but I was hoping someone who knows where the right place is
would move it there.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758148: similar old bug

[Brent S. Elmer Ph.D.]

 1408116336.7040.3.camel@belmer
In-Reply-To: 1408116336.7040.3.camel@belmer
Content-Type: text/plain; charset=UTF-8
X-Mailer: Evolution 3.12.2-1+b1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 15 Aug 2014 11:25:36 -0400 Brent S. Elmer Ph.D. webe...@aim.com 
wrote:

 I created a file with the export and put it in /etc/X11/Xsession.d.
 Unfortunately, it did not help at all and sent both cores of my CPU to
 be continuously  95%.  This is probably not the right package for this
 bug report but I was hoping someone who knows where the right place is
 would move it there.
 
 Brent
 
 
 
I'm guessing that mutter would be a better place for this bug report.
On my system, the following were updated on July 23, 2014 which would be
the right time frame for when I started seeing the problem.

gir1.2-mutter-3.0
libmutter0d
mutter-common

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#738702: same problem only different library

[Brent S. Elmer Ph.D.]

Is this the same problem:

(gdb) run
Starting
program: /home/brente/atp_home/tests/fix_20140521/input/atp_bin/atp_engine 
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need set solib-search-path or set sysroot?
Traceback (most recent call last):
  File /usr/share/gdb/auto-load/usr/lib/i386-linux-gnu/libstdc
++.so.6.0.20-gdb.py, line 59, in module
from libstdcxx.v6.printers import register_libstdcxx_printers
  File
/usr/lib/i386-linux-gnu/../../share/gcc-4.9/python/libstdcxx/v6/printers.py, 
line 392
raise ValueError, Unsupported implementation for %s %
str(node.type)
^
SyntaxError: invalid syntax


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#743220: gnome-backgrounds dies

[Brent S. Elmer Ph.D.]

I ran gnome-control-center from a terminal and clicked on change
background and immediately got a segfault.  Nothing shows in the
terminal except 'Segmentation fault'.

I found the following in syslog:

kernel: [ 3943.042104] gnome-control-c[4050]: segfault at 9612000 ip
b68d9159 sp bfa1ea60 error 4 in libgdk-3.so.0.1000.7[b68b3000+ac000]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#742612: cups: error updating cups on AMD64 wheezy machine

[Brent S. Elmer Ph.D.]

Package: cups
Version: 1.5.3-5+deb7u1
Severity: normal

I get the following errors when updateing cups on my AMD64 wheezy computer:

Setting up cups (1.5.3-5+deb7u1) ...
insserv: warning: script 'K99modelersrv' missing LSB tags and overrides
insserv: warning: script 'rc.modeler' missing LSB tags and overrides
insserv: There is a loop at service modelersrv if started
insserv: There is a loop between service minissdpd and mountnfs if started
insserv:  loop involving service mountnfs at depth 10
insserv:  loop involving service nfs-common at depth 9
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends on minissdpd and therefore on system
facility `$all' which can not be true!
insserv: Starting rc.modeler depends 

Bug#679918: update causing fallback to old gtk theme look

[Brent S. Elmer Ph.D.]

On Sat, 2014-03-15 at 14:19 +, althaser wrote:
 Hey Brent,
 
 
 this is an old bug report.
 
 
 Could you please still reproduce this issue with newer gnome-shell
 version like 3.4.2-7+deb7u1 or 3.8.4-5+b1 ?
 
 
 thanks
 regards
 althaser
 
 
The bug has gone away.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#685804: gnome-shell crash

[Brent S. Elmer Ph.D.]

On Thu, 2014-03-20 at 19:40 +, althaser wrote:
 Hey Brent,
 
 
 this is an old bug report.
 
 
 Could you please still reproduce this issue with newer gnome-shell
 version like 3.4.2-7+deb7u1 or 3.8.4-5+b1 ?
 
 
 thanks
 regards
 althaser

The bug must have been fixed with subsequent gnome-shell versions.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#741550: python2.7:i386 fails to install on wheezy amd-64 system

[Brent S. Elmer Ph.D.]

Package: python2.7
Version: 2.7.3-6
Severity: normal

I am trying to install an i386 packages that is failing.  There is a long
string of i386 dependences for the package and when I try to install them one
at a time, it comes down to the following:

# apt-get install python2.7:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python2.7:i386 : Depends: mime-support:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.
root@opt16prof:/home/brente# apt-get install mime-support:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package mime-support:i386 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'mime-support:i386' has no installation candidate



-- System Information:
Debian Release: 7.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python2.7 depends on:
ii  libbz2-1.0 1.0.6-4
ii  libc6  2.13-38+deb7u1
ii  libdb5.1   5.1.29-5
ii  libexpat1  2.1.0-1+deb7u1
ii  libgcc11:4.7.2-5
ii  libncursesw5   5.9-10
ii  libreadline6   6.2+dfsg-0.1
ii  libsqlite3-0   3.7.13-1+deb7u1
ii  libtinfo5  5.9-10
ii  mime-support   3.52-1
ii  python2.7-minimal  2.7.3-6

python2.7 recommends no packages.

Versions of packages python2.7 suggests:
ii  binutils   2.22-8
pn  python2.7-doc  none

-- 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#728836: patch available upstream

[Brent S. Elmer Ph.D.]

This bug has made evolution useless for me.  According to the upstream
bug report, this problem has been fixed in the 3.10 version.  There is a
3.10 in debian experimental but it won't install due to dependency
issues.  I have a jessie system.  To try and install the 3.10 version
from experimental, I load the testing, unstable, and experimental
repositories in my sources but it still says there are unresolved
dependencies.  Is there any way to make the experimental version
install?

If there is no way to install the 3.10 version, according to the
upstream bug report, there is a patch for the 3.8 version that fixes the
problem.  Would it be possible for someone to install the patch?

My upstream bug report 711549 has been marked as a duplicate of 704513.
The patch is in the 704513 bug report.

It would be great if some progress could be made on this bug one way or
the other.  Evolution has been broken for a long time and 3.8 has been
considered obsolete upstream for a long time.  


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#734779: [Pkg-utopia-maintainers] Bug#734779: applet dropdown does not show VPN connected when it is

[Brent S. Elmer Ph.D.]

On Thu, 2014-01-09 at 22:58 -0500, Mike Miller wrote:
 On Thu, 9 Jan 2014 20:06:53 -0500, Brent S. Elmer, Ph.D. wrote:
  On Fri, 2014-01-10 at 01:48 +0100, Michael Biebl wrote:
  reassign 734779 gnome-shell
  thanks
 
  Am 09.01.2014 20:03, schrieb Brent S. Elmer Ph.D.:
   Here is a screen shot showing what I mean.
 
  that screenshot shows gnome-shell, so re-assigning.
  Please provide the version of gnome-shell you are using.
  
  gnome-shell version 3.8.4-5
 
 This certainly looks like #729288. Can you test whether the patch there
 fixes it for you?

Yes, the patch does fix the problem.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#734779: [Pkg-utopia-maintainers] Bug#734779: applet dropdown does not show VPN connected when it is

[Brent S. Elmer, Ph.D.]

On Fri, 2014-01-10 at 01:48 +0100, Michael Biebl wrote:

 reassign 734779 gnome-shell
 thanks
 
 Am 09.01.2014 20:03, schrieb Brent S. Elmer Ph.D.:
  Here is a screen shot showing what I mean.
 
 that screenshot shows gnome-shell, so re-assigning.
 Please provide the version of gnome-shell you are using.


gnome-shell version 3.8.4-5

Bug#722217: legacy304 also

[Brent S. Elmer Ph.D.]

I am running legacy304, so it is not just legacy173.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#732072: openafs-modules-dkms: openafs loses connection, backtrace on restart

[Brent S. Elmer Ph.D.]

On Fri, 2013-12-13 at 12:17 -0800, Russ Allbery wrote:
 Brent S. Elmer Ph.D. webe...@aim.com writes:
  On Fri, 2013-12-13 at 10:55 -0800, Russ Allbery wrote:
 
  Unfortunately, there's no data here to know why AFS got into an
  inconsistent state to start with.  Are there any symptoms at all beyond
  AFS directories not being accessible?  Is this consistently
  reproducible on this system?
 
  No, I don't notice any other symptoms.
  yes, it seems to happen every day.
 
 When AFS stops working, do attempts to access AFS hang, or do you get
 permission denied errors, or something else?
 

It doesn't hang.  I think it was permission denied errors.

 Is there anything in the kernel log (dmesg)?

No, other than the backtrace I already showed you when I did a restart.

 
  I have installed the newer version from backports.  I'll watch it and
  see if that helps.  By the way, would installing openafs from testing on
  a wheezy system be much different than installing from backports?
 
 No, they should be equivalent.  The only difference in wheezy is support
 for newer kernels.
 

After installing the later version from backports on Friday, AFS is
still up and working today.  There wasn't much activity on the machine
since then either.  I will continue to watch it and see if it stays up.

Thanks,

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#732072: openafs-modules-dkms: openafs loses connection, backtrace on restart

[Brent S. Elmer Ph.D.]

Package: openafs-modules-dkms
Version: 1.6.1-3+deb7u1
Severity: normal

I have a recent new install of Debian Wheezy on a 64bit AMD Opteron box and
have openafs-client installed.  Openafs does work and I can access the afs
directories.  After a certain amount of timem, the afs directories are not
accessible anymore even after a klog.  As root, I restart afs using /etc/init.d
/openafs-client restart.  I then see a backtrace for afs in syslog.  It appears
that openafs-client starts again because after a klog I can access the afs
directories again.

1. Is it normal for openafs-client to have to be restarted on a machine that is
not shut down very often?

2. That can't be good for it to backtrace in restart.

Here is the backtrace from the syslog:

Dec 13 10:13:18 opt16prof kernel: [63710.857297] afs: COLD shutting down of:
vcaches... CB... afs... BkG... CTrunc... AFSDB... RxEvent...
UnmaskRxkSignals... RxListener...  ALL allocated tables... done
Dec 13 10:13:18 opt16prof kernel: [63710.954593] enabling dynamically allocated
vcaches
Dec 13 10:13:18 opt16prof kernel: [63710.954598] Starting AFS cache
scan...found 21 non-empty cache files (1%).
Dec 13 10:13:18 opt16prof kernel: [63710.976641] [ cut here
]
Dec 13 10:13:18 opt16prof kernel: [63710.976649] WARNING: at /build/linux-
rrsxby/linux-3.2.51/fs/sysfs/dir.c:481 sysfs_add_one+0x8d/0xa0()
Dec 13 10:13:18 opt16prof kernel: [63710.976653] Hardware name: -[6217Z03]-
Dec 13 10:13:18 opt16prof kernel: [63710.976654] sysfs: cannot create duplicate
filename '/devices/virtual/bdi/afs'
Dec 13 10:13:18 opt16prof kernel: [63710.976657] Modules linked in: openafs(P)
tcp_diag inet_diag ppdev lp bnep ipt_LOG ipt_REJECT iptable_nat nf_nat
nf_conntrack_ipv4 nf_defrag_ipv4 rfcomm bluetooth rfkill iptable_filter
ip_tables ip6t_LOG xt_limit ip6t_REJECT xt_tcpudp ip6t_ah nf_conntrack_ipv6
nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables x_tables
binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 loop
nvidia(P) parport_pc parport shpchp psmouse mperf i2c_amd756 amd_rng
amd64_edac_mod container rng_core edac_mce_amd snd_intel8x0 snd_ac97_codec
evdev i2c_amd8111 i2c_core pcspkr serio_raw k8temp edac_core snd_pcm
snd_page_alloc snd_seq snd_seq_device snd_timer snd processor button soundcore
ac97_bus thermal_sys ext4 crc16 jbd2 mbcache dm_mod microcode sg sd_mod
crc_t10dif sr_mod cdrom ata_generic ohci_hcd ehci_hcd floppy sata_sil pata_amd
aic79xx scsi_transport_spi usbcore firewire_ohci tg3 libphy usb_common libata
firewire_core crc_itu_t scsi_mod [last unloaded: openafs]
Dec 13 10:13:18 opt16prof kernel: [63710.976735] Pid: 14955, comm: afsd
Tainted: P   O 3.2.0-4-amd64 #1 Debian 3.2.51-1
Dec 13 10:13:18 opt16prof kernel: [63710.976737] Call Trace:
Dec 13 10:13:18 opt16prof kernel: [63710.976744]  [81046cbd] ?
warn_slowpath_common+0x78/0x8c
Dec 13 10:13:18 opt16prof kernel: [63710.976748]  [81046d69] ?
warn_slowpath_fmt+0x45/0x4a
Dec 13 10:13:18 opt16prof kernel: [63710.976751]  [81150575] ?
sysfs_add_one+0x8d/0xa0
Dec 13 10:13:18 opt16prof kernel: [63710.976755]  [811505ee] ?
create_dir+0x66/0xa0
Dec 13 10:13:18 opt16prof kernel: [63710.976758]  [811506c3] ?
sysfs_create_dir+0x85/0x9b
Dec 13 10:13:18 opt16prof kernel: [63710.976763]  [810bb3cf] ?
__alloc_pages_nodemask+0x186/0x7aa
Dec 13 10:13:18 opt16prof kernel: [63710.976768]  [811abe22] ?
kobject_add_internal+0xc8/0x181
Dec 13 10:13:18 opt16prof kernel: [63710.976771]  [811ac1f7] ?
kobject_add+0x95/0xa4
Dec 13 10:13:18 opt16prof kernel: [63710.976775]  [8134e6cd] ?
mutex_lock+0xd/0x2d
Dec 13 10:13:18 opt16prof kernel: [63710.976779]  [8124f7ef] ?
device_add+0x109/0x590
Dec 13 10:13:18 opt16prof kernel: [63710.976783]  [8125976f] ?
pm_runtime_init+0xb5/0xc9
Dec 13 10:13:18 opt16prof kernel: [63710.976786]  [8124fd0e] ?
device_create_vargs+0x86/0xbe
Dec 13 10:13:18 opt16prof kernel: [63710.976790]  [810cb7c8] ?
bdi_register+0x5f/0x18b
Dec 13 10:13:18 opt16prof kernel: [63710.976811]  [a0d4a52d] ?
afs_fill_super+0x17d/0x20d [openafs]
Dec 13 10:13:18 opt16prof kernel: [63710.976820]  [a0d4a3b0] ?
afs_root.isra.1+0x131/0x131 [openafs]
Dec 13 10:13:18 opt16prof kernel: [63710.976825]  [810fc731] ?
mount_nodev+0x42/0x78
Dec 13 10:13:18 opt16prof kernel: [63710.976828]  [810fd117] ?
mount_fs+0x61/0x146
Dec 13 10:13:18 opt16prof kernel: [63710.976832]  [811101a6] ?
vfs_kern_mount+0x5f/0x99
Dec 13 10:13:18 opt16prof kernel: [63710.976835]  [81110590] ?
do_kern_mount+0x49/0xd8
Dec 13 10:13:18 opt16prof kernel: [63710.976838]  [8c0b] ?
do_mount+0x660/0x6c6
Dec 13 10:13:18 opt16prof kernel: [63710.976842]  [810c9858] ?
memdup_user+0x36/0x5b
Dec 13 10:13:18 opt16prof kernel: [63710.976845]  [8f19] ?
sys_mount+0x88/0xc3
Dec 13 10:13:18 opt16prof kernel: [63710.976849]  [81354212] ?

Bug#732072: openafs-modules-dkms: openafs loses connection, backtrace on restart

[Brent S. Elmer Ph.D.]

On Fri, 2013-12-13 at 10:55 -0800, Russ Allbery wrote:

 
 Unfortunately, there's no data here to know why AFS got into an
 inconsistent state to start with.  Are there any symptoms at all beyond
 AFS directories not being accessible?  Is this consistently reproducible
 on this system?
 
No, I don't notice any other symptoms.
yes, it seems to happen every day.

 Does using the newer version of openafs-client and openafs-modules-dkms
 from backports.debian.org help?
 

I have installed the newer version from backports.  I'll watch it and
see if that helps.  By the way, would installing openafs from testing on
a wheezy system be much different than installing from backports?

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729877: black screen with cursor no greeter

[Brent S. Elmer Ph.D.]

On Mon, 2013-11-18 at 15:48 +, Simon McVittie wrote:
 On 18/11/13 14:35, Brent S. Elmer wrote:
  Kernel: Linux 3.10.7.130911 (SMP w/2 CPU cores; PREEMPT)
 
 That's not a standard Debian kernel. My guess would be that some options
 required by systemd-logind are not enabled: in particular, it needs
 CONFIG_CGROUPS.
 
 Please check that the kernel compilation options described in
 /usr/share/doc/systemd/README.gz are set appropriately, or try with a
 standard Debian kernel.
 
 S
 

Thanks, that was it.  I booted with a standard Debian kernel and gdm3
started.  I hadn't noticed systemd was installed with the latest gdm3
and gnome updates.  Is that why I have a ton of udev errors scrolling
past on the boot now even with the standard kernel?

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729877: Re: Bug#729877: black screen with cursor no greeter

[Brent S. Elmer Ph.D.]

On Mon, 2013-11-18 at 19:11 +0100, Emilio Pozuelo Monfort wrote:

 Yes, CONFIG_CGROUPS is needed atm, otherwise logind fails to create a session,
 then libpam-systemd doesn't set the required env variables (particularly
 XDG_SESSION_ID) and the greeter fails to run. (see bug #729674).
 
 I am considering the following fix:
 in /usr/share/gnome-shell/js/misc/loginManager.js, line 121, change:
 
 if (haveSystemd())
 
 with:
 
 if (haveSystemd()  GLib.getenv('XDG_SESSION_ID'))
 
 then boot with your custom kernel, gdm should fall back to consolekit and 
 start
 fine.
 
 Let me know if that works.
 
 Emilio

I made the change then rebooted my custom kernel.  That worked, gdm3 did
start and let me log in to gnome.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#728836: evolution: imapx messages vanish

[Brent S. Elmer Ph.D.]

The gnome upstream bug report I filed is 711549.

On Tue, 2013-11-05 at 22:37 -0500, Brent wrote:
 Package: evolution
 Version: 3.8.5-2
 Severity: important
 
 I have evolution set up to use Imapx.  Starting this week, Evolution does not
 show all messages in my Imap Inbox and then the ones that are there go away.
 
 Steps:
 1. Start evolution
 The Inbox will show 0 messages.  After a while it will show the oldest 
 500,
 then 1000, then 1507, then 1666.  There are a few more messages on the server
 that are never shown.  The 1666 messages are as of up to 5 days ago.
 2. Click on another of the Imap folders Sent for example.
 All of the messages in sent will be shown.
 3.  Click on the Inbox again.
  The 1666 messages that were there will go away and they will be reloaded
 again 500, then 1000, then 1507 then 1666.  But still not show them all.
 4.  Click on Send and Receive or just wait until  the automatic refresh
 happens.
  The 1666 messages will go away and then be reloaded the same as before 
 and
 still not load all of them.
 
 This loading and unloading will just continue forever until evolution is shut
 down.
 
 When I run with CAMAL_DEBUG=all I see this in the log which looks suspicious:
 
 [imapx:B] token '*'
 [imapx:B] got untagged response
 [imapx:B] token TOKEN '1667'
 [imapx:B] token TOKEN 'FETCH'
 [imapx:B] Have token 'FETCH' id 1667
 [imapx:B] token '('
 [imapx:B] token TOKEN 'UID'
 [imapx:B] token TOKEN '31456101'
 [imapx:B] token TOKEN 'RFC822.SIZE'
 [imapx:B] token TOKEN '12769'
 [imapx:B] token TOKEN 'RFC822.HEADER'
 [imapx:B] token '*'
 [imapx:B] token TOKEN 'NO'
 [imapx:E] Scanning from start in INBOX
 [imapx:B] adding command, format = 'UID FETCH %s:* (UID FLAGS)'
 [imapx:B] got string '1'
 [imapx:B] completing command buffer is [25] 'UID FETCH 1:* (UID FLAGS)'
 [imapx:B] enqueue job 'UID FETCH 1:* (UID FLAGS)'
 [imapx:B] refuse to queue job on disconnected server
 [imapx:B] Message 20975073 vanished
 [imapx:B] Message 21063871 vanished
 [imapx:B] Message 21098033 vanished
 [imapx:B] Message 21104017 vanished
 [imapx:B] Message 21121092 vanished
 [imapx:B] Message 21121181 vanished
 [imapx:B] Message 21139065 vanished
 
 [imapx:B] Message 31456061 vanished
 [imapx:B] Message 31456062 vanished
 [imapx:B] Message 31456100 vanished
 0xb8687020: 0 0 0 | 99 1666 1666
 0xb8687020: 0 0 0 | 99 1665 1665
 0xb8687020: 0 0 0 | 99 1665 1665
 0xb8687020: 0 0 0 | 99 1664 1664
 0xb8687020: 0 0 0 | 99 1664 1664
 0xb8687020: 0 0 0 | 99 1663 1663
 0xb8687020: -1 0 0 | 99 1663 1663
 0xb8687020: -1 0 0 | 98 1662 1662
 
 0xb8687020: 0 0 0 | 0 5 5
 0xb8687020: 0 0 0 | 0 5 5
 0xb8687020: 0 0 0 | 0 4 4
 0xb8687020: 0 0 0 | 0 4 4
 0xb8687020: 0 0 0 | 0 3 3
 0xb8687020: 0 0 0 | 0 3 3
 0xb8687020: 0 0 0 | 0 2 2
 0xb8687020: 0 0 0 | 0 2 2
 0xb8687020: 0 0 0 | 0 1 1
 0xb8687020: 0 0 0 | 0 1 1
 0xb8687020: 0 0 0 | 0 0 0
 
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.11.5.131027 (PREEMPT)
 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
 Shell: /bin/sh linked to /bin/bash
 
 Versions of packages evolution depends on:
 ii  dbus   1.6.16-1
 ii  debconf [debconf-2.0]  1.5.51
 ii  evolution-common   3.8.5-2
 ii  evolution-data-server  3.8.5-2
 ii  gnome-icon-theme   3.10.0-1
 ii  libatk1.0-02.10.0-2
 ii  libc6  2.17-93
 ii  libcamel-1.2-433.8.5-2
 ii  libecal-1.2-15 3.8.5-2
 ii  libedataserver-1.2-17  3.8.5-2
 ii  libevolution   3.8.5-2
 ii  libglib2.0-0   2.36.4-1
 ii  libgtk-3-0 3.8.4-1
 ii  libical0   0.48-2
 ii  libnotify4 0.7.6-1
 ii  libsoup2.4-1   2.44.1-1
 ii  libwebkitgtk-3.0-0 2.2.0-2
 ii  libxml22.9.1+dfsg1-3
 ii  psmisc 22.20-1
 
 Versions of packages evolution recommends:
 pn  evolution-plugins  none
 ii  spamassassin   3.3.2-7
 ii  yelp   3.10.1-1
 
 Versions of packages evolution suggests:
 pn  evolution-ews   none
 pn  evolution-plugins-experimental  none
 ii  gnupg   1.4.15-1.1
 ii  network-manager 0.9.8.0-5
 
 -- debconf information:
   evolution/kill_processes:
   evolution/needs_shutdown:


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#722217: dead in the water

[Brent S. Elmer Ph.D.]

On Mon, 2013-10-07 at 00:16 +0200, Bastian Blank wrote:
 On Sun, Oct 06, 2013 at 05:52:01PM -0400, Brent S. Elmer Ph.D. wrote:
emacs, and sensord are segfaulting
  in libnvidia-tls.
 
 And what happens without this weird library?
 
 Bastian
 

I don't know what the library is or what happens without it or even how
to get rid of it.

I was able to get one of my systems working again.  libc was in a
halfway updated state.  I guess when it segfaulted during the upgrade it
left it in a bad state.  I could see that it was segfaulting in a post
install script.  I was able to run that post install script manually and
then configure all to get libc fully installed.  Once I did that and
rebooted, the system worked again.  I will add the details when I get a
chance.  That system was a 32bit AMD system.

The other system is a 64bit AMD system.  It seems to be broken in a
slightly different way when it segfaulted during the libc upgrade.  It
seems like it is segfaulting in a pre install script when I try to do a
configure all to try to fix it.  Trying to run the pre install script
manually requires a couple of input arguments that I haven't had a
chance to look into to see what to try.  I will give more details when I
get a chance.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#722217: dead in the water

[Brent S. Elmer Ph.D.]

I am trying to recover my system somehow but a lot of applications are
segfaulting making it very dificult.  emacs, and sensord are segfaulting
in libnvidia-tls.  I tried to downgrade libc6 but that also required
downgrading nvidia so I tried that too.  The problem is that trying to
downgrade libc6 segfaults.  Help.  Is there anything I can do besides
reinstall the whole system.  Here is my attempt at trying to downgrade
libc6 and nvidia through an ssh session into the dead machine.

# apt-get install  libxvmcnvidia1=304.88-6 nvidia-alternative=304.88-6
nvidia-detect=304.88-6 nvidia-glx=304.88-6 nvidia-kernel-dkms=304.88-6
nvidia-kernel-source=304.88-6 nvidia-vdpau-driver=304.88-6
nvidia-settings=304.88-2 xserver-xorg-video-nvidia=304.88-6
libgl1-nvidia-glx=304.88-6 libc6=2.17-92 libc6-dbg=2.17-92
libc6-dev=2.17-92 libc6-i686=2.17-92 libc-dev-bin=2.17-92
nvidia-driver=304.88-6
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
  akonadi-backend-mysql akonadi-server anthy-common aptdaemon
aptdaemon-data argyll autogen baobab cpp-4.3 dconf-cli
  dconf-editor dconf-tools deb-multimedia-keyring epiphany-browser-dbg
etherboot-qemu filelight-l10n fonts-century-catalogue
  fonts-dkg-handwriting fonts-f500 fonts-larabie-deco
fonts-larabie-straight fonts-larabie-uncommon fonts-tuffy
  foobillardplus foobillardplus-data fuseiso g++-4.7 gcc-4.3-base gdm3
geoclue-yahoo gir1.2-gtop-2.0 gir1.2-mx-1.0
  gir1.2-nautilus-3.0 gnome-chess gnome-font-viewer
gnome-icon-theme-extras gnome-packagekit-data gnome-search-tool
  gnome-session-canberra gnome-sudoku gnome-video-effects
grub-legacy-doc gstreamer0.10-plugins-base-dbg
  gstreamer0.10-plugins-good-dbg hyphen-en-us kdepim-runtime
kerneloops-applet kerneloops-daemon libakonadi-calendar4
  libakonadi-contact4 libakonadi-kcal4 libakonadi-kde4 libakonadi-kmime4
libakonadi-notes4 libakonadiprotocolinternals1
  libany-moose-perl libaqbanking-plugins-libgwenhywfar47 libaqbanking20
libaqbanking20-plugins libaqbanking20-plugins-qt
  libaqbanking29 libaqbanking29-plugins libaqbanking29-plugins-qt
libaqhbci13 libaqhbci17 libaqofxconnect4 libaqofxconnect5
  libatspi-dbg libavformat52 libavutil49 libbctsp-java
libboost-iostreams1.49.0 libboost-python1.34.1 libboost-python1.37.0
  libboost-python1.38.0 libboost-python1.39.0 libboost-python1.40.0
libboost-python1.42.0 libboost-python1.48.0
  libcamel-1.2-33 libconfig-tiny-perl libcr-dev libcrypt-blowfish-perl
libcv1 libcvaux1 libdata-amf-perl libdb4.7-java
  libdevel-symdump-perl libdmtx0a libebackend-1.2-2 libecal-1.2-11
libecj-java libedata-cal-1.2-15 libedataserver-1.2-16
  libexpect-perl libffmpegthumbnailer3 libflexdock-jni
libfontconfig1-dbg libgail-dbg libgbf-1-common libgcj-common
  libgda-4.0-4-dbg libgda3-3 libgda3-3-dbg libgda3-bin libgda3-common
libgda3-sqlite libgdl-1-dbg libgetopt-argvfile-perl
  libggiwmh0 libggiwmh0-target-x libglib2.0-0-dbg libgmime2.4-cil
libgnome2-dbg libgnomecanvas2-dbg libgnomedb3-4
  libgnomedb3-4-dbg libgnomedb3-bin libgnomedb3-common
libgnomevfs2-0-dbg libgpac0.4.6 libgraphite3 libgsf-1-114-dbg
  libgsf-gnome-1-114-dbg libgstreamer0.10-0-dbg libgtk2.0-0-dbg
libhal-dev libhal-storage-dev libhighgui1 libicc2 libicu44
  libiec16022-0 libimdi0 libio-stty-perl libisorelax-java libkabc4
libkalarmcal2 libkcal4 libkcalcore4 libkcalutils4
  libkgapi1 libkgapi2-2 libkholidays4 libkmbox4 libkms1
libknopflerfish-osgi-framework-java libkolab0 libkolabxml0
  libkpimidentities4 libkpimtextedit4 libkpimutils4 libkresources4
libloudmouth1-0-dbg libmagickcore3 libmagickcore3-extra
  libmagickwand3 libmailtransport4 libmath-round-perl libmicroblog4
libmono-accessibility4.0-cil libmono-bytefx0.7.6.2-cil
  libmono-c5-1.0-cil libmono-c5-1.1-cil libmono-cairo2.0-cil
libmono-codecontracts4.0-cil
  libmono-compilerservices-symbolwriter4.0-cil libmono-cscompmgd8.0-cil
libmono-custommarshalers4.0-cil libmono-db2-1.0-cil
  libmono-debugger-soft2.0-cil libmono-debugger-soft4.0-cil libmono-dev
libmono-getoptions2.0-cil libmono-http4.0-cil
  libmono-ldap2.0-cil libmono-ldap4.0-cil
libmono-messaging-rabbitmq2.0-cil libmono-messaging-rabbitmq4.0-cil
  libmono-messaging4.0-cil libmono-microsoft-build-engine4.0-cil
libmono-microsoft-build-framework4.0-cil
  libmono-microsoft-build-tasks-v4.0-4.0-cil
libmono-microsoft-build-utilities-v4.0-4.0-cil
libmono-microsoft-build2.0-cil
  libmono-microsoft-csharp4.0-cil libmono-microsoft-visualc10.0-cil
libmono-microsoft-web-infrastructure1.0-cil
  libmono-microsoft8.0-cil libmono-npgsql2.0-cil libmono-npgsql4.0-cil
libmono-opensystem-c4.0-cil libmono-oracle2.0-cil
  libmono-oracle4.0-cil libmono-peapi2.0-cil libmono-peapi4.0-cil
libmono-rabbitmq2.0-cil libmono-rabbitmq4.0-cil
  libmono-relaxng2.0-cil libmono-relaxng4.0-cil libmono-sharpzip2.6-cil
libmono-simd2.0-cil libmono-simd4.0-cil
  libmono-system-componentmodel-composition4.0-cil

Bug#722217: same problem on 2 AMD systems

[Brent S. Elmer Ph.D.]

I upgraded 2 AMD systems with the upgrades that hit testing yesterday
and had the same problem.  Both of the systems happen to also be using
the Nvidia graphics drivers.  Both of the systems are broken today and
will not start gdm3.  I also see a segfault in at least 1 other process
during the boot(I can remember what it was maybe syslog).  After the
segfault in Synaptic, the computers locked up and had to be hard powered
off.  This is a really bad problem.
My Intel jessie computer did not seem to have the problem.  It may be
unique to AMD or maybe AMD and Nvidia.  


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#605434: narrowed it down to version 1.4.4-5

[Brent S. Elmer Ph.D.]

On Mon, 2013-08-19 at 13:18 +0100, Brian Potkin wrote:
 tags 605434 moreinfo
 thanks
 
 
 
 On Fri 22 Apr 2011 at 10:06:48 -0400, Brent S. Elmer Ph.D. wrote:
 
  Using the debian snapshot repository, I have narrowed the issue down to
  the breakage occurring in version 1.4.4-5 as version 1.4.4-4 works.
  There are only two changes in that version according to the changelog:
 
 [Snip]
 
  It looks like the second change by Till Kamppeter is what killed the
  ps-print from emacs.  I don't know if this is an emacs or cups problem.
  I am suspecting a cups problem.  I had forgotten about this bug when I
  submitted bug report 623612 for emacs.  Version 1.4.4-5 is the first
  version I get the errors on the printout itself as described in the
  initial bug report.  It is also the first version that I get an error in
  the cups log:
  
  E [21/Apr/2011:13:29:52 -0400] [Job 6] No %%BoundingBox: comment in
  header!
 
 The patch mentioned may or may not have been a trigger for causing your
 problem. It is still used in Wheezy; is the issue still present there?
 Please say also what make and model your printer is and what PPD/driver
 it uses.
 
 Regards,
 
 Brian.

I have upgraded to jessie now.  I am current with updates in jessie.  I
tried ps-print again in emacs and it works now.  There is quite a bit
newer version of cups in jessie.  Something has fixed it. I don't know
if it was a cups or emacs update or something else.  I can't remember
exactly when it failed last but I am pretty sure it wasn't that long
ago.

The two printers that were failing were:
Infoprint 1870 MFP
IBM_4312

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719761: brltty errors fill daemon.log

[Brent S. Elmer Ph.D.]

On Thu, 2013-08-15 at 15:26 +0200, Mario Lang wrote:
 Brent S. Elmer webe...@aim.com writes:
 
  Package: brltty
  Version: 4.5-2
  Severity: normal
 
  My daemon.log file filled /var/log.  The following brltty errors appeared 
  over
  and over making the file huge:
 
 
 [...]
 
  Jun 23 07:37:14 sanctuary brltty[1256]: bm braille driver version 4.5@5477 
  does
  not match expected version 4.4@5477
 
 You seem to have a mix of brltty 4.5 and 4.4 installed on your system.
 Did you previously perhaps manually compile and install brltty?
 

No, I have not manually done anything with brltty.  I have no need for
brltty.  In fact I have never intentionally installed it.  It must have
been installed with the installation and upgraded at some point during
an upgrade all in Synaptic.  I have removed brltty from my system to
stop the errors.

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#710172: probably gtk upgrade that breaks Evolution

[Brent S. Elmer Ph.D.]

I just upgraded some packages on another machine.  Scrolling was working
in the evolution preview window with the mouse wheel before the
following upgrade and broken after.  I was not able to narrow it down
further since it seems like all of these upgrades depend on each other.
I'm guessing it is the libgtk-3-0 that breaks it.

Commit Log for Mon Jul 15 13:58:31 2013


Upgraded the following packages:
cups (1.5.3-5) to 1.6.2-10
cups-bsd (1.5.3-5) to 1.6.2-10
cups-client (1.5.3-5) to 1.6.2-10
cups-common (1.5.3-5) to 1.6.2-10
cups-filters (1.0.18-2.1) to 1.0.34-3
gnome-themes-standard (3.4.2-2.1) to 3.8.1-2
gnome-themes-standard-data (3.4.2-2.1) to 3.8.1-2
libcups2 (1.5.3-5) to 1.6.2-10
libcupscgi1 (1.5.3-5) to 1.6.2-10
libcupsimage2 (1.5.3-5) to 1.6.2-10
libcupsmime1 (1.5.3-5) to 1.6.2-10
libcupsppdc1 (1.5.3-5) to 1.6.2-10
libgail-3-0 (3.4.2-6) to 3.8.2-3
libgtk-3-0 (3.4.2-6) to 3.8.2-3
libgtk-3-bin (3.4.2-6) to 3.8.2-3
libgtk-3-common (3.4.2-6) to 3.8.2-3

Installed the following packages:
at-spi2-core (2.9.3-1)
cups-daemon (1.6.2-10)
cups-server-common (1.6.2-10)
libatk-bridge2.0-0 (2.9.3-1)
libatspi2.0-0 (2.9.3-1)
libfontembed1 (1.0.34-3)
libqpdf10 (4.1.0-2)

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#714593: same here

[Brent S. Elmer Ph.D.]

This bug hit me too.  This is a really bad bug.  This also makes me
quite disappointed at how fragile gnome-shell is.  How can a seemingly
minor application like bluetooth totally break gnome-shell?  The first
computer this happened on didn't even have a bluetooth device yet if I
try to remove gnome-bluetooth, it wants to remove a lot of other
applications I need.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#712668: initramfs-tools broken with latest move to jessie

[Brent S. Elmer Ph.D.]

On Tue, 2013-06-18 at 13:54 +0100, Ben Hutchings wrote:
 Control: reassign -1 plymouth
 

  When I try and do a reinstall of initramfs-tools in synaptic,
  I get the following error:
  
  E: Internal Error, No file name for initramfs-tools:i386
  
  Something appears to be badly broken.
 
 That sounds like a bug in synaptic, but you'll have to report that
 separately.
 
 Ben.
 

I created a separate report for synaptic. The number is 712678

Brent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#605434: emacs created .ps fine in ps viewers

[Brent S. Elmer Ph.D.]

The emacs created .ps file not only works fine in ps2pdf, it also views
fine in .ps file viewers like Evince and emacs docview.  It seems that
cups is the only place where it doesn't work.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#685764: black title bar on windows after metacity upgrade

[Brent S. Elmer Ph.D.]

On Fri, 2012-08-24 at 08:36 -0400, Brent S. Elmer wrote:
 Package: metacity
 Version: 1:2.34.3-3
 Severity: important
 
 I upgraded metacity on my wheezy box yesterday.  After the upgrade and after
 rebooting, all of my windows in gnome have black title bars and I can't see 
 the
 minimize or maximize buttons.  There is a lot of errors in .xsession-errors.
 

I downgraded several packages that were upgraded yesterday using debian
snapshot.  Then I started upgrading some of the packages again rebooting
in between to see when the title bars turn black.  The title bars turned
black after this set of packages was upgraded.  They all seem to be
dependent on each other so I can't narrow it down any farther.

Upgraded the following packages:
libgail-3-0 (3.4.2-2) to 3.4.2-3
libgtk-3-0 (3.4.2-2) to 3.4.2-3
libgtk-3-0-dbg (3.4.2-2) to 3.4.2-3
libgtk-3-bin (3.4.2-2) to 3.4.2-3
libgtk-3-common (3.4.2-2) to 3.4.2-3


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#685764: black title bar on windows after metacity upgrade

[Brent S. Elmer Ph.D.]

On Fri, 2012-08-24 at 15:40 +0200, Michael Biebl wrote:
 On 24.08.2012 15:32, Brent S. Elmer Ph.D. wrote:
  On Fri, 2012-08-24 at 08:36 -0400, Brent S. Elmer wrote:
  Package: metacity
  Version: 1:2.34.3-3
  Severity: important
 

 Which version of gnome-shell and (lib)mutter do you have installed?
 
I have a back level gnome-shell and (lib)mutter(3.2.2.1) do to issues
that later versions of gnome-shell were having with my radeon graphics
card(bug 670097).  I am afraid to upgrade gnome-shell on my work laptop
because there are so many dependencies and if the freezing comes back it
is hard to get everything downgraded to stop the freezes.  The 3.2.2.1
versions do not have the freezing bug 670097.  
  
 You can try re-applying
 debian/patches/070_revert-widget-set-up-signals-after-initializing.patch
 from 3.4.2-2 [1]
 
 
 [1]
 http://anonscm.debian.org/viewvc/pkg-gnome/tags/gtk%2B3.0/3.4.2-1/debian/patches/070_revert-widget-set-up-signals-after-initializing.patch?revision=34775view=co


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#685764: black title bar on windows after metacity upgrade

[Brent S. Elmer Ph.D.]

On Fri, 2012-08-24 at 16:10 +0200, Michael Biebl wrote:
 On 24.08.2012 16:07, Michael Biebl wrote:
 
  I would suggest you upgrade mutter/gnome-shell (i.e. everything) to 3.4.

That didn't work too well.  When I upgraded everything to 3.4 and reboot
the computer just to make sure, when I log into gnome, everything looks
like it is a really old gtk blocky look.  I remember having this problem
on this computer or another one recently but I don't remember how I
fixed it.  This is no good at all.

Here is what is in my .xsession-errors now:

/etc/gdm3/Xsession: Beginning session setup...
localuser:brente being added to access control list
GNOME_KEYRING_CONTROL=/home/brente/.cache/keyring-zS48BE
GNOME_KEYRING_CONTROL=/home/brente/.cache/keyring-zS48BE
GNOME_KEYRING_CONTROL=/home/brente/.cache/keyring-zS48BE
GPG_AGENT_INFO=/home/brente/.cache/keyring-zS48BE/gpg:0:1
SSH_AUTH_SOCK=/home/brente/.cache/keyring-zS48BE/ssh
GNOME_KEYRING_CONTROL=/home/brente/.cache/keyring-zS48BE
GPG_AGENT_INFO=/home/brente/.cache/keyring-zS48BE/gpg:0:1

(gnome-settings-daemon:6168): color-plugin-WARNING **: There is no
colord server available

(gnome-settings-daemon:6168): updates-plugin-WARNING **: state unknown:
0

(gnome-settings-daemon:6168): PackageKit-WARNING **: failed to set
proxy: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6168): PackageKit-WARNING **: failed to set root:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6168): updates-plugin-WARNING **: failed to set
proxies: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6168): updates-plugin-WARNING **: failed to set
install root: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.PackageKit was not provided by any .service files
gnome-session[6099]: WARNING: Application
'gnome-settings-daemon.desktop' killed by signal 11

(gnome-settings-daemon:6223): color-plugin-WARNING **: There is no
colord server available

(gnome-settings-daemon:6223): updates-plugin-WARNING **: state unknown:
0

(gnome-settings-daemon:6223): PackageKit-WARNING **: failed to set
proxy: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6223): PackageKit-WARNING **: failed to set root:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6223): updates-plugin-WARNING **: failed to set
proxies: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.PackageKit was not provided by any .service files

(gnome-settings-daemon:6223): updates-plugin-WARNING **: failed to set
install root: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.PackageKit was not provided by any .service files
gnome-session[6099]: WARNING: Application
'gnome-settings-daemon.desktop' killed by signal 11
gnome-session[6099]: WARNING: Failed to start app: Unable to start
application: Failed to execute child process padevchooser (No such
file or directory)

(process:6257): GLib-WARNING
**: 
/build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/goption.c:2179:
 ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in 
entry (null):version

(process:6257): GLib-WARNING
**: 
/build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/goption.c:2179:
 ignoring no-arg, optional-arg or filename flags (32) on option of arg-type 1 
in entry (null):daemon

(process:6257): GLib-WARNING
**: 
/build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/goption.c:2179:
 ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in 
entry (null):no-daemon

(process:6257): GLib-WARNING
**: 
/build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/goption.c:2179:
 ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in 
entry (null):secret-mode
Failed to play sound: File or data not found
** Message: applet now removed from the notification area

** (zeitgeist-datahub:6255): WARNING **:
recent-manager-provider.vala:133: Desktop file for
file:///home/brente/P1030527.JPG was not found, exec: firefox-bin,
mime_type: image/jpeg

** (zeitgeist-datahub:6255): WARNING **:
recent-manager-provider.vala:133: Desktop file for
file:///home/brente/atp_home/tests/hub_inv/input/hub_inventory.msg was
not found, exec: notes.bin, mime_type: application/octet-stream

** (zeitgeist-datahub:6255): WARNING **:
recent-manager-provider.vala:133: Desktop file for
file:///home/brente/resume.pdf was not found, exec: firefox-bin,
mime_type: application/pdf
** Message: applet now embedded in 

Bug#685764: fixed ugly gnome

[Brent S. Elmer Ph.D.]

I found a way to fix the ugly old gtk look as from this link:
http://askubuntu.com/questions/88154/how-can-i-restore-a-broken-theme-in-gnome-shell

I removed ~/.config/dconf/ and re logged in and gnome looked right
again.

Now hopefully gnome-shell won't freeze as it was before when I tried
3.4.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#679918: Revertinig to gnome-shell 3.2.2.1 fixes it

[Brent S. Elmer Ph.D.]

I reverted back to gnome-shell 3.2.2.1 and I no longer get the Oh no!
message or the old gtk look.  There is some kind of problem with the
newer gnome-shell or its dependencies with the radeon X driver.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#676984: exim 4 upgrade breaks Python smtplib

[Brent S. Elmer Ph.D.]

I upgraded exim4 in wheezy this morning and I am getting the same
gnome-keyring error as in this bug report.  I am getting the error in a
Python program that uses smtplib to send email.  I used the snapshot
directory to downgrade the exim4 packages in wheezy before today and the
problem went away.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674026: Links in plain text emails still work

[Brent S. Elmer Ph.D.]

I noticed that links that are in plain text emails still work in
evolution.  Most email is not plain text anymore though.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#670097: downgrading gnome-shell seems to help

[Brent S. Elmer Ph.D.]

On May 15 I upgraded gnome-shell and dependent modules.  That
corresponds to when gnome-shell started freezing.  gnome-shell was
freezing several times a day on my laptop.  It has been a day and a half
since downgrading and I have not had any freezes so far.

Here is what I had to do to downgrade after adding the snapshot
repository:

apt-get install gnome-shell=3.2.2.1-2 gnome-shell-common=3.2.2.1-2
libcogl5 libclutter-1.0-0=1.8.4-1 libcogl-pango0=1.8.2-1
gir1.2-clutter-1.0=1.8.4-1 gir1.2-mutter-3.0=3.2.2-1 libmutter0=3.2.2-1

Unfortunately, the downgrade removed evolution before I realized it.
Eventually, I got time to figure out what needed to be downgraded to get
evolution back.  Here is what I had to do to downgrade evolution:

apt-get install evolution=3.2.2-1 evolution-data-server=3.2.2-1
evolution-plugins=3.2.2-1 libclutter-gtk-1.0-0=1.0.4-1
libevolution=3.2.2-1 libmx-1.0-2=1.4.5-1 libcamel-1.2-29=3.2.2-1
evolution-data-server-common=3.2.2-1 libclutter-imcontext-0.1-0=0.1.4-2
libcluttergesture-0.0.2-0=0.0.2.1-6






-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#670097: gnome-shell: random hang causes data loss

[Brent S. Elmer Ph.D.]

I have had this problem on two different computers starting in the last
day or two.  Both are running Wheezy and I generally apply updates
daily.  One of the computers is a Lenovo w500 laptop with a radeon video
card and I am using the free radeon video driver.  The other is a
desktop with an Nvidia card and I am using the proprietary Nvidia video
driver.  The laptop is my work laptop and froze 3 times yesterday and
has frozen twice already today.  When this happens, the image on the
screen freezes.  I can move the mouse and see it moving around the
screen.  I can do ctl-alt-f1 ... to get to other terminals.  When I log
in from the terminal and do a top, nothing is taking excessive CPU or
anything.  One time I left the screen frozen while I ate lunch to see if
it ever would come back but it didn't.  I can do ctl-alt-backspace to
restart X and I am brought to the login screen where I can log in again
and work for a while until it freezes again.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#659029: duplicate/outdated icons in applications menu

[Brent S. Elmer Ph.D.]

I have gotten rid of the .desktop files in ~/.local/share/applications
and ~/.local/share/applications/menu-xdg.  I had already uninstalled
menu-xdg as postings on the web had said that that would help with the
duplicate icons.  I never intentionally put any of these .desktop files
in these directories.  These files must have been put there during the
normal install process.  Removing these .desktop files removed all of
the cruft from the other menu.  I still think there is some kind of a
problem here as a normal user would not know to look for the .desktop
files to get rid of them.  A clean install probably wouldn't have the
cruft.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#659029: duplicate/outdated icons in applications menu

[Brent S. Elmer Ph.D.]

On Tue, 2012-02-07 at 16:21 +0100, Michael Biebl wrote:

 
 Do you have outdated desktop files in /usr/local/share/applications or
 ~/.local/share/applications/?

I removed all ~/.local/share/applications and
~/.local/share/applications/menu-xdg
 
 Do you have the Debian menu enabled (which would explain the duplicate
 entries)? The default is off. Have a look at ~/.config/menus/
 
I don't have the debian menu enabled anymore.

 
 What kind of hardware do you have (it takes at most 2-3 secs here when I
 initially open the Applications tab, subsequent it is almost instantaneous).
 
 I have to acknowledge know, that I rarely use the Application menu and
 got really used to the builtin search
 
 

The computer that is taking several minutes is an older computer AMD
1800+, Nvidia 7800GS.  I haven't cleaned out the .desktop files on that
one yet.

The computer that I cleaned out the .desktop files is a Lenovo w500.
After cleaning out the .desktop files, it is now responsive.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#653467: gtkpod: cannot mount ipod(Critical error)

[Brent S. Elmer Ph.D.]

On Mon, 2012-01-09 at 10:41 +0100, Matteo F. Vescovi wrote:
 tags 653467 + unreproducible
 thanks
 --
 
 Hi!
 
 Any news?
 
 I've asked a friend of mine to test the same situation with an iPod 
 Shuffle like yours and he didn't get that weird message.
 
 Let me know something, or I'll consider this as a casual bug and close 
 it in few days, if you can't provide any useful information.
 
 Thanks for your time.
 

For some reason I didn't get your previous response or it got deleted.

I haven't plugged in my ipod for quite a while so I can't tell you for
sure when it worked the last time.  It may have been a year or so, maybe
longer.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#638012: still a problem

[Brent S. Elmer Ph.D.]

This is still a problem.  Is it going to be addressed?




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#563682: [shutter] window screenshot fails

[Brent S. Elmer Ph.D.]

I just tried Shutter again.  I tried a window, selection, and full
screen.  All of them worked.  I didn't have to do anything other than
start shutter and take the screenshots.  I am currently using the latest
version in Wheezy.  It looks like the problem was fixed although the
version number is not that much higher.  The version in the bug report
was 85.1-1.  The version I am running now is 85.1-2.  I didn't check the
differences in all of the dependencies.  I guess it doesn't matter what
fixed it.

Thanks,
Brent
On Mon, 2011-12-12 at 00:19 -0800, Ryan Niebur wrote:
 Hello Brent,
 
 On Mon, Jan 04, 2010 at 11:04:57AM -0500, Brent S. Elmer Ph.D. wrote:
  Taking a screenshot of a window fails in shutter.  When I try to take a 
  screenshot of a window 
  the shutter window just goes away.
  
  Here is the information in the terminal when I run shutter from the command 
  line and try to 
  take a screenshot of a window.
  
 
 Does the following reply from Mario Kemper, the author of Shutter,
 help you with this issue? This might help to determine the bug here.
 It could also be helpful to try the new upstream version which I have
 just uploaded to unstable.
 
 Thanks,
 Ryan
 
 On Wed, Aug 25, 2010 at 03:46:11PM +0200, Mario Kemper wrote:
   Could you please execute this via terminal (disables xserver's
  access control):
  
  xhost +
  
  
  Are you able to capture a window after doing this?
  
  
  Note: Please undo the above command when finished!
  
  xhost -
  
  
 





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642312: unhandled exception importing SHA26

[Brent S. Elmer Ph.D.]

On Wed, 2011-09-21 at 08:58 -0400, Brent S. Elmer wrote:
 Package: winpdb
 Version: 1.4.8-1
 Severity: grave
 
 When I try to debug a python program in winpdb, I get an unhandled exception
 importing SHA26.
 
 The following line is causing the problem:
 
 from Crypto.Hash import SHA256
 
 in the file /usr/share/pyshared/Crypto/Random/Fortuna/SHAd256.py
 
 It looks like there is no SHA256.so.
 

Actually, SHA256 is there because the program runs outside of winpdb and
also runs in pdb.  The problem seems to be that winpdb doesn't find it.
It seems like winpdb does not use the same PYTHONPATH or PATH or
something.  




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642312: unhandled exception importing SHA26

[Brent S. Elmer Ph.D.]

On Wed, 2011-09-21 at 15:14 +0200, Bernd Zeimetz wrote:
 severity 642312 normal
 tags 642312 unreproducible moreinfo
 thanks
 
 On 09/21/2011 02:58 PM, Brent S. Elmer wrote:
  Package: winpdb
  Version: 1.4.8-1
  Severity: grave
  
  When I try to debug a python program in winpdb, I get an unhandled exception
  importing SHA26.
 
 What about showing us the exception?
 Also please explain what you did to trigger it.
 
 

I start winpdb from the command line like this:

$ winpdb atp.py

winpdb starts up.  I click on the go button then I get the following
exception:

cannot import name SHA256


The problem seems to be that winpdb doesn't know where SHA256 is.  It is
using a different python or PYTHONPATH or PATH than is used when just
running the python program directly from the terminal or running pdb
from the terminal.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642312: unhandled exception importing SHA26

[Brent S. Elmer Ph.D.]

On Wed, 2011-09-21 at 15:14 +0200, Bernd Zeimetz wrote:

 Works all fine here. You'll have to explain why you think there is a bug.
 
 
 Cheers,
 
 Bernd
 

Try creating a python program with the following:

from Crypto import Random

Then run winpdb on that python program and see if you can reproduce the
problem.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640046: [Evolution] Bug#640046: FAILED message when Migrating local user data

[Brent S. Elmer Ph.D.]

On Thu, 2011-09-01 at 23:55 +0200, Yves-Alexis Perez wrote:
 On jeu., 2011-09-01 at 15:13 -0400, Brent S. Elmer wrote:
  Package: evolution
  Version: 3.0.2-1
  Severity: normal
  
  When I start evolution from the command line, I get the following
  failure
  message:
  
  Migrating cached data
  Migrating config data
  Migrating local user data
rmdir /home/brente/.evolution/tasks
FAILED: Directory not empty (contents follows)
tasks
  
  Did something not work right in the 3.0 migration?  Should I just
  delete the
  tasks directory? 
 
 Afair this is a way older migration. You should be able to move tasks
 elsewhere or remove it if it has been correctly migrated.
 
 Regards,

I removed the tasks directory and the FAILED message went away.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640043: [Evolution] Bug#640043: missing dependency libcanberra-gtk-module

[Brent S. Elmer Ph.D.]

On Thu, 2011-09-01 at 23:58 +0200, Yves-Alexis Perez wrote:
 On jeu., 2011-09-01 at 15:09 -0400, Brent S. Elmer wrote:
  When I run evolution from the command line, I get the following error:
  
  Gtk-Message: Failed to load module canberra-gtk-module
  
 And does it prevent evolution to start? Because I don't have
 libcanberra-gtk3-module installed here and it works fine, and I don't
 have any message.
 
 Regards,

No, it does not prevent evolution from starting.

Maybe the library is needed by evolution-plugins which I have installed.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640043: [Evolution] Bug#640043: missing dependency libcanberra-gtk-module

[Brent S. Elmer Ph.D.]

On Fri, 2011-09-02 at 14:36 +0200, Yves-Alexis Perez wrote:
 On ven., 2011-09-02 at 08:35 -0400, Brent S. Elmer Ph.D. wrote:
  Maybe the library is needed by evolution-plugins which I have
  installed.
 
 I have it installed too and it doesn't show the message, but you may be
 right. In the plugins, is “Mail notifications” enabled and is “play
 sound” enabled?
 
 Regards,


Yes, Mail notifications and play sound are enabled.
Maybe the library should at least be a suggested or recommended
dependency for evolution-plugins.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640000: NEWS or README might be a good idea

[Brent S. Elmer Ph.D.]

Sure I read the message.  I don't recall anything about having duplicate
folders or which one is the good one and what to do after verifying the
conversion went okay.  I also looked in the README and NEWS files.
Nothing was mentioned there either.  It would probably be a good idea to
put something in the README.  Evolution is so flaky anyway it is hard to
tell what works as intended and what is broken.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#640043: missing dependency libcanberra-gtk-module(Correction)

[Brent S. Elmer Ph.D.]

On Thu, 2011-09-01 at 15:09 -0400, Brent S. Elmer wrote:
 Package: evolution
 Version: 3.0.2-1
 Severity: normal
 
 When I run evolution from the command line, I get the following error:
 
 Gtk-Message: Failed to load module canberra-gtk-module
 
 Installing libcanberra-gtk-module makes the error go away.
 
 Should libcanberra-gtk-module be a dependency or suggested or something?
 
 
 


Correction

Installing libcanberra-gtk3-module makes the error go away.
libcanberra-gtk-module was already installed.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631997: linux-image-2.6.39-2-486: black screen after grub menu

[Brent S. Elmer Ph.D.]

On Wed, 2011-06-29 at 04:22 +0100, Ben Hutchings wrote:
 On Tue, 2011-06-28 at 23:12 -0400, Wendy Elmer wrote:
 [...]
  I will try the earlier versions when I get a chance.  It may not be
  very soon since that computer is at my church and I will be on
  vacation for a week.  By the way, since I will be using snapshot, is
  there a config file for APT that I can put something to handle the
  snapshots being expired?  See bug 595801.  It is a pain when going to
  snapshot in synaptic and getting the release file expired message.  I
  drop out to the command line and do apt-get -o
  'Acquire::Check-Valid-Until=false' update from the command line to get
  around it.
 
 Sorry, I have no better idea.
 
  recovery mode does not work either.  Still an endless black screen
  after grub with no messages from the kernel.
 
 What processor and how much RAM does this systeam have?
 
 Ben.
 

It is an AMD Athlon 850 MHZ.  It is maxed out at a whopping 256 MB ram.
It is an old HP computer which has very oddball hardware that I am
trying to keep crippling along because the church doesn't have the money
to buy a better one.  The reason I am running the old custom kernel is
because it has an oddball conexant riptide sound card that I have to
special handle in the kernel build(3rd party driver and firmware) in
order to make it work and it is a pain.

Brent





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631294: [udev] upgrade from udev 167-3 to 170-1 broke system(no mouse or keyboard)

[Brent S. Elmer Ph.D.]

Package: udev
Version: 170-1
Severity: critical

--- Please enter the report below this line. ---
I have a wheezy box that I upgraded udev from 167-3 to 170-1 last week when the 
new udev package hit testing.
After the upgrade, I have no mouse or keyboard when X starts.  Now that the new 
udev is installed I do see that kernel 2.6.32 is required.
The 167 version required kernel version 2.6.27.  I have kernel 2.6.30 
installed.  
At boot, I see a message saying udev requires kernel  2.6.32 not started.  
In Xorg.0.log it says The server relies on udev to provide the list of input 
devices.  
If no devices become available, reconfigure udef or disable AutoAddDevices.  
I found how to disable AutoAddDevices in xorg.conf.  
I'm not sure if I did it right but now in Xorg.0.log I see messages like failed 
to load module kbd and failed to 
load module mouse instead of the previous message saying udev would provide the 
list of input devices.
The problem is that it seems that a lot of things don't work.  I see messages 
during boot 
like error fetching interface information: Device not found.  I'm not sure if 
the network is working.  The keyboard does work 
when I boot into single user/recovery mode.  

Is there some way I can recover from this given that I can get into recover 
mode?  What are some things I can try?

Note: this report is being sent from a different computer so the system 
information below is not for the computer that has the problem.
The problem computer was up to date for wheezy/testing as of 6-17-2011 when the 
new udev was installedexcept for a 2.6.30 kernel.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38

Debian Release: wheezy/sid
  500 testing www.debian-multimedia.org 
  500 testing debian.linux.ibm.com 
  500 stable  security.debian.org 
  500 squeeze www.lamaresh.net 
  500 karmic  ppa.launchpad.net 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libc6(= 2.10) | 2.13-4
libselinux1  (= 1.32) | 2.0.98-1+b1
libudev0 (= 171-1) | 171-1
lsb-base(= 3.0-6) | 3.2-27
util-linux   (= 2.16) | 2.17.2-9.1


Recommends  (Version) | Installed
=-+-===
usbutils  | 1:001-1
pciutils  | 1:3.1.7-9


Package's Suggests field is empty.








-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631294: [udev] upgrade from udev 167-3 to 170-1 broke system(no mouse or keyboard)

[Brent S. Elmer Ph.D.]

On Wed, 2011-06-22 at 20:36 +0200, Marco d'Itri wrote:
 retitle 631294 in some situations, preinst does not check the required kernel 
 version
 severity 631294 important
 thanks
 
 On Jun 22, Brent S. Elmer Ph.D. webe...@aim.com wrote:
 
  The 167 version required kernel version 2.6.27.  I have kernel 2.6.30 
  installed.  
  At boot, I see a message saying udev requires kernel  2.6.32 not started.  
 This is clearly the problem: you need to upgrade your kernel.
 

Yes, but how do I start in a mode that will have networking working but
not start X?  Once X starts, I can't do anything.  It seems that single
user/recovery mode in the grub menu does not start networking.  In the
udev dependencies, it says it breaks linux-image-2.6-* (2.6.28).
Shouldn't that be  2.6.32?  Any help would be appreciated to get out of
this without having to reinstall the computer.

Brent






-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#630513: [Evolution] Bug#630513: two Inboxs for imap, messages not staying marked read

[Brent S. Elmer Ph.D.]

On Thu, 2011-06-16 at 15:30 +0200, Yves-Alexis Perez wrote:

 
 It might be worth trying with IMAP+ backend (or IMAP, in case you
 already uses IMAP+). It doesn't sound familiar, but you might want to
 check on bugzilla.gnome.org, on evolution and evolution-data-server
 components.
 
 Regards,

IMAP+ seems to be working better.  I still have the two inboxes.  I have
noticed that sometimes the two inboxes show different unread message
counts.  It kind of looks like that the first Inbox message count is
showing the unread count on the imap server and the second Inbox message
count is showing the unread count locally.  I do not have the setting on
to automatically synchronize remote mail locally.  When I click on
send/receive, the first Inbox unread message count goes to the same
number as the second as if synchronizing the local and the server.
Could the two inboxes be some kind of new feature where one represents
the server and one local? Is evolution copying all of the messages
locally even though I don't have the option turned on?  How could I
tell?  The other day the first Inbox was not showing any unread messages
so it is hard to figure out patterns.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#630513: [Evolution] Bug#630513: two Inboxs for imap, messages not staying marked read

[Brent S. Elmer Ph.D.]

On Thu, 2011-06-16 at 15:30 +0200, Yves-Alexis Perez wrote:

 
 It might be worth trying with IMAP+ backend (or IMAP, in case you
 already uses IMAP+). It doesn't sound familiar, but you might want to
 check on bugzilla.gnome.org, on evolution and evolution-data-server
 components.
 
 Regards,

I have had issues in the past with IMAP+ not being able to display some
messages.  I am trying IMAP+ again.  I still see 2 inboxes but messages
are being marked as read and staying that way with IMAP+.  However,
neither IMAP or IMAP+ ever has the correct unread message count in
parenthesis next to Inbox.  Currently with IMAP+ the first Inbox has no
unread count in paranthesis and the second Inbox has (80) which doesn't
seem to change as messages are being read.  The unread message count has
always been a problem in evolution.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#628968: [reportbug] reportbug crashes with assertion failed

[Brent S. Elmer Ph.D.]

Package: reportbug
Version: 5.1.1
Severity: normal

--- Please enter the report below this line. ---
reportbug won't let me submit a bug report.  It crashes with the following:

Gdk:ERROR:/build/buildd-gtk+2.0_2.24.4-3-i386-ouUeDk/gtk+2.0-2.24.4/gdk/gdkregion-generic.c:1114:miUnionNonO:
 assertion failed: (r-x1  r-x2)
Aborted

I am trying to submit a bug report for python-gtk2.  I enter python-gtk2 for 
the package and it queries for previous bugs and displays them.
I click on Continue and it crashes.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38.110412

Debian Release: wheezy/sid
  500 testing www.debian-multimedia.org 
  500 testing debian.linux.ibm.com 
  500 stable  security.debian.org 
  500 squeeze www.lamaresh.net 
  500 karmic  ppa.launchpad.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
python (= 2.5) | 2.6.6-14
apt | 0.8.14.1
python-reportbug  (= 5.1.1) | 5.1.1


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-
postfix  | 
 OR exim4| 4.76-1
 OR mail-transport-agent | 
gnupg| 1.4.11-3
 OR pgp  | 
debconf-utils ( 1.1.0) | 
debsums  (= 2.0.47) | 
file   ( 1.30) | 5.04-5+b1
dlocate  | 1.02
python-urwid | 
python-gtk2  | 2.24.0-1
python-vte   | 1:0.24.3-2+b1
python-gtkspell  | 2.25.3-9
xdg-utils| 1.1.0~rc1-2
emacs22-bin-common   | 
 OR emacs23-bin-common   | 23.3+1-1



--- Output from package bug script ---
** Environment settings:
EDITOR=emacs

** /home/brente/.reportbugrc:
reportbug_version 4.10.2
mode expert
ui gtk2
email webe...@aim.com
no-cc
header X-Debbugs-CC: webe...@aim.com
smtphost reportbug.debian.org





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#628969: [python-gtk2] frequent glibc crashes

[Brent S. Elmer Ph.D.]

Package: python-gtk2
Version: 2.24.0-1
Severity: normal

--- Please enter the report below this line. ---
I have been starting to get glibc errors lately in a python-gtk application.  
Usually it has been a *** glibc detected *** ... double free with no backtrace.
This time it is a corrupted double-linked list with a backtrace.  It doesn't 
seem to be reproducible with any particular pattern.
It seems to be more random.

*** glibc detected *** /usr/bin/python2.6: corrupted double-linked list: 
0xb158f170 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6(+0x6aaa1)[0xb7532aa1]
/lib/i686/cmov/libc.so.6(+0x701d3)[0xb75381d3]
/lib/i686/cmov/libc.so.6(realloc+0xdd)[0xb753848d]
/lib/libglib-2.0.so.0(g_realloc+0x3a)[0xb70f131a]
/lib/libglib-2.0.so.0(g_realloc_n+0x8a)[0xb70f168a]
/usr/lib/libgdk-x11-2.0.so.0(+0x2cdc9)[0xb69eedc9]
/usr/lib/libgdk-x11-2.0.so.0(+0x2dc4d)[0xb69efc4d]
/usr/lib/libgdk-x11-2.0.so.0(gdk_region_union+0x88)[0xb69f0548]
/usr/lib/libgdk-x11-2.0.so.0(+0x37ffc)[0xb69f9ffc]
/usr/lib/libgdk-x11-2.0.so.0(+0x382ba)[0xb69fa2ba]
/usr/lib/libgdk-x11-2.0.so.0(+0x383ce)[0xb69fa3ce]
/usr/lib/libgdk-x11-2.0.so.0(+0x3848b)[0xb69fa48b]
/usr/lib/libgtk-x11-2.0.so.0(+0x15d555)[0xb6bba555]
/usr/lib/libgtk-x11-2.0.so.0(+0x15f62a)[0xb6bbc62a]
/usr/lib/libgtk-x11-2.0.so.0(+0x164a56)[0xb6bc1a56]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__BOXED+0x88)[0xb71aa7e8]
/usr/lib/libgobject-2.0.so.0(+0xc347)[0xb718c347]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xc0)[0xb718d920]
/usr/lib/libgobject-2.0.so.0(+0x200fe)[0xb71a00fe]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x806)[0xb71a93f6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x32)[0xb71a95a2]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_size_allocate+0x15b)[0xb6cd649b]
/usr/lib/libgtk-x11-2.0.so.0(+0x78880)[0xb6ad5880]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__BOXED+0x88)[0xb71aa7e8]
/usr/lib/libgobject-2.0.so.0(+0xc347)[0xb718c347]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xc0)[0xb718d920]
/usr/lib/libgobject-2.0.so.0(+0x200fe)[0xb71a00fe]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x806)[0xb71a93f6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x32)[0xb71a95a2]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_size_allocate+0x15b)[0xb6cd649b]
/usr/lib/libgtk-x11-2.0.so.0(+0x28551e)[0xb6ce251e]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__BOXED+0x88)[0xb71aa7e8]
/usr/lib/libgobject-2.0.so.0(+0xc347)[0xb718c347]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x192)[0xb718d9f2]
/usr/lib/libgobject-2.0.so.0(+0x200fe)[0xb71a00fe]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x806)[0xb71a93f6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x32)[0xb71a95a2]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_size_allocate+0x15b)[0xb6cd649b]
/usr/lib/libgtk-x11-2.0.so.0(gtk_container_resize_children+0x7f)[0xb6b0fedf]
/usr/lib/libgtk-x11-2.0.so.0(+0x285a24)[0xb6ce2a24]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x7c)[0xb71a9d6c]
/usr/lib/libgobject-2.0.so.0(+0xc347)[0xb718c347]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x192)[0xb718d9f2]
/usr/lib/libgobject-2.0.so.0(+0x2078d)[0xb71a078d]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x806)[0xb71a93f6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x32)[0xb71a95a2]
/usr/lib/libgtk-x11-2.0.so.0(gtk_container_check_resize+0x8a)[0xb6b0fb9a]
/usr/lib/libgtk-x11-2.0.so.0(+0xb2e40)[0xb6b0fe40]
/usr/lib/libgdk-x11-2.0.so.0(+0x17368)[0xb69d9368]
/lib/libglib-2.0.so.0(+0x3ea41)[0xb70e5a41]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1d2)[0xb70ea252]
/lib/libglib-2.0.so.0(+0x43a30)[0xb70eaa30]
/lib/libglib-2.0.so.0(g_main_loop_run+0x183)[0xb70eb0f3]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9)[0xb6b99bd9]
/usr/lib/python2.6/dist-packages/gtk-2.0/gtk/_gtk.so(+0x16b43f)[0xb6fac43f]
/usr/bin/python2.6(PyEval_EvalFrameEx+0x44d0)[0x80e08c0]
/usr/bin/python2.6(PyEval_EvalFrameEx+0x5437)[0x80e1827]
/usr/bin/python2.6(PyEval_EvalCodeEx+0x848)[0x80e2968]
/usr/bin/python2.6(PyEval_EvalCode+0x57)[0x80e2a67]
/usr/bin/python2.6(PyRun_FileExFlags+0x9f)[0x8104d7f]
/usr/bin/python2.6[0x80d9b13]
/usr/bin/python2.6(PyEval_EvalFrameEx+0x4658)[0x80e0a48]
/usr/bin/python2.6(PyEval_EvalCodeEx+0x848)[0x80e2968]
=== Memory map: 
08048000-08235000 r-xp  08:09 946/usr/bin/python2.6
08235000-08284000 rw-p 001ed000 08:09 946/usr/bin/python2.6
08284000-0828d000 rw-p  00:00 0 
09384000-09e6 rw-p  00:00 0  [heap]
afb0-afb7d000 rw-p  00:00 0 
afb7d000-afc0 ---p  00:00 0 
afce-afcfc000 r-xp  08:02 5461   /lib/libgcc_s.so.1
afcfc000-afcfd000 rw-p 0001b000 08:02 5461   /lib/libgcc_s.so.1
afcfd000-afcfe000 ---p  00:00 0 
afcfe000-b04fe000 rw-p  00:00 0 
b04fe000-b04ff000 ---p  00:00 0 
b04ff000-b0cff000 rw-p  00:00 0 
b0cff000-b0d0 ---p  00:00 0 
b0d0-b150 rw-p  00:00 0 
b150-b1591000 rw-p  00:00 0 
b1591000-b160 ---p  

Bug#618861: always hangs on initial startup if proxy on

[Brent S. Elmer Ph.D.]

It looks like the proxy can't be on at all when initially starting
evolution.  If the proxy is on on initial evolution startup, evolution
will hang forever saying 0% complete on retrieving and displaying
messages.  It seems that if evolution is started without the proxy and
everything starts up, then the proxy can be turned on and evolution will
retrieve mail through the proxy.  This is a severe regression from the
previous version.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#605434: narrowed it down to version 1.4.4-5

[Brent S. Elmer Ph.D.]

Using the debian snapshot repository, I have narrowed the issue down to
the breakage occurring in version 1.4.4-5 as version 1.4.4-4 works.
There are only two changes in that version according to the changelog:

cups (1.4.4-5) unstable; urgency=low

  [ Martin Pitt ]
  * ubuntu-upstart.dpatch: Drop the dependency on starting smbd, it
causes
samba to hang on package upgrades or manual restarts. There doesn't
seem
to be a good way to express this dependency right now. (LP: #639768)
Instead, send a SIGHUP to smbd if it is running, which causes it to
reload
printers.

  [ Till Kamppeter ]
  * pstops-based-workflow-only-for-printing-ps-on-a-ps-printer.dpatch:
Let CUPS use the former PostScript-based filter chain only if the
input
file is PostScript and the printer is a PostScript printer with
manufacturer-supplied PPD file. This avoids ugly PS-PDF-PS
conversions
which are bad for the performance and sometimes cause issues
(Closes: #593338, requested by Ricoh).

 -- Martin Pitt mp...@debian.org  Thu, 16 Sep 2010 18:57:06 +0200


It looks like the second change by Till Kamppeter is what killed the
ps-print from emacs.  I don't know if this is an emacs or cups problem.
I am suspecting a cups problem.  I had forgotten about this bug when I
submitted bug report 623612 for emacs.  Version 1.4.4-5 is the first
version I get the errors on the printout itself as described in the
initial bug report.  It is also the first version that I get an error in
the cups log:

E [21/Apr/2011:13:29:52 -0400] [Job 6] No %%BoundingBox: comment in
header!




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#623612: narrowed it down to version 1.4.4-5 of cups

[Brent S. Elmer Ph.D.]

See bug report 605434.  I don't know if this is an emacs problem only
showing up when this version of cups is installed or it is a problem
with one of the two changes in this version of cups.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#623606: removed offending files, okay now

[Brent S. Elmer Ph.D.]

I looked at the error messages and found the *ITMAgents1 files and
removed them from /etc/init.d/ and /etc/rc*.d/.  After that, updates
worked fine.  I reinstalled the package that those files belong to and
it didn't put the offending files back into /etc/.  I'm not sure what
put the files there before but they had a timestamp of April 14.  




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#623612: related to cups upgrade

[Brent S. Elmer Ph.D.]

Actually, the page does print even with the error message.  The problem
is that the output is garbage.  I submitted bug 605434 a while back for
the garbage output.  The emacs ps-print started failing when cups was
update for the versions in that bug report.  Note that only the cups
package breaks emacs printing.  If I pin cups to 1.4.4-3 and upgrade the
other cups packages (cups-bsd, cups-client, cups-common) to the current
wheezy version 1.4.6-4, ps-print in emacs does work.  There has been no
response at all to the cups bug report.  It seems to be very specific to
emacs.




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#622260: fails to build for 2.6.38 kernel

[Brent S. Elmer Ph.D.]

On Mon, 2011-04-11 at 12:35 -0700, Russ Allbery wrote:
 Brent S. Elmer webe...@aim.com writes:
 
  I am trying to build a 2.6.38 kernel and openafs modules for the kernel.
  I get the following error:
 
  make[1]: Entering directory `/usr/local/src/modules/openafs'
  sh debian/prep-modules /usr/local/src/linux-source-2.6.38
  touch setup
  dh ./debian/rules
  dh: Unknown sequence ./debian/rules (choose from: binary binary-arch binary-
  indep build build-arch build-indep clean install install-arch install-indep)
  make[1]: *** [./debian/rules] Error 9
  make[1]: Leaving directory `/usr/local/src/modules/openafs'
  Module /usr/src/modules/openafs failed.
 
 What commands did you run to get to this point?  The output above seems
 like something ran:
 
 debian/rules debian/rules
 
 which isn't going to work.
 

The way I normally build my kernels and modules.

time fakeroot make-kpkg --append-to-version=.110411 --initrd
kernel-image modules-image

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#622260: fails to build for 2.6.38 kernel

[Brent S. Elmer Ph.D.]

On Mon, 2011-04-11 at 12:51 -0700, Russ Allbery wrote:
 Brent S. Elmer Ph.D. webe...@aim.com writes:
 
  The way I normally build my kernels and modules.
 
  time fakeroot make-kpkg --append-to-version=.110411 --initrd
  kernel-image modules-image
 
 Could you try editing /usr/src/modules/openafs/debian/rules and adding:
 
 debian/rules:
 
 to that file?  It looks like make-kpkg is running make with an explicit
 target of debian/rules, which isn't going to work properly with the
 wildcard rule.  That might get around it.  If that works, I can make that
 change in the next release.
 
 Unfortunately, make-kpkg is rarely tested since it's no longer widely
 used; usually people use either module-assistant or DKMS at this point.
 But I'll try to keep it working.
 

openafs modules built after I added debian/rules:

Thanks,
Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#618861: [Evolution] Bug#618861: Narrowed the problem down

[Brent S. Elmer Ph.D.]

On Tue, 2011-04-05 at 07:45 +0200, Yves-Alexis Perez wrote:
 On lun., 2011-04-04 at 19:34 -0400, Wendy Elmer wrote:
  On Mon, 2011-04-04 at 07:25 +0200, Yves-Alexis Perez wrote:
  
   On dim., 2011-04-03 at 21:08 -0400, Wendy Elmer wrote:
   
   Thanks for your debugging session, it really helps.
   
So, I see two problems:
1. evolution 2.32 does not issue prompts when going through
squid/squidguard which is a regression from 2.30
   
   Ok so that might be related to #620260
   
   If you re-enable proxy stuff, could you tell us if it breaks again or
   not? If it does, could you take some network traces using tcpdump?
  
  Yes, it does break again if evolution needs to get a password.  If
  evolution stores the password by checking the remember password box then
  retrieving mail works.
 
 This one wether or not proxy settings are enabled?

Yes, retrieving new mail works fine with or without the proxy if
evolution has already stored the imap password with remember password.

 
To test this, I turned on the squid network
  proxy, unchecked the box remember password and closed evolution and
  restarted.  Evolution hung again with no password prompt and the 0%
  complete messages.  I closed evolution, changed to direct network
  connection, and restarted evolution.  Evolution started and retrieved
  messages.  There was no password prompt because evolution got the
  password from the keyring.
 
 So when password are in gnome-keyring it'd change the situation? Or is
 it just unrelated to password handling?

No, a password in the keyring does not change the situation.  If
evolution needs the imap password and the proxy is on, evolution hangs
whether getting the password from the keyring or through a pop-up
evolution prompt.  When the proxy if off, evolution will use the keyring
password if it exists otherwise prompt for the password.

 
I repeated both tests this time removing all
  keyrings in ~/.gnome2/keyrings each time.  The direct network connection
  case prompted for the password.  The network proxy case did not prompt
  for the password and hung again.
 
 
 So when there's no password anymore, it works without proxy but it
 doesn't with.

yes

 
  I don't know much about tcpdump but I tried what was in the 620260 bug
  report.  port 110 did not give anything so I left off the port hoping it
  would capture on all ports.  Here is what I ran and the results.
  
  
  tcpdump -s0 -w evo_noproxy.pcap -nlei any
  started evolution with no proxy then closed evolution
  
  tcpdump -s0 -w evo_proxy.pcap -nlei any
  started evolution with proxy then killed evolution
  
  The squid proxy port is 3128.
 
 Ok, I can see there's a tentative connection on the 3128 port but
 there's nothing in there which could help us track that done. By the
 way, is the proxy working (for browsing)?
Yes, the proxy works for browsing, weather applet update, apt-get, ...

 
 Regards,





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#620166: [Evolution] Bug#620166: imap+ Unable to retrieve message

[Brent S. Elmer Ph.D.]

On Thu, 2011-03-31 at 16:11 +0200, Yves-Alexis Perez wrote:
 On mer., 2011-03-30 at 13:12 -0400, Brent S. Elmer wrote:
  Package: evolution
  Version: 2.32.2-1
  Severity: normal
  
  I have been trying to use imap+ instead of imap in evolution because some 
  say
  imap+ works better.  When using imap+ I frequently see the following:
  Unable to retrieve message
  Error fetching message:  UID FETCH completed
  
  If I switch back to imap, I can read the message.  Sometimes I can read the
  message with imap+ if I close evolution and then come back in. 
 
 Could you give us some data about the server? It looks like a
 server-specific issue.
 
 Regards,

The server is imap.aim.com.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#586226: started failing again

[Brent S. Elmer Ph.D.]

On Wed, 2011-01-05 at 15:59 -0800, Russ Allbery wrote:

 
 Aha!  I was working under the incorrect assumption that dnsmasq was all
 that was needed after boot to enable networking, but actually
 NetworkManager is involved in getting basic connectivity.
 
 Yes, I don't think there's anything that dnsmasq can do, nor do I think
 there's anything that OpenAFS can do in this case.  If one is using
 NetworkManager, network services just won't be available at boot, and
 nothing one can put into the init script will help.  They won't be
 available until after NetworkManager runs and authenticates, which often
 has to wait until the user logs in so that NetworkManager has access to
 wireless authentication credentials.

I believe the wired network is up at this point but the wireless is not.

 
  Could AFS be fixed to retry DNS queries after a longish timeout either
  when there's no reply or when a REFUSED rcode is received? The behaviour
  of ntpd in the log above shows fairly well how to get it right.
 
 Starting AFS when there's no network available should generally work when
 using dynroot provided that one doesn't attempt to access any files in AFS
 until the network is available, but one will get timeouts if one tries to
 access AFS before the network is present.
 
  It's not clear to me that there exists any sane change in the behaviour
  of dnsmasq that would help things.
 
 Agreed.  I think the bug against dnsmasq can be closed.
 
 Brent, I'm confused by the bug history here: what happens when AFS doesn't
 start?  Your log messages in the original bug report only show a log
 message that isn't printed, so far as I know, by the init script that
 comes with the openafs-client package.  What sort of behavior do you see
 when AFS is started prior to the network being available?
 

I have removed the bit in the startup script that was checking for
intranet connectivity and am just letting AFS start regardless of
network or intranet connectivity.  I checked to make sure I am using
dynroot and I am.  I'm not sure of the history of why the start script
was checking for intranet connectivity.  Like you said, as long as I
don't try to access anything in /afs when not connected, it shouldn't
cause any problems always starting AFS.

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#586226: started failing again

[Brent S. Elmer Ph.D.]

On Tue, 2010-12-14 at 14:30 -0800, Russ Allbery wrote:
 Brent S. Elmer Ph.D. webe...@aim.com writes:
 
 There may not be a good fix for this other than to add a sleep statement
 somewhere in the startup with a ping similar to what you describe, unless
 there's some way to get dnsmasq to report when it's actually done.
 

I suppose this is a result of the effort to speed up boot times.  What I
ended up doing is looping a few times with a sleep and dig +short to see
if work intranet urls resolve yet.  The dig +short returns nothing if it
doesn't resolve so it seemed better than the ping.  Would this be
considered a bug in dnsmasq the way it is working?  It seems dnsmasq
shouldn't report starting a named until it actually has.  Gnome actually
starts before the dig loop is done and openafs is started so startup
doesn't actually seem any slower.  It beats having to manually start
openafs as root each time I boot when on my work network.

Thanks,
Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#586226: started failing again

[Brent S. Elmer Ph.D.]

The suggestion to do the following in /etc/init.d/openafs-client had
been working great until some update in squeeze a few weeks ago.

Try changing this line

  # Should-Start: $syslog

to look like this

  # Should-Start: $syslog $named

I believe that will solve your problem.

I'm not sure what update broke it but now opanafs-client attempts to start 
before dnsmasq is fully started.  In the 
script I put in a ps to see if dnsmasq is started and the ps shows that dnsmasq 
is started(at least partially).
I put in a ping to a url and it was unresolvable which tells me that dnsmasq is 
not fully started.

Next I put in a sleep in a loop with the ping and eventually the ping resolves 
presumably once dnsmasq fully starts.
So, is the problem with openafs not honoring the Should-Start or dnsmasq 
reporting that it is started before it really is 
fully started?

Brent




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org