[Bug 1584449] Re: Can't alt-tab or super+1 to Nautilus
Hmm, yeah, It could maybe be a duplicate of that bug. I have done some testing now, when I start nautilus from the dash or from the icon that's "locked to launcher" I won't find Nautilus (files) in the alt+tab list. But if I start nautilus from the terminal it work's fine... You can see screenshot here, https://dl.dropboxusercontent.com/1/view/loze950apno48h9/Apps/Shutter/Selection_003.jpg (Sorry for the bad quality, another bug, but in Shutter...=)) Well, anyway, If I now "Lock to launcher" on that nautilus icon and start it from the locked one or from the "dash menu", it will start nautilus but I won't be in the alt+tab list. When it works as it should the command is like this, purity@Noiden:~$ ps aux |grep -i naut purity6476 0.5 0.3 1606252 80624 pts/2 Sl+ 11:16 0:03 nautilus When I start it from the "locked to launcher" icon and it's not listed in the alt+tab the command looks like this, purity@Noiden:~$ ps aux |grep -i naut purity6894 16.6 0.3 1540552 74552 ? Sl 11:26 0:00 /usr/bin/nautilus --gapplication-service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584449 Title: Can't alt-tab or super+1 to Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1584449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584449] Re: Can't alt-tab or super+1 to Nautilus
What do you mean by "default launcher configuration"? It's the default file manager in Unity - Ubuntu 16.04. It worked fine in 15.10 but not after upgrading to 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584449 Title: Can't alt-tab or super+1 to Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1584449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584449] [NEW] Can't alt-tab or super+1 to Nautilus
Public bug reported: Nautilus does not show up in the alt+tab "menu" when started, I tried with super+1 to change to nautilus but nothing happens, I can't even click on the icon to get the window back. I must right click on the icon and choose something like "Documents" to get up a nautilus-window again or wait until the icon stops fading in red, which take around 10-30 seconds. Ubuntu 16.04 LTS nautilus: Installed: 1:3.18.4.is.3.14.3-0ubuntu4 Candidate: 1:3.18.4.is.3.14.3-0ubuntu4 Version table: *** 1:3.18.4.is.3.14.3-0ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 22 12:17:39 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'geometry' b"'1257x1000+319+109'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2016-02-01 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2016-05-20 (1 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584449 Title: Can't alt-tab or super+1 to Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1584449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490154] Re: unity-tweak-tool doesn't start on new 15.10 install (Schemas Missing: org.gnome.settings-daemon.peripherals.touchpad)
I have this version, Package: unity-tweak-tool Versions: 0.0.7-0~200~ubuntu15.10.1 (/var/lib/apt/lists/ppa.launchpad.net_freyja-dev_unity-tweak-tool-daily_ubuntu_dists_wily_main_binary-amd64_Packages) and still has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490154 Title: unity-tweak-tool doesn't start on new 15.10 install (Schemas Missing: org.gnome.settings-daemon.peripherals.touchpad) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1490154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157643] Re: procps fail to start
Is there happening anything with this? I got the following errors now when I am trying to upgrade some packages. invoke-rc.d: initscript procps, action start failed. dpkg: error processing procps (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of udev: udev depends on procps; however: Package procps is not configured yet. dpkg: error processing udev (--configure): dependency problems - leaving unconfigured Setting up libssl-doc (1.0.1-4ubuntu5.9) ... Setting up libssl-dev (1.0.1-4ubuntu5.9) ... dpkg: dependency problems prevent configuration of openssh-server: openssh-server depends on procps; however: Package procps is not configured yet. dpkg: error processing openssh-server (--configure): dependency problems - leaving unconfigured Setting up libdrm2 (2.4.43-0ubuntu0.0.1) ... No apport report written because the error message indicates its a followup error from a previous failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157643] [NEW] procps fail to start
*** This bug is a security vulnerability *** Public security bug reported: root@x:~# lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 root@xxx:~# apt-cache policy procps procps: Installed: 1:3.2.8-11ubuntu6 Candidate: 1:3.2.8-11ubuntu6 Version table: *** 1:3.2.8-11ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status I have a VPS that i upgraded from Ubuntu 10.10 to 11.10 and then to 12.04.2 LTS. But something is wrong and now i can't upgrade procps. I get the following output, root@xx:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up procps (1:3.2.8-11ubuntu6) ... start: Job failed to start invoke-rc.d: initscript procps, action start failed. dpkg: error processing procps (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: procps E: Sub-process /usr/bin/dpkg returned an error code (1) the /var/log/upstart/procps.log says, kernel.printk = 4 4 1 7 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 error: permission denied on key 'kernel.kptr_restrict' net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.tcp_syncookies = 1 vm.mmap_min_addr = 65536 And the output when i try to start procps is just the following, root@x:~# service procps start start: Job failed to start ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: failed procps start ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1137345] Re: Fatal error initscripts
** Attachment added: apt.log.2 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1137345/+attachment/3552488/+files/apt.log.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1137345 Title: Fatal error initscripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1137345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1137345] [NEW] Fatal error initscripts
Public bug reported: Setting up initscripts (2.88dsf-13.10ubuntu11.1) ... mkdir: cannot create directory `/dev/shm': File exists dpkg: error processing initscripts (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Processing triggers for libc-bin ... ERROR:root:got an error from dpkg for pkg: 'initscripts': 'subprocess installed post-installation script returned err$ ldconfig deferred processing now taking place Processing triggers for initramfs-tools ... Errors were encountered while processing: initscripts Error in function: ERROR:root:not handled exception: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ERROR:root:SystemError from cache.commit(): installArchives() failed Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/update-manager/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. installArchives() failed ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: apt.log https://bugs.launchpad.net/bugs/1137345/+attachment/3552487/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1137345 Title: Fatal error initscripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1137345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112937] Re: vmware server will not connect remotely
Dominique , both solutions work just as well for me. However I have to say yours is much more elegant. Thank you for the insight. -- vmware server will not connect remotely https://bugs.launchpad.net/bugs/112937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112937] Re: vmware server will not connect remotely
Hi Wilbur, I am no linux expert, I am just the person who originally tried to file the bug but if you follow my instructions in the first post with the modification describe below, I think you may have success. I have only tried it on 32 bit installs but it has worked on all of those and I cannot see why it would not work on a 64 bit install either edit /etc/pam.d/vmware-authd 1. sudo cp /etc/pam.d/vmware-authd /etc/pam.d/vmware-authd.orig this means you have a copy of the original file if you make a mistake. 2. change the file from #%PAM-1.0 auth sufficient /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix2.so shadow nullok auth required /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix_auth.so shadow nullok account sufficient /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix2.so account required /usr/lib/vmware-server/lib/libpam.so.0/security/pam_unix_acct.so To #%PAM-1.0 auth sufficient %pamdir%/pam_unix2.so shadow nullok auth required %pamdir%/pam_unix_auth.so shadow nullok account sufficient %pamdir%/pam_unix2.so account required %pamdir%/pam_unix_acct.so 3. You must do this on the server you want to connect to, not the machine you are connecting from 4.You probably need to do this everytime apt installs a newer version of vmware until it gets fixed because on all the updates I have instaled so far the file gets overwritten. Hope this helps. -- vmware server will not connect remotely https://bugs.launchpad.net/bugs/112937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112937] vmware server will not connect remotely
Public bug reported: this is for the package vmware-server in the commercial repository but this cant be chosen from your list of packages When installing vmware-server there is an error in the file /etc/pam.d /vmware-authd the file is installed as follows: #%PAM-1.0 auth sufficient %pamdir%/pam_unix2.so shadow nullok auth required %pamdir%/pam_unix_auth.so shadow nullok accountsufficient %pamdir%/pam_unix2.so accountrequired %pamdir%/pam_unix_acct.so however the %pamdir%/ should not be in each line and instead it should read: #%PAM-1.0 auth sufficient pam_unix2.so shadow nullok auth required pam_unix_auth.so shadow nullok accountsufficient pam_unix2.so accountrequired pam_unix_acct.so This then allows people to remotely connect through vmware server console. Also when installing on feisty server make is a dependency but is not installed so the install fails until make is installed ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- vmware server will not connect remotely https://bugs.launchpad.net/bugs/112937 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs