[Desktop-packages] [Bug 1341708] Re: wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33

2014-07-19 Thread Tuomas Suutari
*** This bug is a duplicate of bug 1323089 ***
https://bugs.launchpad.net/bugs/1323089

** This bug has been marked a duplicate of bug 1323089
   wpa_supplicant writes to syslog every 2 minutes

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1341708

Title:
  wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33

Status in “wpa” package in Ubuntu:
  New

Bug description:
  Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: 
CTRL-EVENT-SCAN-STARTED 
  Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: 
send_and_recv-nl_recvmsgs failed: -33

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4
  Uname: Linux 3.16.0-3-lowlatency x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 14 15:00:14 2014
  InstallationDate: Installed on 2014-04-27 (78 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1224764] Re: scanimage crashed with SIGSEGV in memchr()

2014-05-06 Thread Tuomas Suutari
Same here. Kubuntu 13.10

Here's a backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to LWP 22748]
memchr () at ../sysdeps/x86_64/memchr.S:39
39  ../sysdeps/x86_64/memchr.S: No such file or directory.
(gdb) bt
#0  memchr () at ../sysdeps/x86_64/memchr.S:39
#1  0x7787a267 in __GI__IO_getline_info (fp=fp@entry=0x7fffe4001370, 
buf=buf@entry=0x7fffeb3898f0 kazaa, n=n@entry=2047, delim=delim@entry=10, 
extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
#2  0x7787a398 in __GI__IO_getline (fp=fp@entry=0x7fffe4001370, 
buf=buf@entry=0x7fffeb3898f0 kazaa, n=n@entry=2047, delim=delim@entry=10, 
extract_delim=extract_delim@entry=1) at iogetline.c:38
#3  0x7787ecbc in __GI_fgets_unlocked (buf=buf@entry=0x7fffeb3898f0 
kazaa, n=n@entry=2048, fp=0x7fffe4001370) at iofgets_u.c:55
#4  0x7fffea98265d in internal_getent (result=result@entry=0x7fffeb38a530, 
buffer=buffer@entry=0x7fffeb3898f0 kazaa, buflen=buflen@entry=2048, 
errnop=errnop@entry=0x7fffeb38b680) at nss_files/files-XXX.c:207
#5  0x7fffea982a44 in _nss_files_getservbyname_r (name=0x7fffeb9f8812 
sane-port, proto=0x7798a03e gaih_inet_typeproto+30 tcp, 
result=0x7fffeb38a530, buffer=0x7fffeb3898f0 kazaa, buflen=2048, 
errnop=0x7fffeb38b680) at nss_files/files-service.c:41
#6  0x77920bc2 in __getservbyname_r (name=name@entry=0x7fffeb9f8812 
sane-port, proto=proto@entry=0x7798a03e gaih_inet_typeproto+30 tcp, 
resbuf=resbuf@entry=0x7fffeb38a530, buffer=buffer@entry=0x7fffeb3898f0 kazaa, 
buflen=buflen@entry=2048,
result=result@entry=0x7fffeb38a520) at ../nss/getXXbyYY_r.c:266
#7  0x778d62cb in gaih_inet_serv (servicename=0x7fffeb9f8812 
sane-port, tp=tp@entry=0x7798a034 gaih_inet_typeproto+20, 
st=st@entry=0x7fffeb38a5b0, req=optimised out) at 
../sysdeps/posix/getaddrinfo.c:164
#8  0x778d6633 in gaih_inet (name=name@entry=0x7fffe4001138 
kuutio.local, service=0x7fffeb38a7f0, req=req@entry=0x7fffeb38a950, 
pai=pai@entry=0x7fffeb38a7b0, naddrs=naddrs@entry=0x7fffeb38a790) at 
../sysdeps/posix/getaddrinfo.c:341
#9  0x778da914 in __GI_getaddrinfo (name=0x7fffe4001138 kuutio.local, 
service=optimised out, hints=0x7fffeb38a950, pai=0x7fffeb38a948) at 
../sysdeps/posix/getaddrinfo.c:2473
#10 0x7fffeb9f4c3c in ?? () from 
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1
#11 0x7fffeb9f4f48 in ?? () from 
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1
#12 0x7fffeb5da5db in avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#13 0x7fffeb5d5ecc in ?? () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#14 0x7fffeb39a9e6 in dbus_connection_dispatch () from 
/lib/x86_64-linux-gnu/libdbus-1.so.3
#15 0x7fffeb5dc606 in ?? () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
#16 0x7fffeb7e9668 in avahi_simple_poll_dispatch () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#17 0x7fffeb7e994d in avahi_simple_poll_loop () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#18 0x7fffeb7e9a14 in ?? () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
#19 0x76ab1f6e in start_thread (arg=0x7fffeb38b700) at 
pthread_create.c:311
#20 0x779049cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Sane versions at the client:

tuomas@epsilon:~ $ dpkg -l | grep sane
ii  libksane-data 4:4.11.2-0ubuntu1 
 all  scanner library (data files)
ii  libksane0 4:4.11.2-0ubuntu1 
 amd64scanner library (runtime)
ii  libsane:amd64 1.0.23-0ubuntu3   
 amd64API library for scanners
ii  libsane-common1.0.23-0ubuntu3   
 amd64API library for scanners -- documentation and support 
files
ii  libsane-dev   1.0.23-0ubuntu3   
 amd64API development library for scanners [development files]
ii  libsane-hpaio 3.13.9-1ubuntu0.1 
 amd64HP SANE backend for multi-function peripherals
ii  sane-utils1.0.23-0ubuntu3   
 amd64API library for scanners -- utilities
ii  xsane 0.998-5ubuntu1
 amd64featureful graphical frontend for SANE (Scanner Access 
Now Easy)
ii  xsane-common  0.998-5ubuntu1
 all  featureful graphical frontend for SANE (Scanner Access 
Now Easy)

The Sane server is Debian Wheeze 7.5 with sane 1.0.22-7.4 and libsane-
hpaio 3.12.6-3.1+deb7u1.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1224764


[Desktop-packages] [Bug 1224764] Re: scanimage crashed with SIGSEGV in memchr()

2014-05-06 Thread Tuomas Suutari
If I stop avahi daemon at the Sane server, the segfault goes away.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1224764

Title:
  scanimage crashed with SIGSEGV in memchr()

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  clearly still  unstable

  chad@chad-VirtualBox:~$ scanimage -L
  device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
  device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' 
is a Hewlett-Packard Deskjet_F4400_series all-in-one
  chad@chad-VirtualBox:~$ scanimage -L
  device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
  device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5' 
is a Hewlett-Packard Deskjet_F4400_series all-in-one
  chad@chad-VirtualBox:~$ scanimage -f 
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
  Segmentation fault (core dumped)
  chad@chad-VirtualBox:~$ scanimage -f 
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
  
{ID:0,INUSE:0,DEVICE:net:10.0.0.50:plustek:libusb:004:002,NAME:UMAX 
3400 flatbed 
scanner},{ID:1,INUSE:0,DEVICE:net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5,NAME:Hewlett-Packard
 Deskjet_F4400_series all-in-one},chad@chad-VirtualBox:~$ ^C
  chad@chad-VirtualBox:~$ scanimage -f 
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
  Segmentation fault (core dumped)
  chad@chad-VirtualBox:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: sane-utils 1.0.23-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 12 22:56:32 2013
  ExecutablePath: /usr/bin/scanimage
  InstallationDate: Installed on 2013-07-27 (47 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130727)
  MarkForUpload: True
  ProcCmdline: scanimage -f {ID:%i,INUSE:0,DEVICE:%d,NAME:%v\ %m\ 
%t},
  SegvAnalysis:
   Segfault happened at: 0x7f462dca8e20 memchr+192:   movdqa (%rdi),%xmm0
   PC (0x7f462dca8e20) ok
   source (%rdi) (0x7f462e40a000) not located in a known VMA region (needed 
readable region)!
   destination %xmm0 ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   memchr () at ../sysdeps/x86_64/memchr.S:88
   __GI__IO_getline_info (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 
z3950, n=n@entry=1023, delim=delim@entry=10, 
extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
   __GI__IO_getline (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100 
z3950, n=n@entry=1023, delim=delim@entry=10, 
extract_delim=extract_delim@entry=1) at iogetline.c:38
   __GI_fgets_unlocked (buf=buf@entry=0x7f462179d100 z3950, n=n@entry=1024, 
fp=0x688950) at iofgets_u.c:55
   internal_getent (result=result@entry=0x7f462179d530, 
buffer=buffer@entry=0x7f462179d100 z3950, buflen=buflen@entry=1024, 
errnop=errnop@entry=0x7f462179e680) at nss_files/files-XXX.c:207
  Title: scanimage crashed with SIGSEGV in memchr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1224764/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1208091] Re: scanimage assert failure: *** Error in `scanimage': double free or corruption (top): 0x0000000002598130 ***

2014-05-06 Thread Tuomas Suutari
Is this possibly a duplicate of #1224764 ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1208091

Title:
  scanimage assert failure: *** Error in `scanimage': double free or
  corruption (top): 0x02598130 ***

Status in “sane-backends” package in Ubuntu:
  Confirmed
Status in “sane-backends” package in Debian:
  Incomplete

Bug description:
  Similar errors occur when the normal user runs this command
  Accessing sacnner using network, setup notes are here
  http://ubuntuforums.org/showthread.php?t=1519201
  My other virtualbox client has no issue here
  the server is running xubuntu 13.04
  This output is from the saucy client

  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f 
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
  
{ID:0,INUSE:0,DEVICE:net:10.0.0.50:plustek:libusb:003:002,NAME:UMAX 
3400 flatbed 
scanner},{ID:1,INUSE:0,DEVICE:net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5,NAME:Hewlett-Packard
 Deskjet_F4400_series all-in-one},
  www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d 
'net:10.0.0.50:plustek:libusb:003:002'
  *** Error in `scanimage': double free or corruption (top): 0x02598130 
***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x80996)[0x7f4379829996]
  /lib/x86_64-linux-gnu/libc.so.6(fclose+0x14d)[0x7f43798179bd]
  
/lib/x86_64-linux-gnu/libnss_files.so.2(_nss_files_getservbyname_r+0x11b)[0x7f4373df7adb]
  /lib/x86_64-linux-gnu/libc.so.6(getservbyname_r+0xd2)[0x7f43798bf022]
  /lib/x86_64-linux-gnu/libc.so.6(+0xcb72b)[0x7f437987472b]
  /lib/x86_64-linux-gnu/libc.so.6(+0xcba93)[0x7f4379874a93]
  /lib/x86_64-linux-gnu/libc.so.6(getaddrinfo+0xf4)[0x7f4379878d74]
  /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(+0x6c3c)[0x7f437939cc3c]
  
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(sane_net_init+0x428)[0x7f437939d438]
  /usr/lib/x86_64-linux-gnu/libsane.so.1(+0x3b00)[0x7f4379b73b00]
  /usr/lib/x86_64-linux-gnu/libsane.so.1(sane_dll_open+0xe2)[0x7f4379b74842]
  scanimage[0x401fa8]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f43797cade5]
  scanimage[0x403924]
  === Memory map: 
  0040-0040a000 r-xp  08:01 1355   
/usr/bin/scanimage
  0060a000-0060b000 r--p a000 08:01 1355   
/usr/bin/scanimage
  0060b000-0060c000 rw-p b000 08:01 1355   
/usr/bin/scanimage
  0258d000-025ae000 rw-p  00:00 0  
[heap]
  7f4373bdd000-7f4373bf2000 r-xp  08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373bf2000-7f4373df1000 ---p 00015000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df1000-7f4373df2000 r--p 00014000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df2000-7f4373df3000 rw-p 00015000 08:01 1604   
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7f4373df3000-7f4373dff000 r-xp  08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373dff000-7f4373ffe000 ---p c000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373ffe000-7f4373fff000 r--p b000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f4373fff000-7f437400 rw-p c000 08:01 1621   
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  7f437400-7f4374021000 rw-p  00:00 0 
  7f4374021000-7f437800 ---p  00:00 0 
  7f437810e000-7f437810f000 ---p  00:00 0 
  7f437810f000-7f437890f000 rw-p  00:00 0  
[stack:17829]
  7f437890f000-7f4378916000 r-xp  08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378916000-7f4378b15000 ---p 7000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b15000-7f4378b16000 r--p 6000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b16000-7f4378b17000 rw-p 7000 08:01 1615   
/lib/x86_64-linux-gnu/librt-2.17.so
  7f4378b17000-7f4378b5b000 r-xp  08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378b5b000-7f4378d5a000 ---p 00044000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5a000-7f4378d5b000 r--p 00043000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5b000-7f4378d5c000 rw-p 00044000 08:01 5920   
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
  7f4378d5c000-7f4378d73000 r-xp  08:01 1617   
/lib/x86_64-linux-gnu/libpthread-2.17.so
  7f4378d73000-7f4378f73000 ---p 00017000 08:01 1617   
/lib/x86_64-linux-gnu/libpthread-2.17.so
  

[Desktop-packages] [Bug 896638] Re: Screen lock does not grab all keys

2012-05-03 Thread Tuomas Suutari
With Precise it seems that also Alt key-press events are going through
the screen lock, i.e. the HUD opens, if Alt is pressed while screen is
locked.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/896638

Title:
  Screen lock does not grab all keys

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  When screen is locked with gnome screensaver, it is still possible to
  send Win-key event to the underlaying desktop. I think there should be
  no way to interact with the underlaying desktop without unlocking.

  To reproduce:
   1. Start from Unity session. Make sure that Dash is not open.
   2. Lock screen from the top-right gear button
   3. Press shift to make the unlock dialog appear
   4. Press Windows key
   5. Type in your password and unlock the screen

  What should happen:
  The desktop should be in the same state it was left before the locking. Dash 
should not be open.

  What happens:
  Dash has been opened, i.e. the Windows key event was passed to desktop 
although it was locked.

  Wonder if it is possible to pass through any other key events. Didn't
  find any though with a quick test.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Nov 26 19:01:25 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LC_TIME=en_DK.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 896638] [NEW] Screen lock does not grab all keys

2011-11-26 Thread Tuomas Suutari
Public bug reported:

When screen is locked with gnome screensaver, it is still possible to
send Win-key event to the underlaying desktop. I think there should be
no way to interact with the underlaying desktop without unlocking.

To reproduce:
 1. Start from Unity session. Make sure that Dash is not open.
 2. Lock screen from the top-right gear button
 3. Press shift to make the unlock dialog appear
 4. Press Windows key
 5. Type in your password and unlock the screen

What should happen:
The desktop should be in the same state it was left before the locking. Dash 
should not be open.

What happens:
Dash has been opened, i.e. the Windows key event was passed to desktop although 
it was locked.

Wonder if it is possible to pass through any other key events. Didn't
find any though with a quick test.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Nov 26 19:01:25 2011
EcryptfsInUse: Yes
ProcEnviron:
 LC_TIME=en_DK.UTF-8
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 oneiric running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/896638

Title:
  Screen lock does not grab all keys

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  When screen is locked with gnome screensaver, it is still possible to
  send Win-key event to the underlaying desktop. I think there should be
  no way to interact with the underlaying desktop without unlocking.

  To reproduce:
   1. Start from Unity session. Make sure that Dash is not open.
   2. Lock screen from the top-right gear button
   3. Press shift to make the unlock dialog appear
   4. Press Windows key
   5. Type in your password and unlock the screen

  What should happen:
  The desktop should be in the same state it was left before the locking. Dash 
should not be open.

  What happens:
  Dash has been opened, i.e. the Windows key event was passed to desktop 
although it was locked.

  Wonder if it is possible to pass through any other key events. Didn't
  find any though with a quick test.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Nov 26 19:01:25 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LC_TIME=en_DK.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 896638] Re: Screen lock does not grab all keys

2011-11-26 Thread Tuomas Suutari
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/896638

Title:
  Screen lock does not grab all keys

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  When screen is locked with gnome screensaver, it is still possible to
  send Win-key event to the underlaying desktop. I think there should be
  no way to interact with the underlaying desktop without unlocking.

  To reproduce:
   1. Start from Unity session. Make sure that Dash is not open.
   2. Lock screen from the top-right gear button
   3. Press shift to make the unlock dialog appear
   4. Press Windows key
   5. Type in your password and unlock the screen

  What should happen:
  The desktop should be in the same state it was left before the locking. Dash 
should not be open.

  What happens:
  Dash has been opened, i.e. the Windows key event was passed to desktop 
although it was locked.

  Wonder if it is possible to pass through any other key events. Didn't
  find any though with a quick test.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Nov 26 19:01:25 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LC_TIME=en_DK.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp