Bug#1023425: gnome-shell: crash on startup after upgrade from 42.4

[Kjö Hansi Glaz]

Hi,

I upgraded my system again last night, and then tried to reinstall 
gnome-shell 43.0-2. Now everything works fine.


I guess that the previous upgrade may have had incompatible packages 
versions that were not handeled well by apt dependencies?


So it shows a bug, but less serious that it looked yesterday!

Thanks again for your work on GNOME and debian!

Bug#1023425: gnome-shell: crash on startup after upgrade from 42.4

[Kjö Hansi Glaz]

Subject: gnome-shell: crash on startup after upgrade from 42.4
Package: gnome-shell
Version: 43.0-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

Upgrade my sid system from gnome-shell 42.4-2 to 43.0-2

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Restart the system.

   * What was the outcome of this action?

The system boots up to gdm service startup, then the display blinks. It 
is not possible to access a tty to login in a shell.


I had to start in recovery mode and to downgrade gnome-shell and mutter 
by hand to version 42.4-2


   * What outcome did you expect instead?

The graphical session to start up, or in case of failure, being able to 
access a shell.



My system is MacBookPro9,2 with i915 graphics.

Please find below "coredumpctl info" output.

Please let me know if you need more information

Thanks for maintaing gnome-shell.


lspci -vv -s 00:02.0


00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core 
processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])

Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 48, IOMMU group 2
Memory at a000 (64-bit, non-prefetchable) [size=4M]
Memory at 9000 (64-bit, prefetchable) [size=256M]
I/O ports at 2000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915


coredumpctl info


PID: 2371 (gnome-shell)
UID: 1000 (kjo)
GID: 1000 (kjo)
Signal: 11 (SEGV)
Timestamp: Thu 2022-11-03 21:09:10 CET (45min ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: 
/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service

Unit: user@1000.service
User Unit: org.gnome.Shell@wayland.service
Slice: user-1000.slice
Owner UID: 1000 (kjo)
Boot ID: 9752a2d6fde049f5b76c872b3827824d
Machine ID: b9adf7e9bf9f26d80afe8bdb52d7f9a8
Hostname: ziggy
Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1000.9752a2d6fde049f5b76c872b3827824d.2371.166750615000.zst 
(present)

Disk Size: 12.0M
Message: Process 2371 (gnome-shell) of user 1000 dumped core.

Module linux-vdso.so.1 with build-id 
e14a78332591687c6ecc5aaab7d80c97f73059c7
Module libgiognomeproxy.so with build-id 
0eb1e3b029ee38a2fd88831bdc072db7e6b0fa24
Module libgioremote-volume-monitor.so with build-id 
5924f54f8ceb9aed48745b79550c4c0e68d9fae2
Module libtelepathy-logger.so.3 with build-id 
9c5ee58594405138f1c5907cf075afe223f9e93b
Module libdbus-glib-1.so.2 with build-id 
90430c691f4ef85d90b05889fe88a181f2fdc767
Module libtelepathy-glib.so.0 with build-id 
f86f22bc6f26f556280365ef5b9fcab7a1b002db
Module libmp3lame.so.0 with build-id 
5608dbb8e56f055feb7a55ce4e83ffc66fc7

Module libmpg123.so.0 with build-id b109ea5988217206e2f3037d18a153d2345e3532
Module libopus.so.0 with build-id c660cf724fd7835d53a33b5f2d494471104cb556
Module libvorbisenc.so.2 with build-id 
15116f34e1cc88f88c13d4e6ce5aab9a05c2ad55

Module libFLAC.so.8 with build-id d002f9c229612cbb6ac63c0e833401a3b63bb1fa
Module libasyncns.so.0 with build-id 
2f138035552f4b777ccafb65b22b5da8983ea7ac
Module libsndfile.so.1 with build-id 
abfba3b21e81f0b27d5c90ab17a053dc7d45f8f8
Module libpulsecommon-16.1.so with build-id 
0f7e302d4bc34228488b6b4fce8c1b986e422f03
Module libpulse-mainloop-glib.so.0 with build-id 
dc346fd641bc6c776c8ab2b2ae30227b6c12d1d5

Module libpulse.so.0 with build-id 1ace166a6383f89cba02f7829ef3245bfc15f532
Module libgvc.so with build-id b42a251e93669ff08d865bc0e7cd340396305f77
Module libcrypt.so.1 with build-id 2442239fad26c8122cf7dd8e54af2b15c7a17fa6
Module libaccountsservice.so.0 with build-id 
39cf83accf4e52a9de65a52077e30f8bc0afe618
Module libgeocode-glib-2.so.0 with build-id 
d5fab0a8e95aecc0b1e1d6b42e3928e0b45c3303
Module libgweather-4.so.0 with build-id 
2bd9a031123ff85b51526f28c9dffd9dc5741aee

Module librsvg-2.so.2 with build-id db07b8609508e07840554ca6563f953996daa8e9
Module libpixbufloader-svg.so with build-id 
ea2347470e47e8305d6f383ab5ec3beb6a02c786

Module libgdm.so.1 with build-id 4f65c3e33bbd076fb2a246bcb40e920c9f90765c
Module libgeoclue-2.so.0 with build-id 
97b46636b6eb153ea751280fce8614533c90df10
Module libmalcontent-0.so.0 with build-id 
efb0cc8c610e11042dd1765462df3c34d7dd97f3
Module libibus-1.0.so.5 with build-id 
577a1aad70179d19924e940a6f4e8be6a0c7691e
Module libnghttp2.so.14 with build-id 
da1f9cf6839a6882e78d2551e3bb321a5e7e83fd

Module libpsl.so.5 with build-id ea212f1398c6f4a35aef2b84e2ba67792550e0a8
Module libsqlite3.so.0 with build-id 
8a18485a5acac1fc54a1ed3bb699b9e70b67f964
Module libsoup-3.0.so.0 with build-id 
abf3e3b10f1e0a26f23ce37e95cd85ec9b67efb3

Module 

Bug#1013141: kleopatra: fails to verify .sign files

[Kjö Hansi Glaz]

Package: kleopatra
Version: 4:22.04.1-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

In Kleopatra, click "Decrypy/verify…"

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Select a signature file ending with ..sign, e.g. SHA512SUMS.sign from
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS.sign

   * What was the outcome of this action?

A dialog shows:

  An error occured: Kleopatra: Could not open file "SHA512SUMS." for
  reading: No such file or directory (218136657)

   * What outcome did you expect instead?

The "SHA512SUMS" file downloaded along "SHA512SUMS.sign" to be verified.

Please note that if I rename "SHA512SUMS.sign" to "SHA512SUMS.sig",
everything works well


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kleopatra depends on:
ii  dirmngr2.2.35-2
ii  gnupg  2.2.35-2
ii  gpgsm  2.2.35-2
ii  libassuan0 2.5.5-3
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-4
ii  libgpg-error0  1.45-2
ii  libgpgme11 1.17.1-4
ii  libgpgmepp61.17.1-4
ii  libkf5codecs5  5.94.0-1
ii  libkf5configcore5  5.94.0-3
ii  libkf5configgui5   5.94.0-3
ii  libkf5configwidgets5   5.94.0-1
ii  libkf5coreaddons5  5.94.0-1
ii  libkf5crash5   5.94.0-1
ii  libkf5dbusaddons5  5.94.0-1
ii  libkf5i18n55.94.0-1+b1
ii  libkf5iconthemes5  5.94.0-1
ii  libkf5itemmodels5  5.94.0-1
ii  libkf5libkleo5 [libkf5libkleo5-22.04]  4:22.04.1-1
ii  libkf5mime5abi1 [libkf5mime5-22.04]22.04.1-1
ii  libkf5notifications5   5.94.0-1
ii  libkf5textwidgets5 5.94.0-1
ii  libkf5widgetsaddons5   5.94.0-2
ii  libkf5windowsystem55.94.0-1
ii  libkf5xmlgui5  5.94.0-1+b1
ii  libqgpgme7 1.16.0-1.2
ii  libqt5core5a   5.15.4+dfsg-3
ii  libqt5dbus55.15.4+dfsg-3
ii  libqt5gui5 5.15.4+dfsg-3
ii  libqt5network5 5.15.4+dfsg-3
ii  libqt5printsupport55.15.4+dfsg-3
ii  libqt5widgets5 5.15.4+dfsg-3
ii  libstdc++6 12.1.0-4
ii  paperkey   1.6-1
ii  pinentry-qt1.2.0-1

kleopatra recommends no packages.

kleopatra suggests no packages.

-- no debconf information

Bug#1006266: Should not honor all_proxy?

[Kjö Hansi Glaz]

Hi,

I just hit this bug, and I'm wondering why reportbug honors all_proxy
while it doesn't support SOOCKS proxy?

GNOME sets all_proxy and ALL_PROXY when selecting a SOCKS proxy in the
settings.

While searching the web, I didn't find a specification for all_proxy,
but it seems widely used for SOCKS.

Thanks for maintaing reportbug

Bug#1013128: kleopatra: Kleopatra toolbar misses most icons on Gnome

[Kjö Hansi Glaz]

Subject: kleopatra: Kleopatra toolbar misses most icons on Gnome
Package: kleopatra
Version: 4:22.04.1-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

Install kleopatra, while using Gnome desktop (task-gnome-desktop
installed)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Start the application.

   * What was the outcome of this action?

The application toolbar is missing most icons. Only "Lookup on
server..." has an icon.

   * What outcome did you expect instead?

The toolbar to have icons, as shown on the screenshot in gnome-software.

Installing breeze-icon-theme solves he issue. Perhaps kleopatra should
recommands breeze-icon-theme, as quassel and pcmanfm do.

Thanks for maintaing kleopatra.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kleopatra depends on:
ii  dirmngr2.2.35-2
ii  gnupg  2.2.35-2
ii  gpgsm  2.2.35-2
ii  libassuan0 2.5.5-3
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-4
ii  libgpg-error0  1.45-2
ii  libgpgme11 1.17.1-4
ii  libgpgmepp61.17.1-4
ii  libkf5codecs5  5.94.0-1
ii  libkf5configcore5  5.94.0-3
ii  libkf5configgui5   5.94.0-3
ii  libkf5configwidgets5   5.94.0-1
ii  libkf5coreaddons5  5.94.0-1
ii  libkf5crash5   5.94.0-1
ii  libkf5dbusaddons5  5.94.0-1
ii  libkf5i18n55.94.0-1+b1
ii  libkf5iconthemes5  5.94.0-1
ii  libkf5itemmodels5  5.94.0-1
ii  libkf5libkleo5 [libkf5libkleo5-22.04]  4:22.04.1-1
ii  libkf5mime5abi1 [libkf5mime5-22.04]22.04.1-1
ii  libkf5notifications5   5.94.0-1
ii  libkf5textwidgets5 5.94.0-1
ii  libkf5widgetsaddons5   5.94.0-2
ii  libkf5windowsystem55.94.0-1
ii  libkf5xmlgui5  5.94.0-1+b1
ii  libqgpgme7 1.16.0-1.2
ii  libqt5core5a   5.15.4+dfsg-3
ii  libqt5dbus55.15.4+dfsg-3
ii  libqt5gui5 5.15.4+dfsg-3
ii  libqt5network5 5.15.4+dfsg-3
ii  libqt5printsupport55.15.4+dfsg-3
ii  libqt5widgets5 5.15.4+dfsg-3
ii  libstdc++6 12.1.0-4
ii  paperkey   1.6-1
ii  pinentry-qt1.2.0-1

kleopatra recommends no packages.

kleopatra suggests no packages.

-

Bug#1005065: bookletimposer does not start, bug 1005065

[Kjö Hansi Glaz]

Hi,

GMiller:
>> I can't reproduce this bug under latest debian. This looks specific
>> to your setup. Please provide steps for me to reproduce the bug
>> under debian stable.
> 
> By "latest debian" I assume you mean 11 Bullseye.

Yes.

> The problem may have been fixed in Bullseye?

Bookletimposer also works fine on fresh Debian 10 Buster. I don't think
the problem you describe has been spotted. But as you report a bug on
Debian, please provide steps to reproduce it on Debian.

> I will try "bookletimposer" again later this year after Ubuntu 22.04
> is released (based on 11 Bullseye) and let you know the result.
> 
Yes please. Thanks by advance.

Bug#1005065: bookletimposer does not start

[Kjö Hansi Glaz]

Hi,

GMiller:
> Package: bookletimposer
> Version: 0.3
> 
Thanks for trying bookletimposer.

> Traceback (most recent call last):
> File "/usr/bin/bookletimposer", line 165, in 
> main()
> File "/usr/bin/bookletimposer", line 140, in main
> ui = gui.BookletImposerUI(preferences)
> File "/usr/lib/python3/dist-packages/bookletimposer/gui.py", line 68, in 
> __init__
> self.__create_gui()
> File "/usr/lib/python3/dist-packages/bookletimposer/gui.py", line 78, in 
> __create_gui
> builder.add_from_file(os.path.join(config.get_datadir(),
> gi.repository.GLib.Error: g-file-error-quark: Failed to open file 
> “data/bookletimposer.ui”: No such file or directory (4)
> 
I can't reproduce this bug under latest debian. This looks specific to
your setup. Please provide steps for me to reproduce the bug under
debian stable.

Cheers

Bug#1002581: Patch tested

[Kjö Hansi Glaz]

Hi,

I hit this bug and was able to reproduce it with the following steps :

- add to sources.list:

deb cdrom://[Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64 DVD
Binary-1 20211218-11:13] bullseye Release

- make a change in software-properties-gtk, e.g. enable contrib

- click the "Close" button

- click the "Refresh" button

I applied the proposed path that fixed the issue for me.

Cheers

Bug#1001531: debian-cd: Please verify debian-cd signing key on keys.openpgp.org

[Kjö Hansi Glaz]

Package: debian-cd
Severity: normal

Dear debian-cd team,

The key used to sign Debian CDs cannot be downloaded from
keys.openpgp.org, as it is not verified. Would you please verify it?

It would also be useful to add a link to download the key on
https://www.debian.org/CD/verify to ease access to people new to OpenPGP
that are not familiar with searching the OpenPGP keyrings.

Please accept my apologies if I didn't file this issue in the right
place.

Thanks by advance

Bug#993668: CUPS is still missing in fresh GNOME Desktop install with 11.1

[Kjö Hansi Glaz]

Hi,

> Tagging this bug as pending

I installed a fresh system with 11.1 installer, and Settings -> Printers
in GNOME printing is still showing "Sorry! The system printing service
doesn't seem to be available.".

Did something went wrong?

Thanks by advance

Bug#991566: r-cran-bookdown: Please package version 0.22

[Kjö Hansi Glaz]

Package: r-cran-bookdown
Version: 0.21+dfsg-1
Severity: wishlist

Dear Maintainer,

Upstream released bookdown version 0.22 last april[1]. It includes
interesting new features and bugfixes. Would you consider packaging it?

Thanks for your work on bookdown in debian.

[1] https://github.com/rstudio/bookdown/releases/tag/v0.22

Bug#973424: Bug fixed in bookletimposer git

[Kjö Hansi Glaz]

I belive the duplicate naming is fixed in bookletimposer master.

Bug#978693: Bookletimposer - variable mismatch in file config.py

[Kjö Hansi Glaz]

Hi,

Sorry for the delay and thanks for the bug report.

I belive this is fixed by commit 7e335e6 in bookletimposer.

Thanks again

Bug#945165: Broken localisation

[Kjö Hansi Glaz]

I belive the bug is fixed in upstream master.

Bug#945167: SVG icon isn't found

[Kjö Hansi Glaz]

I belive the bug is fixed in upstream master.

Bug#945168: GTK button looks wrong

[Kjö Hansi Glaz]

I belive the bug is fixed in upstream master.

Louis-Philippe Véronneau:
> Package: bookletimposer
> Version: 0.3~beta1-1
> Severity: minor
> 
> The button for the "Copy the same group of input pages..." in the
> main GUI window looks wrong. I've attached a screenshot.
> 

Bug#935189: python-pypdf2 removal

[Kjö Hansi Glaz]

I pushed a 0.3beta1 tag ported to python3 and depends on python3-pypdf2.
Feedback is welcome!

Cheers

Bug#939104: bookletimposer: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency

[Kjö Hansi Glaz]

I pushed a 0.3beta1 tag ported to python3 and depends on
python3-distutils-extra. Feedback is welcome!

Cheers

Bug#926414: python3-grapefruit: Can't load python3-grapefruit under python 3.7.3

[Kjö Hansi Glaz]

Package: python3-grapefruit
Version: 0.1~a3+dfsg-6
Severity: important

bpython version 0.17.1 on top of Python 3.7.3 /usr/bin/python3
>>> import grapefruit
Traceback (most recent call last):
  File "", line 1, in 
import grapefruit
  File
"/usr/lib/python3/dist-packages/bpython/curtsiesfrontend/repl.py", line
251, in load_module
module = self.loader.load_module(name)
  File "/usr/lib/python3/dist-packages/grapefruit.py", line 22, in 
from past.builtins import xrange
ModuleNotFoundError: No module named 'past'

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-grapefruit depends on:
ii  python33.7.3-1
ii  python3-pkg-resources  40.8.0-1

python3-grapefruit recommends no packages.

Versions of packages python3-grapefruit suggests:
pn  python-grapefruit-doc  

-- no debconf information

Bug#737005: bookletimposer fails to start when current directory contains a 'data' directory

[Kjö Hansi Glaz]

BookeltImposer master should now only look for locale data directiory
when environnment variable DEBUG is set.

Bug#737165: bookletimposer crashes when Gtk couldn't be initialized

[Kjö Hansi Glaz]

BookletImposer master should now work when GTK couldn't be initialized.

Bug#886154: more stack trace

[Kjö Hansi Glaz]

Hi,

Simon McVittie:
> On Tue, 02 Jan 2018 at 18:42:00 +0000, Kjö Hansi Glaz wrote:
>> #1  0x7fe7b7c65278 in st_label_set_text (label=0x558a749ee890
>> [StLabel], text=0x558a772bcf90 "76") at ../src/st/st-label.c:331
> 
> Does the text "76" mean anything to you? Perhaps it's a battery level or
> the name of a wireless network near you or something? That would narrow
> it down a bit... it's hard to tell what caused a crash like this where
> most of the stack is "interpret JavaScript".
> 
No, sorry.

>> #23 0x7fe7b13f1040 in js::jit::InvokeFunctionInfo () at
>> /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
> 
> libmozjs-52-0-dbgsym would provide more information about this part of
> the stack, although it probably isn't particularly interesting.
> 
It was already installed.

> "thread apply all bt" might also be interesting: that'll tell us which
> threads were active and which were just waiting.

On gnome-shell coredump:

(gdb) thread apply all bt

Thread 15 (Thread 0x7fe774ff9700 (LWP 2073)):
#0  0x7fe7b8451b26 in futex_wait_cancelable (private=, expected=0, futex_word=0x558a723d0138)
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe7b8451b26 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x558a723d0180, cond=0x558a723d0110) at pthread_cond_wait.c:502
#2  0x7fe7b8451b26 in __pthread_cond_wait (cond=0x558a723d0110,
mutex=0x558a723d0180) at pthread_cond_wait.c:655
#3  0x7fe7afe393c4 in
js::ConditionVariable::wait(js::LockGuard&) (this=, lock=...)
at ./js/src/threading/posix/ConditionVariable.cpp:118
#4  0x7fe7afe39615 in
js::ConditionVariable::wait_for(js::LockGuard&,
mozilla::BaseTimeDuration const&)
(this=0x558a723d0110, lock=..., a_rel_time=...) at
./js/src/threading/posix/ConditionVariable.cpp:134
#5  0x7fe7b0234da5 in
js::GlobalHelperThreadState::wait(js::AutoLockHelperThreadState&,
js::GlobalHelperThreadState::CondVar,
mozilla::BaseTimeDuration)
(timeout=..., which=js::GlobalHelperThreadState::PRODUCER, locked=...,
this=) at ./js/src/vm/HelperThreads.cpp:786
#6  0x7fe7b0234da5 in js::HelperThread::threadLoop()
(this=0x558a7270e198) at ./js/src/vm/HelperThreads.cpp:1868
#7  0x7fe7b02555d2 in js::detail::ThreadTrampoline::callMain<0ul>(mozilla::IndexSequence<0ul>)
(this=0x558a7273d640) at ./js/src/threading/Thread.h:234
#8  0x7fe7b02555d2 in js::detail::ThreadTrampoline::Start(void*) (aPack=0x558a7273d640)
at ./js/src/threading/Thread.h:227
#9  0x7fe7b844b519 in start_thread (arg=0x7fe774ff9700) at
pthread_create.c:456
#10 0x7fe7b818da4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 14 (Thread 0x7fe7757fa700 (LWP 2072)):
#0  0x7fe7b8451b26 in futex_wait_cancelable (private=, expected=0, futex_word=0x558a723d013c)
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe7b8451b26 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x558a723d0180, cond=0x558a723d0110) at pthread_cond_wait.c:502
#2  0x7fe7b8451b26 in __pthread_cond_wait (cond=0x558a723d0110,
mutex=0x558a723d0180) at pthread_cond_wait.c:655
#3  0x7fe7afe393c4 in
js::ConditionVariable::wait(js::LockGuard&) (this=, lock=...)
at ./js/src/threading/posix/ConditionVariable.cpp:118
#4  0x7fe7afe39615 in
js::ConditionVariable::wait_for(js::LockGuard&,
mozilla::BaseTimeDuration const&)
(this=0x558a723d0110, lock=..., a_rel_time=...) at
./js/src/threading/posix/ConditionVariable.cpp:134
#5  0x7fe7b0234da5 in
js::GlobalHelperThreadState::wait(js::AutoLockHelperThreadState&,
js::GlobalHelperThreadState::CondVar,
mozilla::BaseTimeDuration)
(timeout=..., which=js::GlobalHelperThreadState::PRODUCER, locked=...,
this=) at ./js/src/vm/HelperThreads.cpp:786
#6  0x7fe7b0234da5 in js::HelperThread::threadLoop()
(this=0x558a7270dcc0) at ./js/src/vm/HelperThreads.cpp:1868
#7  0x7fe7b02555d2 in js::detail::ThreadTrampoline::callMain<0ul>(mozilla::IndexSequence<0ul>)
(this=0x558a7273d620) at ./js/src/threading/Thread.h:234
#8  0x7fe7b02555d2 in js::detail::ThreadTrampoline::Start(void*) (aPack=0x558a7273d620)
at ./js/src/threading/Thread.h:227
#9  0x7fe7b844b519 in start_thread (arg=0x7fe7757fa700) at
pthread_create.c:456
---Type  to continue, or q  to quit---
#10 0x7fe7b818da4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 13 (Thread 0x7fe7767fc700 (LWP 2070)):
#0  0x7fe7b8451b26 in futex_wait_cancelable (private=, expected=0, futex_word=0x558a723d013c)
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe7b8451b26 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x558a723d0180, cond=0x558a723d0110) at pthread_cond_wait.c:502
#2  0x7fe7b8451b26 in __pthread_cond_wait (cond=0x558a723d0110,
mutex=0x558a723d0180) at pthread_cond_wait.c:655
#3  0x7fe7afe393c4 in
js::ConditionVariable::wait(js::LockGuard&

Bug#886154: gnome-shell: segfault in libgobject

[Kjö Hansi Glaz]

Hi again

Simon McVittie:
> On Tue, 02 Jan 2018 at 19:03:12 +0100, Kjö Hansi Glaz wrote:
>> On the journal, I see:
>>
>> janv. 02 15:10:59 debian kernel: gnome-shell[2009]: segfault at 1b 
>> ip 7f775a314da2 sp 7ffc562f53a0 error 4 in libgobject-2.0.
> 
> Is there anything else at a nearby timestamp in the Journal? I'd expect
> to see messages logged from at least Xwayland, followed by all your
> applications crashing as they lose their Wayland or X11 displays. Any
> useful information here would be within a few seconds before or after
> the segfault.

Here it is:

janv. 02 19:18:20 debian gnome-shell[1981]: invalid unclassed pointer in
cast to 'ClutterText'
janv. 02 19:18:20 debian gnome-shell[1981]: clutter_text_get_editable:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:20 debian gnome-shell[1981]: clutter_text_get_text:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:20 debian gnome-shell[1981]: clutter_text_set_text:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:20 debian gnome-shell[1981]: clutter_content_invalidate:
assertion 'CLUTTER_IS_CONTENT (content)' failed
janv. 02 19:18:25 debian gnome-shell[1981]: invalid unclassed pointer in
cast to 'ClutterText'
janv. 02 19:18:25 debian gnome-shell[1981]: clutter_text_get_editable:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:25 debian gnome-shell[1981]: clutter_text_get_text:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:25 debian gnome-shell[1981]: clutter_text_set_text:
assertion 'CLUTTER_IS_TEXT (self)' failed
janv. 02 19:18:25 debian gnome-shell[1981]: clutter_content_invalidate:
assertion 'CLUTTER_IS_CONTENT (content)' failed

These happen every 5 seconds and doesn't seem related to the crash.

janv. 02 19:18:30 debian kernel: gnome-shell[1981]: segfault at 60 ip
7fe7ba4d0da2 sp 7fff897c1cb0 error 4 in libgobject-2.0.so.0.540
janv. 02 19:18:30 debian systemd[1]: Created slice
system-systemd\x2dcoredump.slice.
janv. 02 19:18:30 debian systemd[1]: Started Process Core Dump (PID
21041/UID 0).
janv. 02 19:18:32 debian gnome-terminal-[11504]: Error reading events
from display: Connexion ré-initialisée par le correspondant
janv. 02 19:18:32 debian gnome-calendar[19855]: Error reading events
from display: Relais brisé (pipe)
janv. 02 19:18:32 debian nautilus[18249]: Error reading events from
display: Relais brisé (pipe)
janv. 02 19:18:32 debian evolution-alarm[2270]: Error reading events
from display: Relais brisé (pipe)
janv. 02 19:18:32 debian parcimonie-appl[2279]: Error reading events
from display: Relais brisé (pipe)
janv. 02 19:18:32 debian systemd[1929]: gnome-terminal-server.service:
Main process exited, code=exited, status=1/FAILURE
janv. 02 19:18:32 debian systemd[1929]: gnome-terminal-server.service:
Failed with result 'exit-code'.
janv. 02 19:18:32 debian org.gnome.Shell.desktop[1981]: (EE)
janv. 02 19:18:32 debian org.gnome.Shell.desktop[1981]: Fatal server error:
janv. 02 19:18:32 debian org.gnome.Shell.desktop[1981]: (EE) failed to
read Wayland events: Connection reset by peer
janv. 02 19:18:32 debian org.gnome.Shell.desktop[1981]: (EE)
janv. 02 19:18:32 debian gnome-session[1950]:
gnome-session-binary[1950]: WARNING: Application
'org.gnome.Shell.desktop' killed by signal 11
janv. 02 19:18:32 debian polkitd(authority=local)[983]: Unregistered
Authentication Agent for unix-session:1 (system bus name :1.36, object p
janv. 02 19:18:32 debian gedit[18518]: Error reading events from
display: Relais brisé (pipe)
janv. 02 19:18:32 debian gnome-session-binary[1950]: WARNING:
Application 'org.gnome.Shell.desktop' killed by signal 11
janv. 02 19:18:32 debian gnome-session-binary[1950]: Unrecoverable
failure in required component org.gnome.Shell.desktop
janv. 02 19:18:32 debian libvirtd[1101]: 2018-01-02 18:18:32.249+:
1101: error : virNetSocketReadWire:1810 : End of file while reading da
janv. 02 19:18:32 debian sudo[20902]: pam_unix(sudo:session): session
closed for user root
janv. 02 19:18:32 debian pulseaudio[2060]: ICE default IO error handler
doing an exit(), pid = 2060, errno = 11
janv. 02 19:18:32 debian thunderbird.desktop[19178]:
xcb_connection_has_error() a retourné une valeur true
janv. 02 19:18:32 debian audit[19178]: AVC apparmor="DENIED"
operation="open" profile="thunderbird"
name="/etc/pulse/client.conf.d/00-disable
janv. 02 19:18:32 debian upowerd[1985]: unhandled action 'unbind' on
/sys/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0
janv. 02 19:18:32 debian bluetoothd[1544]: Endpoint unregistered:
sender=:1.41 path=/MediaEndpoint/A2DPSource
janv. 02 19:18:32 debian bluetoothd[1544]: Endpoint unregistered:
sender=:1.41 path=/MediaEndpoint/A2DPSink
janv. 02 19:18:32 debian systemd[1929]: pulseaudio.service: Main process
exited, code=exited, status=1/FAILURE
janv. 02 19:18:32 debian systemd[1929]: pulseaudio.service: Failed with
result 'exit-code'.
janv. 02 19:18:32 debia

Bug#886154: more stack trace

[Kjö Hansi Glaz]

The bug just happened again.

Actually there are two crashes, which you can find below:

$ coredumpctl | tee
TIMEPID   UID   GID SIG COREFILE  EXE
Tue 2018-01-02 19:18:33 CET2042  1000  1000   6 present
/usr/bin/Xwayland
Tue 2018-01-02 19:18:33 CET1981  1000  1000  11 present
/usr/bin/gnome-shell

$ coredumpctl gdb 1981
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
   PID: 1981 (gnome-shell)
   UID: 1000 (kjo)
   GID: 1000 (kjo)
Signal: 11 (SEGV)
 Timestamp: Tue 2018-01-02 19:18:30 CET (16min ago)
  Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-1.scope
  Unit: session-1.scope
 Slice: user-1000.slice
   Session: 1
 Owner UID: 1000 (kjo)
   Boot ID: 7e34854b901a48808bccff6b81e1ad5c
Machine ID: 
  Hostname: debian
   Storage:
/var/lib/systemd/coredump/core.gnome-shell.1000.7e34854b901a48808bccff6b81e1ad5c.1981.151491711000.lz4
   Message: Process 1981 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 1981:
#0  0x7fe7ba4d0da2 g_type_check_instance_cast
(libgobject-2.0.so.0)
#1  0x7fe7b7c65278 st_label_set_text (libst-1.0.so)
#2  0x7fe7ba4b2a3e g_object_setv (libgobject-2.0.so.0)
#3  0x7fe7ba4b39ce g_object_set_property
(libgobject-2.0.so.0)
#4  0x7fe7b919b4b7 n/a (libgjs.so.0)
#5  0x7fe7b023d6c6 n/a (libmozjs-52.so.0)
#6  0x7fe7b0252feb n/a (libmozjs-52.so.0)
#7  0x7fe7b025fcbe n/a (libmozjs-52.so.0)
#8  0x7fe7b02438f1 n/a (libmozjs-52.so.0)
#9  0x7fe7b024e846 n/a (libmozjs-52.so.0)
#10 0x7fe7b024ee1f n/a (libmozjs-52.so.0)
#11 0x7fe7b024f0f9 n/a (libmozjs-52.so.0)
#12 0x7fe7b0041079 n/a (libmozjs-52.so.0)
#13 0x0495889ce3c6 n/a (n/a)
#14 0x558a775b3400 n/a (n/a)
#15 0x049588bedfb5 n/a (n/a)
#16 0x558a75f3d3b8 n/a (n/a)
#17 0x0495889c4888 n/a (n/a)
#18 0x7fe7b0447e22 n/a (libmozjs-52.so.0)
#19 0x7fe7b045044b n/a (libmozjs-52.so.0)
#20 0x7fe7b024e8c4 n/a (libmozjs-52.so.0)
#21 0x7fe7b024ee1f n/a (libmozjs-52.so.0)
#22 0x7fe7b024f0f9 n/a (libmozjs-52.so.0)
#23 0x7fe7b00e3554
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE
(libmozjs-52.so.0)
#24 0x7fe7b91bbdb6 gjs_call_function_value (libgjs.so.0)
#25 0x7fe7b918d3f5 gjs_closure_invoke (libgjs.so.0)
#26 0x7fe7b91ab015 n/a (libgjs.so.0)
#27 0x7fe7ba4aaf9d g_closure_invoke
(libgobject-2.0.so.0)
#28 0x7fe7ba4c76bc n/a (libgobject-2.0.so.0)
#29 0x7fe7ba1d2893 n/a (libglib-2.0.so.0)
#30 0x7fe7ba1d1e15 g_main_context_dispatch
(libglib-2.0.so.0)
#31 0x7fe7ba1d21e0 n/a (libglib-2.0.so.0)
#32 0x7fe7ba1d24f2 g_main_loop_run (libglib-2.0.so.0)
#33 0x7fe7b8700e6c meta_run (libmutter-1.so.0)
#34 0x558a714e843c n/a (gnome-shell)
#35 0x7fe7b80c1561 n/a
(/lib/x86_64-linux-gnu/libc-2.25.so (deleted))

GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...Reading symbols from
/usr/lib/debug/.build-id/f9/74cabafae12353a7b2181aa4ba8f043b14afe4.debug...done.
done.
[New LWP 1981]
[New LWP 1983]
[New LWP 2024]
[New LWP 2059]
[New LWP 2066]
[New LWP 21040]
[New LWP 21035]
[New LWP 2067]
[New LWP 1984]
[New LWP 2068]
[New LWP 2071]
[New LWP 2069]
[New LWP 2070]
[New LWP 2072]
[New LWP 2073]
[Thread debugging using libthread_db enabled]
Using host libthread_db library 

Bug#886156: systemd: crashes the system on reloading

[Kjö Hansi Glaz]

Package: systemd
Version: 236-2
Severity: normal

Dear Maintainer,

When I upgrade the system with apt, the system often becomes
unresponsive after reloading systemd. Please find below the journal
output when this happens:

déc. 31 02:11:37 debian systemd[1]: Reloading.
déc. 31 02:11:37 debian kernel: BUG: unable to handle kernel paging request at 
0044004b
déc. 31 02:11:37 debian kernel: IP: __task_pid_nr_ns+0xc7/0xf0
déc. 31 02:11:37 debian kernel: PGD 0 P4D 0 
déc. 31 02:11:37 debian kernel: Oops:  [#1] SMP
déc. 31 02:11:37 debian kernel: Modules linked in: vhost_net vhost tap rfcomm 
fuse cmac bnep btusb btrtl btbcm btintel bluetooth drbg ansi_cp
déc. 31 02:11:37 debian kernel:  binfmt_misc thunderbolt xt_nat bcma 
snd_hda_core snd_hwdep snd_pcm_oss snd_mixer_oss sbs snd_pcm mei_me snd_
déc. 31 02:11:37 debian kernel:  raid1 raid0 multipath linear md_mod sr_mod 
cdrom sd_mod uas usb_storage crct10dif_pclmul crc32_pclmul crc32c
déc. 31 02:11:37 debian kernel: CPU: 3 PID: 1 Comm: systemd Not tainted 
4.14.0-2-amd64 #1 Debian 4.14.7-1
déc. 31 02:11:37 debian kernel: Hardware name: Apple Inc. 
MacBookPro9,2/Mac-, BIOS MBP91.88Z.00D3.B08.1208081132 
08/08/2012
déc. 31 02:11:37 debian kernel: task: 979d1ce5f040 task.stack: 
ad71018cc000
déc. 31 02:11:37 debian kernel: RIP: 0010:__task_pid_nr_ns+0xc7/0xf0
déc. 31 02:11:37 debian kernel: RSP: 0018:ad71018cfdc8 EFLAGS: 00010206
déc. 31 02:11:37 debian kernel: RAX:  RBX: 979d12323400 
RCX: 00440047
déc. 31 02:11:37 debian kernel: RDX: b4e42d20 RSI:  
RDI: 979d0de8d9a0
déc. 31 02:11:37 debian kernel: RBP: ad71018cfdc8 R08: 1000 
R09: 001e
déc. 31 02:11:37 debian kernel: R10: 0020 R11: 979d11bb801d 
R12: ad71018cff18
déc. 31 02:11:37 debian kernel: R13: 979b9d059900 R14: 979d0de8d410 
R15: 979d12323400
déc. 31 02:11:37 debian kernel: FS:  7f5d18dd4980() 
GS:979d2f38() knlGS:
déc. 31 02:11:37 debian kernel: CS:  0010 DS:  ES:  CR0: 
80050033
déc. 31 02:11:37 debian kernel: CR2: 0044004b CR3: 00045c246004 
CR4: 001626e0
déc. 31 02:11:37 debian kernel: Call Trace:
déc. 31 02:11:37 debian kernel:  cgroup_procs_show+0x19/0x30
déc. 31 02:11:37 debian kernel:  cgroup_seqfile_show+0x4c/0xb0
déc. 31 02:11:37 debian kernel:  kernfs_seq_show+0x21/0x30
déc. 31 02:11:37 debian kernel:  seq_read+0x2ec/0x3f0
déc. 31 02:11:37 debian kernel:  kernfs_fop_read+0x134/0x180
déc. 31 02:11:37 debian kernel:  ? security_file_permission+0x9b/0xc0
déc. 31 02:11:37 debian kernel:  __vfs_read+0x18/0x40
déc. 31 02:11:37 debian kernel:  vfs_read+0x8e/0x130
déc. 31 02:11:37 debian kernel:  SyS_read+0x55/0xc0
déc. 31 02:11:37 debian kernel:  system_call_fast_compare_end+0xc/0x97
déc. 31 02:11:37 debian kernel: RIP: 0033:0x7f5d1871175d
déc. 31 02:11:37 debian kernel: RSP: 002b:7ffea35b1b70 EFLAGS: 0293 
ORIG_RAX: 
déc. 31 02:11:37 debian kernel: RAX: ffda RBX: 55c69a002910 
RCX: 7f5d1871175d
déc. 31 02:11:37 debian kernel: RDX: 1000 RSI: 55c699feb290 
RDI: 0018
déc. 31 02:11:37 debian kernel: RBP: 7f5d189cd440 R08: 7f5d189d1178 
R09: 1010
déc. 31 02:11:37 debian kernel: R10: 0020 R11: 0293 
R12: 
déc. 31 02:11:37 debian kernel: R13:  R14: 0018 
R15: 55c69a06fff0
déc. 31 02:11:37 debian kernel: Code: 04 74 0e 89 f6 48 8d 04 76 48 8d 04 c5 90 
05 00 00 48 8b bf 58 05 00 00 48 01 c7 31 c0 48 8b 0f 48 85 c
déc. 31 02:11:37 debian kernel: RIP: __task_pid_nr_ns+0xc7/0xf0 RSP: 
ad71018cfdc8
déc. 31 02:11:37 debian kernel: CR2: 0044004b
déc. 31 02:11:37 debian kernel: ---[ end trace b6c75a92425e9881 ]---
déc. 31 02:11:37 debian kernel: [ cut here ]
déc. 31 02:11:37 debian kernel: WARNING: CPU: 1 PID: 1 at 
/build/linux-NHzxYj/linux-4.14.7/kernel/fork.c:419 __put_task_struct+0xf0/0x150
déc. 31 02:11:37 debian kernel: Modules linked in: vhost_net vhost tap rfcomm 
fuse cmac bnep btusb btrtl btbcm btintel bluetooth drbg ansi_cp
déc. 31 02:11:37 debian kernel:  binfmt_misc thunderbolt xt_nat bcma 
snd_hda_core snd_hwdep snd_pcm_oss snd_mixer_oss sbs snd_pcm mei_me snd_
déc. 31 02:11:37 debian kernel:  raid1 raid0 multipath linear md_mod sr_mod 
cdrom sd_mod uas usb_storage crct10dif_pclmul crc32_pclmul crc32c
déc. 31 02:11:37 debian kernel: CPU: 1 PID: 1 Comm: systemd Tainted: G  D   
  4.14.0-2-amd64 #1 Debian 4.14.7-1
déc. 31 02:11:37 debian kernel: Hardware name: Apple Inc. 
MacBookPro9,2/Mac-, BIOS MBP91.88Z.00D3.B08.1208081132 
08/08/2012
déc. 31 02:11:37 debian kernel: task: 979d1ce5f040 task.stack: 
ad71018cc000
déc. 31 02:11:37 debian kernel: RIP: 0010:__put_task_struct+0xf0/0x150
déc. 31 02:11:37 debian kernel: RSP: 0018:ad71018cfda0 EFLAGS: 

Bug#886154: gnome-shell: segfault in libgobject

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.26.2-2
Severity: normal

Dear Maintainer,

A few times a day, gnome-shell (used as a wayland compositor) crashes,
ending the whole user session. I failed to determine a pattern in the
crash.

On the journal, I see:

janv. 02 15:10:59 debian kernel: gnome-shell[2009]: segfault at 1b ip 
7f775a314da2 sp 7ffc562f53a0 error 4 in libgobject-2.0.

2nd time:

janv. 02 16:01:18 debian kernel: gnome-shell[20253]: segfault at c0573 ip 
7f534d926da2 sp 7ffcb92eb860 error 4 in libgobject-2.0.

I found a core file with the same timastamp:

-rw--- 1 user user 122M janv.  2 16:01 core

Opening it with gdb --core

Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core -listen 
4 -listen 5 -displayfd'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f0012018a70 in ?? ()
[Current thread is 1 (LWP 20272)]
(gdb) bt
#0  0x7f0012018a70 in ?? ()
#1  0x0a392000 in ?? ()
#2  0x in ?? ()

I installed -dbgsym packages for all xwayland package dependencies, but
it doesn't help. Please provide guidance if you need more informations.

Also, I don't know if I should file this bug under gnome-shell or xwayland.

Thanks for maintaining gnome-shell


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  caribou  0.4.21-4
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-2
ii  evolution-data-server3.26.3-4
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.26.2-2
ii  gir1.2-caribou-1.0   0.4.21-4
ii  gir1.2-freedesktop   1.54.1-4
ii  gir1.2-gcr-3 3.20.0-6
ii  gir1.2-gdesktopenums-3.0 3.24.1-2
ii  gir1.2-gdm-1.0   3.26.2.1-3
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.54.1-4
ii  gir1.2-gnomebluetooth-1.03.26.1-2
ii  gir1.2-gnomedesktop-3.0  3.26.2-4
ii  gir1.2-gtk-3.0   3.22.26-2
ii  gir1.2-gweather-3.0  3.26.1-2
ii  gir1.2-ibus-1.0  1.5.17-3
ii  gir1.2-mutter-1  3.26.2-1
ii  gir1.2-networkmanager-1.01.10.2-1
ii  gir1.2-nmgtk-1.0 1.8.10-1
ii  gir1.2-pango-1.0 1.40.14-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.20-2
ii  gir1.2-soup-2.4  2.60.2-2
ii  gir1.2-upowerglib-1.00.99.7-1
ii  gjs  1.50.2-2
ii  gnome-backgrounds3.26.2-2
ii  gnome-settings-daemon3.26.2-1
ii  gnome-shell-common   3.26.2-2
ii  gsettings-desktop-schemas3.24.1-2
ii  libasound2   1.1.3-5
ii  libatk-bridge2.0-0   2.26.1-1
ii  libatk1.0-0  2.26.1-2
ii  libc62.25-6
ii  libcairo21.15.8-3
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libdbus-glib-1-2 0.108-3
ii  libecal-1.2-19   3.26.3-4
ii  libedataserver-1.2-223.26.3-4
ii  libgcr-base-3-1  3.20.0-6
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libgirepository-1.0-11.54.1-4
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.50.2-2
ii  libglib2.0-0 2.54.2-5
ii  libglib2.0-bin   2.54.2-5
ii  libgstreamer1.0-01.12.4-1
ii  libgtk-3-0   3.22.26-2
ii  libical3 3.0.1-5
ii  libjson-glib-1.0-0   1.4.2-3
ii  libmutter-1-03.26.2-1
ii  libnm-glib4  1.10.2-1
ii  libnm-util2  1.10.2-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpolkit-agent-1-0  0.105-18
ii  

Bug#857391: Patch incompatible with wayland

[Kjö Hansi Glaz]

Hi,

I encountered the problem covered by this bug report and tried the
attached patch on my sid system. Unfortunately, it doesn't work under
wayland :

(gnome-logs:20337): Gtk-WARNING **: cannot open display:

Cheers

Bug#883574: [Pkg-libvirt-maintainers] Bug#883574: libvirt-daemon-system: fails to start any VM with apparmor enforced

[Kjö Hansi Glaz]

Hi,

> Please provide logging output

audit[3232]: AVC apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="libvirt-3219c451-fcb5-4e6d-
kernel: audit: type=1400 audit(1512470093.378:89): apparmor="STATUS"
operation="profile_replace" profile="unconfined"
audit[3253]: AVC apparmor="DENIED" operation="mount" info="failed mntpnt
match" error=-13 profile="/usr/sbin/libvirtd
kernel: audit: type=1400 audit(1512470093.386:90): apparmor="DENIED"
operation="mount" info="failed mntpnt match" err
libvirtd[1321]: 2017-12-05 10:34:53.404+: 1338: error :
virCommandHandshakeWait:2718 : Child quit during startup
libvirtd[1321]: 2017-12-05 10:34:53.407+: 1338: error :
qemuProcessReportLogError:1885 : internal error: Process

libvirt: QEMU Driver error : internal error: Process exited prior to
exec: libvirt:  error : Fail
Error: libvirt failed to start domain

> and steps to reproduce,

>From libvirt create new virtual machine in qemu:///system

The same error happens if I start any other VM, which used to start fine
with libvirt 3.8.0

> kernel version and what else might be needed to reproduce the problem.

4.14.0-1-amd64

> Ask yourself what makes your installation different from the ones
> that work with apparmor enabled.

I'm sorry but I don't see how my libvirt/apparmor installation differs
from another sid system.

Cheers

Bug#883574: libvirt-daemon-system: fails to start any VM with apparmor enforced

[Kjö Hansi Glaz]

Package: libvirt-daemon-system
Version: 3.9.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Apparmor is in enforce mode.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Try to start any VM.

   * What was the outcome of this action?

I get the following error:

   libvirtError: internal error: Process exited prior to exec: libvirt:
   error : Failed to switch root mount into slave mode: Permission denied

Please note that I don't see any line in the journal.

   * What outcome did you expect instead?

The VM to start. Setting apparmor to complain mode (aa-complain
usr.sbin.libvirtd) worksaround the issue


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.116
ii  debconf [debconf-2.0]  1.5.65
ii  gettext-base   0.19.8.1-4
ii  iptables   1.6.1-2+b1
ii  libacl12.2.52-3+b1
ii  libapparmor1   2.11.1-3
ii  libaudit1  1:2.8.1-2
ii  libblkid1  2.30.2-0.1
ii  libc6  2.25-3
ii  libcap-ng0 0.7.7-3.1+b1
ii  libdbus-1-31.12.2-1
ii  libdevmapper1.02.1 2:1.02.145-4.1
ii  libgnutls303.5.16-1
ii  libnl-3-2003.2.27-2
ii  libnl-route-3-200  3.2.27-2
ii  libnuma1   2.0.11-2.1
ii  libselinux12.7-2
ii  libvirt-clients3.9.0-1
ii  libvirt-daemon 3.9.0-1
ii  libvirt0   3.9.0-1
ii  libxml22.9.4+dfsg1-5.1
ii  libyajl2   2.1.0-2+b3
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20170808
ii  policykit-10.105-18

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils  1.5-14
ii  dmidecode 3.1-1
ii  dnsmasq-base  2.78-1
ii  ebtables  2.0.10.4-3.5+b1
ii  iproute2  4.9.0-2.1
ii  parted3.2-18

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.11.1-3
pn  auditd  
ii  nfs-common  1:1.3.4-2.1+b1
ii  pm-utils1.4.1-17
pn  radvd   
ii  systemd 235-3
pn  systemtap   
pn  zfsutils

-- debconf information:
  libvirt-daemon-system/id_warning: true

Bug#859336: Cloned bug report

[Kjö Hansi Glaz]

Hi,

Thanks mercedes508 for reporting this issue with seahorse. However, it
appears that the error you face "trying for the first time to sign,
every signature after that first error goes fine." is not related to the
one that was tracked by this bug.

I thus cloned this bug report as 862552 [1].

Please follow up there.

Thanks again for your contribution!

1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862552

Bug#806445:

[Kjö Hansi Glaz]

> 3. "Sign This Key" (whatever option I choose)
>   * 8.2: General Error
>   * stretch: General Error
>   * stretch + patch: General Error

This last line is wrong:

3. "Sign This Key" (whatever option I choose)
   * stretch + patch: OK

According to more tests, I *can* sign keys with the patch under sid and
stretch, while I can't without.

However, even without the patch, I can't add subkeys.

Bug#806445:

[Kjö Hansi Glaz]

> So, Kjö, Beren and Sebastian: can one of you please confirm whether
> you've experienced one of the problems this bug report is about on
> Debian Jessie?

0. "Add subkey to ..."
   * 8.2: General Error
   * stretch: General Error
   * stretch + patch: General Error

1. check the checkbox "I trust signatures from 'USER' on others key"
   * 8.2: OK
   * stretch: General Error
   * stretch + patch: OK

2. change the value of the field "You Trust The Owner:"
   * 8.2: OK
   * stretch: General Error
   * stretch + patch: OK

3. "Sign This Key" (whatever option I choose)
   * 8.2: General Error
   * stretch: General Error
   * stretch + patch: General Error

So you're right, the patch pointed on message #10 does not solve the
issue this bug was initially about, nor the error while signing key.
However, the patch solves the regressions introduced by Debian Stretch.

> If yes, what version of libgpgme11 do you
> have installed.

Debian 8.2 I have libgpgme11 1.5.1-6.

I'm trying to find if upstream has patches that solves the subkey and
signing issues.

Bug#806445: Yo

[Kjö Hansi Glaz]

The same bug happens when I:

- check the checkbox "I trust signatures from 'USER' on others key"
- change the value of the field "You Trust The Owner:"
- "Sign This Key" (whatever option I choose)

The upstream patch
https://git.gnome.org/browse/seahorse/patch/?id=cdfc5b297d7420e47b9c973e8b8cb1b0fb576421
applies on 3.20.0.

The attached debdiff fixes the issue for me.

diff -Nru seahorse-3.20.0/debian/changelog seahorse-3.20.0/debian/changelog
--- seahorse-3.20.0/debian/changelog2016-12-05 18:51:47.0 +0100
+++ seahorse-3.20.0/debian/changelog2017-04-01 16:06:42.0 +0200
@@ -1,3 +1,12 @@
+seahorse (3.20.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * 01_ignore_KEY_CONSIDERED.patch: patch from upstream git. Ignore
+KEY_CONSIDERED line introduced in gpg 2.1.13 (Closes: #806445).
+  * Bump libgpgme-dev build-dependency to >= 1.7.0
+
+ -- Kjö Hansi Glaz <k...@a4nancy.net.eu.org>  Sat, 01 Apr 2017 16:06:42 +0200
+
 seahorse (3.20.0-3) unstable; urgency=medium
 
   * Switch libgpgme11-dev build-dependency to libgpgme-dev.
diff -Nru seahorse-3.20.0/debian/control seahorse-3.20.0/debian/control
--- seahorse-3.20.0/debian/control  2016-12-05 18:50:49.0 +0100
+++ seahorse-3.20.0/debian/control  2017-04-01 16:06:42.0 +0200
@@ -16,7 +16,7 @@
libgck-1-dev (>= 3.11.91),
libgcr-3-dev (>= 3.11.91),
libglib2.0-dev (>= 2.10.0),
-   libgpgme-dev (>= 1.0.0),
+   libgpgme-dev (>= 1.7.0),
libgtk-3-dev (>= 3.16),
libldap2-dev,
libsecret-1-dev (>= 0.16),
diff -Nru seahorse-3.20.0/debian/control.in seahorse-3.20.0/debian/control.in
--- seahorse-3.20.0/debian/control.in   2016-12-05 18:50:49.0 +0100
+++ seahorse-3.20.0/debian/control.in   2017-04-01 16:06:42.0 +0200
@@ -12,7 +12,7 @@
libgck-1-dev (>= 3.11.91),
libgcr-3-dev (>= 3.11.91),
libglib2.0-dev (>= 2.10.0),
-   libgpgme-dev (>= 1.0.0),
+   libgpgme-dev (>= 1.7.0),
libgtk-3-dev (>= 3.16),
libldap2-dev,
libsecret-1-dev (>= 0.16),
diff -Nru seahorse-3.20.0/debian/patches/01_ignore_KEY_CONSIDERED.patch 
seahorse-3.20.0/debian/patches/01_ignore_KEY_CONSIDERED.patch
--- seahorse-3.20.0/debian/patches/01_ignore_KEY_CONSIDERED.patch   
1970-01-01 01:00:00.0 +0100
+++ seahorse-3.20.0/debian/patches/01_ignore_KEY_CONSIDERED.patch   
2017-04-01 16:06:42.0 +0200
@@ -0,0 +1,56 @@
+From cdfc5b297d7420e47b9c973e8b8cb1b0fb576421 Mon Sep 17 00:00:00 2001
+From: Tobias Mueller <mue...@cryptobitch.de>
+Date: Tue, 14 Feb 2017 22:05:19 +0100
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=778607
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806445
+Origin: 
https://git.gnome.org/browse/seahorse/commit/?id=cdfc5b297d7420e47b9c973e8b8cb1b0fb576421
+Subject: gpg: Ignore KEY_CONSIDERED line introduced in gpg 2.1.13
+
+gpg 2.1.13 introduced a new status line, KEY_CONSIDERED:
+https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html
+gpgme 1.7.0 supported it:
+https://lists.gnupg.org/pipermail/gnupg-commits/2016-May/012130.html
+
+The line seems innocent in the sense that it tells you what keys GnuPG
+looked at without doing anything.  We can probably safely ignore that
+line, as we ignore many other lines already.
+
+https://bugzilla.gnome.org/show_bug.cgi?id=778607
+
+Signed-off-by: Stef Walter <st...@redhat.com>
+ * Fixed this so it compiles
+---
+ configure.ac| 2 +-
+ pgp/seahorse-gpgme-key-op.c | 3 ++-
+ 2 files changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 0f748e3..fc4493c 100644
+--- a/configure.ac
 b/configure.ac
+@@ -10,7 +10,7 @@ GTK_REQ=3.4.0
+ GTK_MAX=GTK_VERSION_3_4
+ 
+ GNUPG_ACCEPTED="2.0.12 2.1.4"
+-GPGME_REQUIRED=1.0.0
++GPGME_REQUIRED=1.7.0
+ LIBSECRET_REQUIRED=0.16
+ AVAHI_GLIB_REQUIRED=0.6
+ 
+diff --git a/pgp/seahorse-gpgme-key-op.c b/pgp/seahorse-gpgme-key-op.c
+index a765033..3f81850 100644
+--- a/pgp/seahorse-gpgme-key-op.c
 b/pgp/seahorse-gpgme-key-op.c
+@@ -330,7 +330,8 @@ seahorse_gpgme_key_op_edit (gpointer data, 
gpgme_status_code_t status,
+   status == GPGME_STATUS_BAD_PASSPHRASE || status == 
GPGME_STATUS_USERID_HINT ||
+   status == GPGME_STATUS_SIGEXPIRED || status == 
GPGME_STATUS_KEYEXPIRED ||
+   status == GPGME_STATUS_PROGRESS || status == 
GPGME_STATUS_KEY_CREATED ||
+-  status == GPGME_STATUS_ALREADY_SIGNED || status == 
GPGME_STATUS_MISSING_PASSPHRASE) 
++  status == GPGME_STATUS_ALREADY_SIGNED || status == 
GPGME_STATUS_MISSING_PASSPHRASE ||
++  status == GPGME_STATUS_KEY_CONSIDERED)
+   return parms->err;
+ 
+   g_debug ("[edit key] s

Bug#858278: gnome-shell segfaults on networkmanager upgrade

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.22.3-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

An apt upgrade containing network-manager (1.6.2-2, 1.6.2-3)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt upgrade

   * What was the outcome of this action?

gnome-shell crashed. As I use a GNOME Wayland session, this closed the
session and displaid GDM.

The system journal contains:

kernel: gnome-shell[4078]: segfault at 10 ip 7fd67e5768f1 sp 
7ffd09cc7430 error 6 in libnm-glib.so.4.9.0 (deleted)[7fd67e566000+4]
gnome-shell[4078]: g_type_instance_get_private: assertion 'instance != NULL && 
instance->g_class != NULL' failed
gnome-session[4045]: gnome-session-binary[4045]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
gnome-session-binary[4045]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 11
gnome-session-binary[4045]: Unrecoverable failure in required component 
org.gnome.Shell.desktop
org.gnome.Shell.desktop[4078]: (EE)
org.gnome.Shell.desktop[4078]: Fatal server error:
org.gnome.Shell.desktop[4078]: (EE) failed to read Wayland events: Connection 
reset by peer
org.gnome.Shell.desktop[4078]: (EE)

   * What outcome did you expect instead?

The session to keep running, or some confirmation before killing the
session.

Thanks for maintaining gnome-shell!

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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.22.6-1
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-atspi-2.0 2.22.0-5+b1
ii  gir1.2-caribou-1.0   0.4.21-1+b1
ii  gir1.2-freedesktop   1.50.0-1+b1
ii  gir1.2-gcr-3 3.20.0-5
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.3-1
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-gnomebluetooth-1.03.20.1-1
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.9-4
ii  gir1.2-gweather-3.0  3.20.4-1
ii  gir1.2-ibus-1.0  1.5.14-2
ii  gir1.2-mutter-3.03.22.3-2
ii  gir1.2-networkmanager-1.01.6.2-3
ii  gir1.2-nmgtk-1.0 1.4.6-1
ii  gir1.2-pango-1.0 1.40.4-1
ii  gir1.2-polkit-1.00.105-17
ii  gir1.2-soup-2.4  2.56.0-2
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-2
ii  gir1.2-upowerglib-1.00.99.4-4+b1
ii  gjs  1.46.0-1+b2
ii  gnome-backgrounds3.22.1-1
ii  gnome-settings-daemon3.22.2-1
ii  gnome-shell-common   3.22.3-2
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-2
ii  libecal-1.2-19   3.22.6-1
ii  libedataserver-1.2-223.22.6-1
ii  libgcr-base-3-1  3.20.0-5
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgirepository-1.0-11.50.0-1+b1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1+b2
ii  libglib2.0-0 2.50.3-2
ii  libglib2.0-bin   2.50.3-2
ii  libgstreamer1.0-01.10.4-1
ii  libgtk-3-0   3.22.9-4
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-5
ii  libjson-glib-1.0-0   1.2.6-1
ii  libmozjs-24-024.2.0-5.1+b2
ii  libmutter0i  3.22.3-2
ii  libnm-glib4  1.6.2-3
ii  libnm-util2  1.6.2-3
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  

Bug#820968: gnome-shell: Mouse stuck after switching desktop via shortcut keys

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.22.2-4
Followup-For: Bug #820968

Hi,

I have the same issue, even though

/org/gnome/desktop/wm/preferences/focus-mode=click

Very often, after changing window, only the shell interface reacts to
mouse clicks, not the window conntents. This looks similar to #771805
and #748224, even though the circumstances are not exactly the same.

Cheers

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evolution-data-server3.22.4-1
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-atspi-2.0 2.22.0-5
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.50.0-1
ii  gir1.2-gcr-3 3.20.0-5
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.1-2
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.7-2
ii  gir1.2-gweather-3.0  3.20.4-1
ii  gir1.2-ibus-1.0  1.5.14-2
ii  gir1.2-mutter-3.03.22.2-3
ii  gir1.2-networkmanager-1.01.6.0-1
ii  gir1.2-nmgtk-1.0 1.4.4-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  gir1.2-polkit-1.00.105-17
ii  gir1.2-soup-2.4  2.56.0-2
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-2
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gjs  1.46.0-1+b1
ii  gnome-backgrounds3.22.1-1
ii  gnome-settings-daemon3.22.1-1
ii  gnome-shell-common   3.22.2-4
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-2
ii  libecal-1.2-19   3.22.4-1
ii  libedataserver-1.2-223.22.4-1
ii  libgcr-base-3-1  3.20.0-5
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libgirepository-1.0-11.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1+b1
ii  libglib2.0-0 2.50.2-2
ii  libglib2.0-bin   2.50.2-2
ii  libgstreamer1.0-01.10.3-1
ii  libgtk-3-0   3.22.7-2
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-5
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-5.1
ii  libmutter0i  3.22.2-3
ii  libnm-glib4  1.6.0-1
ii  libnm-util2  1.6.0-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpolkit-agent-1-0  0.105-17
ii  libpolkit-gobject-1-00.105-17
ii  libpulse-mainloop-glib0  10.0-1
ii  libpulse010.0-1
ii  libsecret-1-00.18.5-2
ii  libstartup-notification0 0.12-4
ii  libsystemd0  232-18
ii  libtelepathy-glib0   0.24.1-1.1
ii  libwayland-client0   1.12.0-1
ii  libx11-6 2:1.6.4-3
ii  libxfixes3   1:5.0.3-1
ii  mutter   3.22.2-3
ii  python3  3.5.3-1
ii  telepathy-mission-control-5  1:5.16.3-2.1

Versions of packages gnome-shell recommends:
ii  gdm33.22.1-2
ii  gkbd-capplet3.22.0.1-1
ii  gnome-contacts  3.22.1-1+b1
ii  gnome-control-center  

Bug#740503: debian-installer: check-missing-firmware does not work with a USB drive that contains a partition table

[Kjö Hansi Glaz]

Package: debian-installer
Version: stretch-alpha8-amd64
Followup-For: Bug #740503

Dear Maintainer,

   * What led up to the situation?

I followed the steps at
https://www.debian.org/releases/testing/amd64/ch06s04.html.en to put the
required firmware for installing over wifi.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I put the USB stick containing FAT filesystem on its 1st partition, with
a firmware/ directory containing the contents of
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/testing/current/firmware.tar.gz

   * What was the outcome of this action?

The isntaller fails to load the firmware and proposes to try again over
and over.

   * What outcome did you expect instead?

The firmware to be loaded to continue installation over wifi.

Please note that the right firmware was there as unpacking it and
placing it in /lib/firmware manually worked.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Bug#846534: libvirt-daemon-system: VM with usb host device fails to start when apparmor is enabled

[Kjö Hansi Glaz]

Package: libvirt-daemon-system
Version: 2.4.0-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Define a VM with an USB host device:


  


  
  


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Try to start the VM on a system with apparmor enabled

   * What was the outcome of this action?

libvirtError: internal error: qemu unexpectedly closed the monitor: 
2016-12-01T22:30:29.196276Z qemu-system-x86_64: -device 
usb-host,hostbus=3,hostaddr=5,id=hostdev0,bus=usb.0,port=4: failed to find host 
usb device 3:5

The system journal contains apparmor errors, see below.

   * What outcome did you expect instead?

The VM to start.

   * Notes

Please note that there is an ubuntu bug for this issue:

https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1515791

   * System log when starting the VM:

déc. 01 23:34:34 host audit[8338]: AVC apparmor="STATUS" 
operation="profile_replace" name="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
pid=8338 comm="apparmor_parser"
déc. 01 23:34:34 host kernel: audit: type=1400 audit(1480631674.577:394): 
apparmor="STATUS" operation="profile_replace" 
name="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" pid=8338 
comm="apparmor_parser"
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/sys/module/vhost/parameters/max_mem_regions" pid=8340 
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host kernel: audit: type=1400 audit(1480631674.625:395): 
apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/sys/module/vhost/parameters/max_mem_regions" pid=8340 
comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/proc/8340/task/8343/comm" pid=8340 comm="qemu-system-x86" 
requested_mask="rw" denied_mask="rw" fsuid=117 ouid=117
déc. 01 23:34:34 host kernel: audit: type=1400 audit(1480631674.625:396): 
apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/proc/8340/task/8343/comm" pid=8340 comm="qemu-system-x86" 
requested_mask="rw" denied_mask="rw" fsuid=117 ouid=117
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/proc/8340/task/8344/comm" pid=8340 comm="qemu-system-x86" 
requested_mask="rw" denied_mask="rw" fsuid=117 ouid=117
déc. 01 23:34:34 host kernel: audit: type=1400 audit(1480631674.625:397): 
apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/proc/8340/task/8344/comm" pid=8340 comm="qemu-system-x86" 
requested_mask="rw" denied_mask="rw" fsuid=117 ouid=117
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/c189:256" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/+usb:2-1:1.0" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/c189:129" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/c189:0" pid=8340 comm="qemu-system-x86" requested_mask="r" 
denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/+usb:1-1.1:1.1" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/+usb:3-0:1.0" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/+usb:2-1.8.3:1.1" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" operation="open" 
profile="libvirt-bd2a0f7a-1637-4dc2-90c4-55b9b1980d86" 
name="/run/udev/data/c189:132" pid=8340 comm="qemu-system-x86" 
requested_mask="r" denied_mask="r" fsuid=117 ouid=0
déc. 01 23:34:34 host audit[8340]: AVC apparmor="DENIED" 

Bug#843471: libspice-client-gtk-3.0-5: virt-manager segfaults in libspice-client-gtk

[Kjö Hansi Glaz]

Package: libspice-client-gtk-3.0-5
Version: 0.33-3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I opened a VM with spice display in virt-manager

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I didn't identify the precise action that trigger the crash, but it
happened to me several times today.

   * What was the outcome of this action?

A segfault, with the following backtrace when running under gdb (sorry, I
didn't find a -dbg package for libspice-client):

Thread 1 "python2" received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: Aucun fichier ou dossier de ce type.
(gdb) 
(gdb) bt
#0  0x76f7a496 in strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x7fffa90e270d in  () at 
/usr/lib/x86_64-linux-gnu/libspice-client-gtk-3.0.so.5
#2  0x7fffe4aaa230 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x7fffe4aa9579 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x7633645b in  (instance=0x57b799a0, 
detailed_signal=0x7fffe4b31ca4 "selection-received") at 
././gobject/gsignal.c:3487
#4  0x7631af75 in g_closure_invoke (closure=0x56b2ac80, 
return_value=return_value@entry=0x0, n_param_values=3, 
param_values=param_values@entry=0x7fffcf10, 
invocation_hint=invocation_hint@entry=0x7fffce90) at 
././gobject/gclosure.c:804
#5  0x7632cf82 in signal_emit_unlocked_R 
(node=node@entry=0x565fd800, detail=detail@entry=0, 
instance=instance@entry=0x57b799a0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffcf10)
at ././gobject/gsignal.c:3635
#6  0x76335bcc in g_signal_emit_valist 
(instance=instance@entry=0x57b799a0, signal_id=signal_id@entry=81, 
detail=detail@entry=0, var_args=var_args@entry=0x7fffd138) at 
././gobject/gsignal.c:3391
#8  0x7fffe49c11a3 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x7fffe49c523d in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7fffe4934651 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x7631b1a4 in _g_closure_invoke_va 
(closure=closure@entry=0x565fdd70, 
return_value=return_value@entry=0x7fffd4d0, 
instance=instance@entry=0x57b799a0, args=args@entry=0x7fffd5a0, 
n_params=, param_types=0x565fdda0)
at ././gobject/gclosure.c:867
#12 0x76335391 in g_signal_emit_valist (instance=0x57b799a0, 
signal_id=, detail=0, var_args=var_args@entry=0x7fffd5a0) at 
././gobject/gsignal.c:3300
#13 0x76335faf in g_signal_emit (instance=, 
signal_id=, detail=)
at ././gobject/gsignal.c:3447
#14 0x7fffe4a80d0c in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x7fffe4933584 in gtk_main_do_event () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x7fffe97deb95 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#17 0x7fffe980fb52 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#18 0x760417d7 in g_main_context_dispatch (context=0x56557300) at 
././glib/gmain.c:3203
#19 0x760417d7 in g_main_context_dispatch 
(context=context@entry=0x56557300) at ././glib/gmain.c:3856
#20 0x76041a40 in g_main_context_iterate 
(context=context@entry=0x56557300, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929
#21 0x76041aec in g_main_context_iteration 
(context=context@entry=0x56557300, may_block=may_block@entry=1)
at ././glib/gmain.c:3990
#22 0x758f470d in g_application_run (application=0x56563290 
[GtkApplication], argc=0, argv=0x0) at ././gio/gapplication.c:2381
#23 0x75df4038 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#24 0x75df3a9a in ffi_call (cif=, fn=, 
rvalue=, avalue=0x56903288)
at ../src/x86/ffi64.c:525
#25 0x769bf79c in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
#26 0x769c1268 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
---Type  to continue, or q  to quit---
#27 0x769b5239 in  () at 
/usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so
#28 0x5563bb13 in PyObject_Call ()
#29 0x55654cbf in PyEval_EvalFrameEx ()
#30 0x55654aaf in PyEval_EvalFrameEx ()
#31 0x55654aaf in PyEval_EvalFrameEx ()
#32 0x5564d3c5 in PyEval_EvalCodeEx ()
#33 0x5564d169 in PyEval_EvalCode ()
#34 0x5567cfef in  ()
#35 0x55677fd2 in PyRun_FileExFlags ()
#36 0x55677b1e in PyRun_SimpleFileExFlags ()
#37 0x55628ec1 in Py_Main ()
#38 0x76f1a2b1 in __libc_start_main (main=
0x556287f0 , argc=3, argv=0x7fffe328, init=, 
fini=, rtld_fini=, stack_end=0x7fffe318) at 
../csu/libc-start.c:291
#39 0x556286ea in _start ()
(gdb) 

-- System Information:
Debian Release: 

Bug#809787: gnome-shell: 100% CPU when pasting - Error transferring wayland clipboard to X11

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.18.3-2
Followup-For: Bug #809787

I forwarded this bug upstream as
https://bugzilla.gnome.org/show_bug.cgi?id=760745

> The only fix is to login remotely and kill that process.

Putting text in the wayland clipboard also workaround this bug.

Bug#808377: gnome-shell: Extensions don't load under wayland

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.18.3-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Activate a few extensions using gnome-tweak-tool. All these extensions
work fine.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Reboot the computer and restart gnome wayland session.

   * What was the outcome of this action?

No extensions are activated.

   * What outcome did you expect instead?

The extensions that were activated before reboot should be activated
again, which is the behaviour of the shell under X.

Thanks for maintaining GNOME in debian!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  evolution-data-server3.18.3-1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.18.3-2
ii  gir1.2-caribou-1.0   0.4.19-1
ii  gir1.2-clutter-1.0   1.24.2-1
ii  gir1.2-freedesktop   1.46.0-3
ii  gir1.2-gcr-3 3.18.0-1
ii  gir1.2-gdesktopenums-3.0 3.18.1-1
ii  gir1.2-gdm-1.0   3.18.2-1
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.46.0-3
ii  gir1.2-gnomebluetooth-1.03.18.1-1
ii  gir1.2-gnomedesktop-3.0  3.18.2-1
ii  gir1.2-gtk-3.0   3.18.6-1
ii  gir1.2-gweather-3.0  3.18.1-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.18.2-1
ii  gir1.2-networkmanager-1.01.0.8-2
ii  gir1.2-nmgtk-1.0 1.0.8-1
ii  gir1.2-pango-1.0 1.38.1-1
ii  gir1.2-polkit-1.00.105-14
ii  gir1.2-soup-2.4  2.52.2-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.3-1+b2
ii  gjs  1.44.0-1
ii  gnome-backgrounds3.18.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gnome-settings-daemon3.18.2-1
ii  gnome-shell-common   3.18.3-2
ii  gsettings-desktop-schemas3.18.1-1
ii  libatk-bridge2.0-0   2.18.1-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-4
ii  libcairo21.14.4-1
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libclutter-1.0-0 1.24.2-1
ii  libcogl-pango20  1.22.0-1
ii  libcogl201.22.0-1
ii  libcroco30.6.10-1
ii  libdbus-glib-1-2 0.102-1
ii  libecal-1.2-19   3.18.3-1
ii  libedataserver-1.2-213.18.3-1
ii  libgcr-base-3-1  3.18.0-1
ii  libgdk-pixbuf2.0-0   2.32.3-1
ii  libgirepository-1.0-11.46.0-3
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.44.0-1
ii  libglib2.0-0 2.46.2-1
ii  libgstreamer1.0-01.6.2-1
ii  libgtk-3-0   3.18.6-1
ii  libical1a1.0.1-0.1
ii  libjson-glib-1.0-0   1.0.4-2
ii  libmozjs-24-024.2.0-3
ii  libmutter0g  3.18.2-1
ii  libnm-glib4  1.0.8-2
ii  libnm-util2  1.0.8-2
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpolkit-agent-1-0  0.105-14
ii  libpolkit-gobject-1-00.105-14
ii  libpulse-mainloop-glib0  7.1-2
ii  libpulse07.1-2
ii  libsecret-1-00.18.3-1
ii  libstartup-notification0 0.12-4
ii  libsystemd0  228-2
ii  libtelepathy-glib0   0.24.1-1.1
ii  libx11-6 2:1.6.3-1
ii  libxfixes3 

Bug#807880: apparmor-profiles-extra: AppArmor profile prevents evince from starting under wayland

[Kjö Hansi Glaz]

Package: apparmor-profiles-extra
Version: 1.6
Severity: normal

Dear Maintainer,

   * What led up to the situation?

1) Install and enable evince Apparmor profile shipped in
   apparmor-profile-extra
2) Use GNOME wayland

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Launch evince.

   * What was the outcome of this action?

The following line in system journal:

kernel: audit: type=1400 audit(1450058045.992:347): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince" 
name="/run/user/1000/weston-shared-BEqtJs" pid=32238 comm="evince" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

   * What outcome did you expect instead?

evince to show up!

The following patch solves the issue for me:

diff --git a/apparmor.d/usr.bin.evince b/apparmor.d/usr.bin.evince
index d77fb3b..8e93137 100644
--- a/apparmor.d/usr.bin.evince
+++ b/apparmor.d/usr.bin.evince
@@ -109,6 +109,8 @@
   # evince creates a temporary stream file like '.goutputstream-XX' in the
   # directory a file is saved. This allows that behavior.
   owner /**/.goutputstream-* w,
+
+  owner /{,var/}run/user/*/weston-shared-* rw,
 }
 
 /usr/bin/evince-previewer {

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apparmor-profiles-extra depends on:
ii  apparmor  2.10-2+b1

apparmor-profiles-extra recommends no packages.

apparmor-profiles-extra suggests no packages.

-- Configuration Files:
/etc/apparmor.d/usr.bin.evince changed:
/usr/bin/evince {
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  # Terminals for using console applications. These abstractions should ideally
  # have 'ix' to restrict access to what only evince is allowed to do
  #include 
  # By default, we won't support launching a terminal program in Xterm or
  # KDE's konsole. It opens up too many unnecessary files for most users.
  # People who need this functionality can uncomment the following:
  ##include 
  ##include 
  /usr/bin/evince rmPx,
  /usr/bin/evince-previewer Px,
  /usr/bin/yelp Cx -> sanitized_helper,
  /usr/bin/bug-buddy px,
  # 'Show Containing Folder' (LP: #1022962)
  /usr/bin/nautilus Cx -> sanitized_helper, # Gnome
  /usr/bin/pcmanfm Cx -> sanitized_helper,  # LXDE
  /usr/bin/krusader Cx -> sanitized_helper, # KDE
  /usr/bin/thunar Cx -> sanitized_helper,   # XFCE
  # For Xubuntu to launch the browser
  /usr/bin/exo-open ixr,
  /usr/lib/@{multiarch}/xfce4/exo-1/exo-helper-1 ixr,
  /etc/xdg/xdg-xubuntu/xfce4/helpers.rc r,
  /etc/xdg/xfce4/helpers.rc r,
  # For text attachments
  /usr/bin/gedit ixr,
  # For Send to
  /usr/bin/nautilus-sendto Cx -> sanitized_helper,
  # allow directory listings (ie 'r' on directories) so browsing via the file
  # dialog works
  / r,
  /**/ r,
  # This is need for saving files in your home directory without an extension.
  # Changing this to '@{HOME}/** r' makes it require an extension and more
  # secure (but with 'rw', we still have abstractions/private-files-strict in
  # effect).
  owner @{HOME}/** rw,
  owner /media/**  rw,
  owner @{HOME}/.local/share/gvfs-metadata/** l,
  owner /{,var/}run/user/*/gvfs-metadata/** l,
  owner @{HOME}/.gnome2/evince/*   rwl,
  owner @{HOME}/.gnome2/accels/rw,
  owner @{HOME}/.gnome2/accelsevince   rw,
  owner @{HOME}/.gnome2/accels/evince  rw,
  # Maybe add to an abstraction?
  /etc/dconf/**   r,
  owner @{HOME}/.cache/dconf/user rw,
  owner @{HOME}/.config/dconf/userr,
  owner /{,var/}run/user/*/dconf/ w,
  owner /{,var/}run/user/*/dconf/user rw,
  owner /{,var/}run/user/*/dconf-service/keyfile/ w,
  owner /{,var/}run/user/*/dconf-service/keyfile/user rw,
  owner /{,var/}run/user/*/at-spi2-*/   rw,
  owner /{,var/}run/user/*/at-spi2-*/** rw,
  # from http://live.gnome.org/Evince/SupportedDocumentFormats. Allow
  # read and write for all supported file formats
  /**.[bB][mM][pP] rw,
  /**.[dD][jJ][vV][uU] rw,
  /**.[dD][vV][iI] rw,
  /**.[gG][iI][fF] rw,
  /**.[jJ][pP][gG] rw,
  /**.[jJ][pP][eE][gG] rw,
  /**.[oO][dD][pP] rw,
  /**.[fFpP][dD][fF]   rw,
  /**.[pP][nN][mM] rw,
  /**.[pP][nN][gG] rw,
  /**.[pP][sS] rw,
  /**.[eE][pP][sS] rw,
  /**.[tT][iI][fF] rw,
  /**.[tT][iI][fF][fF] rw,
  /**.[xX][pP][mM] rw,
  /**.[gG][zZ] rw,
  /**.[bB][zZ]2rw,
  /**.[cC][bB][rRzZ7]  rw,
  /**.[xX][zZ] rw,
  # evince creates a temporary stream file like '.goutputstream-XX' in the
  # directory a file is saved. This allows that behavior.
  owner 

Bug#802791: apparmor-profiles-extra: AppArmor profile prevents pidgin from starting

[Kjö Hansi Glaz]

Package: apparmor-profiles-extra
Version: 1.5
Followup-For: Bug #802791

The following snippet is enough to make pidgin start on my sid system:

$ cat /etc/apparmor.d/local/usr.bin.pidgin
# Site-specific additions and overrides for usr.bin.pidgin.
# For more details, please see /etc/apparmor.d/local/README.

owner @{HOME}/.cache/gstreamer-1.0/registry.x86_64.bin r,
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner r,

Thanks for maintaining apparmor profiles in Debian!

Cheers

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apparmor-profiles-extra depends on:
ii  apparmor  2.10-2+b1

apparmor-profiles-extra recommends no packages.

apparmor-profiles-extra suggests no packages.

-- no debconf information

Bug#803171: torbrowser-launcher: AppArmor profiles broken with latest Tor Browser

[Kjö Hansi Glaz]

Hi,

intrigeri:
> does the package work for you if you *don't* manually set to enforce
> mode the profiles we intentionally have set to complain mode in
> the packaging?
> 
Yes, it works then.

However, I find it surprising that there is an apparmor profile shipped
in the package and that its failures are expected. Perhaps they should
be dropped, or written in README.debian or another more appropriate
location.

Cheers

Bug#803171: torbrowser-launcher: AppArmor profiles broken with latest Tor Browser

[Kjö Hansi Glaz]

Package: torbrowser-launcher
Version: 0.2.0-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I installed torbrowser-launcher, on an uptodate sid installation with
apparmor enabled.

I switched the included profiles to enforce mode with:

$ sudo aa-enforce usr.bin.torbrowser-launcher
Setting /etc/apparmor.d/usr.bin.torbrowser-launcher to enforce mode.
$ sudo aa-enforce torbrowser.start-tor-browser
Setting /etc/apparmor.d/torbrowser.start-tor-browser to enforce mode.
$ sudo aa-enforce torbrowser.Browser.firefox
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried to start torbrowser-launcher.

   * What was the outcome of this action?

$ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Checked for update within 24 hours, skipping
Latest version of TBB is installed, launching
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in 
torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 
69, in main
app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
117, in __init__
self.start_launcher()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
151, in start_launcher
self.run(False)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
634, in run
subprocess.call([self.common.paths['tbb']['start']], 
cwd=self.common.paths['tbb']['dir_tbb'])
  File "/usr/lib/python2.7/subprocess.py", line 522, in call
return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 13] Permission non accordée

   * What outcome did you expect instead?

I expect Tor Browser to start

   * Proposed solution

Adding the following in apparmor.d/local/ solved the problem for me.
These might need to be added to the profile shipped in the Debian
package.

$ cat apparmor.d/local/torbrowser.start-tor-browser
# Site-specific additions and overrides for torbrowser.start-tor-browser.
# For more details, please see /etc/apparmor.d/local/README.
/sbin/ldconfig ix,
/usr/bin/gcc-5 ix,
/usr/bin/env r,
/bin/bash ix,

$ cat apparmor.d/local/usr.bin.torbrowser-launcher
# Site-specific additions and overrides for usr.bin.torbrowser-launcher.
# For more details, please see /etc/apparmor.d/local/README.

/sbin/ldconfig rix,
/sbin/ldconfig.real rix,
/usr/bin/gcc-5 rix,
/bin/sed rix,
/usr/bin/tail ix,

@{HOME}/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/{Browser/,}start-tor-browser.desktop
 rix,
@{HOME}/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser/execdesktop
 ix,

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.19-6
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil2.2.1-3+b1
ii  python-twisted   15.2.1-1
ii  python-txsocksx  1.15.0.2-1
ii  tor  0.2.7.4-rc-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.10-2+b1
pn  python-pygame  

-- Configuration Files:
/etc/apparmor.d/torbrowser.start-tor-browser changed:
$ diff -Naur deb/etc/apparmor.d/torbrowser.start-tor-browser 
/etc/apparmor.d/torbrowser.start-tor-browser
--- deb/etc/apparmor.d/torbrowser.start-tor-browser 2015-08-12 
12:35:34.0 +0200
+++ /etc/apparmor.d/torbrowser.start-tor-browser2015-10-26 
14:58:35.692329726 +0100
@@ -1,6 +1,6 @@
 #include 

-/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/{Browser/,}start-tor-browser
 flags=(complain) {
+/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/{Browser/,}start-tor-browser
 {
   #include 
   #include 
   #include 

/etc/apparmor.d/usr.bin.torbrowser-launcher changed:
$ diff -Naur deb/etc/apparmor.d/usr.bin.torbrowser-launcher 
/etc/apparmor.d/usr.bin.torbrowser-launcher
--- etc/apparmor.d/usr.bin.torbrowser-launcher  2015-08-12 12:35:33.0 
+0200
+++ /etc/apparmor.d/usr.bin.torbrowser-launcher 2015-10-26 15:54:02.001050005 
+0100
@@ -1,7 +1,7 @@
 # Last Modified: Thu Jan  2 15:12:38 2014
 #include 

-/usr/bin/torbrowser-launcher flags=(complain) {
+/usr/bin/torbrowser-launcher {
   #include 
   #include 
   

Bug#797474: gnupg2: Pinentry fails with passpharse too long

[Kjö Hansi Glaz]

Package: gnupg2
Version: 2.1.7-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

I upgraded my system, which installed gnupg2 from 2.0.28-3 to 2.1.7-2

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Try to decrypt a message with gnupg2, e.g. with 'gpg2 --decrypt'

   * What was the outcome of this action?

Pinentry answers me Passphrase too long, and decryption fails.

   * What outcome did you expect instead?

The message to be decrypted

Please note that the very same things works with the 'gpg' command.

I think that this is upstream issue 2038
(https://bugs.gnupg.org/gnupg/issue2038)

Thanks for working on gnupg in debian!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages gnupg2 depends on:
ii  dpkg   1.18.2
ii  gnupg-agent2.1.7-2
ii  install-info   6.0.0.dfsg.1-3
ii  libassuan0 2.2.1-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.19-19
ii  libgcrypt201.6.3-2
ii  libgpg-error0  1.19-2
ii  libksba8   1.3.3-1
ii  libreadline6   6.3-8+b3
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg2 recommends:
ii  dirmngr  2.1.7-2

Versions of packages gnupg2 suggests:
pn  gnupg-doc   none
ii  parcimonie  0.9-2
pn  xloadimage  none

-- no debconf information

Bug#794882: glade: Please consider packaging 3.19.0

[Kjö Hansi Glaz]

Package: glade
Version: 3.18.3-1
Severity: wishlist

Dear Maintainer,

Glade team recently released Glade 3.19.0 [1]. Would you consider
packaging it, e.g. in experimental?

While this is a development release, it adds support for
GtkSidebarWidget, GtkStack and GtkStackSwitcher, GtkHeaderBar,
GtkSearchBar, GThemedIcon and GtkLockButton, which are all very useful
if not necessary to develop applications following the last version of
GNOME Human Interface Guidelines [2].

Thanks for maintaining glade in debian!

[1]: http://lists.ximian.com/pipermail/glade-devel/2015-June/002090.html
[2]: https://developer.gnome.org/hig/3.16/

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages glade depends on:
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-19
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libgladeui-2-6   3.18.3-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0   3.16.6-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libxml2  2.9.2+dfsg1-3

Versions of packages glade recommends:
ii  devhelp   3.16.1-1
pn  libgtk-3-dev  none

glade suggests no packages.

-- no debconf information


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

Bug#775736: network-manager: NetworkManager fills journal with send_rs() cannot send router solicitation: -1

[Kjö Hansi Glaz]

Package: network-manager
Version: 0.9.10.0-5
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I use NetworkManager in an environment where the firewall drops IPv6.

   * What was the outcome of this action?

NetworkManager sends to the system journal the following line every 5
seconds:

NetworkManager[PID]: error [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): 
cannot send router solicitation: -1.

   * What outcome did you expect instead?

I expect this error message to show once if it may be useful, but not to
show up every 5 seconds.

   * Other reports

This problem looks very similar to the following Fedora bug reports:

- https://bugzilla.redhat.com/show_bug.cgi?id=1034443
- https://bugzilla.redhat.com/show_bug.cgi?id=1010540

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.14-1
ii  init-system-helpers1.22
ii  isc-dhcp-client4.3.1-5
ii  libc6  2.19-13
ii  libdbus-1-31.8.14-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt201.6.2-4+b1
ii  libglib2.0-0   2.42.1-1
ii  libgnutls-deb0-28  3.3.8-5
ii  libgudev-1.0-0 215-9
ii  libmm-glib01.4.0-1
ii  libndp01.4-2
ii  libnewt0.520.52.17-1+b1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-5
ii  libnm-util20.9.10.0-5
ii  libpam-systemd 215-9
ii  libpolkit-gobject-1-0  0.105-8
ii  libreadline6   6.3-8+b3
ii  libsoup2.4-1   2.48.0-1
ii  libsystemd0215-9
ii  libteamdctl0   1.12-1
ii  libuuid1   2.25.2-4.1
ii  lsb-base   4.1+Debian13+nmu1
ii  policykit-10.105-8
ii  udev   215-9
ii  wpasupplicant  2.3-1

Versions of packages network-manager recommends:
ii  crda3.13-1
ii  dnsmasq-base2.72-2
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.4.0-1
pn  ppp none

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4+b2
pn  libteam-utils  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#763698: Fwd: Upstream patch available

[Kjö Hansi Glaz]

forwarded 763698 https://bugzilla.redhat.com/show_bug.cgi?id=1183727
tag 763698 patch
thanks

I added a patch in upstream bugtracker at
https://bugzilla.redhat.com/show_bug.cgi?id=1183727. It could easily be
backorted in debian.


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

Bug#758085: bookletimposer: Needs to migrate away from deprecated static Python bindings for the GObject library

[Kjö Hansi Glaz]

Hi,

 bookletimposer still depends on the static Python bindings for the
 GObject library, which are deprecated and will go away some day.
 It should migrate to the new gobject-introspection system.

Please tell which file still depends on the static python bindings.

Thanks by advance,

Kjö


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

Bug#765308: Acknowledgement (nautilus: Nautilus fails to open LUKS-encrypted USB stick)

[Kjö Hansi Glaz]

I managed to reproduce this bug under Fedora 21 alpha1 live, so it's
not debian-specific.

Cheers


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

Bug#764609: Acknowledgement (gnome-shell often crashes when opening activity wiew with a full-screen VM opened virt-manager)

[Kjö Hansi Glaz]

Please find attached the corresponding backtrace. I installed
gnome-shell-dbg. Please tell me if you need other symbols.

---

Program received signal SIGSEGV, Segmentation fault.
0x7f2999545892 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(gdb) t a a bt

Thread 13 (Thread 0x7f296fdc9700 (LWP 24683)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f29ad4c25e7 in g_cond_wait_until () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f29ad452a69 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f29ad45308b in g_async_queue_timeout_pop () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f29ad4a537c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f29ad4a4925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f29ad21f0a4 in start_thread (arg=0x7f296fdc9700) at 
pthread_create.c:309
#7  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7f299b090700 (LWP 24556)):
#0  0x7f29acf4c0ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f29ad47dee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f29ad47dffc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f29ad47e039 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f29ad4a4925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f29ad21f0a4 in start_thread (arg=0x7f299b090700) at 
pthread_create.c:309
#6  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f2993fff700 (LWP 24560)):
#0  0x7f29acf4c0ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f29ad47dee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f29ad47e272 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f29adc7df06 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f29ad4a4925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f29ad21f0a4 in start_thread (arg=0x7f2993fff700) at 
pthread_create.c:309
#6  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f2992ffd700 (LWP 24565)):
#0  0x7f29acf4c0ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f29ad47dee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f29ad47dffc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f299835827d in ?? () from 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x7f29ad4a4925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f29ad21f0a4 in start_thread (arg=0x7f2992ffd700) at 
pthread_create.c:309
#6  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f29927fc700 (LWP 24566)):
#0  0x7f29acf4c0ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f29a90becc1 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f29a90b02a1 in pa_mainloop_poll () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f29a90b093e in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f29a90b09f0 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f29a90bec56 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f299f4ffa98 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so
#7  0x7f29ad21f0a4 in start_thread (arg=0x7f29927fc700) at 
pthread_create.c:309
#8  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f2991ffb700 (LWP 24567)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f299ea7b2fd in PR_WaitCondVar () from 
/usr/lib/x86_64-linux-gnu/libnspr4.so
#2  0x7f29a8abfb34 in ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
#3  0x7f299ea80848 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so
#4  0x7f29ad21f0a4 in start_thread (arg=0x7f2991ffb700) at 
pthread_create.c:309
#5  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f29917fa700 (LWP 24568)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f299ea7b2fd in PR_WaitCondVar () from 
/usr/lib/x86_64-linux-gnu/libnspr4.so
#2  0x7f29a8b32f2e in ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
#3  0x7f299ea80848 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so
#4  0x7f29ad21f0a4 in start_thread (arg=0x7f29917fa700) at 
pthread_create.c:309
#5  0x7f29acf54c2d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f29b04b8a40 (LWP 24552)):
#0  0x7f2999545892 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#1  0x7f2999545903 in ?? () from 

Bug#765308: nautilus: Nautilus fails to open LUKS-encrypted USB stick

[Kjö Hansi Glaz]

Package: nautilus
Version: 3.14.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Plug a LUKS-encrypted USB stick created by Disks (gnome-disk-utility)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Click on the entry corresponding to the USB stick in nautilus's left
panel.

   * What was the outcome of this action?

None.

   * What outcome did you expect instead?

I'd expect to be prompred for my passphrase and then to be show the
content of my USB stick.

Note that I can unlock and mount the USB stick from Disks

Thanks for maintaining Nautilus in Debian!

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.14.0-1
ii  gvfs   1.22.0-1+b1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-11
ii  libcairo-gobject2  1.12.16-5
ii  libcairo2  1.12.16-5
ii  libexempi3 2.2.1-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.14.2-1
ii  libgdk-pixbuf2.0-0 2.31.1-2
ii  libglib2.0-0   2.42.0-2
ii  libglib2.0-data2.42.0-2
ii  libgnome-desktop-3-10  3.14.0-1
ii  libgtk-3-0 3.14.2-1
ii  libnautilus-extension1a3.14.0-1
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libselinux12.3-2
ii  libtracker-sparql-1.0-01.2.2-1
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-4
ii  nautilus-data  3.14.0-1
ii  shared-mime-info   1.3-1

Versions of packages nautilus recommends:
ii  eject  2.1.5+deb1+cvs20081104-13.1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.12.0-2
ii  gvfs-backends  1.22.0-1+b1
ii  librsvg2-common2.40.4-1

Versions of packages nautilus suggests:
ii  brasero  3.11.4-1
ii  eog  3.14.0-1
ii  evince [pdf-viewer]  3.14.0-2
ii  totem3.14.0-2
ii  tracker  1.2.2-1
ii  xdg-user-dirs0.15-2

-- 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#764609: gnome-shell often crashes when opening activity wiew with a full-screen VM opened virt-manager

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.14.0-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Open a full-screen virtual machine (VM) in virt-manager.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Open the activity view (by pressing super) while using the full-screen VM.

   * What was the outcome of this action?

Gnome-shell often crashes and restart (several times a day) with the
following log output:

   gnome-session[2215]: Failed to open BO for returned DRI2 buffer (1280x800, 
dri2 back buffer, named 6).
   gnome-session[2215]: This is likely a bug in the X Server that will lead to 
a crash soon.
   kernel: gnome-shell[10990]: segfault at 3c ip 7f10f7a2d05b sp 
7fff23469cf0 error 4 in i965_dri.so[7f10f76c2000+50c000]
   x-session-manager[2215]: WARNING: Application 'gnome-shell.desktop' killed 
by signal 11
   gnome-session[2215]: x-session-manager[2215]: WARNING: Application 
'gnome-shell.desktop' killed by signal 11

   * What outcome did you expect instead?

No crash.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  evolution-data-server3.12.6-1.1
ii  gir1.2-accountsservice-1.0   0.6.37-3+b1
ii  gir1.2-atspi-2.0 2.12.0-2
ii  gir1.2-caribou-1.0   0.4.15-1
ii  gir1.2-clutter-1.0   1.20.0-1
ii  gir1.2-freedesktop   1.42.0-2
ii  gir1.2-gcr-3 3.14.0-2
ii  gir1.2-gdesktopenums-3.0 3.14.0-1
ii  gir1.2-gdm3  3.14.0-1
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.42.0-2
ii  gir1.2-gnomebluetooth-1.03.14.0-1
ii  gir1.2-gnomedesktop-3.0  3.14.0-1
ii  gir1.2-gtk-3.0   3.14.1-1
ii  gir1.2-ibus-1.0  1.5.8-2
ii  gir1.2-mutter-3.03.14.0-1
ii  gir1.2-networkmanager-1.00.9.10.0-3
ii  gir1.2-nmgtk-1.0 0.9.10.0-2
ii  gir1.2-pango-1.0 1.36.8-2
ii  gir1.2-polkit-1.00.105-7
ii  gir1.2-soup-2.4  2.48.0-1
ii  gir1.2-telepathyglib-0.120.24.1-1
ii  gir1.2-telepathylogger-0.2   0.8.1-1
ii  gir1.2-upowerglib-1.00.99.1-3
ii  gjs  1.42.0-1
ii  gnome-backgrounds3.14.0-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gnome-settings-daemon3.14.0-2
ii  gnome-shell-common   3.14.0-1
ii  gnome-themes-standard3.14.0-1
ii  gsettings-desktop-schemas3.14.0-1
ii  libatk-bridge2.0-0   2.12.1-1+b1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libcanberra-gtk3-0   0.30-2.1
ii  libcanberra0 0.30-2.1
ii  libclutter-1.0-0 1.20.0-1
ii  libcogl-pango20  1.18.2-2
ii  libcogl201.18.2-2
ii  libcroco30.6.8-3
ii  libdbus-glib-1-2 0.102-1
ii  libecal-1.2-16   3.12.6-1.1
ii  libedataserver-1.2-183.12.6-1.1
ii  libgcr-base-3-1  3.14.0-2
ii  libgdk-pixbuf2.0-0   2.31.1-2
ii  libgirepository-1.0-11.42.0-2
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1
ii  libglib2.0-0 2.42.0-2
ii  libgstreamer1.0-01.4.3-1
ii  libgtk-3-0   3.14.1-1
ii  libical1 1.0-1
ii  libjson-glib-1.0-0   1.0.2-1
ii  libmozjs-24-024.2.0-2
ii  libmutter0e  3.14.0-1
ii  libnm-glib4  0.9.10.0-3
ii  libnm-util2  0.9.10.0-3
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpolkit-agent-1-0  0.105-7
ii  libpolkit-gobject-1-00.105-7
ii  

Bug#764492: caribou: on screen keyboard do not use configured keyboard layout

[Kjö Hansi Glaz]

Package: caribou
Version: 0.4.15-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

In System Settings - Language and region my preferred input source is
Français (variante).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Open System Settings - Accessibility and enable Visual keyboard

   * What was the outcome of this action?

The virtual keybpard displayed is querty (rendering it difficult to find
the right key) and doesn't have the french accents easily accessible
(rendering it difficult to write french).

   * What outcome did you expect instead?

I expect that the layout of the virtual keyboard would be the one I
selected for my session.

Thanks for maintaining Caribou

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages caribou depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-caribou-1.0   0.4.15-1
ii  gir1.2-clutter-1.0   1.20.0-1
ii  gir1.2-glib-2.0  1.42.0-2
ii  gir1.2-gtk-3.0   3.14.1-1
ii  libatk1.0-0  2.14.0-1
ii  libatspi2.0-02.12.0-2
ii  libc62.19-11
ii  libcairo-gobject21.12.16-5
ii  libcairo21.12.16-5
ii  libclutter-1.0-0 1.20.0-1
ii  libcogl-pango20  1.18.2-2
ii  libcogl-path20   1.18.2-2
ii  libcogl201.18.2-2
ii  libdbus-1-3  1.8.8-2
ii  libdrm2  2.4.58-2
ii  libegl1-mesa [libegl1-x11]   10.2.8-1
ii  libgbm1  10.2.8-1
ii  libgdk-pixbuf2.0-0   2.30.8-1+b1
ii  libglib2.0-0 2.42.0-2
ii  libgtk-3-0   3.14.1-1
ii  libjson-glib-1.0-0   1.0.2-1
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libwayland-client0   1.6.0-2
ii  libwayland-cursor0   1.6.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]   10.2.8-1
ii  libwayland-server0   1.6.0-2
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2
ii  libxi6   2:1.7.4-1
ii  libxkbcommon00.4.3-2
ii  libxrandr2   2:1.4.2-1
ii  python   2.7.8-1
ii  python-dbus  1.2.0-2+b3
ii  python-gi3.14.0-1
ii  python-pyatspi   2.12.0+dfsg-3

caribou recommends no packages.

caribou suggests no packages.

-- no debconf information


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

Bug#763698: virt-manager: the toolbar in the virtual machine window is too big

[Kjö Hansi Glaz]

Package: virt-manager
Version: 1:1.0.1-2
Severity: minor

Dear Maintainer,

   * What led up to the situation?

An upgrade to 1:1.0.1-2

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Open the virtual machine window by double-clicking in a virtual
machine name.

   * What was the outcome of this action?

The toolbar is higher that before and only the snapshot icon fills its
whole height.

   * What outcome did you expect instead?

The same tooblar height than before.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gconf2   3.2.6-3
ii  gir1.2-gtk-3.0   3.14.0-1
ii  gir1.2-gtk-vnc-2.0   0.5.3-1.2
ii  gir1.2-libvirt-glib-1.0  0.1.7-2.1
ii  gir1.2-spice-client-gtk-3.0  0.25-1
ii  gir1.2-vte-2.90  1:0.36.3-1
ii  librsvg2-common  2.40.4-1
ii  python-dbus  1.2.0-2+b3
ii  python-gi3.14.0-1
ii  python-gi-cairo  3.14.0-1
ii  python-ipaddr2.1.11-2
ii  python-libvirt   1.2.8-1
ii  python-urlgrabber3.9.1-4
pn  python2.7:anynone
pn  python:any   none
ii  virtinst 1:1.0.1-2

Versions of packages virt-manager recommends:
ii  gnome-icon-theme 3.12.0-1
ii  libvirt-daemon   1.2.8-3
ii  python-spice-client-gtk  0.25-1

Versions of packages virt-manager suggests:
ii  gnome-keyring3.14.0-1
ii  python-gnomekeyring  2.32.0+dfsg-3
pn  python-guestfs   none
pn  ssh-askpass  none
ii  virt-viewer  0.6.0-1

-- 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#733113: gnome-shell-extensions: Alternative status menu fails to display an Hibernate entry

[Kjö Hansi Glaz]

Hi,

On Thu, Jul 24, 2014 at 12:44:52PM +0200, intrigeri wrote:
 since #733112 is now gone, I suspect this bug can't be
 reproduced anymore. Correct?

There is no Alternative status menu anymore in jessie nor in sid, so I
can't test anymore. But the bug became irrelevant then.

Cheers


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

Bug#753919: gnome-control-center: unlock button does nothing

[Kjö Hansi Glaz]

Package: gnome-control-center
Version: 1:3.8.3-7+b2
Severity: important

Dear Maintainer,

   * What led up to the situation?

Open gnome-control-center.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Click the icon of a panel that requires privileges, e.g. Date  Time or
Users. Most of the panel is grayed out, which is expected.

Click on the Unlock button.

   * What was the outcome of this action?

Nothing happens but the following line is printed on std{out|err}:

   (gnome-control-center:4316): Gtk-WARNING **: Error acquiring permission: 
Failed to acquire permission for action-id 
org.gnome.controlcenter.datetime.configure

   * What outcome did you expect instead?

Being asked for my credentials and able to use the panel after entering
them.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.37-1
ii  apg2.2.3.dfsg.1-2
ii  colord 1.2.1-1
ii  desktop-file-utils 0.22-1
ii  gnome-control-center-data  1:3.8.3-7
ii  gnome-desktop3-data3.8.4-2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-menus3.8.0-2
ii  gnome-settings-daemon  3.8.5-2+b2
ii  gsettings-desktop-schemas  3.8.2-2
ii  libaccountsservice00.6.37-1
ii  libatk1.0-02.12.0-1
ii  libc6  2.19-4
ii  libcairo2  1.12.16-2
ii  libcanberra-gtk3-0 0.30-2
ii  libcanberra0   0.30-2
ii  libcheese-gtk233.12.0-1
ii  libcheese7 3.12.0-1
ii  libclutter-gtk-1.0-0   1.5.2-2
ii  libcolord-gtk1 0.1.25-1.1+b1
ii  libcolord2 1.2.1-1
ii  libcups2   1.7.3-6
ii  libdbus-glib-1-2   0.102-1
ii  libfontconfig1 2.11.0-5
ii  libgdk-pixbuf2.0-0 2.30.7-1
ii  libgl1-mesa-glx [libgl1]   10.2.1-2
ii  libglib2.0-0   2.40.0-3
ii  libgnome-bluetooth11   3.8.1-3
ii  libgnome-desktop-3-7   3.8.4-2
ii  libgoa-1.0-0b  3.12.2-1
ii  libgoa-backend-1.0-1   3.12.2-1
ii  libgtk-3-0 3.12.2-1+b1
ii  libgtop2-7 2.28.5-2
ii  libibus-1.0-5  1.5.7-1
ii  libkrb5-3  1.12.1+dfsg-3
ii  libmm-glib01.0.0-5+b1
ii  libnm-glib-vpn10.9.8.10-4
ii  libnm-glib40.9.8.10-4
ii  libnm-gtk0 0.9.8.10-1
ii  libnm-util20.9.8.10-4
ii  libpango-1.0-0 1.36.3-1
ii  libpangocairo-1.0-01.36.3-1
ii  libpolkit-gobject-1-0  0.105-6
ii  libpulse-mainloop-glib05.0-2
ii  libpulse0  5.0-2
ii  libpwquality1  1.2.3-1
ii  libsmbclient   2:4.1.9+dfsg-1
ii  libsocialweb-client2   0.25.20-6
ii  libupower-glib10.9.23-2+b2
ii  libwacom2  0.8-1
ii  libx11-6   2:1.6.2-2
ii  libxi6 2:1.7.2-1
ii  libxml22.9.1+dfsg1-3

Versions of packages gnome-control-center recommends:
ii  cups-pk-helper 0.2.5-2
ii  gkbd-capplet   3.6.0-1
ii  gnome-online-accounts  3.12.2-1
ii  gnome-user-guide   3.8.2-1
ii  gnome-user-share   3.8.3-1
ii  iso-codes  3.54-1
ii  mesa-utils 8.1.0-2+b1
ii  mousetweaks3.12.0-1
ii  network-manager-gnome  0.9.8.10-1
ii  ntp1:4.2.6.p5+dfsg-3
ii  policykit-1-gnome  0.105-2
ii  rygel  0.22.2-2
ii  system-config-printer  1.4.3-4

Versions of packages gnome-control-center suggests:
ii  gnome-screensaver3.6.1-1
ii  gstreamer1.0-pulseaudio  1.2.4-1
ii  libcanberra-gtk-module   0.30-2
ii  libcanberra-gtk3-module  0.30-2
ii  x11-xserver-utils7.7+2

-- 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#733112: [Pkg-systemd-maintainers] Bug#733112: libsystemd-login0: logind not found by gdm3

[Kjö Hansi Glaz]

Hi,

I don't have access to the buggy system anymore. On a new jessie install
the problem doesn't show up. This problem might still be an issue for
wheezy to jessie migration.

Cheers


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

Bug#733112: libsystemd-login0: logind not found by gdm3

[Kjö Hansi Glaz]

Hi,

  Can you repeat that with -s 2048 so that we can actually see a bit of
  the message’s content? Also, a trace of what’s happening on dbus would
  be useful. I think you can use dbus-monitor for that.
 
 Do you think you'll be able to provide the additional information
 Michael asked?
 
I sent it to Michael on Jan 13.

Cheers


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

Bug#733112: [Pkg-systemd-maintainers] Bug#733112: libsystemd-login0: logind not found by gdm3

[Kjö Hansi Glaz]

Hi,

On Wed, Dec 25, 2013 at 09:33:30PM +0100, Tollef Fog Heen wrote:
  I use systemd as init. It seems that gdm3 fails to communicate with
  logind as it fallsback to consolekit as a login manager.
  
  As a result, several features of gnome doesn't work as expected.
 
 Do you have libpam-systemd installed?  If not, does installing it fix
 the problem?
 
I do have libpam-systemd

$ dpkg -l libpam-systemd
ii  libpam-systemd:amd64  204-5   amd64   
system and service manager - PAM module


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

Bug#733112: libsystemd-login0: logind not found by gdm3

[Kjö Hansi Glaz]

Package: libsystemd-login0
Version: 204-5
Severity: normal

Dear Maintainer,

I use systemd as init. It seems that gdm3 fails to communicate with
logind as it fallsback to consolekit as a login manager.

As a result, several features of gnome doesn't work as expected.

Please find attached a strace of systemd-logind before restarting gdm3
and logging in.

Hope it helps

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libsystemd-login0 depends on:
ii  libc6  2.17-97
ii  multiarch-support  2.17-97

libsystemd-login0 recommends no packages.

libsystemd-login0 suggests no packages.

-- no debconf information
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
epoll_wait(4, {{EPOLLERR, {u32=3, u64=3}}}, 1, 4294967295) = 1
lseek(5, 0, SEEK_SET)   = 0
read(5, tty2\n, 63)   = 5
open(/dev/tty1, O_RDWR|O_NOCTTY|O_CLOEXEC) = 19
ioctl(19, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(19, VT_GETSTATE, 0x7fffd8a721f0)  = 0
close(19)   = 0
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
epoll_wait(4, {{EPOLLERR, {u32=3, u64=3}}}, 1, 4294967295) = 1
lseek(5, 0, SEEK_SET)   = 0
read(5, tty7\n, 63)   = 5
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
epoll_wait(4, {{EPOLLIN, {u32=4, u64=4}}}, 1, 4294967295) = 1
epoll_wait(10, {{EPOLLIN, {u32=8205840, u64=8205840}}}, 1, 0) = 1
recvmsg(9, {msg_name(0)=NULL, 
msg_iov(1)=[{l\1\0\1x\0\0\0\2\0\0\0\247\0\0\0\1\1o\0\27\0\0\0/org/fre..., 
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 304
recvmsg(9, 0x7fffd8a72130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
open(/proc/32101/cgroup, O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
sendmsg(9, {msg_name(0)=NULL, 
msg_iov(2)=[{l\3\1\1\24\0\0\0\177\0\0\0W\0\0\0\6\1s\0\6\0\0\0:1.180\0\0..., 
104}, {\17\0\0\0No such process\0, 20}], msg_controllen=0, msg_flags=0}, 
MSG_NOSIGNAL) = 124
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
epoll_wait(4, {{EPOLLIN, {u32=4, u64=4}}}, 1, 4294967295) = 1
epoll_wait(10, {{EPOLLIN, {u32=8205840, u64=8205840}}}, 1, 0) = 1
recvmsg(9, {msg_name(0)=NULL, 
msg_iov(1)=[{l\1\0\1#\0\0\0\26\0\0\0\177\0\0\0\10\1g\0\1s\0\0\1\1o\0\27\0\0\0...,
 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 179
recvmsg(9, 0x7fffd8a72130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
sendmsg(9, {msg_name(0)=NULL, 
msg_iov(2)=[{l\2\1\1\360\2\0\0\200\0\0\0#\0\0\0\6\1s\0\6\0\0\0:1.184\0\0..., 
56}, {\350\2\0\0\0\0\0\0\25\0\0\0ControlGroupHierarch..., 752}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 808
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
epoll_wait(4, {{EPOLLIN, {u32=4, u64=4}}}, 1, 4294967295) = 1
epoll_wait(10, {{EPOLLIN, {u32=8205840, u64=8205840}}}, 1, 0) = 1
recvmsg(9, {msg_name(0)=NULL, 
msg_iov(1)=[{l\1\0\1J\0\0\0\27\0\0\0\207\0\0\0\10\1g\0\4\0\0\0\0\0\0\0...,
 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 226
recvmsg(9, 0x7fffd8a72130, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
lstat(/run/systemd/system/, {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
timerfd_create(CLOCK_MONOTONIC, 0x80800 /* TFD_??? */) = 19
timerfd_settime(19, 0, {it_interval={25, 0}, it_value={25, 0}}, NULL) = 0
epoll_ctl(10, EPOLL_CTL_ADD, 19, {EPOLLIN, {u32=8251968, u64=8251968}}) = 0
sendmsg(9, {msg_name(0)=NULL, 
msg_iov(2)=[{l\1\0\1\v\0\0\0\201\0\0\0\207\0\0\0\1\1o\0\25\0\0\0/org/fre..., 
152}, {\6\0\0\0:1.184\0, 11}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) 
= 163
poll([{fd=9, events=POLLIN}], 1, 25000) = 1 ([{fd=9, revents=POLLIN}])
recvmsg(9, {msg_name(0)=NULL, 
msg_iov(1)=[{l\2\1\1\4\0\0\0*\0\0\0=\0\0\0\6\1s\0\4\0\0\0:1.1\0\0\0\0..., 
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 84
epoll_ctl(10, EPOLL_CTL_DEL, 19, NULL)  = 0
close(19)   = 0
recvmsg(9, 0x7fffd8a71a10, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily 
unavailable)
timerfd_create(CLOCK_MONOTONIC, 0x80800 /* TFD_??? */) = 19
timerfd_settime(19, 0, {it_interval={25, 0}, it_value={25, 0}}, NULL) = 0
epoll_ctl(10, EPOLL_CTL_ADD, 19, {EPOLLIN, {u32=8251968, u64=8251968}}) = 0
sendmsg(9, 

Bug#733113: gnome-shell-extensions: Alternative status menu fails to display an Hibernate entry

[Kjö Hansi Glaz]

Package: gnome-shell-extensions
Version: 3.8.4-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Install and enable Alternative Status Menu from gnome-shell-extensions.

Use systemd as init.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Click the topright user menu

   * What was the outcome of this action?

There is no Hibernate entry.

Syslog reads:

dbus[]: [system] Rejected send message, 2 matched rules;
type=method_call, sender=:1.201 (uid=1000 pid= comm=)
interface=org.freedesktop.ConsoleKit.Manager
member=CanHibernate error name=(unset) requested_reply=0
destination=:1.6 (uid=0 pid= comm=)

   * What outcome did you expect instead?

An Hibernate entry

   * Initial debugging

I added hacked a bit in the code of the extension and found that it uses
LoginManagerConsoleKit instead of LoginManagerSystemd (defined in
/usr/share/gnome-shell/js/misc/loginManager.js).

It seems me this is a consequence of a bug in either logind of gdm that
I filed as #733112.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-shell-extensions depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  gir1.2-gtop-2.0  2.28.5-2
ii  gnome-session3.8.4-3
ii  gnome-shell  3.8.4-5
ii  gvfs 1.16.3-1+b2

Versions of packages gnome-shell-extensions recommends:
ii  gnome-tweak-tool  3.8.1-2

gnome-shell-extensions suggests no packages.

-- no debconf information


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

Bug#687500: hangs in console instead of switching to display manager

[Kjö Hansi Glaz]

Package: plymouth
Followup-For: Bug #687500

I can't reproduce this bug either with an uptodate jessie system,
neither with plymouth from experimental.

I was able to reproduce the bug on 12 Jul 2013.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages plymouth depends on:
ii  initramfs-tools0.115
ii  libc6  2.17-97
ii  multiarch-support  2.17-97

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base  7.0.3
ii  plymouth-drm  0.8.8-6+deb8u3

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed [not included]

-- 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#726872: gnome-shell: Fails to lock screen while configured to do so

[Kjö Hansi Glaz]

Package: gnome-shell
Version: 3.8.4-5
Followup-For: Bug #726872

Dear Maintainer,

   * What led up to the situation?

I configured systemd (that I use as my init system) to blank screen when
closing the lid. systemd/logind.conf contains HandleLidSwitch=lock.

Before the upgrade to gnome-shell 3.8 (the shell becoming the
screensaver, as far as I understood), the screen was actually locked
when I closed the laptop's lid.

In gnome-control-center, I configured:

- Privacy - Screen Lock - Automatic Screen Lock: On
- Privacy - Screen Lock - Lock Screen After Blank: Screen Turns Off

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Close my laptop lid, then reopen it.

   * What was the outcome of this action?

The session is not locked.

   * What outcome did you expect instead?

An unlock screen asking for my password


Thanks for maintaining gnome-shell in debian!


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  evolution-data-server3.8.5-3
ii  gdm3 3.8.4-6
ii  gir1.2-accountsservice-1.0   0.6.34-2
ii  gir1.2-caribou-1.0   0.4.12-1
ii  gir1.2-clutter-1.0   1.14.4-3
ii  gir1.2-freedesktop   1.36.0-2+b1
ii  gir1.2-gcr-3 3.8.2-4
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.36.0-2+b1
ii  gir1.2-gmenu-3.0 3.8.0-2
ii  gir1.2-gnomebluetooth-1.03.8.1-2
ii  gir1.2-gnomedesktop-3.0  3.8.4-2
ii  gir1.2-gtk-3.0   3.8.4-1
ii  gir1.2-ibus-1.0  1.5.3-7
ii  gir1.2-mutter-3.03.8.4-2
ii  gir1.2-networkmanager-1.00.9.8.0-5
ii  gir1.2-nmgtk-1.0 0.9.8.4-1
ii  gir1.2-pango-1.0 1.36.0-1
ii  gir1.2-polkit-1.00.105-4
ii  gir1.2-soup-2.4  2.44.1-1
ii  gir1.2-telepathyglib-0.120.22.0-1
ii  gir1.2-telepathylogger-0.2   0.8.0-2
ii  gir1.2-upowerglib-1.00.9.23-2+b1
ii  gjs  1.36.1-2
ii  gnome-bluetooth  3.8.1-2
ii  gnome-icon-theme-symbolic3.10.1-1
ii  gnome-settings-daemon3.8.5-2
ii  gnome-shell-common   3.8.4-5
ii  gnome-themes-standard3.8.4-1
ii  gsettings-desktop-schemas3.8.2-2
ii  libatk-bridge2.0-0   2.10.0-1+b1
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-93
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcamel-1.2-43  3.8.5-3
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libclutter-1.0-0 1.14.4-3
ii  libcogl-pango12  1.14.0-3
ii  libcogl121.14.0-3
ii  libcroco30.6.8-2
ii  libdbus-1-3  1.6.18-1
ii  libdbus-glib-1-2 0.100.2-1
ii  libecal-1.2-15   3.8.5-3
ii  libedataserver-1.2-173.8.5-3
ii  libegl1-mesa [libegl1-x11]   9.2.2-1
ii  libgck-1-0   3.8.2-4
ii  libgcr-base-3-1  3.8.2-4
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libgirepository-1.0-11.36.0-2+b1
ii  libgjs0c [libgjs0-libmozjs185-1.0]   1.36.1-2
ii  libglib2.0-0 2.36.4-1
ii  libgnome-menu-3-03.8.0-2
ii  libgstreamer1.0-01.2.1-1
ii  libgtk-3-0   3.8.4-1
ii  libical0 0.48-2
ii  libjson-glib-1.0-0   0.16.2-1
ii  libmozjs185-1.0  1.8.5-1.0.0+dfsg-4+b1
ii  libmutter0b  3.8.4-2
ii  libnm-glib4  0.9.8.0-5
ii  libnm-gtk0   0.9.8.4-1
ii  libnm-util2  0.9.8.0-5
ii  libnspr4 

Bug#730093: gdm3 doesn't display the login screen

[Kjö Hansi Glaz]

Package: gdm3
Version: 3.8.4-6
Severity: important

Dear Maintainer,

   * What led up to the situation?

Upgrade gdm3 to version 3.8.4-6 that just hit jessie

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Reboot the computer

   * What was the outcome of this action?

No login screen appears, but a black screen.

   * What outcome did you expect instead?

A login screen.

   * Some more info

I included :0-slave and :0-greeter logs below.

I read several bug reports on gdm3 on the bug tracker but was unable to
understand if I actually face one of them.

This looks a bit like #724731, but it is supposed to be solved.

I do not really understand if it might be #729674. I use debian jessie
default kernel.

Please tell me if there's anything I can do to help you sorting out what
looks like a big mess of similar bugs to me.

-- /var/log/gdm3/:0-slave.log

gdm-simple-slave[15084]: Failed to give slave programs access to the display. 
Trying to proceed.
gdm-launch-environment][15102]: pam_unix(gdm-launch-environment:session): 
session opened for user Debian-gdm by (uid=0)
gdm-launch-environment][15102]: pam_systemd(gdm-launch-environment:session): 
Failed to create session: No such process
gdm-launch-environment][15102]: 
pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring PAM_TTY 
:0
gdm-launch-environment][15102]: pam_unix(gdm-launch-environment:session): 
session closed for user Debian-gdm
gdm-simple-slave[15084]: GLib-GObject: g_object_ref: assertion 
`object-ref_count  0' failed
gdm-simple-slave[15084]: GLib-GObject: g_object_unref: assertion 
`object-ref_count  0' failed

-- /var/log/gdm3/:0-greeter.log

libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
JS ERROR: !!!   Exception in callback for signal: sessions-loaded
JS ERROR: !!! message = 'Argument 'string' (type utf8) may not be 
null'
JS ERROR: !!! fileName = '/usr/share/gjs-1.0/overrides/GLib.js'
JS ERROR: !!! lineNumber = '105'
JS ERROR: !!! stack = '_pack_variant([object 
Array],null)@/usr/share/gjs-1.0/overrides/GLib.js:105
_pack_variant([object Array],[object 
Array])@/usr/share/gjs-1.0/overrides/GLib.js:152
((s),[object Array])@/usr/share/gjs-1.0/overrides/GLib.js:263
_proxyInvoker(GetSession,false,[object Array],[object 
Array])@/usr/share/gjs-1.0/overrides/Gio.js:79
(null,function () {[native code]})@/usr/share/gjs-1.0/overrides/Gio.js:125
(function () {[native code]})@/usr/share/gnome-shell/js/misc/loginManager.js:152
wrapper(function () {[native code]})@/usr/share/gjs-1.0/lang.js:213
()@/usr/share/gnome-shell/js/ui/screenShield.js:517
wrapper()@/usr/share/gjs-1.0/lang.js:213
()@/usr/share/gjs-1.0/lang.js:154
()@/usr/share/gjs-1.0/lang.js:248
_initializeUI()@/usr/share/gnome-shell/js/ui/main.js:163
_sessionsLoaded([object Object])@/usr/share/gnome-shell/js/ui/main.js:109
_emit(sessions-loaded)@/usr/share/gjs-1.0/signals.js:124
([object Object])@/usr/share/gnome-shell/js/ui/sessionMode.js:177
done()@/usr/share/gnome-shell/js/misc/fileUtils.js:33
([object Array])@/usr/share/gnome-shell/js/misc/fileUtils.js:51
onNextFileComplete([object GObject_Object],[object 
GObject_Object])@/usr/share/gnome-shell/js/misc/fileUtils.js:21
'

(gnome-shell:15147): GLib-GIO-WARNING **: Type of return value is incorrect: 
expected `(b)', got `()''
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

(gnome-settings-daemon:15137): GLib-GIO-WARNING **: Error releasing name 
org.gnome.SettingsDaemon: La connexion est fermée

(gnome-settings-daemon:15137): GLib-GIO-WARNING **: Error releasing name 
org.gnome.SettingsDaemon.Power: La connexion est fermée

(gnome-settings-daemon:15137): GLib-GIO-WARNING **: Error releasing name 
org.gnome.SettingsDaemon.XRANDR: La connexion est fermée

(gnome-settings-daemon:15137): GLib-GIO-WARNING **: Error releasing name 
org.gnome.SettingsDaemon.Keyboard: La connexion est fermée

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdm3 depends on:
ii  accountsservice  0.6.34-2
ii  adduser  3.113+nmu3
ii  dconf-cli0.18.0-1
ii  dconf-gsettings-backend  0.18.0-1
ii  debconf [debconf-2.0]1.5.52
ii  gir1.2-gdm3  3.8.4-6
ii  gnome-session [x-session-manager]3.8.4-3
ii  gnome-session-bin3.8.4-3
ii  gnome-session-flashback 

Bug#687032: gdm3: Please mention that the fallback mode of GDM3 is used

[Kjö Hansi Glaz]

notfound 687032 3.8.4-6
thanks

Package: gdm3
Followup-For: Bug #687032

Dear Maintainer,

I belive this bug is outdated as gdm3 now uses gnome-shell.

Cheers


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

Bug#717143: nautilus: Columns not resizeable in list view

[Kjö Hansi Glaz]

Package: nautilus
Version: 3.4.2-1+build1
Severity: normal


Dear Maintainer,


* What led up to the situation?

  - Open nautilus
  - Go to a local folder
  - Display it in list view


* What exactly did you do (or not do) that was effective (or
  ineffective)?

Put the mouse on the space between two columns header.


* What was the outcome of this action?

The mouse cursor shows arrows (-) as if I could resize the columns,
but trying to resize them has no effect.


* What outcome did you expect instead?

I expect to be able to resize the columns, as in previous versions of
nautilus. (At lease, if it is a feature that the columns are nor
resizeable anymore, then I expect the cursor not to show resizing
arrows.)


By the way, thanks for maintaining GNOME in Debian!


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.21-1
ii  gsettings-desktop-schemas  3.4.2-3
ii  gvfs   1.16.3-1
ii  libatk1.0-02.8.0-2
ii  libc6  2.17-7
ii  libcairo-gobject2  1.12.14-4
ii  libcairo2  1.12.14-4
ii  libexempi3 2.2.1-1
ii  libexif12  0.6.21-1
ii  libgail-3-03.8.2-3
ii  libgdk-pixbuf2.0-0 2.28.2-1
ii  libglib2.0-0   2.36.3-3
ii  libglib2.0-data2.36.3-3
ii  libgnome-desktop-3-2   3.4.2-2
ii  libgtk-3-0 3.8.2-3
ii  libnautilus-extension1a3.4.2-1+build1
ii  libnotify4 0.7.5-2
ii  libpango1.0-0  1.32.5-5+b1
ii  libselinux12.1.13-2
ii  libtracker-sparql-0.14-0   0.14.1-3
ii  libx11-6   2:1.6.0-1
ii  libxml22.9.1+dfsg1-2
ii  nautilus-data  3.4.2-1+build1
ii  shared-mime-info   1.0-1+b1

Versions of packages nautilus recommends:
ii  brasero  3.8.0-1
ii  eject2.1.5+deb1+cvs20081104-13
ii  gnome-sushi  0.4.1-4
ii  gvfs-backends1.16.3-1
ii  librsvg2-common  2.36.4-2

Versions of packages nautilus suggests:
ii  eog3.8.2-1
ii  evince [pdf-viewer]3.4.0-3.1+b1
ii  totem  3.0.1-8+b1
ii  tracker0.14.1-3
ii  vlc [mp3-decoder]  2.0.7-3
ii  vlc-nox [mp3-decoder]  2.0.7-3
ii  xdg-user-dirs  0.15-1

-- 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#687500: hangs in console instead of switching to display manager

[Kjö Hansi Glaz]

Package: plymouth
Version: 0.8.8-10
Followup-For: Bug #687500

Dear Maintainer,

I reproduced this bug on jessie with latest plymouth from experimental.

My system is Lenovo ThinkPad X200 with an intel graphical adapter managed
by the i915 module:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series 
Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

I saw this bug is tagged moreinfo. Is there any information you'd like
me to provide?

Thanks by advance for your answer

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages plymouth depends on:
ii  initramfs-tools0.113
ii  libc6  2.17-7
ii  multiarch-support  2.17-7

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base  7.0.3
ii  plymouth-drm  0.8.8-10

-- Configuration Files:
/etc/plymouth/plymouthd.conf changed [not included]

-- 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#698679: systemd: Fail to resume from hibernate when booting with systemd

[Kjö Hansi Glaz]

Hi,

On Tue, Jan 22, 2013 at 09:52:55AM +0100, Michael Biebl wrote:
 On 22.01.2013 09:32, Kjö Hansi Glaz wrote:
 
  My desktop system is not usable after resuming from hibernate. During
  resume, it boots fine, but I end up with a black screen on which I only
  see the mouse cursor. Changind TTY (CTRL+ALT+F1) doesn't make the cursor
  disappear.
 
 That is strange given that systemd is not involved with hibernate/resume
 at allWhen you resume a hibernated system, you could even drop the
 init=/bin/systemd boot parameter, since init is not started on resume..
 Resuming from hibernate is entirely handled within the initramfs.
 
After some more investigation it seems me that systemd might not be
involved at all in the issue. There were an upgrade of libdrm the same
day I switched to systemd which I suspect to bring an erratic behaviour
which mislead me during my tests. I still have to werify this
hypothesis before reassigning the bug. You might prefer to close this
one before I open another one?

All my apologies for the inconvenience.


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

Bug#698679: systemd: Fail to resume from hibernate when booting with systemd

[Kjö Hansi Glaz]

Package: systemd
Version: 44-7
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Boot with `init=/bin/systemd`.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Hibernate and try to resume.

   * What was the outcome of this action?

My desktop system is not usable after resuming from hibernate. During
resume, it boots fine, but I end up with a black screen on which I only
see the mouse cursor. Changind TTY (CTRL+ALT+F1) doesn't make the cursor
disappear.

   * What outcome did you expect instead?

After resuming when using `init=/bin/systemd`, I expect to see the
dialog askig for my password that I see when using regular old init.

My system is uptodate wheezy on a lenovo ThinkPad X200, using radeon
graphics driver. Find below lspci.

Thanks by advance for your attention,

Cheers

$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI 
Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network 
Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 
(rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port 
SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] 
Network Connection

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages systemd depends on:
ii  dpkg 1.16.9
ii  initscripts  2.88dsf-34
ii  libacl1  2.2.51-8
ii  libaudit01:1.7.18-1.1
ii  libc62.13-37
ii  libcap2  1:2.22-1.2
ii  libcryptsetup4   2:1.4.3-4
ii  libdbus-1-3  1.6.8-1
ii  libkmod2 9-2
ii  liblzma5 5.1.1alpha+20120614-2
ii  libpam0g 1.1.3-7.1
ii  libselinux1  2.1.9-5
ii  libsystemd-daemon0   44-7
ii  libsystemd-id128-0   44-7
ii  libsystemd-journal0  44-7
ii  libsystemd-login044-7
ii  libudev0 175-7
ii  libwrap0 7.6.q-24
ii  udev 175-7
ii  util-linux   2.20.1-5.3

Versions of packages systemd recommends:
ii  libpam-systemd  44-7

Versions of packages systemd suggests:
ii  python2.7.3~rc2-1
ii  python-cairo  1.8.8-1+b2
ii  python-dbus   1.1.1-1
pn  systemd-gui   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#695131: bug fixed for me in unstable

[Kjö Hansi Glaz]

Control: fixed 695131 0.2.3-3

Hi,

The last upload of cups-pk-helper 0.2.3-3 in unstable fixes the bug for
me.

Cheers


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

Bug#696241: gnome-control-center fails to add printer, says HP-Color-LaserJet-CP1515n is not a valid printer name.

[Kjö Hansi Glaz]

forcemerge 696241 695131 
reassign 696241 cups-pk-helper 0.2.3-2
thanks

Hi,

 gnome-control-center fails to add my network printer. After finishing
 the configuration wizard, I'm getting the following error message (see
 also the attached screenshot):
 
   Failed to add new printer.
 
 Here's the relevant part of the ~/.xsession-errors file: [...]
 
   (gnome-control-center:16609): printers-cc-panel-WARNING **: 
 HP-Color-LaserJet-CP1515n is not a valid printer name.

I found that the message \%s\ is not a valid printer name. comes
from the cups-pk-helper function _cph_cups_is_printer_name_valid
(cups-pk-helper-0.2.3/src/cups.c:397).

The printer name is validated by the function
_cph_cups_is_printer_name_valid_internal
(cups-pk-helper-0.2.3/src/cups.c:327), which doesn't allow dash.

However, printers added through the CUPS web interface or
system-config-printer have dash in their default names. The function
refuses names that cups actually allows.

I build a cups-pk-helper package with the following patch applied and it
fixes the bugs I experienced:

--- cups-pk-helper-0.2.3.orig/src/cups.c
+++ cups-pk-helper-0.2.3/src/cups.c
@@ -347,7 +347,7 @@ _cph_cups_is_printer_name_valid_internal
 return FALSE;
 
 for (i = 0; i  len; i++) {
-if (!g_ascii_isalnum (name[i])  name[i] != '_')
+if (!g_ascii_isalnum (name[i])  name[i] != '_'  name[i] != 
'-')
 return FALSE;
 }

Cheers,

Kjö


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

Bug#696241: Upstream patch

[Kjö Hansi Glaz]

Control: tag -1 + patch

Hi again,

Upstream has a patch for this issue:


http://cgit.freedesktop.org/cups-pk-helper/patch/?id=f00aee0b43c31e94087668b23b72e873c660de5e

I applied it to cups-pk-helper 0.2.3-2 and it fixes the problem for me.

Cheers


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

Bug#696241: gnome-control-center fails to add network printer

[Kjö Hansi Glaz]

Package: gnome-control-center
Version: 1:3.4.2+git20121016.29d7c0-1
Followup-For: Bug #696241

Dear Maintainer,

   * What led up to the situation?

- Open the printer section of gnome-control-center
- Authenticate
- Click +
- Select my network printer

   * What was the outcome of this action?

An error dialog stating Failed to add new printer. is displayed and
the printer is not added

The terminal output reads:

(gnome-control-center:15283): printers-cc-panel-WARNING **: Install
system-config-printer which provides DBus method
GroupPhysicalDevices to group duplicates in device list.

(gnome-control-center:15283): printers-cc-panel-WARNING **: You
should install system-config-printer which provides DBus method
GetBestDrivers. Using fallback solution for now.

(gnome-control-center:15283): printers-cc-panel-WARNING **:
CLP-620-Series is not a valid printer name.

   * What outcome did you expect instead?

The printer to be installed.

Please note that system-config-printer is installed and that I have an
uptodate wheezy system.

I installed the printer with the old system-config-printer interface
and it worked well.

Cheers,

K.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.21-7
ii  apg2.2.3.dfsg.1-2
ii  desktop-file-utils 0.20-0.1
ii  gnome-control-center-data  1:3.4.2+git20121016.29d7c0-1
ii  gnome-desktop3-data3.4.2-1
ii  gnome-icon-theme   3.4.0-2
ii  gnome-icon-theme-symbolic  3.4.0-2
ii  gnome-menus3.4.2-5
ii  gnome-settings-daemon  3.4.2+git20121218.7c1322-1
ii  gsettings-desktop-schemas  3.4.2-3
ii  libatk1.0-02.4.0-2
ii  libc6  2.13-37
ii  libcairo-gobject2  1.12.2-2
ii  libcairo2  1.12.2-2
ii  libcanberra-gtk3-0 0.28-6
ii  libcanberra0   0.28-6
ii  libcheese-gtk213.4.2-2
ii  libcheese3 3.4.2-2
ii  libclutter-1.0-0   1.10.8-2
ii  libcogl-pango0 1.10.2-6
ii  libcogl9   1.10.2-6
ii  libcolord1 0.1.21-1
ii  libcomerr2 1.42.5-1
ii  libcups2   1.5.3-2.9
ii  libdbus-1-31.6.8-1
ii  libdbus-glib-1-2   0.100-1
ii  libfontconfig1 2.9.0-7.1
ii  libgcrypt111.5.0-3
ii  libgdk-pixbuf2.0-0 2.26.1-1
ii  libglib2.0-0   2.33.12+really2.32.4-3
ii  libgnome-bluetooth10   3.4.2-1
ii  libgnome-desktop-3-2   3.4.2-1
ii  libgnome-menu-3-0  3.4.2-5
ii  libgnomekbd7   3.4.0.2-1
ii  libgnutls262.12.20-2
ii  libgoa-1.0-0   3.4.2-1
ii  libgssapi-krb5-2   1.10.1+dfsg-3
ii  libgstreamer0.10-0 0.10.36-1
ii  libgtk-3-0 3.4.2-4
ii  libgtop2-7 2.28.4-3
ii  libjson-glib-1.0-0 0.14.2-1
ii  libk5crypto3   1.10.1+dfsg-3
ii  libkrb5-3  1.10.1+dfsg-3
ii  libnm-glib40.9.4.0-6
ii  libnm-gtk0 0.9.4.1-2
ii  libnm-util20.9.4.0-6
ii  libnotify4 0.7.5-1
ii  libpango1.0-0  1.30.0-1
ii  libpolkit-gobject-1-0  0.105-3
ii  libpulse-mainloop-glib02.0-6
ii  libpulse0  2.0-6
ii  libsocialweb-client2   0.25.20-2
ii  libupower-glib10.9.17-1
ii  libwacom2  0.6-1
ii  libx11-6   2:1.5.0-1
ii  libxcomposite1 1:0.4.3-2
ii  libxdamage11:1.1.3-2
ii  libxext6   2:1.3.1-2
ii  libxfixes3 1:5.0-4
ii  libxi6 2:1.6.1-1
ii  libxklavier16  5.2.1-1
ii  libxml22.8.0+dfsg1-7
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages gnome-control-center recommends:
ii  cups-pk-helper 0.2.3-2
ii  gnome-online-accounts  3.4.2-1
ii  gnome-session  3.4.2.1-3
ii  gnome-user-guide   3.4.2-1+build1
ii  iso-codes  3.40-1
ii  mesa-utils 8.0.1-2+b3
ii  mousetweaks3.4.2-1
ii  policykit-1-gnome  0.105-2

Versions of packages gnome-control-center suggests:
ii  gnome-screensaver 3.4.1-1
ii  gstreamer0.10-pulseaudio  0.10.31-3+nmu1
ii  libcanberra-gtk-module0.28-6
ii  x11-xserver-utils 7.7~3

-- 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#634930: gpa: GPA unusable due to General Assuan error

[Kjö Hansi Glaz]

Package: gpa
Version: 0.9.0-2
Followup-For: Bug #634930

Dear Maintainer,

Some info on the status of this bug on a fresh wheezy.

- Install wheezy with the installer beta2
- Install gpa
- Start gpa
- I get three dialogs. I can't click/close any of them

1. GPA error

The GPGME library returned an unexpected error. The error was:

General Assuan error

This is probably a bug in GPA.
GPA will now try to recover from this error.

2. 

You do not have a private key yet. Do you want to generate one now
(recommanded) or do it later?

3.

GnuPG is rebuilding the trust database. This might take a few
seconds.

- On the terminal, I get the following message:

** Message: switched engine to `/usr/bin/gpg2'

- I had to kill gpa from a terminal to close it
- I installed 0.9.3-1 from experimental and I got the same behaviour.
- I created a public/private key pair using the commandline, then start GPA: I
  still get the General Assuan error but I can click close, and then
  use the GPA interface. However, most actions throws General Assuan
  error and fail

Thanks by advance for your work,

Kjö


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

Bug#684675: debian-installer: installer silently fails when detecting network hardware

[Kjö Hansi Glaz]

Package: debian-installer
Version: 7.0 beta1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

- download debian installer 7.0 beta1 i386 netinst iso
- download hd-media boot.img.gz
- download firmware tarball and extract it
- zcat boot.img.gz on a USB drive
- add the iso
- add the firmware/ directory
- boot the USB drive containing the installer on an IBM ThinkPad X200

   * What was the outcome of this action?

The installer gets stuck at network hardware detection: only the title is
displayed, nothing happens for more than half an hour.

Last message in the console log is:

mount: sending ioctl 5310 to a partition!

   * What outcome did you expect instead?

Get the choice of which network hardware to use or get an error message
explaining what happens.

Cheers


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

Bug#682431: vidalia: apparmor profiles deny reading theme

[Kjö Hansi Glaz]

Package: vidalia
Version: 0.2.19-2
Severity: minor

Dear Maintainer,

   * What led up to the situation?

Start vidalia under GNOME 3 with apparmor enabled

   * What was the outcome of this action?

The theme is not applied as in other QT4 applications.

In the kernel logs, I get:

apparmor=DENIED operation=open parent=23799 profile=/usr/bin/vidalia 
name=/usr/share/themes/Adwaita/gtk-2.0/gtkrc pid=25341 comm=vidalia 
requested_mask=r denied_mask=r fsuid=1000 ouid=0
apparmor=DENIED operation=open parent=23799 profile=/usr/bin/vidalia 
name=/usr/share/themes/Default/gtk-2.0-key/gtkrc pid=25341 comm=vidalia 
requested_mask=r denied_mask=r fsuid=1000 ouid=0
apparmor=DENIED operation=file_lock parent=23799 
profile=/usr/bin/vidalia name=/usr/share/icons/Human/index.theme pid=25341 
comm=vidalia requested_mask=k denied_mask=k fsuid=1000 ouid=0
apparmor=DENIED operation=file_lock parent=23799 
profile=/usr/bin/vidalia name=/usr/share/icons/Tangerine/index.theme 
pid=25341 comm=vidalia requested_mask=k denied_mask=k fsuid=1000 ouid=0
apparmor=DENIED operation=file_lock parent=23799 
profile=/usr/bin/vidalia name=/usr/share/icons/gnome/index.theme pid=25341 
comm=vidalia requested_mask=k denied_mask=k fsuid=1000 ouid=0
apparmor=DENIED operation=file_lock parent=23799 
profile=/usr/bin/vidalia name=/usr/share/icons/hicolor/index.theme 
pid=25341 comm=vidalia requested_mask=k denied_mask=k fsuid=1000 ouid=0

   * What outcome did you expect instead?

That apparmor profiles let vidalia read the theme. Adding the following lines 
in /etc/apparmor.d/local/usr.bin.vidalia fixes the issue for me:

/usr/share/themes/**r,
@{HOME}/.themes/r,
@{HOME}/.themes/**  r,

Thanks by advance,

K.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages vidalia depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.44
ii  libc6  2.13-33
ii  libgcc11:4.7.1-2
ii  libqt4-network 4:4.8.2-1
ii  libqt4-xml 4:4.8.2-1
ii  libqtcore4 4:4.8.2-1
ii  libqtgui4  4:4.8.2-1
ii  libstdc++6 4.7.1-2
ii  tor0.2.3.19-rc-1
ii  ucf3.0025+nmu3

vidalia recommends no packages.

Versions of packages vidalia suggests:
ii  apparmor 2.7.103-4
ii  xul-ext-torbutton [iceweasel-torbutton]  1.4.6-1


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

Bug#682431: vidalia: apparmor profiles deny reading theme

[Kjö Hansi Glaz]

On Sun, Jul 22, 2012 at 07:58:53PM +0200, intrigeri wrote:
 Hi,
 
 I cannot reproduce that with 0.2.20-1, that had some improvements in
 this area. Please try to reproduce it, and report back.
 
I reproduced the issue with a fresh wheezy VM with gnome desktop, installing
the packages vidalia and apparmor from unstable and rebooting with
apparmor=1 security=apparmor:

apparmor=DENIED operation=open parent=2727 profile=/usr/bin/vidalia 
name=/usr/share/themes/Adwaita/gtk-2.0/gtkrc pid=4974 comm=vidalia 
requested_mask=r denied_mask=r fsuid=1000 ouid=0
apparmor=DENIED operation=open parent=2727 profile=/usr/bin/vidalia 
name=/usr/share/themes/Default/gtk-2.0-key/gtkrc pid=4974 comm=vidalia 
requested_mask=r denied_mask=r fsuid=1000 ouid=0


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

Bug#427669: icedove really slow

[Kjö Hansi Glaz]

Hi,

On Sun, Jun 03, 2012 at 11:24:48AM +0200, Carsten Schoenert wrote:
 Hello!
 
 On Wed, Jun 10, 2009 at 11:58:07PM +0200, Kjö Hansi Glaz wrote:
  Package: icedove
  Version: 2.0.0.19-1
  Severity: normal
  
  
  I experience the same problem. Displaying simple mails is really 
  slow, and icedove becomes as slow as it is nearly unusable.
 
 Do you still have problems with long textmails?
 I can't confirm this behavior on actual squeeze (3.1.6) and wheezy
 (10.0.4-1) versions.
 If there was such problems in old versions this could be still 
 fixed upstream.
 
I totally reinstalled my system and I don't use Icedove anymore so I
can't easily test.

Good luck for squashing this bug



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

Bug#627085: libpam-mount: multiple logins of the same UID result in multiple mounts, not all mounts are cleanly umounted

[Kjö Hansi Glaz]

Package: libpam-mount
Version: 2.14~git+d1d6f871-1
Followup-For: Bug #627085

I experience the same issue using pam_mount to mount an aufs, so I think this
is not a diplicate of the cifs bug #586009

Cheers,

Kjö

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages libpam-mount depends on:
ii  base-files  6.7
ii  libc6   2.13-32
ii  libcryptsetup4  2:1.4.1-3
ii  libhx28 3.12.1-1
ii  libmount1   2.20.1-4
ii  libpam-runtime  1.1.3-7.1
ii  libpam0g1.1.3-7.1
ii  libssl1.0.0 1.0.1c-1
ii  libxml2 2.7.8.dfsg-9
ii  mount   2.20.1-4

libpam-mount recommends no packages.

Versions of packages libpam-mount suggests:
pn  cifs-utils  none
pn  davfs2  none
pn  fuse-utils  2.8.7-2
pn  lsof4.86+dfsg-1
pn  ncpfs   none
pn  openssl 1.0.1c-1
pn  psmisc  22.16-1
pn  sshfs   none
pn  tc-utilsnone
pn  xfsprogsnone

-- Configuration Files:
/etc/security/pam_mount.conf.xml changed [not included]

-- 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#670197: plymouth: Please upgrade to plymouth 0.8.4

[Kjö Hansi Glaz]

Package: plymouth
Version: 0.8.3-20
Severity: wishlist

Dear Maintainer,

Plymouth 0.8.4 is out [1]. I would find nice to have it packaged in wheezy.

Thanks by advance,

K.

[1]: http://lists.freedesktop.org/archives/plymouth/2012-March/000611.html



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

Bug#619711: How to solve for wheezy?

[Kjö Hansi Glaz]

Hi,

I think that this bug must be solve before wheezy release. It basically
prevents a normal user from booting a newly installed encrypted system
with non-english keyboard layout.

My tests shows that the patch proposed by Andreas Altergott works on a
freshed install wheezy.

I'm up for any other necessary testing.

Cheers,

Kjö



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

Bug#645547: [i915] intermittent memory corruption after hibernation unless i915.modeset=0

[Kjö Hansi Glaz]

On Fri, Mar 30, 2012 at 12:44:52PM -0500, Jonathan Nieder wrote:
 tags 645547 + upstream patch
 quit
 
 Kjö Hansi Glaz wrote:
 
  I tried appending `i915.modeset=0` and thus falling back to vesa makes
  hibremation/resume working.
 
  I also tested 3.2.0-rc4 from experimetal (with modesetting enabled) and
  experience the same kind of problems that with 3.1.0. Sometimes
  processes segfault, sometimes the whole kernel hangs.
 
 Thanks again for tracking this down.  Please test the attached patch
 against a 3.2.y kernel, such as the one from sid. 

From my experience of a dozen of hibernate/resume cycles, this patch works.

Thanks for following this bug!



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

Bug#659197: glade: Glade segfaults when trying to open ComboBox editor

[Kjö Hansi Glaz]

Package: glade
Version: 3.10.2-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

- select a GtkComboBox
- click on the Edit... toolbar button

   * What was the outcome of this action?

glade segfaults:

$ gdb glade
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/glade...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/glade 
[Thread debugging using libthread_db enabled]
GladeUI-Message: No displayable values for property 
GtkMessageDialog::message-type
GladeUI-Message: No displayable values for property GtkTreeSelection::mode
GladeUI-Message: 14 missing displayable value for 
GtkCellRendererAccel::accel-mods

(glade:12206): GladeUI-CRITICAL **: Unable to load module 'vte' from any search 
paths

(glade:12206): GladeUI-WARNING **: Failed to load external library 'vte'

(glade:12206): GladeUI-WARNING **: Impossible de trouver le symbole 
« vte_terminal_get_type »

(glade:12206): GladeUI-WARNING **: Impossible de récupérer le type à partir de 
« VteTerminal »

(glade:12206): GladeUI-WARNING **: Failed to load the GType for 'VteTerminal'

(glade:12206): GladeUI-WARNING **: Tried to include undefined widget class 
'VteTerminal' in a widget group

(glade:12206): GladeUI-CRITICAL **: Unable to load module 'gtksourceview-3.0' 
from any search paths

(glade:12206): GladeUI-WARNING **: Failed to load external library 
'gtksourceview-3.0'

(glade:12206): GladeUI-WARNING **: Impossible de trouver le symbole 
« gtk_source_view_get_type »

(glade:12206): GladeUI-WARNING **: Impossible de récupérer le type à partir de 
« GtkSourceView »

(glade:12206): GladeUI-WARNING **: Failed to load the GType for 'GtkSourceView'

(glade:12206): GladeUI-WARNING **: Tried to include undefined widget class 
'GtkSourceView' in a widget group
[New Thread 0x7fffe8b1c700 (LWP 12211)]
[New Thread 0x7fffe3fff700 (LWP 12212)]
[New Thread 0x7fffe37fe700 (LWP 12213)]
[New Thread 0x7fffe2dfb700 (LWP 12219)]
[Thread 0x7fffe3fff700 (LWP 12212) exited]

Gtk-ERROR **: GtkBox child GladeEditorTable minimum height: -4  0

Program received signal SIGTRAP, Trace/breakpoint trap.
0x7696a888 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x7696a888 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7696ac02 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7757c40d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x776b27f3 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x7757c675 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#5  0x776b27f3 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#6  0x7757c705 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x776b27f3 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x7776b708 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x7776b855 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7702a75a in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7703bf7a in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x77045e11 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x77045fb2 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7777f229 in gtk_widget_size_allocate () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x776a5066 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x776a564d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#17 0x7702a75a in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x7703bf7a in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x77045e11 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x77045fb2 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x7777f229 in gtk_widget_size_allocate () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#22 0x776698c9 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#23 0x7702a75a in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x7703bf7a in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x77045e11 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x77045fb2 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 

Bug#645547: working with vesa

[Kjö Hansi Glaz]

Hi,

I tried appending `i915.modeset=0` and thus falling back to vesa makes
hibremation/resume working.

I also tested 3.2.0-rc4 from experimetal (with modesetting enabled) and
experience the same kind of problems that with 3.1.0. Sometimes
processes segfault, sometimes the whole kernel hangs.

Below are some call traces under 3.2.0 (copied by hand so not complete, but
I can copy next one if it helps.

Please ask for any other useful information I could provide.

1st crash
=

gnome-panel: __find_get_block_slow

Call Trace:
__find_get_block
___getblk
__breadahead
__ext4_get_inode_loc
ext4_iget
ext4_lookup
d_alloc_and_lookup
walk_component
path_lookupat
do_path_lookup
user_path_at_empty
user_path_at_empty
vfs_fstatat
generic_permission
sys_newstat
__call_rcu
sys_faccessat
system_call_fastpath

Segfault after resume
=

[27139.171820] nautilus[2973]: segfault at 20054 ip 7f404317337a
sp 7fff94f81008 error 4 in libglib-2.0.so.0.3000.2[7f404313e000+f6000]

2nd crash
=

squid3: kmem_cache_alloc 0x9c/0xea

Call trace:
alloc_buffer_head
alloc_page_buffers
__get_blkid
ext4_getblk
ext4_bread
__dentry_open
htree_dirblock_to_tree
dput
ext4_htree_fill_free
ext4_readdir
ext4_readdir
ext4_readdir
do_flip_open
fillonedir
fillonedir
kmem_cache_free
sys_getdents
system_call_fastpath




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

Bug#652084: gosmore use 100% CPU and does nothing

[Kjö Hansi Glaz]

Package: gosmore
Version: 0.0.0.20100711-2
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

Install gosmore, and start it.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I started gosmore straight after installing it.

   * What was the outcome of this action?

It printed gosmore is in the public domain and comes without warranty
and then doesn't display anything but use 100% CPU. Thinking it might be
rebuilding some data, I let it run for several hours and nothing
happened.

   * What outcome did you expect instead?

Display the GUI or inform the user about what it is doing.

*** End of the template - remove these lines ***


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages gosmore depends on:
ii  libatk1.0-0 2.2.0-2 
ii  libc6   2.13-21 
ii  libcairo2   1.10.2-6.1  
ii  libcurl3-gnutls 7.22.0-3
ii  libfontconfig1  2.8.0-3 
ii  libfreetype62.4.8-1 
ii  libgcc1 1:4.6.2-5   
ii  libgdk-pixbuf2.0-0  2.24.0-1
ii  libglib2.0-02.30.2-4
ii  libgtk2.0-0 2.24.8-2
ii  libpango1.0-0   1.29.4-2
ii  libstdc++6  4.6.2-5 
ii  libxml2 2.7.8.dfsg-5

Versions of packages gosmore recommends:
ii  gpsd  3.3-5

Versions of packages gosmore suggests:
pn  josm  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#645547: linux-image-3.0.0-1-amd64: New processes segfault after several resume from hibernation

[Kjö Hansi Glaz]

Package: linux-2.6
Version: 3.0.0-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Hibernate the laptop and resume several times.

   * What was the outcome of this action?

After several hibernate-resume cycles (sometimes 2, sometimes 6 or more)
new processes start to segfault, while already running processes
continue to run (please see kernel log below).

   * What outcome did you expect instead?

That new processes doesn't segfault.

   * Other tests

Similar issues occurs with 3.1.0-rc6 from experimental.

Please feel free to ask if I can do anything to help debugging this
issue.

Thanks by advance.

-- Package-specific info:
** Version:
sinux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/host-racine ro

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[24941.711217] EXT4-fs (dm-1): re-mounted. Opts: acl,errors=remount-ro,commit=0
[24941.853620] EXT4-fs (dm-2): re-mounted. Opts: commit=0
[24941.860143] EXT4-fs (dm-4): re-mounted. Opts: 
nobarrier,noauto_da_alloc,delalloc,commit=600,commit=0
[24941.862722] EXT4-fs (dm-5): re-mounted. Opts: 
nobarrier,noauto_da_alloc,delalloc,commit=600,commit=0
[24941.875739] EXT4-fs (dm-7): re-mounted. Opts: 
nobarrier,noauto_da_alloc,delalloc,commit=600,commit=0
[24942.142723] PM: Marking nosave pages: 0009e000 - 0010
[24942.142728] PM: Marking nosave pages: bd4a1000 - bd4a7000
[24942.142730] PM: Marking nosave pages: bd5b8000 - bd60f000
[24942.142734] PM: Marking nosave pages: bd6c6000 - bd9ff000
[24942.142752] PM: Marking nosave pages: bda0 - 0001
[24942.144107] PM: Basic memory bitmaps created
[24942.144109] PM: Syncing filesystems ... done.
[24942.226309] Freezing user space processes ... (elapsed 0.01 seconds) done.
[24942.240942] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[24942.257397] PM: Preallocating image memory... done (allocated 597494 pages)
[24943.947605] PM: Allocated 2389976 kbytes in 1.68 seconds (1422.60 MB/s)
[24943.948410] Suspending console(s) (use no_console_suspend to debug)
[24944.000946] e1000e :00:19.0: PME# enabled
[24944.000957] e1000e :00:19.0: wake-up capability enabled by ACPI
[24944.104353] HDA Intel :00:1b.0: PCI INT B disabled
[24944.360020] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[24944.360318] PM: freeze of devices complete after 411.136 msecs
[24944.361062] PM: late freeze of devices complete after 0.740 msecs
[24944.361441] ACPI: Preparing to enter system sleep state S4
[24944.524048] PM: Saving platform NVS memory
[24944.527173] Disabling non-boot CPUs ...
[24944.528519] CPU 1 is now offline
[24944.529290] Extended CMOS year: 2000
[24944.529377] PM: Creating hibernation image:
[24944.532503] PM: Need to copy 286385 pages
[24944.532503] PM: Normal pages needed: 286385 + 1024, available pages: 734964
[24944.532503] PM: Restoring platform NVS memory
[24944.532503] Extended CMOS year: 2000
[24944.532503] Enabling non-boot CPUs ...
[24944.532503] Booting Node 0 Processor 1 APIC 0x1
[24944.532503] smpboot cpu 1: start_ip = 99000
[24944.528497] Disabled fast string operations
[24944.620327] NMI watchdog enabled, takes one hw-pmu counter.
[24944.624012] Switched to NOHz mode on CPU #1
[24944.688053] CPU1 is up
[24944.689341] ACPI: Waking up from system sleep state S4
[24945.040021] e1000e :00:19.0: BAR 0: set to [mem 0xf260-0xf261] 
(PCI address [0xf260-0xf261])
[24945.040027] e1000e :00:19.0: BAR 1: set to [mem 0xf2624000-0xf2624fff] 
(PCI address [0xf2624000-0xf2624fff])
[24945.040033] e1000e :00:19.0: BAR 2: set to [io  0x1820-0x183f] (PCI 
address [0x1820-0x183f])
[24945.040048] e1000e :00:19.0: restoring config space at offset 0xf (was 
0x100, writing 0x10b)
[24945.040069] e1000e :00:19.0: restoring config space at offset 0x1 (was 
0x10, writing 0x100107)
[24945.040088] uhci_hcd :00:1a.0: power state changed by ACPI to D0
[24945.040091] uhci_hcd :00:1a.0: power state changed by ACPI to D0
[24945.040125] uhci_hcd :00:1a.0: power state changed by ACPI to D0
[24945.040127] uhci_hcd :00:1a.0: power state changed by ACPI to D0
[24945.040163] uhci_hcd :00:1a.2: power state changed by ACPI to D0
[24945.040165] uhci_hcd :00:1a.2: power state changed by ACPI to D0
[24945.040199] uhci_hcd :00:1a.2: power state changed by ACPI to D0
[24945.040201] uhci_hcd :00:1a.2: power state changed by ACPI to D0
[24945.040248] ehci_hcd :00:1a.7: power state changed by ACPI to D0
[24945.040253] ehci_hcd :00:1a.7: power state changed by ACPI to D0
[24945.040290] HDA Intel :00:1b.0: restoring config space at offset 0x1 
(was 0x100106, writing 0x100102)
[24945.040479] uhci_hcd :00:1d.0: power state changed by ACPI to D0

Bug#644541: vidalia: Open tor ControlPort on startup if AuthenticationMethod is defined

[Kjö Hansi Glaz]

Package: vidalia
Version: 0.2.14-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

In vidalia configuration file, add, for example

[Tor]
Changed=True
AuthenticationMethod=None

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

(re)start vidalia

   * What was the outcome of this action?

Tor ControlPort gets opened while it was not before.

Tor log shows:

[notice] New control connection opened.
[notice] New control connection opened.
[notice] Tor 0.2.2.33 (git-56122e2e9be4c477) opening log file.
[notice] Tor 0.2.2.33 (git-56122e2e9be4c477) opening log file.
[warn] ControlPort is open, but no authentication method has been 
configured.  This means that any program on your computer can reconfigure your 
Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.
[notice] Opening Control listener on 127.0.0.1:9051

   * What outcome did you expect instead?

Tor ControlPort keeps closed. I see no reason to open it.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vidalia depends on:
ii  adduser3.113  
ii  debconf [debconf-2.0]  1.5.40 
ii  libc6  2.13-21
ii  libgcc11:4.6.1-4  
ii  libqt4-network 4:4.7.3-5  
ii  libqt4-xml 4:4.7.3-5  
ii  libqtcore4 4:4.7.3-5  
ii  libqtgui4  4:4.7.3-5  
ii  libstdc++6 4.6.1-4
ii  tor0.2.2.33-1 
ii  ucf3.0025+nmu2

vidalia recommends no packages.

Versions of packages vidalia suggests:
ii  xul-ext-torbutton [iceweasel-torbutton]  1.4.3-1

-- debconf information:
* vidalia/users:
* vidalia/tor-daemon-interaction: nothing



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

Bug#640943: (no subject)

[Kjö Hansi Glaz]

Subject: installation-reports: d-i complains about unencrypted swap while swap 
is on an encrypted LV
Package: installation-reports
Severity: normal

*** Please type your report below this line ***


-- Package-specific info:

Boot method: usb
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 4-Sept-2011
SHA256SUM: f008bdc8cbb6c214e02d63331906ff03058b076dba499adb3d3c988f023c7af4

Machine: Lenovo Thinkpad X200
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:

To reproduce the problem:
- use default choices until the disk partitionning;
- choose automatic partitionnig using encrypted LVM
   --or--
- manually partition the disk with an encrypted volume containing a LVM
  with a LV for the root filesystem and a LV for swap

Issue: d-i complains the swap is unencrypted and refuse to continue
while the swap is actually on a LV which is itself on an encrypted PV

Workaround: reboot the installer, install without a swap, then manually
setup swap (not forgetting /etc/initramfs-tools/conf.d/resume for
suspend to disk)

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20110904-00:04
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux hostname 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series 
Chipset Memory Controller Hub [8086:2a40] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e0]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e4]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 
Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e4]
lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 
Series Chipset MEI Controller [8086:2a44] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e6]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LF 
Gigabit Network Connection [8086:10bf] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20ee]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #4 [8086:2937] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #5 [8086:2938] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #6 [8086:2939] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #2 [8086:293c] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f1]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) 
HD Audio Controller [8086:293e] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f2]
lspci -knn: Kernel driver in use: HDA Intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 1 [8086:2940] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 2 [8086:2942] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 4 [8086:2946] 

Bug#640944: (no subject)

[Kjö Hansi Glaz]

Subject: installation-reports: d-i complains about unencrypted swap while swap 
is on an encrypted LV
Package: installation-reports
Severity: normal

*** Please type your report below this line ***


-- Package-specific info:

Boot method: usb
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 4-Sept-2011
SHA256SUM: f008bdc8cbb6c214e02d63331906ff03058b076dba499adb3d3c988f023c7af4

Machine: Lenovo Thinkpad X200
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:

To reproduce the problem:
- use default choices until the disk partitionning;
- choose automatic partitionnig using encrypted LVM
   --or--
- manually partition the disk with an encrypted volume containing a LVM
  with a LV for the root filesystem and a LV for swap

Issue: d-i complains the swap is unencrypted and refuse to continue
while the swap is actually on a LV which is itself on an encrypted PV

Workaround: reboot the installer, install without a swap, then manually
setup swap (not forgetting /etc/initramfs-tools/conf.d/resume for
suspend to disk)

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20110904-00:04
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux hostname 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series 
Chipset Memory Controller Hub [8086:2a40] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e0]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e4]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 
Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e4]
lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 
Series Chipset MEI Controller [8086:2a44] (rev 07)
lspci -knn: Subsystem: Lenovo Device [17aa:20e6]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LF 
Gigabit Network Connection [8086:10bf] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20ee]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #4 [8086:2937] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #5 [8086:2938] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #6 [8086:2939] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f0]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #2 [8086:293c] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f1]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) 
HD Audio Controller [8086:293e] (rev 03)
lspci -knn: Subsystem: Lenovo Device [17aa:20f2]
lspci -knn: Kernel driver in use: HDA Intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 1 [8086:2940] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 2 [8086:2942] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 4 [8086:2946] 

Bug#580209: sonata: Sonata segfault with custom gtk-im-module if GTK_IM_MODULE is not set

[Kjö Hansi Glaz]

Hi

[...]

 uim 1:1.7.0-2 in unstable now, is it still reproducible?

I managed to test with unstable and the bug appears to be fixed in 1:1.7.0-2.

Complete test, on an uptodate unstable system:

- install sonata and uim-gtk2.0 1:1.7.0-2 (testing, unstable)
- copy previously attached .XCompose to ~
- start sonata
= no bug

- install uim-gtk2.0 1:1.5.7-9.1 (stable) and its dependancies
- start sonata
= segfault

So the bug seems to be actually fixed in uim uim-gtk2.0.

I'm thus closing the bug.

Cheers,

K.



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

Bug#580209: sonata: Sonata segfault with custom gtk-im-module if GTK_IM_MODULE is not set

[Kjö Hansi Glaz]

Hi,

On Sat, Jul 16, 2011 at 03:30:58PM +0900, d+...@vdr.jp wrote:
 Hi,
 
 On Fri, Jul 15, 2011 at 04:13:25PM +0200, Kjö Hansi Glaz wrote:
   sorry, this is unreproducible.
  
  Under stable I still reproduce it if .XCompose is present and
  GTK_IM_MODULE env var is not set.
 
 if GTK_IM_MODULE is set, xim or uim, does sonata crash?
 
If GTK_IM_MODULE is set to xim, sonata doesn't crash.

If GTK_IM_MODULE is set to uim, sonata crash.

   do you set env val XCOMPOSEFILE
  
  No I don't set this env var.
  
   and use ~/.XCompose file?
  
  Yes I do use .XCompose file.
 
 ok, if XCOMPOSEFILE is not set, uim uses ~/.XCompose automatically.
 can you send your ~/.XCompose file?

Find it attached

 and your locale is fr_FR.UTF-8 to use sonata?
 
Yes

   uim 1:1.7.0-2 in unstable now, is it still reproducible?
  
  I can't easily install it under stable, nor trivially backport it, so I
  might take some time to test.
 
 sorry, there is no plan to backport uim 1.7.0 for dependency reason.
 
   i think this bug is related with Bug#599837 (fixed in 1:1.7.0-1).
  
  Might be, but I don't get this problem with other applications than
  sonata.
 
 other PyGTK apps do not crash?  for example:
 
 http://www.pygtk.org/pygtk2tutorial/examples/entry.py

No, as said before on this bug, I use various other pyGtk apps and they
doesn't crash. I tried with entry.py and it doesn't crash either.

Regards,

Kjö
include %S/en_US.UTF-8/Compose

# From http://canonical.org/~kragen/setting-up-keyboard.html

# Custom additions: Typography
Multi_key period period period  : … U2026   # HORIZONTAL ELLIPSIS
# These two are already present for me:
# Multi_key minus minus minus   : — U2014   # EM DASH
# Multi_key minus minus period  : – U2013   # EN DASH
Multi_key minus minus space : – # EN DASH (followed by 
space)
Multi_key backslash minus : ­  U00AD   # SOFT HYPHEN
Multi_key comma space : ‚ U201A   # SINGLE LOW-9 QUOTATION MARK
Multi_key comma comma : „ U201E   # DOUBLE LOW-9 QUOTATION MARK
Multi_key apostrophe space: ’ U2019   # RIGHT SINGLE QUOTATION 
MARK
Multi_key apostrophe apostrophe   : ” U201D   # RIGHT DOUBLE 
QUOTATION MARK
#Multi_key grave space : ‘ U2018   # LEFT SINGLE QUOTATION MARK
#Multi_key grave grave : “ U201C   # LEFT DOUBLE QUOTATION MARK
Multi_key less bar: ↵ U21B5   # DOWNWARDS ARROW WITH CORNER 
LEFTWARDS
Multi_key o period: • U2022   # BULLET
# By default Multi_key period period does this, but we broke that with 
the ... binding.
Multi_key o comma : ·  periodcentered  # MIDDLE DOT
Multi_key space space :U00A0   # NO-BREAK SPACE
#Multi_key backslash comma :   U2009   # THIN SPACE
#Multi_key minus less  : ← leftarrow   # LEFTWARDS ARROW
Multi_key minus asciicircum   : ↑ uparrow # UPWARDS ARROW
#Multi_key minus greater   : → rightarrow  # RIGHTWARDS ARROW
Multi_key minus v : ↓ downarrow   # DOWNWARDS ARROW
Multi_key less greater: ↔ U2194   # LEFT RIGHT ARROW 
(kragen's)

Multi_key equal less: ⇐ U21D0   # LEFTWARDS DOUBLE ARROW
Multi_key equal greater: ⇒ U21D2   # RIGHTWARDS DOUBLE ARROW
Multi_key equal asciicircum   : ⇑ U21D1 # UPWARDS ARROW
Multi_key equal v : ⇓ U21D3   # DOWNWARDS ARROW
Multi_key less colon greater: ⇔ U21D4   # LEFT RIGHT 
DOUBLE ARROW

# Custom additions: Mathematical symbols
Multi_key exclam equal: ≠ U2260   # NOT EQUAL TO
#Multi_key less equal  : ≤ U2264   # LESS-THAN OR EQUAL TO
#Multi_key greater equal   : ≥ U2265   # GREATER-THAN OR EQUAL 
TO
#Multi_key i n : ∈ U220A   # ELEMENT OF
Multi_key minus C  : ∈ U220A   # ELEMENT OF 
#Multi_key exclam i n: ∉ U2209   # NOT AN ELEMENT OF
Multi_key slash minus C: ∉ U2209   # NOT AN ELEMENT OF
#Multi_key a p : ≅ U2245   # APPROXIMATELY EQUAL TO
Multi_key asciitilde equal : ≅ U2245   # APPROXIMATELY 
EQUAL TO
Multi_key colon equal : ≔ U2254   # COLON EQUALS
#Multi_key s q : √ U221A   # SQUARE ROOT
Multi_key v minus : √ U221A   # SQUARE ROOT
Multi_key slash backslash : ∧  U2227   # LOGICAL AND
Multi_key backslash slash : ∨  U2228   # LOGICAL OR
Multi_key o asterisk  : ∘   U2218   # RING OPERATOR 
(function composition)
Multi_key E E : ∃  U2203   # THERE EXISTS
Multi_key slash E E: ∄   U2204   # THERE DOES NOT 
EXIST
Multi_key A A : ∀  U2200   # FOR ALL
Multi_key Q E D : ∎   U220E   # END OF PROOF

# Custom additions: Greek letters.  Mapping corresponds to Emacs Greek input 
method.
Multi_key asterisk a  : α  U03B1   # GREEK SMALL LETTER ALPHA
Multi_key asterisk b  : β  U03B2   # GREEK SMALL LETTER BETA
Multi_key asterisk c  : ψ  U03C8   # GREEK SMALL

Bug#580209: sonata: Sonata segfault with custom gtk-im-module if GTK_IM_MODULE is not set

[Kjö Hansi Glaz]

Hi,

On Fri, Jul 15, 2011 at 12:18:15PM +0900, d+...@vdr.jp wrote:
 tags 580209 + moreinfo unreproducible
 thanks
 
 sorry, this is unreproducible.

Under stable I still reproduce it if .XCompose is present and
GTK_IM_MODULE env var is not set.

 uim 1:1.7.0-2 in unstable now, is it still reproducible?

I can't easily install it under stable, nor trivially backport it, so I
might take some time to test.

 do you set env val XCOMPOSEFILE

No I don't set this env var.

 and use ~/.XCompose file?

Yes I do use .XCompose file.

 i think this bug is related with Bug#599837 (fixed in 1:1.7.0-1).

Might be, but I don't get this problem with other applications than
sonata.

Cheers,

K.





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

Bug#583120: bug registered on freedesktop bugzilla

[Kjö Hansi Glaz]

 [...]
 
 Please can you put this information in a bug report on
 https://bugs.freedesktop.org, under product 'DRI', component
 'DRM/Radeon'.  Let us know the bug number or URL so we can track it.
 
Done, bug 38554 [1].

[1]. https://bugs.freedesktop.org/show_bug.cgi?id=38554



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

Bug#583120: Test with 2.6.39-2-686-pae

[Kjö Hansi Glaz]

Hi,

I run basically the same tests as intrigeri did with linux-image
2.6.39-2-686-pae (installed in a squeeze system).


single user mode with KMS
=

1) boot in single user mode (see [1] for result of `ps aux`)
2) remove unused modules (see [2] for reslut of `lsmod`)
3) `echo freezer  /sys/power/pm_test` ; `echo disk  /sys/power/state`
   the freeze successes (stuff happens then bash comes back)
4) `echo devices  /sys/power/pm_test` ; `echo disk  /sys/power/state`
   the screen remains black, power and battery LEDs on, kernel doesn't
   answer to sysrq


single user mode without KMS


1) boot in single user mode with `radeon.modeset=0` on kernel command line
   (see [3] for result of `ps aux`)
2) remove unused modules (see [4] for reslut of `lsmod`)
3) `echo freezer  /sys/power/pm_test` ; `echo disk  /sys/power/state`
   the freeze successes
4) `echo devices  /sys/power/pm_test` ; `echo disk  /sys/power/state`
   seems to succeed (stuff happens then bash comes back)


single user mode with KMS, noapic, nolapic
==

Same test with `noapic nolapic` on kernel command line;
Same result as single user mode with KMS


single user mode with KMS, acpi=off
===

Same test with `acpi=off` on kernel command line;
The system doesn't boot, so I can't test


Hope it helps, feel free to ask for more tests,

K.


Notes
=

[1]. Result of ps aux, KMS enabled:

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  1.3  0.0   2080   608 ?Ss   11:20   0:00 init [S]   
  
root 2  0.0  0.0  0 0 ?S11:20   0:00 [kthreadd]
root 3  0.0  0.0  0 0 ?S11:20   0:00 [ksoftirqd/0]
root 4  0.0  0.0  0 0 ?S11:20   0:00 [kworker/0:0]
root 5  0.0  0.0  0 0 ?S11:20   0:00 [kworker/u:0]
root 6  0.0  0.0  0 0 ?S11:20   0:00 [migration/0]
root 7  0.0  0.0  0 0 ?S11:20   0:00 [watchdog/0]
root 8  0.0  0.0  0 0 ?S   11:20   0:00 [cpuset]
root 9  0.0  0.0  0 0 ?S   11:20   0:00 [khelper]
root10  0.0  0.0  0 0 ?S   11:20   0:00 [netns]
root11  0.0  0.0  0 0 ?S11:20   0:00 [sync_supers]
root12  0.0  0.0  0 0 ?S11:20   0:00 [bdi-default]
root13  0.0  0.0  0 0 ?S   11:20   0:00 [kintegrityd]
root14  0.0  0.0  0 0 ?S   11:20   0:00 [kblockd]
root15  0.5  0.0  0 0 ?S11:20   0:00 [kworker/0:1]
root16  0.0  0.0  0 0 ?S11:20   0:00 [khungtaskd]
root17  0.0  0.0  0 0 ?S11:20   0:00 [kswapd0]
root18  0.0  0.0  0 0 ?SN   11:20   0:00 [ksmd]
root19  0.0  0.0  0 0 ?SN   11:20   0:00 [khugepaged]
root20  0.0  0.0  0 0 ?S11:20   0:00 [fsnotify_mark]
root21  0.0  0.0  0 0 ?S   11:20   0:00 [crypto]
root24  0.0  0.0  0 0 ?S11:20   0:00 [kworker/0:2]
root   165  0.0  0.0  0 0 ?S11:20   0:00 [khubd]
root   166  0.0  0.0  0 0 ?S   11:20   0:00 [ata_sff]
root   169  0.0  0.0  0 0 ?S11:20   0:00 [scsi_eh_0]
root   170  0.0  0.0  0 0 ?S11:20   0:00 [scsi_eh_1]
root   172  0.0  0.0  0 0 ?S11:20   0:00 [kworker/u:1]
root   173  0.0  0.0  0 0 ?S11:20   0:00 [kworker/u:2]
root   256  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   257  0.0  0.0  0 0 ?S   11:20   0:00 [kcryptd_io]
root   258  0.0  0.0  0 0 ?S   11:20   0:00 [kcryptd]
root   265  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   270  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   275  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   280  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   285  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   290  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   295  0.0  0.0  0 0 ?S   11:20   0:00 [kdmflush]
root   311  0.0  0.0  0 0 ?S11:20   0:00 [jbd2/dm-1-8]
root   312  0.0  0.0  0 0 ?S   11:20   0:00 
[ext4-dio-unwrit]
root   368  0.1  0.1   2588  1096 ?Ss  11:20   0:00 udevd --daemon
root   514  0.7  0.0  0 0 ?S11:20   0:00 [kworker/0:3]
root   628  0.0  0.0  0 0 ?S   11:20   0:00 [ttm_swap]
root   929  0.0  0.0  0 0 ?S11:20   0:00 [jbd2/dm-3-8]
root   930  0.0  0.0  0 0 ?S   

Bug#617789: seems incompatible with iceweasel 3.6.16-5

[Kjö Hansi Glaz]

Package: iceweasel-vimperator
Severity: normal

I second Sander Marechal's question. Stable version of the package is
currently unusable.




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

Bug#593574: Deprecation warning

[Kjö Hansi Glaz]

Package: python-pypdf
Version: 1.12-3
Severity: normal


This is solved in upstream 1.13, packaging it as proposed in #615961
would solve it.




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

Bug#615961: python-pypdf: Please package new upstream version

[Kjö Hansi Glaz]

Package: python-pypdf
Version: 1.12-3
Severity: wishlist


Upstream released 0.13.

Here is the related changelog:

Version 1.13, 2010-12-04


 - Fixed a typo in code for reading a \b escape character in strings.

 - Improved __repr__ in FloatObject.

 - Fixed a bug in reading octal escape sequences in strings.

 - Added getWidth and getHeight methods to the RectangleObject class.

 - Fixed compatibility warnings with Python 2.4 and 2.5.

 - Added addBlankPage and insertBlankPage methods on PdfFileWriter class.

 - Fixed a bug with circular references in page's object trees (typically
   annotations) that prevented correctly writing out a copy of those pages.

 - New merge page functions allow application of a transformation matrix.

 - To all patch contributors: I did a poor job of keeping this ChangeLog
   up-to-date for this release, so I an missing attributions here for any
   changes you submitted.  Sorry!  I'll do better in the future.

-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (900, 'stable'), (200, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-pypdf depends on:
ii  python  2.6.6-3+squeeze5 interactive high-level object-orie
ii  python-support  1.0.10   automated rebuilding support for P

python-pypdf recommends no packages.

python-pypdf suggests no packages.

-- no debconf information



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

Bug#604156: [lenny-squeeze] bluez-utils blocks conversion to dependency based

[Kjö Hansi Glaz]

Package: upgrade-reports
Severity: normal


I can confirm this bug. It happened on 3 upgrades of desktop systems from lenny
to squeeze.

This bug dosen't breaks anything, but the sysv-rc debconf failed
migration message suggests that the user should fix something and *then*
reconfigure sysv-rc, but there is nothing to correct, which is
confusing. She just has to do 'dpkg-reconfigure sysv-rc' after the
upgrade, but it's unclear. As a result, I expect most desktop system
users won't do it, letting them with the old boot system.



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

Bug#603510: gdm3: reload initscript action doesn't properly reload configuration

[Kjö Hansi Glaz]

On Sun, Nov 21, 2010 at 10:09:55AM +0100, Josselin Mouette wrote:
 Le dimanche 21 novembre 2010 à 01:23 +0100, Kjö Hansi Glaz a écrit : 
   Starting from 5) I can’t reproduce your bug. Only the faulty setting is
   not applied.
   
  I tried again and was able to reproduce it. After `invoke-rc.d gdm
  reload`:
  - the next connexion to gdm the settings was applied OK
  - all the following connections, no settings from
/etc/gdm3/greeter.gconf-defaults was applied
 
 Could you please explain what makes you think that no settings are
 applied? Which settings exactly are not applied?
 
- I see the default background instead of the one I set;
- the user list is displayed despite I disabled it;
- I see the power management icon in GDM

   There shouldn’t be anything different than with invoke-rc.d.
   
  I fixed the problem introduced by the test invoking dpkg-reconfigure and
  it worked again.
 
 The only thing that could cause it is a permission issue. Is your umask
 set to a special value?
 
Yes, 027



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