[Bug 1653259] Re: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795
Just found a workaround... I have installed ccsm and added the specific window-classes to "Gerneral" -> "Composite" -> "Undirect match" like: "& !(class=google- chrome)" I had a simular problem with Virtual-Box in Full-Screen Mode ... therefor I have added "& class=VirtualBox" as well... now it is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653259 Title: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653259] Re: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795
I have the same situation here with a Ubuntu 16.04 running on a Kaby- Lake CPU. Fullscreen in Google-Chrome or in the editor "Atom" crashes Unity. Cant minimize the fullscreen-window again, cant click anything. Only possible way is rebooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653259 Title: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090379] Re: Keyboard shortcuts does not work when last window is closed because Desktop does not get focus automatically.
Noted, that mentioned solution in #8 reduces the problems but not eliminates it. You can also install the "unity-tweak-tool" and go to "Window/Additionals" and activate "follow Mouse" or "sloppy" for focus. This is another improvement I think because Desktop is automatically "selected" / got focus only if the mouse is on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090379 Title: Keyboard shortcuts does not work when last window is closed because Desktop does not get focus automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1090379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
Just installed an automated update to Kernel 4.4.0-22-generic. Now, the workarround with the "aliases" has also stopped working. Unable to shutdown Ubuntu with mounted CIFS (only after 120 sec. of trying and finnaly failing...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577885 Title: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090379] Re: Keyboard shortcuts does not work when last window is closed because Desktop does not get focus automatically.
Can be confirmed with Ubuntu 16.04 (Unity) as well. But for me it was related to "conky". Seems like that after closing last Window, conky (which is installed and active) get the focus. Problem solved with ccsm (Window-management / Window Rules) added "class=Conky" to field "No Focus". After adding this the problem was solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090379 Title: Keyboard shortcuts does not work when last window is closed because Desktop does not get focus automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1090379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577885] [NEW] 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)
Public bug reported: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the command "umount /media/server ..." I have not tested if this also occurs when I am connected via ethernet. I think it is because the (Wifi)Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: cifs delay nfs shutdown umount ** Description changed: I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 - After login to unity, I mount it with a bash-script (mount -a) + After login to unity, I mount it with a bash-script (mount -a) which is + called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the comman "umount /media/server ..." I have not tested if this also appears when I am connected via ethernet. I think it is because the Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. - Failure can be avaided if I umount the network-drives manually previouse + Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. ** Description changed: - I prepare for mounting with the following entry in /etc/fstab my - Synology NAS : + Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 + with no issue. + + + I prepare for mounting with the following entry in /etc/fstab my Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the process stops at the comman "umount /media/server ..." I have not tested if this also appears when I am connected via ethernet. I think it is because the Network is already disabled prior all umounts are done. This issue happens even if I type in a shutdown command into a Terminal or if I choose shutdown form the menue, also if I use the power-button. Failure can be avoided if I umount the network-drives manually previouse to reboot. Interim solution was, to create an alias for "shutdown" like "sh /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local. ** Description changed: Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04 with no issue. - - I prepare for mounting with the following entry in /etc/fstab my Synology NAS : + I prepare for mounting with the following entry in /etc/fstab my + Synology NAS : //192.168.178.61/data /media/server/server_data cifs users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev 0 After login to unity, I mount it with a bash-script (mount -a) which is called from ~/.config/autostart/myMounts.desktop Doing this, and shuting down or rebooting lead into a very delayed shutdown (round about 2 minutes) Pressing ESC Key, showed that the - process stops at the comman "umount /media/server ..." + process stops at the command "umount /media/server ..." - I have not tested if this also appears when I am connected via ethernet. - I think it is because the Network is already disabled prior all umounts - are done. + I have not tested if this also occurs when I am connected via ethernet. + I think it is because the (Wifi)Network is
[Bug 1512760] Re: Java applications leaks shmem chunks
The same here (using JetBrains) and developing QT applications. Only solution until now is, log off and on again (this solves the issue for 10 -15 minutes, depending on how often I have to start a Qt Application). java -showversion >> java version "1.7.0_85" OpenJDK Runtime Environment (IcedTea 2.6.1) (7u85-2.6.1-5ubuntu0.14.04.1) OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512760 Title: Java applications leaks shmem chunks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1512760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459571] Re: Keyboard shortcuts stop working
Have to correct myself in #4 , no luck with only changing ccsm Settings like mentioned. Interesting Information: I ´ve tried to workarround with xbindkeys... directelly after starting xbindkeys, all definded keys are working correctelly, after a while, sometimes after hibernate the keys stop working again (but xbindkeys is still running), if I kill xbindkeys in this stage and restart it, it is working probably again. Dont know if this Information is usefull or not -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459571 Title: Keyboard shortcuts stop working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1459571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224732] Re: Custom keyboard shortcuts don't work
I´ve got the same problem, tried the solution in #63 with no success. Further in in ccsm I deactivated the gnome contability setting. Since this time I did not have any issue with my custom shortcuts again. (Tried this on two different systems which showed the same problem...) Can anyone verify this ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459571] Re: Keyboard shortcuts stop working
This problem also affects me (but with 14.04). If it happens not only the system shortcuts like Ctrl+Alt+T does not work ... also my custom keybinding which i have definded stopp working until I reboot once or twice. My Workarround so far: Install ccsm, and deactivate the commands and the gnome-compatibility. After that I got no further problems with the key-bindungs. Maybe someone can confirm this or make use of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459571 Title: Keyboard shortcuts stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1459571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036456] Re: [Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!
Additionally to the new CPU which was exchanged (see comment no 23) I exchanged the used HDD with a new Samsung 840 Series SSD Drive. Same Problem. Randomly CPU-Stuck message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036456 Title: [Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036456] Re: BUG: soft lockup - CPU#0 stuck for 22s!
Still same problem also here. I just bought a new CPU and exchanged my original installed CPU (Intel P6200) to Intel i5-460m CPU. Same problem with new CPU. Nearly every resume from suspend to ram failed with CPU stuck for 22s. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036456 Title: BUG: soft lockup - CPU#0 stuck for 22s! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012277] Re: Closing laptop lid should not blank external monitor
found that this behavior is more or less like a screensaver ... When I connect an external mouse or keyboard, connect my Laptop to my TV via HDMI and close the Laptop-lid, the TV is blanking like usual, but after moving my external mouse, the display is coming back immediatelly. No problem then. Can someone confirm this ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012277 Title: Closing laptop lid should not blank external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1012277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012277] Re: Closing laptop lid should not blank external monitor
Same here with Fujitsu AH530 and Samsung TV (connected via HDMI). Confusing point: I also installed XBMC ,which should be shared with twin-view option (xrandr .--same as LVDS1). When I´m using XBMC in full-screen mode, it is working well !! The Samsung TV is blanking for ~2sec. when the laptop-lid is closed but then it starts again and works correctelly. I´m using XBMC only in application form, not in stand alone mode. Maybe this information would be helbful for someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012277 Title: Closing laptop lid should not blank external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1012277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998884] Re: Resume from standby error on Fujitsu Lifebook AH530
Hello, I´m not sure If I´m right here, but I´ve got the same issue. After a few weeks the failure was gone like Steven Beer discribed. However, after the latest kernel update the problem was present again. Can someone confirm this failuremode ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998884 Title: Resume from standby error on Fujitsu Lifebook AH530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
