[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I see this on systems with LDAP, and systems without. It's just happened on this machine, which is built from scratch about 1 week ago. It's with a new user - so all the user config is as created by a new clean Ubuntu system. I haven't customised PAM at all. I see lots of failures in auth.log, but none of them are specific to this condition. E.g: Feb 14 19:21:25 wilpena pkexec[29914]: david: Executing command [USER=root] [TTY=unknown] [CWD=/hom e/david] [COMMAND=/usr/lib/update-notifier/package-system-locked] Feb 14 19:40:28 wilpena compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Feb 14 19:40:28 wilpena compiz: PAM adding faulty module: pam_kwallet.so Feb 14 19:40:28 wilpena compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlog in" not met by user "david" Feb 14 22:17:17 wilpena dbus[595]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.44" (uid=0 pid=2810 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1637 comm="NetworkManager ") Feb 14 22:17:17 wilpena compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Feb 14 22:17:17 wilpena compiz: PAM adding faulty module: pam_kwallet.so Feb 15 09:12:42 wilpena dbus[595]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.68" (uid=1000 pid=3214 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.1" (uid=0 pid=667 comm="/usr/sbin/bluetoothd ") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342024] Re: Unity exits while screen locked
OK - $ which unity /usr/bin/unity and running 'unity' definitely fixes the problem. This still leaves me with the problem that there are no crash reports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342024 Title: Unity exits while screen locked To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1342024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342024] Re: Unity exits while screen locked
Obviously I wasn't going to put up with this problem for 5 months. I now run metacity. Because it's 5 months ago, I can't actually remember, but I expect it did: $ ps aux | grep unity And got no results. Then I did $ DISPLAY=:0 unity Don't remember about compiz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342024 Title: Unity exits while screen locked To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1342024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192890] Re: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m'
OK - so your python 2 is broken (which is the problem). You have solved your specific issue by pointing a specific command at python 3 instead. That command now works. Your python 2 is still broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192890 Title: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1192890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192890] Re: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m'
An, you say it's python 2, but from the stack trace, it plainly isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192890 Title: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1192890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192890] Re: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m'
This seems to be because I had python3 from a backport installed. It's not obvious why it wasn't upgraded, but it's not going to affect many people. ** Changed in: ubuntu Assignee: (unassigned) => David Ireland (e-david) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192890 Title: update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1192890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192890] [NEW] update-manager fails to upgrade from quantal to raring No module named '_sysconfigdata_m'
Public bug reported:
I ran update manager and chose to upgrade to raring. The packages all
downloaded. On installation, I repeatedly saw something like this in the
console:
File "/usr/lib/python3.3/site.py", line 633, in
main()
File "/usr/lib/python3.3/site.py", line 618, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python3.3/site.py", line 284, in addusersitepackages
user_site = getusersitepackages()
File "/usr/lib/python3.3/site.py", line 260, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python3.3/site.py", line 250, in getuserbase
USER_BASE = get_config_var('userbase')
File "/usr/lib/python3.3/sysconfig.py", line 610, in get_config_var
return get_config_vars().get(name)
File "/usr/lib/python3.3/sysconfig.py", line 560, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/usr/lib/python3.3/sysconfig.py", line 432, in _init_posix
from _sysconfigdata import build_time_vars
File "/usr/lib/python3.3/_sysconfigdata.py", line 6, in
from _sysconfigdata_m import *
ImportError: No module named '_sysconfigdata_m'
Eventually, update-manager silently exited.
Now when I try to start it again from gnome-terminal, I see the above,
and update-manager immediately exits.
In fact, python3.3 doesn't run, with the same error, and
apt-get install python3.3
Results in the same error repeatedly
_sysconfigdata_m.py is in
http://packages.ubuntu.com/raring/amd64/libpython3.3-minimal/filelist
But it wasn't installed, so I installed it by hand using dpkg.
python3.3 still doesn't run, but now I
apt-get install python3.3
without seeing this error, and all the unconfigured packages from the
upgrade get configured.
The reporting guidelines don't seem to apply to upgrade issues, but for
completeness
$ lsb_release -rd
Description:Ubuntu 13.04
Release:13.04
What I expected: I expected update-manager to upgrade my system, or to report
that it had failed
What happened: update-manager exited, without reporting failure, leaving my
system in an unusable state
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192890
Title:
update-manager fails to upgrade from quantal to raring No module named
'_sysconfigdata_m'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1192890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802466] Re: shotwell doesn't work with google's 2-step verification
I mean, there's a link to a ticket above, and that ticket says it's 50% finished. Actually it now says it's 50% finished, as well as saying it's fixed. The good news is if you download the current release from Yorba, it installs easily, and two factor auth does work for Picasaweb. That is what I wanted, so thanks for the clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802466 Title: shotwell doesn't work with google's 2-step verification To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/802466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802466] Re: shotwell doesn't work with google's 2-step verification
Adding a save password feature for use with application passwords is not 'hacky'. compromising on the security of my Google accounts by disabling two factor authentication is not advice I'm going to take. All the big account providers are offering two factor authentication, so this suggestion borders on absurd. It's now been nearly two years since the this was reported and the proposed solution is '50%' finished. The proposed solution will offer little additional benefit over saving the password as far as I am concerned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802466 Title: shotwell doesn't work with google's 2-step verification To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/802466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823170] [NEW] Same as bug #362359
Public bug reported: Bug #362359 is reported as fixed, however I have seen the same symptoms on lucid, maverick and now natty. running Natty in classic mode with compiz on. HP pavilion dv6000 series. Focus gets locked to a window after indeterminate time, usually during any activity requiring keyboard as well as mouse input. Only fix seems to be reboot. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823170 Title: Same as bug #362359 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/823170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726496] Re: Cannot use Unity or Classic desktop with effects after the latest nvidia+xorg update
Affects me too. Nvidia 7400 on HP Pavilion laptop. Enabling 173 driver appears to work so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726496 Title: Cannot use Unity or Classic desktop with effects after the latest nvidia+xorg update -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571534] Re: Lucid - Mouse stops working after shortly after login
Same bug affects me. Hp Pavilion DV6000 Logitech USB optical mouse. No such problem until Lucid install -- Lucid - Mouse stops working after shortly after login https://bugs.launchpad.net/bugs/571534 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279086] [NEW] unable to mount camera
Public bug reported: Camera is Panasonic fz28 kern log is as follows Oct 6 14:58:13 davidi-laptop kernel: [18662.832040] usb 1-1: USB disconnect, address 5 Oct 6 14:58:25 davidi-laptop kernel: [18674.724156] usb 1-1: new high speed USB device using ehci_hcd and address 6 Oct 6 14:58:25 davidi-laptop kernel: [18674.859437] usb 1-1: configuration #1 chosen from 1 choice Oct 6 14:58:25 davidi-laptop kernel: [18674.864698] scsi8 : SCSI emulation for USB Mass Storage devices Oct 6 14:58:25 davidi-laptop kernel: [18674.869496] usb-storage: device found at 6 Oct 6 14:58:25 davidi-laptop kernel: [18674.869507] usb-storage: waiting for device to settle before scanning Then popup Unable to mount Panasonic (Matsushita) Lumix DMC-FZ10 Camera Error initialising camera: -1: Unspecified error Using Interpid Ibex on HP Pavilion laptop. No such problem until upgraded from Hardy ** Affects: ubuntu Importance: Undecided Status: New -- unable to mount camera https://bugs.launchpad.net/bugs/279086 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
