[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Please bring this functionality to Ubuntu's Nautilus. Disco now has the distressing search functionality extended even to the save dialog. The Gnome team is extremely resistant to bring back the old intuitive functionality. I tried to explain the problems at https://gitlab.gnome.org/GNOME/nautilus/issues/244 , as did many others. People are still requesting the old type-ahead thing, so the trade-offs have not been accounted for. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #244 https://gitlab.gnome.org/GNOME/nautilus/issues/244 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Lubomir, thank you for doing this! Chris Billington's suggestion about being able to restore this behavior to the official Nautilus is a great one. I'd love to see official support for this feature... actually, I think it is crucial to have this option available for the users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
Still affects me. I have symlinked Deja Dup cache deja-dup -> /media/username/Space/.deja-dup-cache -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1217959 Title: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup" Status in Déjà Dup: Incomplete Status in duplicity package in Ubuntu: Incomplete Bug description: Linux release: Ubuntu 13.04 64bit Kernel: 3.8.0-29-generic Python: 2.7.4 Deja Dup: 26.0 Duplicity: 0.6.21 Hi. I've tried to do my monthly or so backup recently, but Deja Dup crashed after trying to backup a very large file (VM disk with Windows 7, 50GB or so). I tried to do another one, this time excluding all my large VM's. However, now when trying to do a backup I'm getting the following error a few seconds after inputting my encryption password: Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found in backup I've tried reinstalling both deja-dup and duplicity, purging duplicity, deleting deja-dup and duplicity from /home/tom/.cache, deleting the backup files on the external drive, deleting it's config as described here http://askubuntu.com/questions/53980/how-to-delete- all-the-settings-for-deja-dup. I know (well, I have some evidence supporting this) that the drive itself isn't faulty as I managed to backup my old laptop to the drive using duplicity and it worked fine (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs momentarily. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710931] Re: Ctrl+N shortcut does not work when desktop has focus
Affects me, thanks for upstreaming it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1710931 Title: Ctrl+N shortcut does not work when desktop has focus Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: When a Nautilus window is open, Ctrl+N opens a new window that shows the same folder as the focused Nautilus window. However, when the desktop is focused, the shortcut doesn't work - instead I see an error that x-nautilus-desktop:// is not supported. This functionality was previously reported as working in #307229. This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today) with GNOME Files 3.24.2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1710931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)
This is an essential feature that needs to be brought back. I have the same problems as Dmitriy and drunckoder. Everything worked nicely in 17.04 after disabling recursive search. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Drop interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1665501] Re: file transfer in nautilus slows grossly over a couple of minutes
During file transfer kswapd0 starts using CPU a lot. This happens on 4.8 kernel but not on 4.4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1665501 Title: file transfer in nautilus slows grossly over a couple of minutes Status in nautilus package in Ubuntu: Confirmed Bug description: I have found that kswapd0 is running at 100%. If i run ' echo 3 > /proc/sys/vm/drop_caches' the transfer of data improves but not to initial levels. If that is not done more than a few times the system eventually grinds to a halt and reboot is required. The file transfer is usually between external usb drives. Beginning of xfer speeds are usually 17 - 20 mbit but will slow to less than 1mbit. This hasn't previously been a problem but i have tried rebooting with 3 or 4 older kernels and same problem exists. Older kernels wont start for some reason ! That timing coincides with a new graphics board i installed. Not relevant to the issue but may explain earlier than .30 kernels not allowing me to login ! As it is the system is unusable for any major file transfers. I have been patching all relevant patches on to my system which is running 16.10 root@GrahamsPC:~# apt-cache policy nautilus nautilus: Installed: 1:3.20.3-1ubuntu3.1 Candidate: 1:3.20.3-1ubuntu3.1 Version table: *** 1:3.20.3-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.20.3-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 Date: Fri Feb 17 11:46:41 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+224+414'" InstallationDate: Installed on 2016-07-12 (219 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-14 (125 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669344] Re: Received signal 4 ILL_ILLOPN
Joachim Haga seems to be correct. I ran earlier 4.4 kernel (for unrelated stability problems) but now that I try with 4.8, newest Chromium works. $ uname -a Linux ovidius 4.8.0-41-generic #44-Ubuntu SMP Fri Mar 3 15:26:20 UTC 2017 i686 i686 i686 GNU/Linux $ chromium-browser --version Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Chromium 56.0.2924.76 Built on Ubuntu , running on Ubuntu 16.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1669344 Title: Received signal 4 ILL_ILLOPN Status in chromium-browser package in Ubuntu: Confirmed Bug description: This morning chromium-browser upgraded to 56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me. When trying to load any page, it dumps this traceback: Received signal 4 ILL_ILLOPN 7f78b7a509e7 #0 0x7f78d509500e base::debug::StackTrace::StackTrace() #1 0x7f78d5095403 #2 0x7f78d53aa630 #3 0x7f78b7a509e7 WTF::decommitSystemPages() #4 0x7f78c3f997b0 #5 0x7f78c3f99f17 #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage() #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate() #8 0x7f78c3987678 blink::ChromeClientImpl::create() #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl() #10 0x7f78c3a2aeb3 blink::WebViewImpl::create() #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize() #12 0x7f78cfcd9443 content::RenderViewImpl::Create() #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept() #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage() #15 0x7f78d0d17bd0 #16 0x7f78d0d18034 #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #18 0x7f78c3f35f4f blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork() #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #21 0x7f78d50bc740 base::MessageLoop::RunTask() #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask() #23 0x7f78d50bf19d base::MessageLoop::DoWork() #24 0x7f78d50bf589 base::MessagePumpDefault::Run() #25 0x7f78d50bbb22 base::MessageLoop::RunHandler() #26 0x7f78d50e44b8 base::RunLoop::Run() #27 0x7f78cfcf5629 #28 0x7f78cfde7048 #29 0x7f78cfde7444 #30 0x7f78cfde68c1 content::ContentMain() #31 0x55b0046e086c #32 0x7f78bfec03f1 __libc_start_main #33 0x55b0046e073a r8: r9: r10: 0022 r11: 0206 r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: di: 3fb7e8201000 si: 0001e000 bp: 16113981c210 bx: 16113981c218 dx: 0008 ax: cx: ff68 sp: 7fffa09e5f30 ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: trp: 0006 msk: cr2: [end of stack trace] Being chromium, the overall processes don't die or coredump, so apport never sends any reports here. That is why I am filing via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: enabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAw5DcEAAAXAQSVHBB4Ar8FmllVjiYdUFQBAQEBAQEBAQEBAQEBAQEBFjaAunA4D0AwIDUAFJwQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdGMi1TUEIyAN0= dpms: On modes: 1920x1080 enabled: enabled status: connected Date: Thu Mar 2 10:18:41 2017 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-05-29 (1007 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6072 bytes, mtime: Sat Sep 10 19:28:55 2016) Load-Avg-1min: 0.95 Load-Processes-Running-Percent: 0.2% MachineType: LENOVO 20ALCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-ge
[Desktop-packages] [Bug 1669344] Re: Received signal 4 ILL_ILLOPN
Isn't this almost a security risk since people will be using older versions that work? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1669344 Title: Received signal 4 ILL_ILLOPN Status in chromium-browser package in Ubuntu: Confirmed Bug description: This morning chromium-browser upgraded to 56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me. When trying to load any page, it dumps this traceback: Received signal 4 ILL_ILLOPN 7f78b7a509e7 #0 0x7f78d509500e base::debug::StackTrace::StackTrace() #1 0x7f78d5095403 #2 0x7f78d53aa630 #3 0x7f78b7a509e7 WTF::decommitSystemPages() #4 0x7f78c3f997b0 #5 0x7f78c3f99f17 #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage() #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate() #8 0x7f78c3987678 blink::ChromeClientImpl::create() #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl() #10 0x7f78c3a2aeb3 blink::WebViewImpl::create() #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize() #12 0x7f78cfcd9443 content::RenderViewImpl::Create() #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept() #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage() #15 0x7f78d0d17bd0 #16 0x7f78d0d18034 #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #18 0x7f78c3f35f4f blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork() #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #21 0x7f78d50bc740 base::MessageLoop::RunTask() #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask() #23 0x7f78d50bf19d base::MessageLoop::DoWork() #24 0x7f78d50bf589 base::MessagePumpDefault::Run() #25 0x7f78d50bbb22 base::MessageLoop::RunHandler() #26 0x7f78d50e44b8 base::RunLoop::Run() #27 0x7f78cfcf5629 #28 0x7f78cfde7048 #29 0x7f78cfde7444 #30 0x7f78cfde68c1 content::ContentMain() #31 0x55b0046e086c #32 0x7f78bfec03f1 __libc_start_main #33 0x55b0046e073a r8: r9: r10: 0022 r11: 0206 r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: di: 3fb7e8201000 si: 0001e000 bp: 16113981c210 bx: 16113981c218 dx: 0008 ax: cx: ff68 sp: 7fffa09e5f30 ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: trp: 0006 msk: cr2: [end of stack trace] Being chromium, the overall processes don't die or coredump, so apport never sends any reports here. That is why I am filing via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: enabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAw5DcEAAAXAQSVHBB4Ar8FmllVjiYdUFQBAQEBAQEBAQEBAQEBAQEBFjaAunA4D0AwIDUAFJwQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdGMi1TUEIyAN0= dpms: On modes: 1920x1080 enabled: enabled status: connected Date: Thu Mar 2 10:18:41 2017 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-05-29 (1007 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) InstalledPlugins: /usr/lib/mozilla/plugins: => librhythmbox-itms-detection-plugin.so (size: 6072 bytes, mtime: Sat Sep 10 19:28:55 2016) Load-Avg-1min: 0.95 Load-Processes-Running-Percent: 0.2% MachineType: LENOVO 20ALCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to yakkety on 2016-10-01 (152 days ago) dmi.bios.date: 08/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET76WW (2.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.
[Desktop-packages] [Bug 1669344] Re: Received signal 4 ILL_ILLOPN
After the latest update getting stack traces and "aw snap" pages after every time a tab accesses anything, even Chromium settings page. Received signal 4 ILL_ILLOPN af84a7f4 #0 0xb75a0e04 base::debug::StackTrace::StackTrace() #1 0xb75a12d7 #2 0xb7707c20 ([vdso]+0xc1f) #3 0xaf84a7f4 WTF::decommitSystemPages() #4 0xb1b2e1e5 #5 0xb1b2ed9f #6 0xb1b29bdb blink::NormalPageArena::allocatePage() #7 0xb1b2a792 blink::NormalPageArena::outOfLineAllocate() #8 0xb16df5e7 blink::ChromeClientImpl::create() #9 0xb1797fa1 blink::WebViewImpl::WebViewImpl() #10 0xb1799c5d blink::WebViewImpl::create() #11 0xb1799cd3 blink::WebView::create() #12 0xb53bc1f8 content::RenderViewImpl::Initialize() #13 0xb53bd198 content::RenderViewImpl::Create() #14 0xb53a5a92 content::RenderThreadImpl::CreateView() #15 0xb4bedf66 content::mojom::RendererStubDispatch::Accept() #16 0xb53a6123 #17 0xb74e4299 mojo::InterfaceEndpointClient::HandleValidatedMessage() #18 0xb74e4326 mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept() #19 0xb74e23fb mojo::FilterChain::Accept() #20 0xb74e4026 mojo::InterfaceEndpointClient::HandleIncomingMessage() #21 0xb60492f4 #22 0xb60445af #23 0xb75a2682 base::debug::TaskAnnotator::RunTask() #24 0xb1ab6d9a blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #25 0xb1ab79d1 blink::scheduler::TaskQueueManager::DoWork() #26 0xb1ab4586 #27 0xb75a2682 base::debug::TaskAnnotator::RunTask() #28 0xb75ce937 base::MessageLoop::RunTask() #29 0xb75d04d4 base::MessageLoop::DeferOrRunPendingTask() #30 0xb75d142b base::MessageLoop::DoWork() #31 0xb75d1888 base::MessagePumpDefault::Run() #32 0xb75cdd3f base::MessageLoop::RunHandler() #33 0xb75faed6 base::RunLoop::Run() #34 0xb53dcf03 #35 0xb54ed49d #36 0xb54ed85e #37 0xb54ecce8 content::ContentMain() #38 0x8023fda5 #39 0x8023e0d7 #40 0xb0a25276 __libc_start_main #41 0x8023fc17 gs: 0033 fs: es: 007b ds: 007b edi: 3ac141a0 esi: 3ac141a4 ebp: 3ac14190 esp: bfcb4d50 ebx: af882a00 edx: ffa4 ecx: aca2acc0 eax: trp: 0006 err: ip: af84a7f4 cs: 0073 efl: 00210286 usp: bfcb4d50 ss: 007b [end of stack trace] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1669344 Title: Received signal 4 ILL_ILLOPN Status in chromium-browser package in Ubuntu: Confirmed Bug description: This morning chromium-browser upgraded to 56.0.2924.76-0ubuntu0.16.10.1335 and promptly stopped working for me. When trying to load any page, it dumps this traceback: Received signal 4 ILL_ILLOPN 7f78b7a509e7 #0 0x7f78d509500e base::debug::StackTrace::StackTrace() #1 0x7f78d5095403 #2 0x7f78d53aa630 #3 0x7f78b7a509e7 WTF::decommitSystemPages() #4 0x7f78c3f997b0 #5 0x7f78c3f99f17 #6 0x7f78c3f97b0e blink::NormalPageArena::allocatePage() #7 0x7f78c3f98560 blink::NormalPageArena::outOfLineAllocate() #8 0x7f78c3987678 blink::ChromeClientImpl::create() #9 0x7f78c3a2929a blink::WebViewImpl::WebViewImpl() #10 0x7f78c3a2aeb3 blink::WebViewImpl::create() #11 0x7f78cfcd8769 content::RenderViewImpl::Initialize() #12 0x7f78cfcd9443 content::RenderViewImpl::Create() #13 0x7f78cf5d8692 content::mojom::RendererStubDispatch::Accept() #14 0x7f78d4bc2671 mojo::InterfaceEndpointClient::HandleValidatedMessage() #15 0x7f78d0d17bd0 #16 0x7f78d0d18034 #17 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #18 0x7f78c3f35f4f blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #19 0x7f78c3f36ab0 blink::scheduler::TaskQueueManager::DoWork() #20 0x7f78d5096543 base::debug::TaskAnnotator::RunTask() #21 0x7f78d50bc740 base::MessageLoop::RunTask() #22 0x7f78d50be33d base::MessageLoop::DeferOrRunPendingTask() #23 0x7f78d50bf19d base::MessageLoop::DoWork() #24 0x7f78d50bf589 base::MessagePumpDefault::Run() #25 0x7f78d50bbb22 base::MessageLoop::RunHandler() #26 0x7f78d50e44b8 base::RunLoop::Run() #27 0x7f78cfcf5629 #28 0x7f78cfde7048 #29 0x7f78cfde7444 #30 0x7f78cfde68c1 content::ContentMain() #31 0x55b0046e086c #32 0x7f78bfec03f1 __libc_start_main #33 0x55b0046e073a r8: r9: r10: 0022 r11: 0206 r12: 16113987 r13: 0004 r14: 7f78b7c87448 r15: di: 3fb7e8201000 si: 0001e000 bp: 16113981c210 bx: 16113981c218 dx: 0008 ax: cx: ff68 sp: 7fffa09e5f30 ip: 7f78b7a509e7 efl: 00010286 cgf: 0033 erf: trp: 0006 msk: cr2: [end of stack trace] Being chromium, the overall processes don't die or c
[Desktop-packages] [Bug 1396253] [NEW] gnome-control-center segmentation fault when clicking the Backup icon
Public bug reported: What I did: I opened gnome-control-center either via the menu or from command line. I scrolled down to "System" settings. I clicked "Backup" icon. What I expected: See and manipulate Deja Dup settings. What I got instead: No visible response from the application, it just disappears. Ubuntu 14.10 gnome-control-center 1:3.12.1-5ubuntu2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1396253 Title: gnome-control-center segmentation fault when clicking the Backup icon Status in “gnome-control-center” package in Ubuntu: New Bug description: What I did: I opened gnome-control-center either via the menu or from command line. I scrolled down to "System" settings. I clicked "Backup" icon. What I expected: See and manipulate Deja Dup settings. What I got instead: No visible response from the application, it just disappears. Ubuntu 14.10 gnome-control-center 1:3.12.1-5ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1396253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245637] Re: Page size zero in properties dialog
Carlos Garcia Campos reports that this is fixed in git master and gnome-3-10 branches. Now we just have to wait that they hit downstream. https://bugzilla.gnome.org/show_bug.cgi?id=711093#c1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1245637 Title: Page size zero in properties dialog Status in Evince document viewer: Unknown Status in “evince” package in Ubuntu: Triaged Bug description: What I did: Opened a PDF file, viewed the properties dialog (via the menu or Alt+Enter). What I got: When viewing the properties dialog, the page size is shown as 0 x 0 mm regardless of the real page size. What I expected: The true page size listed in the properties dialog. Tested with many different PDF files. This bug appeared after upgrading to Ubuntu 13.10 and with Evince version 3.10.0-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1245637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245637] Re: Page size zero in properties dialog
Reported to Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=711093 ** Bug watch added: GNOME Bug Tracker #711093 https://bugzilla.gnome.org/show_bug.cgi?id=711093 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1245637 Title: Page size zero in properties dialog Status in “evince” package in Ubuntu: New Bug description: What I did: Opened a PDF file, viewed the properties dialog (via the menu or Alt+Enter). What I got: When viewing the properties dialog, the page size is shown as 0 x 0 mm regardless of the real page size. What I expected: The true page size listed in the properties dialog. Tested with many different PDF files. This bug appeared after upgrading to Ubuntu 13.10 and with Evince version 3.10.0-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1245637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245637] [NEW] Page size zero in properties dialog
Public bug reported: What I did: Opened a PDF file, viewed the properties dialog (via the menu or Alt+Enter). What I got: When viewing the properties dialog, the page size is shown as 0 x 0 mm regardless of the real page size. What I expected: The true page size listed in the properties dialog. Tested with many different PDF files. This bug appeared after upgrading to Ubuntu 13.10 and with Evince version 3.10.0-0ubuntu2. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1245637 Title: Page size zero in properties dialog Status in “evince” package in Ubuntu: New Bug description: What I did: Opened a PDF file, viewed the properties dialog (via the menu or Alt+Enter). What I got: When viewing the properties dialog, the page size is shown as 0 x 0 mm regardless of the real page size. What I expected: The true page size listed in the properties dialog. Tested with many different PDF files. This bug appeared after upgrading to Ubuntu 13.10 and with Evince version 3.10.0-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1245637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168662] Re: full screen flash not working
This regression appeared after updateing from 13.04 to 13.10. Freshly opened browser lets Flash go fullscreen once but not after that. The Flash video becomes black after that but the sound is still playing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1168662 Title: full screen flash not working Status in “flashplugin-nonfree” package in Ubuntu: Confirmed Bug description: have flash issue...full screen videos are not workin in flash for me...tried everything i ve found in webnothin helped... usin ubuntu 13.04 with gnome-shell, flash version 11.2 when i click to play a video its ok, but when i want to watch same thing in full screen, there is only soundfunny part is, its workin sometimes, like 1 of 20 tries. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 20.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 BuildID: 20130404201419 Channel: Unavailable Date: Sat Apr 13 14:50:36 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.3 metric 1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=20.0/20130404201419 (In use) RelatedPackageVersions: totem-mozilla 3.6.3-0ubuntu6 rhythmbox-mozilla 2.98-0ubuntu5 gnome-shell 3.8.0.1-0ubuntu1+js17~raring3 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 7741 dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd05/03/2010:svnAcer:pnAspire7741:pvrV1.09:rvnAcer:rnAspire7741:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.name: Aspire 7741 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1168662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp