[Desktop-packages] [Bug 2077474] Re: second workspace is not visible on the new dynamic activity indicator
After reboot something happened. Instead of the blank space a small (smaller than it has to be) dot appeared. I don't know why. I only updated the kernel. ** Attachment added: "screenshot20240821-2.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+attachment/5807764/+files/screenshot20240821-2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2077474 Title: second workspace is not visible on the new dynamic activity indicator Status in gnome-shell package in Ubuntu: Incomplete Bug description: Second workspace is not visible on the new dynamic activity indicator. Earlier (in the 24.04 release) it worked. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.3 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 23:01:02 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-22 (303 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-06-29 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+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 2077474] Re: second workspace is not visible on the new dynamic activity indicator
While switching to another workspace, the second dot (or line) remains blank. ** Attachment added: "screenshot20240821.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+attachment/5807686/+files/screenshot20240821.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2077474 Title: second workspace is not visible on the new dynamic activity indicator Status in gnome-shell package in Ubuntu: Incomplete Bug description: Second workspace is not visible on the new dynamic activity indicator. Earlier (in the 24.04 release) it worked. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.3 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 23:01:02 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-22 (303 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-06-29 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+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 2077474] [NEW] second workspace is not visible on the new dynamic activity indicator
Public bug reported: Second workspace is not visible on the new dynamic activity indicator. Earlier (in the 24.04 release) it worked. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.3 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 23:01:02 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-22 (303 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-06-29 (52 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Képernyőkép 2024-08-20 22-53-43.png" https://bugs.launchpad.net/bugs/2077474/+attachment/5807471/+files/K%C3%A9perny%C5%91k%C3%A9p%202024-08-20%2022-53-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2077474 Title: second workspace is not visible on the new dynamic activity indicator Status in gnome-shell package in Ubuntu: New Bug description: Second workspace is not visible on the new dynamic activity indicator. Earlier (in the 24.04 release) it worked. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu6~24.04.3 ProcVersionSignature: Ubuntu 6.8.0-40.40.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 20 23:01:02 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-22 (303 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-06-29 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077474/+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 1981863] Re: gnome calendar does not sync with google calendar
Calendar sync doesn't work since yesterday evening. Maybe Google changed something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: Incomplete Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] Re: gnome calendar does not sync with google calendar
I don't know what happened, but gnome calendar syncing again with google :-o Maybe the update of libgnutls30? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: Incomplete Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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
Re: [Desktop-packages] [Bug 1981863] Re: gnome calendar does not sync with google calendar
There are no error messages. I created a new user, logged in and added my google account to gnome online accounts. Sync was not working and there were no error messages. I assume that the original settings for a new user should work. So maybe the problem is something else, not the settings. On júl 19 2022, at 1:55 du, Sebastien Bacher <1981...@bugs.launchpad.net> wrote: > It's working fine here, adding an event in a webbrowser and doing a sync > in gnome-calendar and it shows as expected. Could you check in settings > > online account if there is an error displayed? could you perhaps also > check if evolution displays maybe some error about the calendar account? > > ** Changed in: gnome-calendar (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1981863 > > Title: > gnome calendar does not sync with google calendar > > Status in gnome-calendar package in Ubuntu: > Incomplete > > Bug description: > In the newest Ubuntu stable release (22.04), gnome 42.2, gnome > calendar 41.2 does not sync calendar events from google calendar > through GOA. But when an event is created in gnome calendar, it is > synchronized with google calendar. So the synchronization works only > in one direction. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: Incomplete Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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
Re: [Desktop-packages] [Bug 1981863] Re: gnome calendar does not sync with google calendar
Sorry, I should write “maybe”. But calendar sync worked earlyer. Something changed during the last update of ??.deb and since this sync does not work. Sebastien Bacher <1981...@bugs.launchpad.net> (időpont: 2022. júl. 18., H, 14:11) ezt írta: > Thanks, but one mention that it works for one user in fedora doesn't > mean it's distribution specific > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1981863 > > Title: > gnome calendar does not sync with google calendar > > Status in gnome-calendar package in Ubuntu: > New > > Bug description: > In the newest Ubuntu stable release (22.04), gnome 42.2, gnome > calendar 41.2 does not sync calendar events from google calendar > through GOA. But when an event is created in gnome calendar, it is > synchronized with google calendar. So the synchronization works only > in one direction. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] Re: gnome calendar does not sync with google calendar
The same issue appears in gnome-todo... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] Re: gnome calendar does not sync with google calendar
And see this: https://askubuntu.com/questions/1411856/synchronization-issues-with-google-accounts-and-gnome-online-accounts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] Re: gnome calendar does not sync with google calendar
As I read in other forums, this works fine in Fedora. So this bug is Ubuntu specific. https://askubuntu.com/questions/1408669/gnome-calendar-not-working-in- ubuntu-22-04lts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1981863] [NEW] gnome calendar does not sync with google calendar
Public bug reported: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-calendar google-online-account sync ** Tags added: gnome-calendar ** Tags added: google-online-account sync -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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
Re: [Desktop-packages] [Bug 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview
Memory usage increases only at the first time when a push Super+A. Repeatedly pushing Super+A doesn't cause further jumps. However, this allocated memory never seems to be released (memory usage doesn't drop back to the original level). On Jan 7 2022, at 8:32 am, Daniel van Vugt <1856...@bugs.launchpad.net> wrote: > Is anyone still affected by this bug? If so then please ensure you don't > have any extensions loaded and tell us what version of Ubuntu you are > using. > > > ** Changed in: gnome-shell (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1856838 > > Title: > [memory leak] gnome-shell using a lot of RAM after repeatedly opening > the overview > > Status in GNOME Shell: > New > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. > Spoke to duflu on irc and he suggested I file a bug, and to make sure > I'm not using any extra extensions. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 > ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 > Uname: Linux 5.3.0-24-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Dec 18 10:49:44 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2018-02-04 (681 days ago) > InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary > 20180202-11:07 > RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1856838/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856838 Title: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856838/+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 1946970] Re: Memory leak in gnome-shell after lock and unlock the screen
I switch off all the extensions except for Ubuntu ones. Every lock/unlock action raises the memory usage by ~10MB until it reaches ~280MB. Super-A (app overview) raised further the usage. After a while something happend (Not lock/unlock or Super-A) and now the memory usage of gnome-shell is 302MB and is not changing. What is the normal memory usage of gnome-shell? Is it normal (what I have described) or it should stay at the beginning level? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1946970 Title: Memory leak in gnome-shell after lock and unlock the screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: When the screen is locked and unlocked extra ~100MB memory remains in use and never freed up. After each lock/unlock action additional 10-20MB will be used, and the memory consumption of gnome-shell grows and grows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-18.18-generic 5.13.14 Uname: Linux 5.13.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 14:06:17 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-06 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946970/+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 1946970] [NEW] Memory leak in gnome-shell after lock and unlock the screen
Public bug reported: When the screen is locked and unlocked extra ~100MB memory remains in use and never freed up. After each lock/unlock action additional 10-20MB will be used, and the memory consumption of gnome-shell grows and grows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-18.18-generic 5.13.14 Uname: Linux 5.13.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 14:06:17 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-06 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1946970 Title: Memory leak in gnome-shell after lock and unlock the screen Status in gnome-shell package in Ubuntu: New Bug description: When the screen is locked and unlocked extra ~100MB memory remains in use and never freed up. After each lock/unlock action additional 10-20MB will be used, and the memory consumption of gnome-shell grows and grows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-18.18-generic 5.13.14 Uname: Linux 5.13.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 14:06:17 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-06 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946970/+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 1943488] [NEW] when typeing too fast in the search line searching stops to work
Public bug reported: 1. $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. When I try to find a file/directory in nautilus I start to type some letters (or press CTRL-f befor typing). Normally nautilus tries to find the files and shows the result. 4. When I am typing too fast (or normal speed?) the searching hangs up, a small blue circle goes around in the left bottom corner and nothing happens for long time. If I cut (CTRL-a CTRL-x) the searched text and paste it back (CTRL-f CTRL-v) the searching is successful, and the result appears immidietly. The situation is same e.g. in gnome-software, so I think this problem is globally exists in gnome. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: nautilus searching typing ** Tags added: nautilus searching typing -- 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/1943488 Title: when typeing too fast in the search line searching stops to work Status in nautilus package in Ubuntu: New Bug description: 1. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. When I try to find a file/directory in nautilus I start to type some letters (or press CTRL-f befor typing). Normally nautilus tries to find the files and shows the result. 4. When I am typing too fast (or normal speed?) the searching hangs up, a small blue circle goes around in the left bottom corner and nothing happens for long time. If I cut (CTRL-a CTRL-x) the searched text and paste it back (CTRL-f CTRL-v) the searching is successful, and the result appears immidietly. The situation is same e.g. in gnome-software, so I think this problem is globally exists in gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1943488/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
When I switched off and on google calendar in gnome-calendar, this happened: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
I just tried it out: if I switch off google calendar (set up in Settings/Online accounts), everything is working as it should be. But I need google calendar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
Does anyone else experience this, or just me? With this issue the calendar is unusable, but I couldn't find any bug report about this. But this bug has been around for a long time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
When launching gnome-calendar, the week view (current week) appears for a second and disappear when the header (days of the week) is being written. After switching to previous and next weeks the week view is normal again. Returnig to the current week the week view is blank again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
** Attachment added: "Képernyőkép erről: 2021-08-02 02-02-48.png" https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+attachment/5515158/+files/K%C3%A9perny%C5%91k%C3%A9p%20err%C5%91l%3A%202021-08-02%2002-02-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1938658] [NEW] Week view goes blank when changing weeks or when user screen focus changes.
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+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 1873257] [NEW] gnome-shell crashes randomly
Public bug reported: Ubuntu 20.04, ubuntu session with wayland. After about one hour usage, while firefox has been launched gnome-shell(?) crashed and falled back to gdm login screen. This has happened several times. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:26:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-06 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-07T00:19:12.727815 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873257 Title: gnome-shell crashes randomly Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04, ubuntu session with wayland. After about one hour usage, while firefox has been launched gnome-shell(?) crashed and falled back to gdm login screen. This has happened several times. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:26:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-06 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-07T00:19:12.727815 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873257/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
In Ubuntu 20.04 (with the newest packages) the leak is present. After logging in the memory usage of gnome-shell is 208MB. After pushing Super+A it jumps to 213MB and stay there. After lock/unlock the screen it jumps to 270MB and stays there. Repeated Super+A and lock/unlock seems to do no further changes. After launching firefox it jumps to 290MB and stays there. Closing firefox and launching it again it jumps to 300MB and stasy there. Repeatedly launching firefox (and other apps like terminal, files, settings, etc.) seems to do just small ~100-500kB jumps. Now it sits on 306MB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: Confirmed Bug description: Many times after logging in gnome-shell uses 600-800MB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200MB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
In Ubuntu 20.04 (with the newest packages) the leak is present. After logging in the memory usage of gnome-shell is 208MB. After pushing Super+A it jumps to 213MB and stay there. After lock/unlock the screen it jumps to 270MB and stays there. Repeated Super+A and lock/unlock seems to do no further changes. After launching firefox it jumps to 290MB and stays there. Closing firefox and launching it again it jumps to 300MB and stasy there. Repeatedly launching firefox (and other apps like terminal, files, settings, etc.) seems to do just small ~100-500kB jumps. Now it sits on 306MB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Could be any connection between https://gitlab.gnome.org/GNOME/gjs/issues/52 and the problem here? (I am not an expert) ** Bug watch added: gitlab.gnome.org/GNOME/gjs/issues #52 https://gitlab.gnome.org/GNOME/gjs/issues/52 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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
Re: [Desktop-packages] [Bug 1850201] Re: memory usage is growing over time
The same problem exists for Ubuntu 20.04, Gnome 3.36, gjs 1.63.92, mozjs 68.5. Daniel van Vugt ezt írta (időpont: 2019. okt. 31., Cs, 3:25): > Thanks for testing that. Though I think you mean MB, not kB :) > > ** Summary changed: > > - memory usage is growing over time > + Memory usage grows when locking/unlocking the screen > > ** Changed in: gnome-shell (Ubuntu) >Status: Incomplete => New > > ** Tags added: performance > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1850201 > > Title: > Memory usage grows when locking/unlocking the screen > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > Many times after logging in gnome-shell uses 600-800kB of memory, and > also slows down quite a bit (e.g., 20-30 seconds waiting for login). > Only after multiple resets (Alt+F2 r) drops the memory usage below > 200kB. I use my computer mainly for work, and the above phenomenon is > quite disturbing. After a couple of hours of work memory usage is > growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't > help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest > Ubuntu also behaves similarly. This is an old issue, it was present in > 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all > of them suffer with this problem. Anyone can check this with the > "gnome-shell memory monitor" gnome-shell extension. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.28.4-0ubuntu18.04.2 > ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CurrentDesktop: communitheme:ubuntu:GNOME > Date: Mon Oct 28 20:28:38 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2019-01-04 (297 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: Confirmed Bug description: Many times after logging in gnome-shell uses 600-800MB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200MB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
Here is a similar issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1886 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
I'm trying to catch that function(s) which leaks the memory, but unfortunately I am not an expert. Can anyone help me what to do? I copied /usr/bin/gnome-shell to /usr/bin/gnome-shell.bin and made a script in /usr/bin/gnome-shell: #!/bin/sh if [ $USER = gstest ] ; then exec valgrind --tool=massif --num-callers=500 --massif-out-file=/tmp/massif.out.%p --log-file=/tmp/gnome-shell.valgrind.log.%p $0.bin $* ; fi exec $0.bin $* after that I logged in as gstest and watched the valgrind output with massif-visualizer. But I don't know how to control the frequency of writing out the massif.out.pid file? This file was wrote out couple minutes after logging in, but after that nothing was written out for hours. It would be better to see continuously what is happening when I e.g. push Super+A. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
What does it mean "doesn't free memory immediately"? Hours? Days? I never experienced decrease in memory usage, except for small fluctuations. I think it is a memory leak added to this slow garbage collection. I also wrote about this problem to https://gitlab.gnome.org/GNOME/gjs/issues/217# but the guys there suggested me to report a bug here, because they thoght that this is not a garbage collection issue. And it seems to me that gnome-shell or gjs is leaking without the extensions too. ** Bug watch added: gitlab.gnome.org/GNOME/gjs/issues #217 https://gitlab.gnome.org/GNOME/gjs/issues/217 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
The main system which I use for work is Ubuntu 18.04.3 LTS. I use gnome with many extensions (see above). At the beginning the memory usage of gnome-shell is ~177MB. (Interesting that in another machine, which is a laptop and has exactly the same system and almost the same hardware, gnome-shell uses ~150MB at the beginning) During my work (using e.g. Octave, LyX, Chrome) the memory usage of gnome-shell is increasing continuously, but when I restart gnome-shell with "Alt+F2 r ", after some time the memory usage doesn't drop to the original value, but ramains at a higher value, which is approx. 200-250MB. This value is slowly increasing. I assume that there is a memory leak somewhere in gnome-shell or gjs (or somewhere else), but only a portion of the leaked memory can be freed with "Alt+F2 r ". I tried to watch what causes the jumps in memory usage, but coudn't figure out it. Sometimes e.g. locking-unlocking the screen, but sometime it seems to be random. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
Yes, MB, not kB. Today I made a new test. I logged in (ubuntu 19.10 on virtualbox, normal ubuntu session) and started the gnome-system-monitor to see what is happening. The memory usage of gnome-shell was ~202MB at the beginning. I locked the session, and unlocked it. The memory usage jumped to ~225MB. A lock and unlocked again, the result was ~226MB. Further lock-unlock action made only small, less than 1MB growings. After that a did nothing, left the system untouched. After an hour the memory usage was ~260MB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: memory usage is growing over time
The test system was 19.10 in virtualbox. I removed almost every extensions, except for the built in ones (ubuntu dock, ubuntu appindicator, etc.). Gnome-shell uses ~200kB at the beginning. If I lock the screen and unlock it, the memory usage jumps to ~210kB. Repeatedly doing this, the memory usage is increasing. Similarly, suspending the system and wakeing it up also cause a jump in the memory usage, which remains there permanently. After manually reset gnome-shell (Alt+F2 r) the memory usage falls back to ~200kB. What is the theoretical memory usage of gnome-shell? When I reset it, the memory usage is ~90kB for a couple of second, and it grows back to ~200kB. It already happened that the memory usage at the beginning of the gnome session was very low (~80kB), and grew very slowly (couple of minutes with countinuous work, launching programs, browsering the web) until it reached the approx. 200kB usage. It is very suspecious. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: memory usage is growing over time Status in gnome-shell package in Ubuntu: Incomplete Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] [NEW] memory usage is growing over time
Public bug reported: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome- shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1850201 Title: memory usage is growing over time Status in gnome-shell package in Ubuntu: New Bug description: Many times after logging in gnome-shell uses 600-800kB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200kB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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
Re: [Desktop-packages] [Bug 1816539] Re: Searching by file type doesn't work
A similar bug ( Bug #1767817) was fixed in bionic (18.04) within 1-2 days when it turned out that it is fixed in disco (19.04). This bug is also fixed in disco. Could it be backported to bionic? On feb 20 2019, at 10:55 du, Balázs Pere wrote: > In the current 19.04 (disco) it works well. > > On feb 20 2019, at 1:29 du, Balázs Pere wrote: > > When I choose a certain file type, the correct hits appears for a second, > > but after that all hits come back. > > > > On Feb 20 2019, at 1:28 pm, Balázs Pere wrote: > > > New packages in > > > https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497 > > > leaves unchanged this bug. > > > > > > On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > > > > Indeed, that seems fixed in the current Ubuntu serie but buggy in > > > > bionic, potentially something we want to fix in a SRU > > > > > > > > ** Changed in: nautilus (Ubuntu) > > > > Importance: Undecided => High > > > > > > > > ** Changed in: nautilus (Ubuntu) > > > > Status: New => Fix Released > > > > > > > > -- > > > > You received this bug notification because you are subscribed to the bug > > > > report. > > > > https://bugs.launchpad.net/bugs/1816539 > > > > > > > > Title: > > > > Searching by file type doesn't work > > > > > > > > Status in nautilus package in Ubuntu: > > > > Fix Released > > > > > > > > Bug description: > > > > When I click on searching in nautilus a down arrow appears on the > > > > right (next to the input field). If I click on this arrow, a pop up > > > > menu appears with "When" and "What" titles. Inside "What" I can choose > > > > file types. Choosing a certain file type nothing happens, nautilus > > > > shows the hits for every file type. This search option doesn't seem to > > > > work. (For "Full Text" see Bug #1767817) > > > > > > > > $ lsb_release -rd > > > > Description: Ubuntu 18.04.2 LTS > > > > Release: 18.04 > > > > > > > > $ apt-cache policy nautilus > > > > nautilus: > > > > Installed: 1:3.26.4-0~ubuntu18.04.3 > > > > Candidate: 1:3.26.4-0~ubuntu18.04.3 > > > > Version table: > > > > *** 1:3.26.4-0~ubuntu18.04.3 500 > > > > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > > > > 100 /var/lib/dpkg/status > > > > 1:3.26.3-0ubuntu4 500 > > > > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > > > > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > > > > > > > > > > > > > > > > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+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
Re: [Desktop-packages] [Bug 1816539] Re: Searching by file type doesn't work
In the current 19.04 (disco) it works well. On feb 20 2019, at 1:29 du, Balázs Pere wrote: > When I choose a certain file type, the correct hits appears for a second, but > after that all hits come back. > > On Feb 20 2019, at 1:28 pm, Balázs Pere wrote: > > New packages in > > https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497 > > leaves unchanged this bug. > > > > On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > > > Indeed, that seems fixed in the current Ubuntu serie but buggy in > > > bionic, potentially something we want to fix in a SRU > > > > > > ** Changed in: nautilus (Ubuntu) > > > Importance: Undecided => High > > > > > > ** Changed in: nautilus (Ubuntu) > > > Status: New => Fix Released > > > > > > -- > > > You received this bug notification because you are subscribed to the bug > > > report. > > > https://bugs.launchpad.net/bugs/1816539 > > > > > > Title: > > > Searching by file type doesn't work > > > > > > Status in nautilus package in Ubuntu: > > > Fix Released > > > > > > Bug description: > > > When I click on searching in nautilus a down arrow appears on the > > > right (next to the input field). If I click on this arrow, a pop up > > > menu appears with "When" and "What" titles. Inside "What" I can choose > > > file types. Choosing a certain file type nothing happens, nautilus > > > shows the hits for every file type. This search option doesn't seem to > > > work. (For "Full Text" see Bug #1767817) > > > > > > $ lsb_release -rd > > > Description: Ubuntu 18.04.2 LTS > > > Release: 18.04 > > > > > > $ apt-cache policy nautilus > > > nautilus: > > > Installed: 1:3.26.4-0~ubuntu18.04.3 > > > Candidate: 1:3.26.4-0~ubuntu18.04.3 > > > Version table: > > > *** 1:3.26.4-0~ubuntu18.04.3 500 > > > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > > > 100 /var/lib/dpkg/status > > > 1:3.26.3-0ubuntu4 500 > > > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > > > > > > > > > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+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
Re: [Desktop-packages] [Bug 1816539] Re: Searching by file type doesn't work
When I choose a certain file type, the correct hits appears for a second, but after that all hits come back. On Feb 20 2019, at 1:28 pm, Balázs Pere wrote: > New packages in > https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/16410497 > leaves unchanged this bug. > > On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > > Indeed, that seems fixed in the current Ubuntu serie but buggy in > > bionic, potentially something we want to fix in a SRU > > > > ** Changed in: nautilus (Ubuntu) > > Importance: Undecided => High > > > > ** Changed in: nautilus (Ubuntu) > > Status: New => Fix Released > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1816539 > > > > Title: > > Searching by file type doesn't work > > > > Status in nautilus package in Ubuntu: > > Fix Released > > > > Bug description: > > When I click on searching in nautilus a down arrow appears on the > > right (next to the input field). If I click on this arrow, a pop up > > menu appears with "When" and "What" titles. Inside "What" I can choose > > file types. Choosing a certain file type nothing happens, nautilus > > shows the hits for every file type. This search option doesn't seem to > > work. (For "Full Text" see Bug #1767817) > > > > $ lsb_release -rd > > Description: Ubuntu 18.04.2 LTS > > Release: 18.04 > > > > $ apt-cache policy nautilus > > nautilus: > > Installed: 1:3.26.4-0~ubuntu18.04.3 > > Candidate: 1:3.26.4-0~ubuntu18.04.3 > > Version table: > > *** 1:3.26.4-0~ubuntu18.04.3 500 > > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > > 100 /var/lib/dpkg/status > > 1:3.26.3-0ubuntu4 500 > > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > > > > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+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
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
It seems to work well. Sometimes it hang up, shows "searching" in the right bottom corner of nautilus window. If I delete back some characters in the input field, it starts to work again. On Feb 20 2019, at 9:11 am, Sebastien Bacher wrote: > Yes, it's fixed in the Disco serie, I've uploaded a test package to > https://launchpad.net/~ubuntu- > desktop/+archive/ubuntu/ppa/+build/16410497 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > In Progress > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: > *** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: In Progress Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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
Re: [Desktop-packages] [Bug 1816539] Re: Searching by file type doesn't work
New packages in https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+build/16410497 leaves unchanged this bug. On Feb 19 2019, at 2:14 pm, Sebastien Bacher wrote: > Indeed, that seems fixed in the current Ubuntu serie but buggy in > bionic, potentially something we want to fix in a SRU > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => High > > ** Changed in: nautilus (Ubuntu) > Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816539 > > Title: > Searching by file type doesn't work > > Status in nautilus package in Ubuntu: > Fix Released > > Bug description: > When I click on searching in nautilus a down arrow appears on the > right (next to the input field). If I click on this arrow, a pop up > menu appears with "When" and "What" titles. Inside "What" I can choose > file types. Choosing a certain file type nothing happens, nautilus > shows the hits for every file type. This search option doesn't seem to > work. (For "Full Text" see Bug #1767817) > > $ lsb_release -rd > Description: Ubuntu 18.04.2 LTS > Release: 18.04 > > $ apt-cache policy nautilus > nautilus: > Installed: 1:3.26.4-0~ubuntu18.04.3 > Candidate: 1:3.26.4-0~ubuntu18.04.3 > Version table: > *** 1:3.26.4-0~ubuntu18.04.3 500 > 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages > 100 /var/lib/dpkg/status > 1:3.26.3-0ubuntu4 500 > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+subscriptions > -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: Fix Released Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+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 1816539] [NEW] Searching by file type doesn't work
Public bug reported: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1816539 Title: Searching by file type doesn't work Status in nautilus package in Ubuntu: New Bug description: When I click on searching in nautilus a down arrow appears on the right (next to the input field). If I click on this arrow, a pop up menu appears with "When" and "What" titles. Inside "What" I can choose file types. Choosing a certain file type nothing happens, nautilus shows the hits for every file type. This search option doesn't seem to work. (For "Full Text" see Bug #1767817) $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.3 Candidate: 1:3.26.4-0~ubuntu18.04.3 Version table: *** 1:3.26.4-0~ubuntu18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1816539/+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
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
If the users think it is important, developers should raise the level of priority. bdr529 <1767...@bugs.launchpad.net> ezt írta (időpont: 2019. febr. 17., V, 20:10): > Ubuntu 18.10 with tracker installed: > With Tracker Search Provider by hamiller Plugin for Gnome Shell, Full-text > Search works, but is limited to 5 results as or2V has written. Full text > search within Nautilus does not. > I still do not understand the classification of the bug on low priority. I > can't believe this. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: >*** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1767817] Re: Full text search does not work
Does anybody know what to change in the source code to made FTS work? I can compile and install it...at my own risk. -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time
I switched from nvidia driver to nouveau driver and the huge memory
usage disappeared. Small jumps (increase) in memory usage stayed with
us.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
Triaged
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
No comment...
** Attachment added: "screenshot of gnome-usage"
https://bugs.launchpad.net/gnome-shell/+bug/1672297/+attachment/5190499/+files/Screenshot%20from%202018-09-19%2011-33-32.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
In Progress
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=PO
Re: [Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
I installed Ubuntu 18.10 gjs and libgjs0g 1.53.3-1 (of Ubuntu 18.10) to
Ubuntu 18.04. It seems that the memory leak lives forever...
Memory usage started from 170MB, and after two hours is over 360MB.
[image: Képernyőkép erről: 2018-09-02 23-46-44.png]
chris pollock <1672...@bugs.launchpad.net> ezt írta (időpont: 2018. aug.
20., H, 16:51):
> This is:
> apt-cache policy gnome-shell
> gnome-shell:
> Installed: 3.28.2-0ubuntu0.18.04.1
> Candidate: 3.28.2-0ubuntu0.18.04.1
>
> apt-cache policy evolution
> evolution:
> Installed: 3.28.1-2
> Candidate: 3.28.1-2
>
> lsb_release -crid
> Distributor ID: Ubuntu
> Description:Ubuntu 18.04.1 LTS
> Release:18.04
> Codename: bionic
>
> uname -a
> Linux localhost 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> Aug 20 08:46:13 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 19537920/16986112/-2551808, res+swap =
> 14004224/11452416/-2551808
> Aug 20 08:46:19 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16916480/16908288/-8192, res+swap = 11382784/11374592/-8192
> Aug 20 08:46:58 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16908288/16908288/0, res+swap = 11374592/11374592/0
> Aug 20 08:47:29 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16908288/16912384/4096, res+swap = 11378688/11378688/0
> Aug 20 08:47:59 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16912384/16912384/0, res+swap = 11378688/11378688/0
>
> Not sure if this pertains to this bug at all. I noticed the above every
> few minutes in my syslog after upgrading to 18.04.1 last week.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672297
>
> Title:
> gnome-shell uses lots of memory, and grows over time
>
> Status in GNOME Shell:
> Confirmed
> Status in gjs package in Ubuntu:
> Fix Released
> Status in gjs source package in Bionic:
> In Progress
>
> Bug description:
> Upstream:
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
>
> ---
>
> gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
> almost 2 GiB.
>
> user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
> /usr/bin/gnome-shell
>
> strace output is voluminous; here is a representative sample:
>
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\231\n\10\0\n\0
> \0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
> \0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11,
> events=POLLIN}, {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,
> events=POLLIN}, {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32,
> events=POLLIN}, {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38,
> events=POLLIN}, {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43,
> events=POLLIN}], 15, 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11,
> events=POLLIN}, {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,
> events=POLLIN}, {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32,
> events=POLLIN}, {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38,
> events=POLLIN}, {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43,
> events=POLLIN
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
Why don't want the developers fix this (and other) bug? Whether do they want me to use the non-LTS releases? Or do they want me to use other distros than Ubuntu? So I would like to use Ubuntu 18.04 with full gnome functionality without bugs. (e.g. without memory leak...) bdr529 <1767...@bugs.launchpad.net> ezt írta (időpont: 2018. aug. 3., P 21:06): > Gnome Documents doesn't find any documents either. > I resigned and use Recoll instead It's very fast and reliable. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: >*** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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
Re: [Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Ubuntu 18.04.1 is coming soon (tomorrow?). What about the bug fixes?
I know a temporary method, but it is not so nice (but it works, saves
~400MB RAM): run after login
sudo killall -u gdm
killall gnome-software
One more, clear gnome-calendar. It launches automatically, uses
constantly 2-400MB RAM, and do nothing.
sudo apt remove gnome-calendar
waffen <1672...@bugs.launchpad.net> ezt írta (időpont: 2018. júl. 16., H, 5:01):
>
> Well for this bug I need to install Xubuntu and lightdm, run very fast
> with no issues, BUT looks like Firefox is eating a lot of RAM in both
> desktops, for my job I need FF to be opened all the time, so the time to
> time I need to close it and relaunch it, if not FF freezing my desktop,
> now even Chrome eats a lower portion of RAM than FF... are you have
> similar problems with FF + ubuntu?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672297
>
> Title:
> gnome-shell uses lots of memory, and grows over time
>
> Status in GNOME Shell:
> Confirmed
> Status in gjs package in Ubuntu:
> Fix Released
> Status in gjs source package in Bionic:
> In Progress
>
> Bug description:
> Upstream:
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
>
> ---
>
> gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
> almost 2 GiB.
>
> user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
> /usr/bin/gnome-shell
>
> strace output is voluminous; here is a representative sample:
>
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\231\n\10\0\n\0
> \0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
> \0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN},
> {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN},
> {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN},
> {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15,
> 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN},
> {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN},
> {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN},
> {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15,
> 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> open("/proc/self/stat", O_RDONLY) = 36
> fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> fcntl(36, F_GETFL) = 0x8000 (flags
> O_RDONLY|O_LARGEFILE)
> fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
> read(36, "", 3072) = 0
> close(36) = 0
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}
Re: [Desktop-packages] [Bug 1774047] Re: gnome (or something) uses a lot of memory
*** This bug is a duplicate of bug 1672297 *** https://bugs.launchpad.net/bugs/1672297 This bug report concerns to the initial size of the system (not the continuously growing size). Is it a duplicate of bug 1672297? Daniel van Vugt ezt írta (időpont: 2018. máj. 30., Sze, 4:35): > > *** This bug is a duplicate of bug 1672297 *** > https://bugs.launchpad.net/bugs/1672297 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1672297, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** This bug has been marked a duplicate of bug 1672297 >gnome-shell uses lots of memory, and grows over time > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1774047 > > Title: > gnome (or something) uses a lot of memory > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > After I log in (ubuntu session) the systen(?), shell(?) uses a lot of > memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has > 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried > it out in virtualbox with a newly installed system. I changed the memory size > and started ubuntu. I think a new, clean system should use the same amount of > memory independently of the RAM size. > Not to mention that the system is unusable, because RAM quickly fills up > (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. > Why does gnome-shell need so much memory? I think it should be fixed, because > 18.04 is an LTS release! I would like to work with it.Description: Ubuntu > > 18.04 LTS > Release: 18.04 > > gnome-shell: > Telepítve: 3.28.1-0ubuntu2 > Jelölt:3.28.1-0ubuntu2 > Verziótáblázat: >*** 3.28.1-0ubuntu2 500 > 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.28.1-0ubuntu2 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue May 29 20:21:39 2018 > DisplayManager: gdm3 > InstallationDate: Installed on 2017-10-20 (221 days ago) > InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215.2) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=hu_HU.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774047 Title: gnome (or something) uses a lot of memory Status in gnome-shell package in Ubuntu: New Bug description: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description: Ubuntu 18.04 LTS Release: 18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release
[Desktop-packages] [Bug 1774047] [NEW] gnome (or something) uses a lot of memory
Public bug reported: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description:Ubuntu 18.04 LTS Release:18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774047 Title: gnome (or something) uses a lot of memory Status in gnome-shell package in Ubuntu: New Bug description: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description: Ubuntu 18.04 LTS Release: 18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+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 1616332] Re: gnome-software using hundreds of MB of memory when not in use
+1 on 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+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
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
I have three computers, two desktops and one laptop. Two of them has a newly installed Ubuntu 18.04 and one has an upgraded 18.04 (from 17.10). In one desktop I installed ubuntu 18.04 in virtualbox. For every operating system I installed tracker. Full text search in nautilus doesn't work in any of them. It must be a bug. On máj 8 2018, at 7:05 du, Wolf Walter wrote: > > I have the same problem. Does also not work with the nautilus version > from flathub. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: > *** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1770886] [NEW] gnome-calendar runs in background and uses a lot of memory
Public bug reported: Some minutes after I logged in I realized that gnome-calendar runs in the background and uses more than 400MB memory. I don't launched it. Is it normal? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 12 20:39:27 2018 InstallationDate: Installed on 2017-10-20 (204 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to bionic on 2018-04-15 (27 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1770886 Title: gnome-calendar runs in background and uses a lot of memory Status in gnome-calendar package in Ubuntu: New Bug description: Some minutes after I logged in I realized that gnome-calendar runs in the background and uses more than 400MB memory. I don't launched it. Is it normal? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 12 20:39:27 2018 InstallationDate: Installed on 2017-10-20 (204 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to bionic on 2018-04-15 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1770886/+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
Re: [Desktop-packages] [Bug 1767817] Re: Full text search does not work
I think nautilus 3.26 should do full text search. If not, there are two possibilities Remove the option from the search menu. Implement/fix the full text search capability. On máj 3 2018, at 5:35 du, Mordi wrote: > > I kind of figured this out. In addition to Tracker, you need Gnome > Documents and gnome-shell-extensions installed. Launch Gnome Documents, > and it will index your files. Now you will be able to search by content > from Gnome Documents and Gnome Shell, but still not from Nautilus. > Perhaps this is because Ubuntu installs an older version of Nautilus > (3.26). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1764995). > https://bugs.launchpad.net/bugs/1767817 > > Title: > Full text search does not work > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Background: I have installed Tracker. It has finished indexing. I can > also use Tracker's command line interface to search by content. > > 1. > Description: Ubuntu 18.04 LTS > Release: 18.04 > > 2. > nautilus: > Installed: 1:3.26.3-0ubuntu4 > Candidate: 1:3.26.3-0ubuntu4 > Version table: > *** 1:3.26.3-0ubuntu4 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > 100 /var/lib/dpkg/status > > 3. I expect to be able to search files by content from Nautilus, > because this feature worked in 17.10. > > 4. I get no results from full text search unless the search matches > file names. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions > -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+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 1764995] [NEW] Full text search in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
Public bug reported: 1) Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2) nautilus: Installed: 1:3.26.3-0ubuntu3 Jelölt:1:3.26.3-0ubuntu3 Verziótáblázat: *** 1:3.26.3-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) I upgraded to Ubuntu 18.04 in one of my computers and made a brand new installation of Ubuntu 18.04 on another computer. In the latter I used minimal installation. I installed tracker too. When tracker finished building the index database I tried to search for something in nautilus. Full text search didn't work, I just got hits for the file names (fts is on). Command line search is working (tracker search ) The problem is the same in both computers. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1764995 Title: Full text search in nautilus 3.26.3 doesn't work (Ubuntu 18.04) Status in nautilus package in Ubuntu: New Bug description: 1) Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) nautilus: Installed: 1:3.26.3-0ubuntu3 Jelölt:1:3.26.3-0ubuntu3 Verziótáblázat: *** 1:3.26.3-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) I upgraded to Ubuntu 18.04 in one of my computers and made a brand new installation of Ubuntu 18.04 on another computer. In the latter I used minimal installation. I installed tracker too. When tracker finished building the index database I tried to search for something in nautilus. Full text search didn't work, I just got hits for the file names (fts is on). Command line search is working (tracker search ) The problem is the same in both computers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1764995/+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 1687614] Re: broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update
I have tried sudo apt install ghostscript=9.18~dfsg~0-0ubuntu2 but I get the following error The following packages have unmet dependencies: ghostscript : Depends: libgs9 (= 9.18~dfsg~0-0ubuntu2) but 9.18~dfsg~0-0ubuntu2.4 is to be installed E: Unable to correct problems, you have held broken packages. Any suggestion? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1687614 Title: broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update Status in ghostscript package in Ubuntu: Confirmed Bug description: After the last ghostscript udpate I have problems with the textext inkscape plugin that uses pstoedit that uses ghostscript. The command looks like this: pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta The error (short version): Error: /invalidaccess in --run-- Current allocation mode is global Last OS error: No such file or directory Current file position is 87896 GPL Ghostscript 9.18: Unrecoverable error, exit code 1 PostScript/PDF Interpreter finished. Return status 256 executed command : /usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 "/tmp/psinsRrD8m" The interpreter seems to have failed, cannot proceed ! See the attached log for the full text. I tried to downgrade to circumvent the issue but unsuccessfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1687614/+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 1366221] Re: gnome-calculator does not show application menu anywhere
UPDATE: The problem seems to come from upgrading from 12.04 to 14.04. In 12.04 I did NOT want the global menu enabled. To disable this, I had to remove indicator-appmenu package (together with appmenu-gtk appmenu-gtk3 appmenu-qt). Now, in 14.04 I was also unable to enable the global menu through system_settings/appearance/behavior (Re)Installing these packages solved the issue. Why these menus did not appear on the local windows is still an open question... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere Status in gnome-calculator package in Ubuntu: Confirmed Bug description: gnome-calculator no longer offers, as of 14.04, an application menu. It used to be there before the upgrade, in 12.04. So switching between scientific and engineering now requires me to use dconf-editor. Note that I did check hovering menu line, application title bar, and thereabouts, to no avail. This application is now useless... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-calculator 1:3.10.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 6 01:12:00 2014 SourcePackage: gnome-calculator UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+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 1366221] Re: gnome-calculator does not show application menu anywhere
Same here. I have no menu in the calculator. This makes the tool useless. There is also no menu in evince and in nautilus. But in these cases, there is at least the gear button which shows a limited subset of options (i.e. not completely useless). Are these issues related? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere Status in gnome-calculator package in Ubuntu: Confirmed Bug description: gnome-calculator no longer offers, as of 14.04, an application menu. It used to be there before the upgrade, in 12.04. So switching between scientific and engineering now requires me to use dconf-editor. Note that I did check hovering menu line, application title bar, and thereabouts, to no avail. This application is now useless... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-calculator 1:3.10.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 6 01:12:00 2014 SourcePackage: gnome-calculator UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+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 1374390] Re: when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen
Sorry, there's no bug. dconf reset -f / solved the problem, although it is not the most elegant solution. ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1374390 Title: when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen Status in “unity” package in Ubuntu: Invalid Bug description: When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed. Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 26 12:35:49 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (345 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (161 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 26 12:10:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374390/+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 1374390] [NEW] when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen
Public bug reported: When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed. Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 26 12:35:49 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (345 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (161 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 26 12:10:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1374390 Title: when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen Status in “unity” package in Ubuntu: New Bug description: When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?) screen appears to unlock. I tried to reinstall unity, unity-services, lightdm, unity-greeter, but nothing has changed. Remark: I have two other machines, one of them works correctly, but on the other the locking (Ctrl+Alt+l) doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 26 12:35:49 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (345 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (201310
[Desktop-packages] [Bug 1373448] [NEW] Unable to set third button emulation on Atmel touchscreen
Public bug reported: My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 24 16:09:59 2014 DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:108d] InstallationDate: Installed on 2013-10-15 (343 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-18 (159 days ago) dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 24 16:08:42 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1373448 Title: Unable to set third button emulation on Atmel touchscreen Status in “xorg” package in Ubuntu: New Bug description: My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 24 16:09:59 201
[Desktop-packages] [Bug 1084938] Re: evdev settings doesn't work at all
Maybe it has usability problems, but in many cases the touchscreen is more confortable than a mouse. I don't believe that it is impossible or very difficult to modify the code so that a touchscreen behave similarly (or the same way) as the touchpad or mouse. In win8 Microsoft could do this. Canonical way not able to do? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Re: evdev settings doesn't work at all
O.K., I understand. But what would be the solution. I would like to use my touchscreen without mouse. But without mouse I haven't got right mouse button. Touch and hold my finger on the screen should replace the right click. I tried out easystroke with half success. Touch and hold worked, but the scrolling (e.g. in nautilus or evince) by sliding myfinger on the screen was switched off by easystroke. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Re: evdev settings doesn't work at all
The same issue like written in "Bug Description". My mashine is ASUS X202E. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211381/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211393/+files/xserver.devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211382/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211388/+files/UdevLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211390/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] LightdmGreeterLogOld.txt
apport information ** Attachment added: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211379/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211384/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211389/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211387/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] peripherals.txt
apport information ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211391/+files/peripherals.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211386/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211380/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] xinput.txt
apport information ** Attachment added: "xinput.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211392/+files/xinput.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211385/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211383/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211378/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211377/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Re: evdev settings doesn't work at all
ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu InstallationDate: Installed on 2013-10-15 (341 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MachineType: ASUSTeK COMPUTER INC. X202E Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: trusty ubuntu Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (157 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 22 14:49:59 2014 xserver.configfile: default xserver.errors: evdev: Atmel Atmel maXTouch Digitizer: ioctl EVIOCGBIT for bitmask in EvdevOpenMTDev failed: Inappropriate ioctl for device Atmel Atmel maXTouch Digitizer: Couldn't open mtdev device PreInit returned 2 for "Atmel Atmel maXTouch Digitizer" xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12380 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Tags added: apport-collected trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211375/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211376/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211372/+files/BootDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211374/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1084938] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1084938/+attachment/4211373/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: My machine is the new Samsung XE700T1C-A01CA, aka ATIV SmartPC Pro. It has the same touchscreen as the previous Series 7 slate, the Atmel maXTouch Digitizer. I modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following options to the touchscreen section: Option "EmulateThirdButton" "1" Option "EmulateThirdButtonButton" "3" Option "EmulateThirdButtonTimeout" "750" Option "EmulateThirdButtonThreshold" "50" and restarted X. Running xinput list-props shows that these properties are indeed set for the Atmel touchscreen device. However, when I touch and hold my finger in the same spot on the screen, nothing happens! I'm not sure what other files or output dumps would be useful for this bug (I'm a programmer but consider me a user as far as this stuff is concerned), so please let me know what else would be helpful and I will include it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+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 1319726] [NEW] In pixman_region32_init_rect: Invalid rectangle passed
Public bug reported: per***@A***oda:~$ /usr/lib/unity/unity-panel-service --lockscreen-mode *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2 [modified: usr/lib/unity/unity-panel-service] ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11 Uname: Linux 3.13.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 15 11:12:44 2014 DistUpgraded: 2014-04-21 23:59:37,219 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:5044] InstallationDate: Installed on 2013-02-15 (453 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-26-generic root=UUID=9e112b4e-2332-4bfd-850d-b576848ee2fa ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (23 days ago) dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33BU dmi.board.vendor: Intel Corporation dmi.board.version: AAD79951-407 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-407:cvn:ct2:cvr: version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 13 13:05:53 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22235 vendor GSM xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1319726 Title: In pixman_region32_init_rect: Invalid rectangle passed Status in “unity” package in Ubuntu: New Bug description: per***@A***oda:~$ /usr/lib/unity/unity-panel-service --lockscreen-mode *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2 [modified: usr/lib/unity/unity-panel-service] ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11 Uname: Linux 3.13.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: tru
[Desktop-packages] [Bug 1317391] [NEW] ginn error subscribing to gestures
Public bug reported: ginn doesn't work. To solve the problem, see http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary- default-multitouch-gestures-in-unity/90383#90383Answer #9 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 8 09:55:24 2014 InstallationDate: Installed on 2013-10-15 (204 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1317391 Title: ginn error subscribing to gestures Status in “unity” package in Ubuntu: New Bug description: ginn doesn't work. To solve the problem, see http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary- default-multitouch-gestures-in-unity/90383#90383Answer #9 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 8 09:55:24 2014 InstallationDate: Installed on 2013-10-15 (204 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1317391/+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 1239302] [NEW] Some word and excel document are not editable, which were editable inversion 4.0.*
Public bug reported: I can not edit somefiles, e.g. http://www.sze.hu/~perebal/launchpad/nevsor.xlsx ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 11:25:40 2013 InstallationDate: Installed on 2013-10-07 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1239302 Title: Some word and excel document are not editable, which were editable inversion 4.0.* Status in “libreoffice” package in Ubuntu: New Bug description: I can not edit somefiles, e.g. http://www.sze.hu/~perebal/launchpad/nevsor.xlsx ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 11:25:40 2013 InstallationDate: Installed on 2013-10-07 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1239302/+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 1236312] [NEW] X fails to start
Public bug reported: After upgradint to 13.10 (and installing unity8 and ubuntu-touch ?) X failed to start. The next error log was generated by X: (on ASUS X202E) [ 2397.673] X.Org X Server 1.14.3 Release Date: 2013-09-12 [ 2397.675] X Protocol Version 11, Revision 0 [ 2397.676] Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu [ 2397.677] Current Operating System: Linux ASUS-perebal 3.11.0-11-generic #17-Ubuntu SMP Tue Oct 1 19:42:04 UTC 2013 x86_64 [ 2397.677] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic.efi.signed root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro recovery nomodeset [ 2397.679] Build Date: 03 October 2013 03:20:13PM [ 2397.681] xorg-server 2:1.14.3-3ubuntu1 (For technical support please see http://www.ubuntu.com/support) [ 2397.682] Current version of pixman: 0.30.2 [ 2397.684]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2397.684] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2397.688] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 7 11:47:23 2013 [ 2397.690] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2397.690] (==) No Layout section. Using the first Screen section. [ 2397.690] (==) No screen section available. Using defaults. [ 2397.690] (**) |-->Screen "Default Screen Section" (0) [ 2397.690] (**) | |-->Monitor "" [ 2397.690] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 2397.690] (==) Automatically adding devices [ 2397.690] (==) Automatically enabling devices [ 2397.690] (==) Automatically adding GPU devices [ 2397.690] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 2397.690]Entry deleted from font path. [ 2397.690] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 2397.690]Entry deleted from font path. [ 2397.690] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 2397.690]Entry deleted from font path. [ 2397.690] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 2397.690]Entry deleted from font path. [ 2397.690] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 2397.690]Entry deleted from font path. [ 2397.690] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 2397.690] (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 2397.690] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2397.690] (II) Loader magic: 0x7fb3e2f4cd20 [ 2397.690] (II) Module ABI versions: [ 2397.690]X.Org ANSI C Emulation: 0.4 [ 2397.690]X.Org Video Driver: 14.1 [ 2397.690]X.Org XInput driver : 19.1 [ 2397.690]X.Org Server Extension : 7.0 [ 2397.691] (--) PCI:*(0:0:2:0) 8086:0166:1043:108d rev 9, Mem @ 0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64 [ 2397.691] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 2397.693] Initializing built-in extension Generic Event Extension [ 2397.694] Initializing built-in extension SHAPE [ 2397.695] Initializing built-in extension MIT-SHM [ 2397.696] Initializing built-in extension XInputExtension [ 2397.697] Initializing built-in extension XTEST [ 2397.698] Initializing built-in extension BIG-REQUESTS [ 2397.699] Initializing built-in extension SYNC [ 2397.700] Initializing built-in extension XKEYBOARD [ 2397.701] Initializing built-in extension XC-MISC [ 2397.702] Initializing built-in extension SECURITY [ 2397.703] Initializing built-in extension XINERAMA [ 2397.704] Initializing built-in extension XFIXES [ 2397.705] Initializing built-in extension RENDER [ 2397.706] Initializing built-in extension RANDR [ 2397.707] Initializing built-in extension COMPOSITE [ 2397.708] Initializing built-in extension DAMAGE [ 2397.709] Initializing built-in extension MIT-SCREEN-SAVER [ 2397.710] Initializing built-in extension DOUBLE-BUFFER [ 2397.710] Initializing built-in extension RECORD [ 2397.711] Initializing built-in extension DPMS [ 2397.712] Initializing built-in extension X-Resource [ 2397.713] Initializing built-in extension XVideo [ 2397.714] Initializing built-in extension XVideo-MotionCompensation [ 2397.715] Initializing built-in extension SELinux [ 2397.715] Initializing built-in extension XFree86-VidModeExtension [ 2397.716] Initializing built-in extension XFree86-DGA [ 2397.717] Initializing built-in extension XFree86-DRI [ 2397.718] Initializing built-in extension DRI2 [ 2397.718] (II) "glx" will be loaded by default. [ 2397.718] (WW) "xmir"
[Desktop-packages] [Bug 1220580] Re: nautilus crashes randomly with segmentation fault
I uninstalled Intel's 01.org drivers, because I thought the crash was caused by it. But no affect, nautilus crashes as before. -- 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/1220580 Title: nautilus crashes randomly with segmentation fault Status in “nautilus” package in Ubuntu: New Bug description: Sometimes when I push Alt key or click on an icon in natilus' window, nautilus crashes, the background of the screen becomes black. But other action can produc such a crash. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 [modified: usr/bin/nautilus usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server usr/lib/nautilus/nautilus-convert-metadata usr/lib/nautilus/nautilus-shell-search-provider] ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Wed Sep 4 10:17:56 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'831x554+360+202'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-01-30 (216 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-28 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1220580/+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 1220580] Re: nautilus crashes randomly with segmentation fault
Apport doesn't notice the problem, no bug reporting window appeard. Interesting, that any other of my computers doesn't produce such a problem. The affected computer is an ASUS X202E. -- 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/1220580 Title: nautilus crashes randomly with segmentation fault Status in “nautilus” package in Ubuntu: New Bug description: Sometimes when I push Alt key or click on an icon in natilus' window, nautilus crashes, the background of the screen becomes black. But other action can produc such a crash. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 [modified: usr/bin/nautilus usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server usr/lib/nautilus/nautilus-convert-metadata usr/lib/nautilus/nautilus-shell-search-provider] ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Wed Sep 4 10:17:56 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'831x554+360+202'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-01-30 (216 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-28 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1220580/+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 1220580] [NEW] nautilus crashes randomly with segmentation fault
Public bug reported: Sometimes when I push Alt key or click on an icon in natilus' window, nautilus crashes, the background of the screen becomes black. But other action can produc such a crash. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 [modified: usr/bin/nautilus usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server usr/lib/nautilus/nautilus-convert-metadata usr/lib/nautilus/nautilus-shell-search-provider] ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Wed Sep 4 10:17:56 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'831x554+360+202'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-01-30 (216 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-28 (128 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages -- 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/1220580 Title: nautilus crashes randomly with segmentation fault Status in “nautilus” package in Ubuntu: New Bug description: Sometimes when I push Alt key or click on an icon in natilus' window, nautilus crashes, the background of the screen becomes black. But other action can produc such a crash. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 [modified: usr/bin/nautilus usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server usr/lib/nautilus/nautilus-convert-metadata usr/lib/nautilus/nautilus-shell-search-provider] ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Wed Sep 4 10:17:56 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'831x554+360+202'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-01-30 (216 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-28 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1220580/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Sorry for that, and yes, it's a different bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Confirmed Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Confirmed Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 160311] Re: Resizing windows by grabbing window borders is difficult
I meant 10.12 :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Confirmed Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Confirmed Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Same problem with Ubuntu 12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Confirmed Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Confirmed Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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
