[Bug 1205384] Re: Lock can be circumvented by switching to console

Can't anybody reproduce this? ** Description changed: Steps to reproduce: - 1)lock your screen + 1)lock your screen using "dm-tool switch-to-greeter" or "dm-tool lock" 2)switch to console via ctrl+alt+F1 3)switch back to X via ctrl+alt+F7 Result: session is unlocked without entering a pas

[Bug 1205384] Re: Lock can be circumvented by switching to console

Your response time is astonishingly quick, thanks for that! I've been calling lxlock (lxsession package) which is essentially just a script file calling dm-tool switch-to-greeter I just verified that calling this directly from a terminal and then following my steps to reproduce leads to the exact

[Bug 1205397] Re: encrypted install fails because unsafe swap is detected

** Summary changed: - encrypted install fails because usafe swap detected + encrypted install fails because unsafe swap is detected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205397 Title: encr

[Bug 1205384] Re: Lock can be circumvented by switching to console

** Summary changed: - Lock can be cirumvented by switching to console + Lock can be circumvented by switching to console ** Description changed: Steps to reproduce: 1)lock your screen 2)switch to console via ctrl+alt+F1 3)switch back to X via ctrl+alt+F7 - Result: session is unlocked wit

[Bug 1205409] Re: open current folder in terminal sets working dir always to home

Things work as expected when the curent directory is opened as root (via "open current folder as root") Note: The above is not a valid workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205409

[Bug 1205409] [NEW] open current folder in terminal sets working dir always to home

Public bug reported: Steps to reproduce: 1)start pcmanfm 2)navigate to an other folder than home 3)click "open current folder in terminal" or press F4 4) lxterminal opens wih home as working directory Expected behaviour: 4) lxterminal opens with the currently displayed directory as working direc

[Bug 1205397] Re: encrypted install fails because usafe swap detected

Workaround: 1) boot via "Try Lubuntu" not "Install Lubuntu" 2) open terminal 3) enter "swapoff --all" press enter 4) start installation This workaround works only if the unsafe swap error has not been raised since the last reboot. If that has been the case even with swapoff --all the installer w

[Bug 1205397] [NEW] encrypted install fails because usafe swap detected

Public bug reported: Steps to reproduce: 1) start installation 2) choose encrypted 3) click install now 4) installation aborts, since an unsafe swap is detected (image in attachment) Expected behaviour: installation starts after clicking install now ProblemType: Bug DistroRelease: Ubuntu 13.10 P

[Bug 1205397] Re: encrypted install fails because usafe swap detected

My humble guess is that the zram swap is mistakenly recognised as a swap on harddisk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205397 Title: encrypted install fails because usafe swap detected

[Bug 1205384] [NEW] Lock can be cirumvented by switching to console

Public bug reported: Steps to reproduce: 1)lock your screen 2)switch to console via ctrl+alt+F1 3)switch back to X via ctrl+alt+F7 Result: session is unlocked without entering a pasword Expected behaviour: session should still be locked when switching back to X ProblemType: Bug DistroRelease: Ub

[Bug 1205377] [NEW] Missing dependency gtk2-engines-murrine

Public bug reported: Version 0.39 needs gtk2-engines-murrine to display scrollbars correctly (screenshot of scrollbars _without_ gtk2-engines-murrine installed is attached) Please add a dependency gtk2-engines-murrine to the lubuntu-artwork package. ProblemType: Bug DistroRelease: Ubuntu 13.10 P

[Bug 1204052] Re: Keybind to lock screen still using removed xscreensaver-command

** Patch added: "rc.xml.patch" https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1204052/+attachment/3746606/+files/rc.xml.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/

[Bug 1204052] Re: Keybind to lock screen still using removed xscreensaver-command

** Patch removed: "patch" https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1204052/+attachment/3746465/+files/rc.xml.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/12040

[Bug 1204052] Re: Keybind to lock screen still using removed xscreensaver-command

patch in attachment ** Patch added: "patch" https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1204052/+attachment/3746465/+files/rc.xml.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launc

[Bug 1204052] Re: Keybind to lock screen still using removed xscreensaver-command

After a little research I was able to fix this myself: lxlock ** Attachment added: "calling lxlock instead of xscreensaver-command" https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1204052/+attachment/3746458/+files/rc.xml -- You receiv

[Bug 1204052] [NEW] Keybind to lock screen still using removed xscreensaver-command

Public bug reported: The keybind to lock the screen (crtl+alt+l) in the openbox default configuration file is still using the obsolete (and removed) xscreensaver-command. File: /usr/share/lubuntu/openbox/rc.xml Relevant part: xscreensaver-command -lock Expected behavior: