** Changed in: lightdm (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1314643
Title:
Logout from xubuntu session causes blank
You should now be using TOR Browser and not vidalia/tor. This bug
report is invalid and no longer maintained. Maintainer please close Bug
Report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Thanks for your help... for now I just disabled session locking. I will
await the Mint team's responce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1610619
Title:
Some ideas for the guest session:
gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
or
gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend 'false'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
After the reinstall xscreensaver is still locking by default. I can disable
this feature in Settings and it is now fine (Because it does not lock).
However, I wanted this locking feature, it is still a bug in that enabling this
locking feature still locks the screen for the guest account,
...Now I am not so sure, the system i am using still has this problem: It is
MintXFCE.
I will purge and reinstall and see if it is a config problem somewhere.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
Public bug reported:
Steps to reproduce bug:
1) Install xubuntu or mint xfce
2) download and set lightdm as desktop manager
3) sign in to a guest session and either close your laptop lid or allow
timeout to start screen lock
Why this is a bug:
xscreensaver will not accept a blank/null
Same for me. Mint updates are fine, it is the ubuntu packages which are
givingng me problems. Packages.linuxmint.com is set for my mint
packages (rafaela), and is not giving me problems, but
archive.ubuntu.com/ubuntu is set for my ubuntu packages (trusty) Here
is the error I am getting:
Failed
Never mind, clicking on those links produces a 404 error, it seems these
packages have been pulled from the PPA, and my system is still looking
for it. Any reason why these packages would be pulled from any server
during an LTS cycle?
--
You received this bug notification because you are a
Public bug reported:
Mirrored displays is not accessible (grayed out) when trying to activate
this feature for multi-monitor support. I am not sure which specific
package to nominate for this bug, but it seems to only be happening on
systems with XFCE4 installed and running (Including Xubuntu,
Public bug reported:
This Bug does not affect the Window Title or Menus from successfully
appearing, but they overlay the File Edit View Bookmarks Help in a
visible manner, making it difficult to use (especially for High
Contrast). I have returned Unity and Compiz back to default settings
and
** Description changed:
This Bug does not affect the Window Title or Menus from successfully
appearing, but they overlay the File Edit View Bookmarks Help in a
visible manner, making it difficult to use (especially for High
Contrast). I have returned Unity and Compiz back to default
Can systemd be safely uninstalled in the mean time for users not yet
testing this function?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is
It was suggested to me that I could use the following workaround to start up
programs affected by this bug by using the following command:
:~#sudo service [PackageName] start
I tested this on an affect program Haguichi and it worked.
--
You received this bug notification because you are a
Also effects Haguichi, and presumably any package that calls on /bin/systemctl.
see my Bug report here: https://answers.launchpad.net/haguichi/+question/258759
This happened only after upgrade to 14.10. Martin Pitt, care to write a
quick tutorial on how to change the correct boot settings to
Here are some conflicting results:
Output from:
:~$ initctl --systemlist
initctl: invalid option: --systemlist
Try `initctl --help' for more information.
brandon@RomeoMontague:~$ initctl --system list
avahi-daemon start/running, process 897
mountnfs-bootclean.sh start/running
rsyslog
Also, systemd is not maintained in launchpad, but in bugzilla. If this
is an error in systemd and it is required for 'some reason', then they
may have to be notified their as well? I dont know if upstart is the
real problem here, and the package being reported for this bug might
need to be
Affects multiple users.
** Changed in: systemd (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Title:
systemctl is
Also, there is no package libdbus or dbus-daemon. So even if systemd
was the intent, how would it ever communicate?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387241
Running latest stable today, I can still confirm this bug, if this is a
problem with gvfs, the importance should be elevated and the maintainer
for that package notified, since that could be a critical issue. I dont
know myself, I need someone far more experienced to take a look at this
bug.
--
20 matches
Mail list logo
