Bug#899004: gnome-shell: crash on attempt to lock

[Josep M. Perez]

Hi,

Since the last update I have locked and unlocked my session several 
times, and rebooted three times and I haven't had any more problems. The 
current set of enabled-extensions is: 
['ubuntu-appindicat...@ubuntu.com', 
'gpa...@gnome-shell-extensions.gnome.org', 
'drive-m...@gnome-shell-extensions.gcampax.github.com'].


So, from my side this bug can be closed. Thanks for your help!

Cheers,

Josep M. Perez



On 22/05/18 12:04, Simon McVittie wrote:

On Tue, 22 May 2018 at 11:18:04 +0200, Josep M. Perez wrote:

So, I opened dconf-editor and saw that for some reason
/org/gnome/shell/disable-extension-version-validation was active, and that
was the default value.

That is correct. By default extensions don't need to declare compatibility
with specific GNOME Shell versions since 3.21.92 (in earlier versions, the
Shell interfaces that extensions use changed more frequently).

If that option had any effect, it would be to disable some of your
extensions. Extensions that say they are compatible with Shell 3.28 should
never be affected by it. gpaste and "removable drive menu" seem to both
be from packages that are updated in sync with the rest of GNOME 3.28,
so I would expect that they declare compatibility with Shell 3.28 and are
unaffected by extension version validation.


Last week, it seemed that disabling the "gpaste" extension solved it. However,
today I updated, rebooted, and it seems that now that it still happens until I
disable the "removable drive menu" extension.

...

I have set it to false, emptied the contents of
/org/gnome/shell/enabled-extensions, and enabled only gpaste and "removable
drive menu" through the "tweaks" application. After this, I can lock the
screen with no trouble.

That sounds like it might be an intermittent bug that doesn't necessarily
depend on the enabled state of those extensions, unfortunately.


ii  gnome-shell-extensions 3.28.1-1
all  Extensions to extend functionality of GNOME Shell

FYI, this is the package containing the "removable drive menu" extension.

 smcv



http://bsc.es/disclaimer

Bug#899004: gnome-shell: crash on attempt to lock

[Josep M. Perez]

Hi,

Sorry for the late response.

On 18/05/18 20:15, Simon McVittie wrote:

Control: tags -1 + moreinfo

On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

How reproducible is this? If you reboot your computer and try repeatedly
locking your screen, does the same thing happen again?
Yes, it happens even if I reboot. This started happening when I went 
from 2.26 to 2.28. Since the crash is related to JS, I started to 
disable extensions. Last week, it seemed that disabling the "gpaste" 
extension solved it. However, today I updated, rebooted, and it seems 
that now that it still happens until I disable the "removable drive 
menu" extension.


So, I opened dconf-editor and saw that for some reason 
/org/gnome/shell/disable-extension-version-validation was active, and 
that was the default value. I have set it to false, emptied the contents 
of /org/gnome/shell/enabled-extensions, and enabled only gpaste and 
"removable drive menu" through the "tweaks" application. After this, I 
can lock the screen with no trouble.


Since activating and deactivating extensions makes the problem go away, 
I will keep you posted about whether this is finally stable.



Is there anything that looks relevant in the systemd journal or syslog
at around the time of the crash?

Not really. It only happens when I attempt to lock the screen.

Did you previously run a version of gnome-shell that did not have this bug?
If you did, what packages did you upgrade around the time it started
happening? (/var/log/apt/history.log* might be useful)

Do you have any GNOME Shell extensions enabled?

I notice that the backtrace you provided involves libnm, the NetworkManager
client library. Is there anything unusual about your networking that might
explain why you see this crash when other people don't?
I have an ethernet connection, a wifi connection and an OpenVPN bridge 
using the tap interface.

I uploaded new versions of gnome-shell, mutter and gjs earlier today
(gnome-shell 3.28.2, mutter 3.28.2 and gjs 1.52.3-2). Please could you
try with those when they become available, and report back with whether
this bug is still visible in those versions?

Yes. The list of versions are:

ii  chrome-gnome-shell 10-1    
all  GNOME Shell extensions integration for web browsers
ii  gnome-shell 3.28.2-1    amd64    
graphical shell for the GNOME desktop
ii  gnome-shell-common 3.28.2-1    
all  common files for the GNOME graphical shell
ii  gnome-shell-dbgsym 3.28.2-1    
amd64    debug symbols for gnome-shell
ii  gnome-shell-extension-appindicator 
22-1    all 
AppIndicator/KStatusNotifierItem support for GNOME Shell
ii  gnome-shell-extension-autohidetopbar 
20171126-2  all  GNOME shell 
automatic topbar hider
ii  gnome-shell-extension-dash-to-panel 
13-1    all  combines the dash 
and the GNOME main panel into a single panel
ii  gnome-shell-extension-dashtodock 
63-1    all  dash-to-dock 
extension for GNOME shell
ii  gnome-shell-extension-disconnect-wifi 
17-2    all  disconnect wifi 
extension for GNOME shell
ii  gnome-shell-extension-hide-activities 
0.00~git20131024.1.6574986-1    all  GNOME shell 
extension that hides the activities button
ii  gnome-shell-extension-impatience 
0.4.5-3 all  speed up the 
gnome-shell animation speed
ii  gnome-shell-extension-move-clock 
1.01-1  all  move clock 
extension for GNOME shell
ii  gnome-shell-extension-multi-monitors 
0.00~git20171014.1.df5d6e4-1    all  Better support for 
additional monitors in GNOME shell
ii  gnome-shell-extension-pixelsaver 
1.10+git20161217-49f47bf-1  all  pixel saver 
extension for GNOME shell
ii  gnome-shell-extension-redshift 
3.20.1-2    all  redshift extension 
for GNOME Shell
ii  gnome-shell-extension-remove-dropdown-arrows 
9-1 all  removes drop down 
arrows from panel on GNOME shell
ii  gnome-shell-extension-shortcuts 
1.1.1-1 all  Creates a shortcuts 
help pop-up in GNOME Shell
ii  gnome-shell-extension-show-ip 
8-3 all  Shows the current 
private or public IP address
ii  gnome-shell-extension-suspend-button 
0~git20171025-2 all  Gnome-shell 
extension to modify the suspend/shutdown buttons
ii  gnome-shell-extension-system-monitor 
35-

Bug#899004: gnome-shell: crash on attempt to lock

[Josep M. Perez]

Package: gnome-shell
Version: 3.28.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

A backtrace follows:

#0  0x770c14f4 in g_hash_table_iter_init
(iter=iter@entry=0x7ffef010, hash_table=0x10004) at
../../../../glib/ghash.c:769
#1  0x72909042 in nm_ip_address_dup (address=) at libnm-
core/nm-setting-ip-config.c:388
#2  0x773aaecb in g_boxed_copy (boxed_type=93825030200288,
src_boxed=src_boxed@entry=0x563791e0) at ../../../../gobject/gboxed.c:343
#3  0x7609f540 in gjs_boxed_from_c_struct(JSContext*, GIStructInfo*,
void*, GjsBoxedCreationFlags) (context=context@entry=0x55dd7a00,
info=info@entry=0x57aec540, gboxed=0x563791e0, flags=)
at gi/boxed.cpp:1235
#4  0x7609b194 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x58331ca0, arg=arg@entry=0x7ffef4b8,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:2909
#5  0x7609bf33 in gjs_array_from_carray_internal(JSContext*,
JS::MutableHandleValue, GITypeInfo*, guint, gpointer)
(context=context@entry=0x55dd7a00, value_p=..., value_p@entry=...,
param_info=param_info@entry=0x58331ca0, length=1, array=) at
gi/arg.cpp:2346
#6  0x7609a446 in gjs_array_from_boxed_array (arg=0x7ffef998,
param_info=0x58331ca0, array_type=, value_p=...,
context=0x55dd7a00) at gi/arg.cpp:2462
#7  0x7609a446 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x7ffef9c0, arg=arg@entry=0x7ffef998,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:3012
#8  0x760a677e in gjs_invoke_c_function(JSContext*, Function*,
JS::HandleObject, JS::HandleValueArray const&,
mozilla::Maybe, GIArgument*)
(context=context@entry=0x55dd7a00, function=function@entry=0x576f0b00,
obj=...,
obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at
gi/function.cpp:1147
#9  0x760a6a24 in function_call(JSContext*, unsigned int, JS::Value*)
(context=context@entry=0x55dd7a00, js_argc=0, vp=0x55f14d50)
at gi/function.cpp:1406
#10 0x7fffed039fdc in js::CallJSNative(JSContext*, bool (*)(JSContext*,
unsigned int, JS::Value*), JS::CallArgs const&) (args=...,
native=0x760a68c0 ,
cx=0x55dd7a00) at ./js/src/jscntxtinlines.h:239
#11 0x7fffed039fdc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=0x55dd7a00, args=...,
construct=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:447
#12 0x7fffed02d087 in js::CallFromStack(JSContext*, JS::CallArgs const&)
(args=..., cx=) at ./js/src/vm/Interpreter.cpp:510
#13 0x7fffed02d087 in Interpret(JSContext*, js::RunState&)
(cx=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:2922
#14 0x7fffed039846 in js::RunScript(JSContext*, js::RunState&)
(cx=cx@entry=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:405
#15 0x7fffed039e1f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=cx@entry=0x55dd7a00, args=...,
construct=construct@entry=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:477
#16 0x7fffed03a099 in InternalCall(JSContext*, js::AnyInvokeArgs const&)
(cx=cx@entry=0x55dd7a00, args=...) at ./js/src/vm/Interpreter.cpp:504
#17 0x7fffed03a0f9 in js::Call(JSContext*, JS::Handle,
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
(cx=cx@entry=0x55dd7a00, fval=..., fval@entry=..., thisv=...,
thisv@entry=..., args=..., rval=rval@entry=...) at
./js/src/vm/Interpreter.cpp:523
#18 0x7fffece2c079 in js::jit::InvokeFunction(JSContext*,
JS::Handle, bool, unsigned int, JS::Value*,
JS::MutableHandle) (cx=0x55dd7a00, obj=...,
constructing=, argc=, argv=0x7fff06c0,
rval=...) at ./js/src/jit/VMFunctions.cpp:114
#19 0x35b97b5083c6 in  ()
#20 0x7fff0780 in  ()
#21 0x7fff0670 in  ()
#22 0xfff9 in  ()
#23 0x7fffee1dc040 in js::jit::InvokeFunctionInfo () at
/usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#24 0x7fffc05739a0 in  ()
#25 0x35b97b59f89b in  ()
#26 0x7820 in  ()
#27 0x7fffa999c700 in  ()
---Type  to continue, or q  to quit---
#28 0x in  ()

(gdb) info sharedlibrary
>FromTo  Syms Read   Shared Object Library
0x779a8c40  0x779c22de  Yes /usr/lib/gnome-
shell/libgnome-shell.so
0x776290a0  0x7770b162  Yes /usr/lib/x86_64-linux-
gnu/libgio-2.0.so.0
0x773a7f10  0x773d9b3e  Yes /usr/lib/x86_64-linux-

Bug#875609: FYI: bug also present in 3.22.3-3

[Josep M. Perez]

Package: gnome-shell
Version: 3.22.3-3
Followup-For: Bug #875609

FYI, this bug is also present in 3.22.3-3

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  g_type_check_instance_cast (type_instance=0x60b92d,
iface_type=93824997189056) at ../../../../gobject/gtype.c:4052
4052../../../../gobject/gtype.c: No such file or directory.
[Current thread is 1 (Thread 0x77f6ca80 (LWP 27725))]
(gdb) bt
#0  0x752a3e26 in g_type_check_instance_cast (type_instance=0x60b92d,
iface_type=93824997189056) at ../../../../gobject/gtype.c:4052
#1  0x779770ac in shell_gtk_embed_window_created_cb
(display=0x55b11f10 [MetaDisplay], window=0x5c6c3400 [MetaWindowX11],
embed=0x57f91300) at shell-gtk-embed.c:67
#5  0x75299f1f in  (instance=instance@entry=0x55b11f10, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#2  0x7527df9d in g_closure_invoke (closure=0x5a8ce2e0,
return_value=0x0, n_param_values=2, param_values=0x7fffda30,
invocation_hint=0x7fffd9b0) at ../../../../gobject/gclosure.c:804
#3  0x75290d2e in signal_emit_unlocked_R
(node=node@entry=0x55aad9a0, detail=detail@entry=0,
instance=instance@entry=0x55b11f10,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffda30) at
../../../../gobject/gsignal.c:3635
#4  0x75299505 in g_signal_emit_valist (instance=0x55b11f10,
signal_id=, detail=0, var_args=var_args@entry=0x7fffdc00)
at ../../../../gobject/gsignal.c:3391
#6  0x7674cce2 in meta_display_notify_window_created
(display=display@entry=0x55b11f10 [MetaDisplay],
window=window@entry=0x5c6c3400 [MetaWindowX11]) at core/display.c:1698
#7  0x7676ae03 in _meta_window_shared_new
(display=display@entry=0x55b11f10 [MetaDisplay],
screen=screen@entry=0x55958400 [MetaScreen],
client_type=client_type@entry=META_WINDOW_CLIENT_TYPE_X11,
surface=surface@entry=0x0, xwindow=xwindow@entry=6291544,
existing_wm_state=existing_wm_state@entry=0, effect=,
attrs=) at core/window.c:1264
#8  0x76782b40 in meta_window_x11_new
(display=display@entry=0x55b11f10 [MetaDisplay], xwindow=6291544,
must_be_viewable=must_be_viewable@entry=0,
effect=effect@entry=META_COMP_EFFECT_CREATE) at x11/window-x11.c:3016
#9  0x76777938 in handle_other_xevent
(display=display@entry=0x55b11f10 [MetaDisplay],
event=event@entry=0x7fffe110) at x11/events.c:1371
#10 0x767784eb in meta_display_handle_xevent (event=0x7fffe110,
display=0x55b11f10 [MetaDisplay]) at x11/events.c:1769
#11 0x767784eb in xevent_filter (xevent=0x7fffe110,
event=, data=0x55b11f10) at x11/events.c:1808
#12 0x717a52af in gdk_event_apply_filters
(xevent=xevent@entry=0x7fffe110, event=event@entry=0x585395e0,
window=window@entry=0x0)
at ../../../../../gdk/x11/gdkeventsource.c:79
#13 0x717a5599 in gdk_event_source_translate_event
(xevent=0x7fffe110, event_source=0x559ff780)
at ../../../../../gdk/x11/gdkeventsource.c:198
#14 0x717a5599 in _gdk_x11_display_queue_events (display=0x55a26040
[GdkX11Display]) at ../../../../../gdk/x11/gdkeventsource.c:341
#15 0x7176f3c0 in gdk_display_get_event
(display=display@entry=0x55a26040 [GdkX11Display]) at
../../../../gdk/gdkdisplay.c:438
#16 0x717a5342 in gdk_event_source_dispatch
(source=source@entry=0x559ff780, callback=,
user_data=)
at ../../../../../gdk/x11/gdkeventsource.c:363
#17 0x74fa4f67 in g_main_dispatch (context=0x557a3c00) at
../../../../glib/gmain.c:3148
#18 0x74fa4f67 in g_main_context_dispatch
(context=context@entry=0x557a3c00) at ../../../../glib/gmain.c:3813
#19 0x74fa51a0 in g_main_context_iterate (context=0x557a3c00,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ../../../../glib/gmain.c:3886
#20 0x74fa54b2 in g_main_loop_run (loop=0x559ecb60) at
../../../../glib/gmain.c:4082
#21 0x76758a8c in meta_run () at core/main.c:572
#22 0x64b7 in main (argc=, argv=) at
main.c:471

Yours faithfully,
Josep M. Perez



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  evolution-data-server3.26.0-1
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2

Bug#814320: linux-image-4.3.0-1-amd64: Slab leak

[Josep M. Perez]

Package: src:linux
Version: 4.3.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The current kernel is having an apparent memory leak on my computer. Over time
it consumes all memory. The output of slabtop -s c after having the system on
for 24h is is the following:

 Active / Total Objects (% used): 2083098 / 2188414 (95.2%)
 Active / Total Slabs (% used)  : 125633 / 125653 (100.0%)
 Active / Total Caches (% used) : 75 / 115 (65.2%)
 Active / Total Size (% used)   : 495649.02K / 507685.21K (97.6%)
 Minimum / Average / Maximum Object : 0.02K / 0.23K / 4096.00K

  OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
1552320 1551740  99%0.25K  97020   16388080K kmalloc-256
 16312  15522  95%1.00K   40784 16312K ext4_inode_cache
 25473  25451  99%0.56K   36397 14556K radix_tree_node
 71652  69487  96%0.19K   3412   21 13648K kmalloc-192
 51387  40537  78%0.19K   2447   21  9788K dentry
 92859  53038  57%0.10K   2381   39  9524K buffer_head
 14609  13272  90%0.55K   20877  8348K inode_cache
161076 128018  79%0.03K   1299  124  5196K kmalloc-32
 78939  73252  92%0.06K   1253   63  5012K kmalloc-64
  4296   4133  96%1.00K   10744  4296K kmalloc-1024
  1060   1009  95%3.31K5302  4240K task_struct
 34089  32793  96%0.12K   1033   33  4132K kernfs_node_cache
  4278   3768  88%0.60K7136  2852K proc_inode_cache
36 36 100%   64.00K 361  2304K kmalloc-65536
   283283 100%8.00K2831  2264K kmalloc-8192
  4248   3997  94%0.50K5318  2124K kmalloc-512
   497490  98%4.00K4971  1988K kmalloc-4096
  2898   2677  92%0.63K4836  1932K shmem_inode_cache
 24920  23282  93%0.07K445   56  1780K anon_vma
   848798  94%2.00K4242  1696K kmalloc-2048
   570556  97%2.05K1903  1520K idr_layer_cache
  1320   1218  92%0.94K3304  1320K mm_struct
   375333  88%2.06K1253  1000K sighand_cache
  1446   1339  92%0.62K2416   964K sock_inode_cache
  6603   4666  70%0.12K213   31   852K kmalloc-node
 1  1 100%  512.00K  11   512K kmalloc-524288
30 30 100%   16.00K 301   480K kmalloc-16384
 11682  11529  98%0.04K118   99   472K ext4_extent_status
   399333  83%1.12K 577   456K signal_cache
  2464   2464 100%0.14K 88   28   352K ext4_groupinfo_4k


The computer has 8 GB of memory. Previously I was able to run a virtualbox
instance of 32-bits Windows 7 with 2GB of memory with no issue. Now whenever I
do so the system slows down to a crawl and ultimately ends up killing the
virtual box processes.



-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160121 (Debian 5.3.1-7) ) #1 SMP Debian 4.3.5-1 (2016-02-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=ccf515b5-e8b8-4536-a473-41b478488cf9 ro

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[85266.116807] ata5: limiting SATA link speed to 1.5 Gbps
[85266.116814] ata5: hard resetting link
[85266.844945] ata5: SATA link down (SStatus 0 SControl 310)
[85266.844970] ata5: EH complete
[85276.960063] ata5: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[85276.960075] ata5: irq_stat 0x0040, connection status changed
[85276.960080] ata5: SError: { CommWake DevExch }
[85276.960092] ata5: limiting SATA link speed to 1.5 Gbps
[85276.960098] ata5: hard resetting link
[85277.682443] ata5: SATA link down (SStatus 0 SControl 310)
[85277.682468] ata5: EH complete
[85278.961885] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85278.961897] ata5: irq_stat 0x0040, connection status changed
[85278.961902] ata5: SError: { DevExch }
[85278.961913] ata5: limiting SATA link speed to 1.5 Gbps
[85278.961919] ata5: hard resetting link
[85279.684200] ata5: SATA link down (SStatus 0 SControl 310)
[85279.684225] ata5: EH complete
[85284.973345] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85284.973357] ata5: irq_stat 0x0040, connection status changed
[85284.973362] ata5: SError: { DevExch }
[85284.973373] ata5: limiting SATA link speed to 1.5 Gbps
[85284.973379] ata5: hard resetting link
[85285.697443] ata5: SATA link down (SStatus 0 SControl 310)
[85285.697467] ata5: EH complete
[85294.976031] ata5: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[85294.976042] ata5: irq_stat 0x0040, connection status changed
[85294.976048] ata5: SError: { DevExch }
[85294.976059] ata5: limiting SATA link speed to 1.5 Gbps
[85294.976066] ata5: 

Bug#758810: [gdm3] gdm3: fails to start gnome

[Josep M. Perez Cancer]

Thanks for your quick response. Indeed that was the problem.

My shell configuration files were quite old. I have updated them with 
the changes in /etc/skel. In addition, for some reason I had 
.bash_profile instead of .profile, and the later was a symlink to the 
former. The symlink dated back to October 2008. I fixed this too, and 
now it is working correctly.


Thanks for your help!

Cheers,
Josep M. Perez


On 21/08/14 17:22, Simon McVittie wrote:

On 21/08/14 15:51, Josep M. Perez Cancer wrote:

Aug 21 13:28:37 bsccs243 /etc/gdm3/Xsession[21442]:

/etc/gdm3/Xsession: Beginning session setup...

Aug 21 13:28:37 bsccs243 /etc/gdm3/Xsession[21442]:

/etc/bash_completion.d/pulseaudio-bash-completion.sh: line 6: syntax
error near unexpected token `'

Aug 21 13:28:37 bsccs243 /etc/gdm3/Xsession[21442]:

/etc/bash_completion.d/pulseaudio-bash-completion.sh: line 6: ` done 
(pactl list cards short 2 /dev/null)'

I think this might be the error that is terminating your X session.
/etc/gdm3/Xsession is a /bin/sh script and sources ~/.profile.

Please try removing bash-specific things from your ~/.profile, moving
them to ~/.bashrc, or guarding them with:

 if [ z$BASH_VERSION != z ]
 then
 ... enable bash completion or source .bashrc or whatever ...
 fi

It might also be useful to guard things that are specific to an
interactive shell with

 if [ -n $PS1 ]
 then
 ... things that only make sense in an interactive shell ...
 fi

If that is indeed the cause of this error, I'll leave it to the gdm
maintainers to decide whether this is a gdm bug or not. According to the
changelog, it has sourced ~/.profile since gdm/2.20.2-1 in 2007, so this
isn't a recent thing (but /etc/X11/Xsession doesn't, which explains why
you don't see this in non-gdm).

 S




WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.

http://www.bsc.es/disclaimer


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

Bug#758810: [gdm3] gdm3: fails to start gnome

[Josep M. Perez Cancer]

Package: gdm3
Version: 3.12.2-2.1
Severity: grave

--- Please enter the report below this line. ---

Since upgrading from gdm to gdm3, it fails to start both the gnome-shell 
session and the classic gnome session. KDM launches them correctly, 
however it is not a good solution since kdm does not work correctly with 
screen locking in gnome 3.


The following lines show the logs that I get since entering the password 
until it is about to restart the X server to show the greeter again:


Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) AIGLX: Resuming AIGLX 
clients after VT switch
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) NOUVEAU(0): NVEnterVT 
is called.
Aug 21 13:28:31 bsccs243 console-kit-daemon[10808]: (process:21365): 
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) NOUVEAU(0): EDID 
vendor LGD, prod id 747
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) NOUVEAU(0): Printing 
DDC gathered Modelines:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) NOUVEAU(0): Modeline 
1366x768x0.0   70.00  1366 1402 1450 1492  768 771 776 782 -hsync 
-vsync (46.9 kHz eP)
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (II) NOUVEAU(0): Modeline 
1366x768x0.0   48.30  1366 1402 1450 1524  768 771 776 792 -hsync 
-vsync (31.7 kHz e)
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: (--) synaptics: AlpsPS/2 
ALPS DualPoint TouchPad: touchpad found
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 2 redefined

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 3 redefined

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 4 redefined

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:31 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 2 redefined

Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 3 redefined

Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Warning: Compat map for 
group 4 redefined

Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Using new definition
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: The XKEYBOARD keymap 
compiler (xkbcomp) reports:
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Warning: Type ONE_LEVEL 
has 1 levels, but RALT has 2 symbols

Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]:  Ignoring extra symbols
Aug 21 13:28:32 bsccs243 gdm-Xorg-:0[21068]: Errors from xkbcomp are not 
fatal to the X server
Aug 21 13:28:32 

Bug#745844: [Pkg-gtkpod-devel] Bug#745844: usbmuxd 1.0.9 fixes all

[Josep M. Perez]

BTW, the log from https://github.com/libimobiledevice/usbmuxd.git 
contains the following entry:


   commit eca4b3cb833a306677a76d4645e2e034f77fc387
   Author: Martin Szulecki m.szule...@libimobiledevice.org
   Date:   Thu Sep 19 20:46:30 2013 +0200

Bump version to 1.0.9


I am not sure why there is no tag nor release associated to that commit.

In addition the build system is based on automake, unlike the source of 
the usbmuxd package, which uses cmake. Am I missing something here?


Cheers,
Josep M. Perez

Bug#745844: [Pkg-gtkpod-devel] Bug#745844: usbmuxd 1.0.9 fixes all

[Josep M. Perez]

Sorry, I feel stupid. Did you notice that there is a link in the 
Sources and Dependencies section in http://www.libimobiledevice.org/ 
tousbmuxd-1.0.9.tar.bz2 
http://www.libimobiledevice.org/downloads/libusbmuxd-1.0.9.tar.bz2 ?


Cheers,
Josep M. Perez


On 04/07/14 14:06, Josep M. Perez wrote:
BTW, the log from https://github.com/libimobiledevice/usbmuxd.git 
contains the following entry:


commit eca4b3cb833a306677a76d4645e2e034f77fc387
Author: Martin Szulecki m.szule...@libimobiledevice.org
Date:   Thu Sep 19 20:46:30 2013 +0200

Bump version to 1.0.9


I am not sure why there is no tag nor release associated to that commit.

In addition the build system is based on automake, unlike the source 
of the usbmuxd package, which uses cmake. Am I missing something here?


Cheers,
Josep M. Perez

Bug#355047: apt tools segfault

[Josep M. Perez Cancer]

I found a way to work around the segfault. Looks like the culprits were 
/var/cache/apt/pkgcache.bin and /var/cache/apt/srcpkgcache.bin. For some 
reason they have been corrupted. Just removing them avoids the segfault.


I attach the versions of those files that crached the apt tools.

Josep M. Perez C.





pkgcache.bin
Description: Binary data


srcpkgcache.bin
Description: Binary data

Bug#355047: apt tools segfault

[Josep M. Perez Cancer]

Followup-For: Bug #355047
Package: apt
Version: 0.6.44.2

*** Please type your report below this line ***
apt-get and apt-cache segfault at the same program location. In the case
of apt-get, update finishes with a segfault and upgrade segfaults while
reading the package list. In the apt-cache case, just doing a search
triggers the segfault.

I have recompiled the package without optimisation and without
stripping and run it through gdb and strace.


-- Debugging session follows:
$ gdb apt-cache
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i486-linux-gnu...Using host libthread_db
library /lib/tls/i686/cmov/libthread_db.so.1.

(gdb) run search apt
Starting program: /usr/bin/apt-cache search apt

Program received signal SIGSEGV, Segmentation fault.
0xa7c60ca3 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0  0xa7c60ca3 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1  0xa7deb5c6 in std::string::compare () from /usr/lib/libstdc++.so.6
#2  0xa7e9ea7a in std::operator!=char, std::char_traitschar, 
std::allocatorchar  ([EMAIL PROTECTED], __rhs=0x0)
   at 
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:2200
#3  0xa7f037d5 in debPackagesIndex::FindInCache (this=0x805b270, 
[EMAIL PROTECTED]) at deb/debindexfile.cc:308
#4  0xa7ecbb30 in CheckValidity ([EMAIL PROTECTED], 
Start={_M_current = 0x805c528}, End={_M_current = 0x805c55c}, 
OutMap=0xafb5afd8)

   at pkgcachegen.cc:580
#5  0xa7ece980 in pkgMakeStatusCache ([EMAIL PROTECTED], 
[EMAIL PROTECTED], OutMap=0xafb5afd8, AllowMem=true) at 
pkgcachegen.cc:715

#6  0x0804d307 in main (argc=3, argv=0xafb5b094) at apt-cache.cc:1791
(gdb) frame 3
#3  0xa7f037d5 in debPackagesIndex::FindInCache (this=0x805b270, 
[EMAIL PROTECTED]) at deb/debindexfile.cc:308

308   if (FileName != File.FileName())
(gdb) print FileName
$1 = {static npos = 4294967295, _M_dataplus = {std::allocatorchar = 
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
 _M_p = 0x805c884 
/var/lib/apt/lists/ftp.nl.debian.org_debian_dists_unstable_main_binary-i386_Packages}}

(gdb) print File
$2 = {Owner = 0xafb5aa94, File = 0xa7f44220}
(gdb) print File.Owner
$3 = (class pkgCache *) 0xafb5aa94
(gdb) print *File.Owner
$4 = {_vptr.pkgCache = 0x805a468, CacheFile = {static npos = 4294967295, 
_M_dataplus = {std::allocatorchar =
   {__gnu_cxx::new_allocatorchar = {No data fields}, No data 
fields}, _M_p = 0xa7e395bc }},
 Map = @0x805c6c8, HeaderP = 0xa7f42000, PkgP = 0xa7f42000, 
VerFileP = 0xa7f42000, PkgFileP = 0xa7f42000, VerP = 0xa7f42000,
 ProvideP = 0xa7f42000, DepP = 0xa7f42000, StringItemP = 0xa7f42000, 
StrP = 0xa7f42000 \230\004, VS = 0xa7f29ca4}

(gdb) print *File.File
$5 = {FileName = 0, Archive = 0, Component = 0, Version = 0, Origin = 0, 
Label = 0, Architecture = 0, Site = 0, IndexType = 0, Size = 0,

 Flags = 0, NextFile = 0, ID = 0, mtime = 0}
(gdb) up
#4  0xa7ecbb30 in CheckValidity ([EMAIL PROTECTED], 
Start={_M_current = 0x805c528}, End={_M_current = 0x805c55c}, 
OutMap=0xafb5afd8)

   at pkgcachegen.cc:580
580   pkgCache::PkgFileIterator File = (*Start)-FindInCache(Cache);
(gdb) frame 3
#3  0xa7f037d5 in debPackagesIndex::FindInCache (this=0x805b270, 
[EMAIL PROTECTED]) at deb/debindexfile.cc:308

308   if (FileName != File.FileName())
(gdb) print *this
$6 = {pkgIndexFile = {_vptr.pkgIndexFile = 0xa7f27048, Trusted = 
true}, URI = {static npos = 4294967295,
   _M_dataplus = {std::allocatorchar = 
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
 _M_p = 0x805bb44 http://ftp.nl.debian.org/debian/}}, Dist = 
{static npos = 4294967295,
   _M_dataplus = {std::allocatorchar = 
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},

 _M_p = 0x805be5c unstable}}, Section = {static npos = 4294967295,
   _M_dataplus = {std::allocatorchar = 
{__gnu_cxx::new_allocatorchar = {No data fields}, No data 
fields}, _M_p = 0x805babc main}}}

(gdb)


-- strace output
$ strace apt-cache search apt
execve(/usr/bin/apt-cache, [apt-cache, search, apt], [/* 31 vars 
*/]) = 0

uname({sys=Linux, node=bscig02, ...}) = 0
brk(0)  = 0x805b000
access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0xa7fab000
access(/etc/ld.so.preload, R_OK)  = -1 ENOENT (No such file or 
directory)

open(/etc/ld.so.cache, O_RDONLY)  = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=108031, ...}) = 0
mmap2(NULL, 108031, PROT_READ, MAP_PRIVATE, 3, 0) = 0xa7f9
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK)  = -1