[Desktop-packages] [Bug 1789356] Re: In Ubuntu 18.10, the wrong background flashes up briefly during the login animation (since Yaru was introduced)
** Description changed: [Impact] The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) + + https://trello.com/c/dfrK5l8Q ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Cosmic) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress -- 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/1789356 Title: In Ubuntu 18.10, the wrong background flashes up briefly during the login animation (since Yaru was introduced) Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) https://trello.com/c/dfrK5l8Q ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme 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/1789356/+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 1813119] Re: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation
** Description changed: + https://trello.com/c/dfrK5l8Q + In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation. This has been separated from the 18.10 problem in bug 1789356 to avoid confusion. They have slightly different themes and require different fixes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 15:15:33 2019 DisplayManager: gdm3 GsettingsChanges: - b'org.gnome.shell' b'command-history' redacted by apport - b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' - b'org.gnome.shell' b'app-picker-view' b'uint32 1' - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'command-history' redacted by apport + b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' + b'org.gnome.shell' b'app-picker-view' b'uint32 1' + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1813119 Title: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation Status in gnome-shell package in Ubuntu: New Bug description: https://trello.com/c/dfrK5l8Q In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation. This has been separated from the 18.10 problem in bug 1789356 to avoid confusion. They have slightly different themes and require different fixes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 15:15:33 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) 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/1813119/+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 1789356] Re: In Ubuntu 18.10, the wrong background flashes up briefly during the login animation (since Yaru was introduced)
This is getting confusing because the Yaru theme is changing faster than we can release fixes to correct the related transitions. To address this confusion, let this bug be about 18.10 only. I have opened bug 1813119 to address the new problem in 19.04. ** Summary changed: - The wrong background flashes up briefly during the login animation since Yaru was introduced + In Ubuntu 18.10, the wrong background flashes up briefly during the login animation (since Yaru was introduced) ** Changed in: mutter (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: mutter (Ubuntu) Status: In Progress => Won't Fix -- 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/1789356 Title: In Ubuntu 18.10, the wrong background flashes up briefly during the login animation (since Yaru was introduced) Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Status in gnome-shell source package in Cosmic: Fix Released Status in mutter source package in Cosmic: In Progress Bug description: [Impact] The wrong background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme 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/1789356/+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 1813119] [NEW] In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation
Public bug reported: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation. This has been separated from the 18.10 problem in bug 1789356 to avoid confusion. They have slightly different themes and require different fixes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 15:15:33 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1813119 Title: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation Status in gnome-shell package in Ubuntu: New Bug description: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation. This has been separated from the 18.10 problem in bug 1789356 to avoid confusion. They have slightly different themes and require different fixes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 15:15:33 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) 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/1813119/+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 1010402] Re: Problem opening UNICODE file
Does this still occur on Ubuntu 18.10 "Cosmic Cuttlefish" with gedit 3.30.2-0ubuntu0.18.10.2? ** Changed in: gedit (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1010402 Title: Problem opening UNICODE file Status in gedit package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy gedit gedit: Installé : 3.4.1-0ubuntu1 Candidat : 3.4.1-0ubuntu1 Table de version : *** 3.4.1-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen gedit to open file What happened instead gedit has problem opening attached RawText file test.rc generated by Windows 7; edit displays: "There was a problem opening the file /mnt/hgfs/vmware/test/test.rc. The file you opened has some invalid characters. If you continue editing this file you could corrupt this document. You can also choose another character encoding and try again." MOST IMPORTANT INFO: After opening file test.rc with Windows' Notepad and removing 'END' at line 387, then saving file, gedit can open file without any problem. After re-adding 'END' at line 387 (using gedit or Notepad) and saving file, gedit can no longer open file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 8 05:37:04 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=fr_CA:fr TERM=xterm PATH=(custom, no user) LANG=fr_CA.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1010402/+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 305927] Re: gedit leaks memory
** Tags added: intrepid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/305927 Title: gedit leaks memory Status in gedit: Confirmed Status in gedit package in Ubuntu: Incomplete Bug description: Binary package hint: gedit It seems gedit doesn't release the memory used to open a file when closing it making it so use ridiculous space in ram for little files if you opened a big file and closed it. Strangely gnome system monitor reports a lower memory use under the processes tab, but reports the used ram in the resources tab and top actually gives the high amounts of used ram. To try this: 1- open gedit 2- open top 3- notice the ram use: 19393 weltall 20 0 38980 19m 10m S0 0.7 0:00.79 gedit 4- get a big file to open (mysql dumps are the best to try. I've tried with a ~50 mb dump) 5- you will notice an higher ram use, for sure > 300mb to open a 50mb file is a bit excessive but this is still an optimization issue which goes beyond this bug report: 19393 weltall 20 0 342m 305m 12m S2 10.1 3:02.14 gedit 6- close the tab which had the file 7- check again top no changes in ram use: 19393 weltall 20 0 342m 305m 12m S0 10.1 3:02.85 gedit this is definitely a memory leak or a bad ram retaining for future use implementation 8- try to reopen the file, gedit will take the same time to parse the file, but the increase of ram use is more little: 19393 weltall 20 0 381m 345m 12m S0 11.4 6:01.23 gedit 9- close the file again the ram use doesn't change again other gnome applications have similar leak issues like nautilus which after some days takes more than 300mb like nothing and closing windows doesn't release ram so maybe the problem might reside in underlying libraries. It seems applications like geany actually releases correctly the ram but i didn't investigate if they use similar libraries i'm using ubuntu intrepid with all the updates from normal repositories (altough this bug has been present since various releases) Description: Ubuntu 8.10 Release: 8.10 gedit: Installed: 2.24.2-0ubuntu1 Candidate: 2.24.2-0ubuntu1 Version table: *** 2.24.2-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 2.24.0-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/305927/+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 470383] Re: gedit crashes when opening files by dragging file icon over gedit application
Does this still occur on Ubuntu 18.10 "Cosmic Cuttlefish" with gedit 3.30.2-0ubuntu0.18.10.2? ** Changed in: gedit (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/470383 Title: gedit crashes when opening files by dragging file icon over gedit application Status in gedit package in Ubuntu: Incomplete Bug description: Binary package hint: gedit Version of Ububtu: 9.10 Gedit Version: 2.28.0-0ubuntu2 I quite often open files by dragging them over the top of an open application. This can be of great use when opening multiple files in multiple directories. Normally the file would open with no problems. In this case, I had opened about three previous XML files, and upon opening the new one, it showed a blank content (as if the file had no content), and then gedit crashed. The files were being opened from a Samba share, mounted using smb:// (rather than in fstab). I believe the connection to the Samba file system may have been dropped (as this happens with this specific file system on occasion). ProblemType: Crash Architecture: i386 Date: Mon Nov 2 09:26:25 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gedit NonfreeKernelModules: nvidia Package: gedit 2.28.0-0ubuntu2 ProcCmdline: gedit /home/username/.gvfs/snook\ on\ lmfdata2.shef.ac.uk/Data/_Final\ Images/Bogotana/Pronuclei\ -\ center\ line\ widest\ point/1\ 4-3-09/#1\ 4-3-09\ bogotana\ pro\ Sperm\ Curve\ Data\ (only\ red)\ -\ 24-4-09.xml ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SegvAnalysis: Segfault happened at: 0x7938e4: mov0x4(%eax),%ecx PC (0x007938e4) ok source "0x4(%eax)" (0x31223d72) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /lib/tls/i686/cmov/libc.so.6 malloc () from /lib/tls/i686/cmov/libc.so.6 IA__g_malloc (n_bytes=8811480) g_input_stream_real_skip_async (stream=0x8a1ac00, IA__g_input_stream_skip_async (stream=0x8a1ac00, Title: gedit crashed with SIGSEGV in malloc() Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/470383/+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 329500] Re: Gedit does not wrap around the right margin
Does this still occur on Ubuntu 18.10 "Cosmic Cuttlefish" with gedit 3.30.2-0ubuntu0.18.10.2? ** Changed in: gedit (Ubuntu) Status: Triaged => Incomplete ** Tags added: intrepid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/329500 Title: Gedit does not wrap around the right margin Status in gedit: Confirmed Status in gedit package in Ubuntu: Incomplete Bug description: Hi, I would like Gedit to doing word wrap automatically when the cursor reaches the right margin. Currently I have to expicitly press the enter key when the cursor comes close to the right margin. M To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/329500/+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 1104877] Re: gedit loses cursor when user rolls up its window
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1104877 Title: gedit loses cursor when user rolls up its window Status in gedit package in Ubuntu: Confirmed Bug description: System description: Ubuntu 12.04 LTS with GNOME Classic (using Compiz); gedit version: 3.4.1-0ubuntu1 Steps to reproduce the bug: 1. Activate roll up behaviour for the windows using gconf: /apps/gwd/mouse_wheel_action = shade 2. Roll up gedit window into window header scrolling up over window titlebar 3. Unroll gedit window by scrolling down over window titlebar After that document editing field loses focus and cursor. Focus can be returned when you click somewhere in the document, but cursor stays invisible and you cannot determine where it is located. Workaround: If you minimize, then restore back gedit window, then cursor reappears and behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1104877/+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 305927] Re: gedit leaks memory
Does this still occur on Ubuntu 18.10 "Cosmic Cuttlefish" with gedit 3.30.2-0ubuntu0.18.10.2? Several memory leaks were fixed in gedit 3.14.0-3. ** Changed in: gedit (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/305927 Title: gedit leaks memory Status in gedit: Confirmed Status in gedit package in Ubuntu: Incomplete Bug description: Binary package hint: gedit It seems gedit doesn't release the memory used to open a file when closing it making it so use ridiculous space in ram for little files if you opened a big file and closed it. Strangely gnome system monitor reports a lower memory use under the processes tab, but reports the used ram in the resources tab and top actually gives the high amounts of used ram. To try this: 1- open gedit 2- open top 3- notice the ram use: 19393 weltall 20 0 38980 19m 10m S0 0.7 0:00.79 gedit 4- get a big file to open (mysql dumps are the best to try. I've tried with a ~50 mb dump) 5- you will notice an higher ram use, for sure > 300mb to open a 50mb file is a bit excessive but this is still an optimization issue which goes beyond this bug report: 19393 weltall 20 0 342m 305m 12m S2 10.1 3:02.14 gedit 6- close the tab which had the file 7- check again top no changes in ram use: 19393 weltall 20 0 342m 305m 12m S0 10.1 3:02.85 gedit this is definitely a memory leak or a bad ram retaining for future use implementation 8- try to reopen the file, gedit will take the same time to parse the file, but the increase of ram use is more little: 19393 weltall 20 0 381m 345m 12m S0 11.4 6:01.23 gedit 9- close the file again the ram use doesn't change again other gnome applications have similar leak issues like nautilus which after some days takes more than 300mb like nothing and closing windows doesn't release ram so maybe the problem might reside in underlying libraries. It seems applications like geany actually releases correctly the ram but i didn't investigate if they use similar libraries i'm using ubuntu intrepid with all the updates from normal repositories (altough this bug has been present since various releases) Description: Ubuntu 8.10 Release: 8.10 gedit: Installed: 2.24.2-0ubuntu1 Candidate: 2.24.2-0ubuntu1 Version table: *** 2.24.2-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 2.24.0-0ubuntu1 0 500 http://it.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/305927/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
Actually there's a simpler solution. Please try this: Download the latest "daily" version of 18.04 and install that from scratch (wiping the previous install): http://cdimages.ubuntu.com/bionic/daily-live/current/bionic-desktop-amd64.iso You should then be completely free of bug 1727356 without needing to even update. But if the problem does still happen after that then please: 1. Reproduce the problem of the login screen not appearing (without using recovery mode). 2. Reboot and start in recovery mode. 3. Run: journalctl -b-1 > prev_boot.txt and send us the resulting file 'prev_boot.txt'. -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1812996] Re: Dock focus bug with Virtualbox
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 What I can't explain here, is the ghost window that seems to appear for Virtualbox: there is alternatively one or two dots next to Virtualbox icon in the dock (while there is no need because no VM/ no secondary instance of this app is launched) I realised this thanks to the focus bug #1812407 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1812996 Title: Dock focus bug with Virtualbox Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: There is a graphical bug with Dock/virtualbox when other apps like Chrome are displayed on full screen. Virtualbox icon on dock continuously switch between 1 or 2 windows (even if No VM is launched) , resulting in modification of icons/dock size this disappear if I reduce the Chrome window See screen capture to have an idea of the visual output. Ubuntu 18.10 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812996/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
Thanks. Unfortunately I can only see problems caused by your changes so it's hard or even impossible to see the original problem. Please undo these changes (or just reinstall Ubuntu and don't redo them): * lightdm is installed. Please uninstall it. * The kernel is starting without modesetting support. Please remove 'nomodeset' from your kernel command line. * Xorg is using the Intel driver when it should be using modesetting instead. Please remove your xorg.conf config files. The modesetting driver should work after you have removed 'nomodeset' from your kernel command line. * GDM isn't trying to use Wayland. Please comment out WaylandEnable=false from /etc/gdm3/custom.conf. This should work after you have removed 'nomodeset' from your kernel command line and have mutter >= 3.28.3-2~ubuntu18.04.2 If you choose to reinstall then you will need to temporarily use the workaround from bug 1727356 again (WaylandEnable=false). But you should only need that prior to installing the fix: mutter >= 3.28.3-2~ubuntu18.04.2 Then you can comment it out again (#WaylandEnable=false). So once you have undone ALL of those changes or reinstalled Ubuntu and updated, please: 1. Reproduce the problem of the login screen not appearing. 2. Reboot and start in recovery mode. 3. Run: journalctl -b-1 > prev_boot.txt and send us the resulting file 'prev_boot.txt'. -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1813103] Re: Xorg crash of a sort
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 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 1769383, 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 1769383 Ubuntu dock/launcher is shown on the lock screen -- 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/1813103 Title: Xorg crash of a sort Status in xorg package in Ubuntu: New Bug description: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid: /apps/compiz-1/plugins/grid/screen0: /apps/compiz-1/plugins/grid/screen0/options: top_edge_action = 0 GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2713] InstallationDate: Installed on 2018-09-07 (138 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=56cc0abb-f0c5-41da-9704-c934188702fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813103/+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 778872] Re: vte use causes /tmp file writing during text scrolling
Some interesting relatively recent discussion at LP: #1430620 Although Ubuntu patched vte years ago, vte2.91 was never patched. ** Bug watch added: GNOME Bug Tracker #631685 https://bugzilla.gnome.org/show_bug.cgi?id=631685 ** Changed in: vte Importance: Medium => Unknown ** Changed in: vte Status: Fix Released => Unknown ** Changed in: vte Remote watch: GNOME Bug Tracker #664611 => GNOME Bug Tracker #631685 ** Changed in: vte2.91 (Ubuntu) Status: Confirmed => Triaged ** Changed in: vte2.91 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/778872 Title: vte use causes /tmp file writing during text scrolling Status in Gnome Virtual Terminal Emulator: Unknown Status in vte package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Triaged Bug description: Binary package hint: terminator If you open gnome-terminal, and run: inotifywait -mr /tmp You can watch files in /tmp. If you cause a terminator window to scroll (ls -la /usr) you'll see many temp files being created and deleted. This doesn't happen with gnome-terminal, and I do not have "infinite scrollback" selected in terminator. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: terminator 0.95-1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Sat May 7 07:18:15 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: terminator UpgradeStatus: Upgraded to natty on 2011-01-11 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/778872/+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 778872] Re: vte use causes /tmp file writing during text scrolling
** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/778872 Title: vte use causes /tmp file writing during text scrolling Status in Gnome Virtual Terminal Emulator: Unknown Status in vte package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Triaged Bug description: Binary package hint: terminator If you open gnome-terminal, and run: inotifywait -mr /tmp You can watch files in /tmp. If you cause a terminator window to scroll (ls -la /usr) you'll see many temp files being created and deleted. This doesn't happen with gnome-terminal, and I do not have "infinite scrollback" selected in terminator. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: terminator 0.95-1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Sat May 7 07:18:15 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: terminator UpgradeStatus: Upgraded to natty on 2011-01-11 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/778872/+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 778872] Re: vte use causes /tmp file writing during text scrolling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vte2.91 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/778872 Title: vte use causes /tmp file writing during text scrolling Status in Gnome Virtual Terminal Emulator: Unknown Status in vte package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Triaged Bug description: Binary package hint: terminator If you open gnome-terminal, and run: inotifywait -mr /tmp You can watch files in /tmp. If you cause a terminator window to scroll (ls -la /usr) you'll see many temp files being created and deleted. This doesn't happen with gnome-terminal, and I do not have "infinite scrollback" selected in terminator. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: terminator 0.95-1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Sat May 7 07:18:15 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: terminator UpgradeStatus: Upgraded to natty on 2011-01-11 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/778872/+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 1740804] Re: Remove old vte package from Ubuntu
We're just going to follow Debian for this removal. ** Changed in: vte (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1740804 Title: Remove old vte package from Ubuntu Status in vte package in Ubuntu: Invalid Bug description: NOTE Debian's debian-installer (specifically cdebconf-gtk-terminal I believe) uses a udeb from the old vte package. See https://bugs.debian.org/887649 Original Bug Report === The old vte source hasn't been maintained upstream since 2011 (when GNOME 3 was released). vte will be dropped from Debian Testing as soon as the debian-installer is ported. The replacement is provided by source vte2.91 (which requires gtk3). sjterm was already requested for removal in LP: #1728241 $ reverse-depends src:vte Reverse-Depends === * stjerm(for libvte9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1740804/+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 1740792] Re: Automatic login still requires user password after suspend/hibernate
I agree with Wolf. To me login and unlock are the same (login is first unlock and unlock is any subsequent unlock), and I expect the setting to not ask for a password to apply in both cases. -- 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/1740792 Title: Automatic login still requires user password after suspend/hibernate Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 package in Baltix: Confirmed Bug description: Description: Ubuntu 17.10 Release: 17.10 gnome-control-center 3.26.2 When I set Ubuntu to automatically login a user the user still has to enter their password when resuming from a suspended session. The only option I can find to fix this is to disable the lock-screen completely, which I don't want to since I still want it to be an option to manually lock it. Setting Privacy > Screen Lock to off doesn't affect this behavior at all. The solution seems to be to use dconf-editor and change org.gnome.desktop.screensaver.ubuntu-lock-on-suspend to false. I got the solution after asking on askubuntu.com: https://askubuntu.com/questions/990056/turn-off-requesting-user- password-after-suspend-17-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1740792/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package wget - 1.20.1-1ubuntu3 --- wget (1.20.1-1ubuntu3) disco; urgency=medium * Revert switching to pcre3 since pcre2 is in main (LP: #1792544) -- Jeremy Bicha Wed, 23 Jan 2019 11:56:34 -0500 ** Changed in: wget (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1116601] Re: gedit *** glibc detected *** gedit: munmap_chunk(): invalid pointer
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1116601 Title: gedit *** glibc detected *** gedit: munmap_chunk(): invalid pointer Status in gedit package in Ubuntu: Expired Bug description: When try to start gedit -> application went crash. lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 apt-cache policy gedit gedit: Installed: 3.6.1-0ubuntu1 Candidate: 3.6.1-0ubuntu1 Version table: *** 3.6.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.6.0-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages Dump info: Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "overlay-scrollbar" *** glibc detected *** gedit: munmap_chunk(): invalid pointer: 0x012e30c7 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f0aa906fb96] /usr/lib/libgtk-3.so.0(gtk_theming_engine_register_property+0xc1)[0x7f0aabb18171] /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so(+0x2560)[0x7f0a9ddc3560] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_class_ref+0x4d6)[0x7f0aa9bee926] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new_valist+0x6d)[0x7f0aa9bd6ecd] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0xd4)[0x7f0aa9bd7374] /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so(create_engine+0x28)[0x7f0a9ddc38d8] /usr/lib/libgtk-3.so.0(gtk_theming_engine_load+0xcb)[0x7f0aabb1d2bb] /usr/lib/libgtk-3.so.0(+0xcd435)[0x7f0aab9d5435] /usr/lib/libgtk-3.so.0(+0xce2a4)[0x7f0aab9d62a4] /usr/lib/libgtk-3.so.0(+0xce8c7)[0x7f0aab9d68c7] /usr/lib/libgtk-3.so.0(+0xce56b)[0x7f0aab9d656b] /usr/lib/libgtk-3.so.0(+0xce8c7)[0x7f0aab9d68c7] /usr/lib/libgtk-3.so.0(gtk_css_provider_get_named+0x14f)[0x7f0aab9d702f] /usr/lib/libgtk-3.so.0(+0x1b193f)[0x7f0aabab993f] /usr/lib/libgtk-3.so.0(gtk_settings_get_for_screen+0x112)[0x7f0aabab9af2] /usr/lib/libgtk-3.so.0(gtk_icon_theme_set_screen+0xaf)[0x7f0aaba24a9f] /usr/lib/libgtk-3.so.0(gtk_icon_theme_get_for_screen+0x82)[0x7f0aaba24c52] gedit(main+0x127)[0x427f37] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f0aa901276d] gedit[0x428329] === Memory map: 0040-004a r-xp 103:0e 14031913 /usr/bin/gedit 006a-006a2000 r--p 000a 103:0e 14031913 /usr/bin/gedit 006a2000-006a5000 rw-p 000a2000 103:0e 14031913 /usr/bin/gedit 012cf000-01352000 rw-p 00:00 0 [heap] 7f0a9000-7f0a90022000 rw-p 00:00 0 7f0a90022000-7f0a9400 ---p 00:00 0 7f0a9800-7f0a98022000 rw-p 00:00 0 7f0a98022000-7f0a9c00 ---p 00:00 0 7f0a9dbab000-7f0a9dbc r-xp 103:0e 11012570 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f0a9dbc-7f0a9ddbf000 ---p 00015000 103:0e 11012570 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f0a9ddbf000-7f0a9ddc r--p 00014000 103:0e 11012570 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f0a9ddc-7f0a9ddc1000 rw-p 00015000 103:0e 11012570 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f0a9ddc1000-7f0a9ddc4000 r-xp 103:0e 3950249 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 7f0a9ddc4000-7f0a9dfc4000 ---p 3000 103:0e 3950249 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 7f0a9dfc4000-7f0a9dfc5000 r--p 3000 103:0e 3950249 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 7f0a9dfc5000-7f0a9dfc6000 rw-p 4000 103:0e 3950249 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so 7f0a9dfc6000-7f0a9dfc7000 ---p 00:00 0 7f0a9dfc7000-7f0a9e7c7000 rw-p 00:00 0 [stack:2443] 7f0a9e7c7000-7f0a9e7c8000 ---p 00:00 0 7f0a9e7c8000-7f0a9efc8000 rw-p 00:00 0 [stack:2442] 7f0a9efc8000-7f0aa4756000 r--p 103:0e 4470451 /usr/lib/locale/locale-archive 7f0aa4756000-7f0aa475b000 r-xp 103:0e 8264205 /usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0 7f0aa475b000-7f0aa495a000 ---p 5000 103:0e 8264205 /usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0 7f0aa495a000-7f0aa495b000 r--p 4000 103:0e 8264205 /usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0 7f0aa495b000-7f0aa495c000 rw-p 5000 103:0e 8264205
[Desktop-packages] [Bug 963033] Re: gedit crashed with SIGABRT in __libc_message()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/963033 Title: gedit crashed with SIGABRT in __libc_message() Status in gedit package in Ubuntu: Expired Bug description: Gedit crashed when I was trying to save file with another name (by Save as... function in "File" menu). File didn't become saved. Really sorry if I duplicated error no 832117 unnecessarily. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 13:04:27 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120322) ProcCmdline: gedit ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gedit Title: gedit crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/963033/+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 1050385] Re: Gedit crashes when opening a new file
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1050385 Title: Gedit crashes when opening a new file Status in gedit package in Ubuntu: Expired Bug description: (gedit:24486): Gtk-CRITICAL **: gtk_device_grab_add: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gdk-CRITICAL **: gdk_device_grab: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gdk-CRITICAL **: gdk_device_ungrab: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gtk-CRITICAL **: gtk_device_grab_remove: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gtk-CRITICAL **: gtk_device_grab_add: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gdk-CRITICAL **: gdk_device_grab: assertion `GDK_IS_DEVICE (device)' failed (gedit:24486): Gdk-ERROR **: The program 'gedit' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 250 error_code 3 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 Date: Thu Sep 13 13:52:19 2012 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LANGUAGE=fr:en TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to quantal on 2011-04-01 (531 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1050385/+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 993310] Re: Tearing/blinking text while scrolling
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/993310 Title: Tearing/blinking text while scrolling Status in gedit package in Ubuntu: Expired Bug description: This is new stuff since upgrade to 12.04 from 11.10 (gedit version 3.4.1). When I scroll text in gedit, the text appears to blink as I scroll generating an unpleasant effect, a bit dazzling. If the window is unactive and I scroll the text, I don't get this behavior. It is almost as if the window was being redrawn twice everytime I scroll, once as a white square, once with the new text. What could be the cause for this? Other apps don't seem to have this problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 Uname: Linux 3.4.0-030400rc4-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 2 10:27:00 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gedit UpgradeStatus: Upgraded to precise on 2012-04-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/993310/+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 971110] Re: gedit crashed with SIGSEGV in gdk_property_change()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/971110 Title: gedit crashed with SIGSEGV in gdk_property_change() Status in gedit package in Ubuntu: Expired Bug description: This bug just occured on a 12.04 systems with the most recent updates installed. The file that caused the crash is attached. Note that I edited the attached file without any problems using other editors such as Emacs. Everytime I open it with GEdit however, the program crashes after struggling a bit. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CheckboxSubmission: 05c436e63dfa019ccd464d7387e4a841 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Sun Apr 1 23:28:20 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824) ProcCmdline: gedit /home/username/Dropbox/ASE/H2\ -\ Ingo/homework2.tex SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit Title: gedit crashed with SIGSEGV in gdk_property_change() UpgradeStatus: Upgraded to precise on 2012-01-12 (80 days ago) UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/971110/+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 954811] Re: gedit crashed with SIGABRT in g_assertion_message()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/954811 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Expired Bug description: When i try open file ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 14 09:52:03 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcCmdline: gedit /media/gamesite/sub/test/plugins/search/phocagallery.php Signal: 6 SourcePackage: gedit StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgtksourceview-3.0.so.0 Title: gedit crashed with SIGABRT in raise() UpgradeStatus: Upgraded to precise on 2012-03-12 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/954811/+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 992095] Re: crashes on start, when adding Dashboard plugin, after using a smb/server file to view.
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/992095 Title: crashes on start, when adding Dashboard plugin, after using a smb/server file to view. Status in gedit package in Ubuntu: Expired Bug description: launching gedit from terminal i see: /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject (gedit:6331): Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases ** ERROR:/build/buildd/pygobject-3.2.0/gi/_gobject/pygobject.c:929:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) launching gedit as superuser, no problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 Date: Mon Apr 30 13:45:12 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/992095/+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 1072008] Re: Gedit filebrowser folder dropdown not working correctly
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1072008 Title: Gedit filebrowser folder dropdown not working correctly Status in gedit package in Ubuntu: Expired Bug description: When browsing subfolders in gedit's filebrowser, the parent folders dropdown on the top should show the parent folders in a nested way. But what it does is to indent all entries like the last one in the hierarchy. I attached a screenshot to show the problem. Ubuntu version: Ubuntu 12.10 (but also happens in 12.04 and 11.10) Gedit version: 3.6.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1072008/+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 1036629] Re: gedit asks for FTP password very very too often
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1036629 Title: gedit asks for FTP password very very too often Status in gedit package in Ubuntu: Expired Bug description: Each time I open a file over FTP with gedit I get asked for my password several times. This also occurs when I switch from one tab to another and even when I mark text in gedit. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.5.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Tue Aug 14 14:11:41 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) SourcePackage: gedit UpgradeStatus: Upgraded to quantal on 2012-08-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1036629/+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 1033618] Re: The program 'gedit' received an X Window System error.
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1033618 Title: The program 'gedit' received an X Window System error. Status in gedit package in Ubuntu: Expired Bug description: Trace/breakpoint trap (core dumped) moma@precise32:~/desktop-radio$ (gedit:2625): Gdk-WARNING **: The program 'gedit' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 233477 error_code 3 request_code 143 minor_code 51) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 Date: Mon Aug 6 19:42:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1033618/+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 942274] Re: gedit crashed with SIGSEGV in gtk_style_context_get_valist()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/942274 Title: gedit crashed with SIGSEGV in gtk_style_context_get_valist() Status in gedit package in Ubuntu: Expired Bug description: This occurred while I was attempting to drag a tab from one gedit window to another. The tab didn't move when dragged with the mouse, instead the entire application crashed. I've attempted to reproduce this and couldn't, so am unsure exactly what conditions cause the bug. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 16:54:26 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120221) ProcCmdline: gedit ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f48779d33a7 : mov0x30(%rax),%rdx PC (0x7f48779d33a7) ok source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: gtk_style_context_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_style_context_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_style_context_set_background () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in gtk_style_context_get_valist() UpgradeStatus: Upgraded to precise on 2012-02-26 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/942274/+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 932375] Re: gedit crashed with SIGSEGV in instance_get_window()
[Expired for gedit-valencia-plugin (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit-valencia-plugin (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/932375 Title: gedit crashed with SIGSEGV in instance_get_window() Status in gedit package in Ubuntu: Expired Status in gedit-valencia-plugin package in Ubuntu: Expired Bug description: Going through the Checkbox Unity Tests for Unity 5.4, got to test #120 and tried on gedit. When right-clicking on the gedit title bar and selecting close, the first time nothing happens, when doing it a second time, gedit crashes. Steps to reproduce: 1. Start gedit 2. Right-click on the title bar 3. Select "Close": nothing happen 4. Right-click on the title bar again 5. Select "Close": gedit crashes Expected behaviour gedit closes on step 3 Actual behaviour gedit crashes on step 5 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Feb 14 22:06:21 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: gedit ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9f15a300fb : mov (%rax),%rax PC (0x7f9f15a300fb) ok source "(%rax)" (0x0001) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: instance_get_window () from /usr/lib/gedit/plugins/libvalencia.so instance_active_filename () from /usr/lib/gedit/plugins/libvalencia.so instance_active_document_is_vala_file () from /usr/lib/gedit/plugins/libvalencia.so ?? () from /usr/lib/gedit/plugins/libvalencia.so ?? () from /usr/lib/gedit/plugins/libvalencia.so Title: gedit crashed with SIGSEGV in instance_get_window() UpgradeStatus: Upgraded to precise on 2012-02-11 (3 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/932375/+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 946794] Re: gedit crashed with SIGABRT: get_icon_fallback() "retval != NULL"
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/946794 Title: gedit crashed with SIGABRT: get_icon_fallback() "retval != NULL" Status in gedit package in Ubuntu: Expired Bug description: gedit crashed with SIGABRT in __kernel_vsyscall() ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: gedit 2.30.4-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-13.56-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Mon Mar 5 05:01:49 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) ProcCmdline: gedit /home/username/Рабочий\ стол/новый\ файл\ (другая\ копия) ProcEnviron: LANG=ru_RU.utf8 SHELL=/bin/bash Signal: 6 SourcePackage: gedit StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: gedit crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: Upgraded to natty on 2012-03-05 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/946794/+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 1813103] [NEW] Xorg crash of a sort
Public bug reported: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid: /apps/compiz-1/plugins/grid/screen0: /apps/compiz-1/plugins/grid/screen0/options: top_edge_action = 0 GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2713] InstallationDate: Installed on 2018-09-07 (138 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=56cc0abb-f0c5-41da-9704-c934188702fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1813103/+attachment/5231879/+files/kernel_log.txt -- 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/1813103 Title: Xorg crash of a sort Status in xorg package in Ubuntu: New Bug description: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid:
[Desktop-packages] [Bug 736842] Re: No application associated to .xcf even if The Gimp is installed
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/736842 Title: No application associated to .xcf even if The Gimp is installed Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox When clicking on an .xcf file from Firefox, The Gimpo should be proposed to open it if installed, or it should be proposed to install it if it's not (which is the default). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0~rc1+build1+nobinonly-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic x86_64 Architecture: amd64 Date: Thu Mar 17 07:31:24 2011 FirefoxPackages: firefox 4.0~rc1+build1+nobinonly-0ubuntu1 flashplugin-installer N/A adobe-flashplugin N/A icedtea-plugin N/A InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110315) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/736842/+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 932375] Re: gedit crashed with SIGSEGV in instance_get_window()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/932375 Title: gedit crashed with SIGSEGV in instance_get_window() Status in gedit package in Ubuntu: Expired Status in gedit-valencia-plugin package in Ubuntu: Expired Bug description: Going through the Checkbox Unity Tests for Unity 5.4, got to test #120 and tried on gedit. When right-clicking on the gedit title bar and selecting close, the first time nothing happens, when doing it a second time, gedit crashes. Steps to reproduce: 1. Start gedit 2. Right-click on the title bar 3. Select "Close": nothing happen 4. Right-click on the title bar again 5. Select "Close": gedit crashes Expected behaviour gedit closes on step 3 Actual behaviour gedit crashes on step 5 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Feb 14 22:06:21 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: gedit ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9f15a300fb : mov (%rax),%rax PC (0x7f9f15a300fb) ok source "(%rax)" (0x0001) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: instance_get_window () from /usr/lib/gedit/plugins/libvalencia.so instance_active_filename () from /usr/lib/gedit/plugins/libvalencia.so instance_active_document_is_vala_file () from /usr/lib/gedit/plugins/libvalencia.so ?? () from /usr/lib/gedit/plugins/libvalencia.so ?? () from /usr/lib/gedit/plugins/libvalencia.so Title: gedit crashed with SIGSEGV in instance_get_window() UpgradeStatus: Upgraded to precise on 2012-02-11 (3 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/932375/+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 935906] Re: Toolbar missing in some filetypes
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/935906 Title: Toolbar missing in some filetypes Status in gedit package in Ubuntu: Expired Bug description: Gedit just for a moment shows a toolbar in certain filetypes, then the toolbar gone, but left a blank space between the main toolbar and the documents tabs. This happen in html, css, php, python. But not in txt files. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6 Uname: Linux 3.2.0-16-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 20:04:07 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120216) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/935906/+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 899158] Re: gedit assert failure: *** glibc detected *** gedit: free(): invalid pointer: 0xb6d02118 ***
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/899158 Title: gedit assert failure: *** glibc detected *** gedit: free(): invalid pointer: 0xb6d02118 *** Status in gedit: Incomplete Status in gedit package in Ubuntu: Expired Bug description: Running Maverick-Linux-in-Live-mode. Opened mozilla-firefox 3.6 and launched About to verify any upgrades available. Also, opened multiple tabs while reading Mozilla.org documentation. Downloaded '.tar.gz' archive of browser v8.0.1. Comparing the '.ini' and '.xml' files to see whats new in the upgraded version, using gedit. While just trying to paste the upgraded-version-of-browser to replace the one installed by OS by default in Live-Mode. Also, a window is kept open for accessing a shared-folder on intranet. Thanks, K Chandrasekhar Omkar. http://kcomkar.pip.verisignlabs.com/ http://kcomkar.mp/ http://omkarkc.blogspot.com/ kcom...@gmail.com kcom...@android.net ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: gedit 2.30.3-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 AssertionMessage: *** glibc detected *** gedit: free(): invalid pointer: 0xb6d02118 *** Date: Fri Dec 2 18:42:31 2011 ExecutablePath: /usr/bin/gedit LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcCmdline: gedit /home/username/Desktop/Mozilla-Firefox-801/firefox/searchplugins/google.xml ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gedit StacktraceTop: __kernel_vsyscall () raise () from /lib/libc.so.6 abort () from /lib/libc.so.6 ?? () from /lib/libc.so.6 ?? () from /lib/libc.so.6 Title: gedit assert failure: *** glibc detected *** gedit: free(): invalid pointer: 0xb6d02118 *** UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/899158/+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 575278] Re: gedit won't exit and consumes 100% CPU
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/575278 Title: gedit won't exit and consumes 100% CPU Status in gedit package in Ubuntu: Expired Bug description: Binary package hint: gedit Start gedit and do nothing. Quit gedit check top and gedit is still in memory at at 200% CPU and system heats up. Kill gedit (with kill or from system monitor) CPU drops to normal levels. Let me know if you want more logs/info This bug is a potential system damage bug if fans in laptops and such can't keep up with a 100% duty cycle for extended periods. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gedit 2.30.0git20100413-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 4 10:06:39 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/575278/+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 952965] Re: gedit crashed with SIGSEGV in scroll_to_cursor()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/952965 Title: gedit crashed with SIGSEGV in scroll_to_cursor() Status in gedit package in Ubuntu: Expired Bug description: I opened text file(~3 MB) and trying to close tab with them. Loading progress didn't disappear. P.S. Sorry for my English. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gedit 3.3.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Mon Mar 12 14:40:47 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120130) ProcCmdline: gedit /home/User Name/workspace/pbrt2obj/hybrid/PBRT_to_OBJ/bin/spheres-differentials-texfilt.pbrt SegvAnalysis: Segfault happened at: 0x80838f6: mov0x8(%eax),%eax PC (0x080838f6) ok source "0x8(%eax)" (0xaab2) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: gedit crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to precise on 2012-03-12 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/952965/+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 1247370] Re: Gedit launched from terminal : Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1247370 Title: Gedit launched from terminal : Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed Status in gedit package in Ubuntu: Expired Bug description: I launch gedit from terminal and it shows: (gedit:11995): Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed if I open a file: (gedit:12698): Gtk-CRITICAL **: gtk_container_remove: assertion `gtk_widget_get_parent (widget) == GTK_WIDGET (container) || GTK_IS_ASSISTANT (container)' failed if I click file open ... on show of file picker: (gedit:12698): Gtk-CRITICAL **: gtk_tree_selection_get_selected: assertion `GTK_IS_TREE_SELECTION (selection)' failed After i do it at first time, no more error messages are spammed. If i close and i re-open, same story. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Nov 2 12:34:12 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1247370/+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 1470590] Re: Unable to save some files as root: An unexpected error: Error writing a file: Invalid argument
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1470590 Title: Unable to save some files as root: An unexpected error: Error writing a file: Invalid argument Status in gedit package in Ubuntu: Expired Bug description: My system: Ubuntu 15.04 I had edited as root the /etc/mtab file and while trying to save it, I had recieved follownig error message (typed as displayed): "Unable to save /etc/mtab". An unexpected error: Error writing a file: Invalid argument Additionally, it's independant from if the backups are enabled or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1470590/+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 1174471] Re: random gedit crash
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1174471 Title: random gedit crash Status in gedit package in Ubuntu: Expired Bug description: I was just typing, editing a file (with a few other opened in other tabs). Suddenly Gedit started consuming a lot of cpu and after a few seconds it crashed. Upon restart, it didn't even give me an option to restore the unsaved file from a backup, which is the worst thing. Doesn't gedit automatically save a hidden backup every very few seconds as ALL decent text editing programs do, from vim to LibreOffice?? that's unbelievable. If it does, then it "forgot" to ask me whether I wanted to restore it. I lost all the unsaved changes. Hope this report gets the relevant files attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Mon Apr 29 20:33:03 2013 InstallationDate: Installed on 2010-06-23 (1041 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to quantal on 2013-01-13 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1174471/+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 1375986] Re: gedit crashed with SIGSEGV in gtk_tree_row_ref_deleted()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1375986 Title: gedit crashed with SIGSEGV in gtk_tree_row_ref_deleted() Status in gedit package in Ubuntu: Expired Bug description: It crashed while open in the background doing nothing. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gedit 3.10.4-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 23:06:06 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-05-22 (131 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) ProcCmdline: gedit /var/src/mozilla-central/nsprpub/pr/include/md/_linux.h SegvAnalysis: Segfault happened at: 0x7fd3279ebd51:cmp%ecx,(%r10,%rax,1) PC (0x7fd3279ebd51) ok source "%ecx" ok destination "(%r10,%rax,1)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1375986/+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 1211768] Re: gedit not load after crash
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1211768 Title: gedit not load after crash Status in gedit package in Ubuntu: Expired Bug description: root: gedit ioctl.c Timeout was reached and killall gedit as root not working ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gedit 3.8.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Tue Aug 13 16:18:16 2013 InstallationDate: Installed on 2013-08-10 (3 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130810) MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1211768/+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 1187436] Re: gedit crashed with SIGABRT in g_assertion_message()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1187436 Title: gedit crashed with SIGABRT in g_assertion_message() Status in gedit package in Ubuntu: Expired Bug description: I often get this bug, expecialy while editing file directly from a FTP server. I've not experienced this error on distro before 13.10. Don't hesitate to ask any question about this, I'll be pleased to help. Adrien ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Jun 4 17:10:21 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2012-06-30 (338 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcCmdline: gedit /home/username/.cache/.fr-wMFrle/L_18624BC0081B_130604_123605.xml ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gedit StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtksourceview-3.0.so.0 Title: gedit crashed with SIGABRT in raise() UpgradeStatus: Upgraded to raring on 2013-04-20 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1187436/+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 1434931] Re: Gedit missing exit, preferences and help
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1434931 Title: Gedit missing exit, preferences and help Status in gedit package in Ubuntu: Expired Bug description: Gedit is missing several menu items: The exit option under File is gone, there's only close which just closes my current tab. Preferences are missing from the Edit menu There is no help menu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 gedit version: 3.10.4-0ubuntu8 Using gnome-flashback (Metacity) for my current session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1434931/+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 1385738] Re: Cannot use TAB to choose symbol from ibus-mozc in gedit 3.10.4-0ubuntu6
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1385738 Title: Cannot use TAB to choose symbol from ibus-mozc in gedit 3.10.4-0ubuntu6 Status in gedit package in Ubuntu: Expired Bug description: When ibus-mozc for Japanese input is installed and activated in gedit I cannot choose the symbols with TAB. Instead gedit just writes a TAB. Also with clicking on the symbol I cannot choose them. This way I cannot use gedit and ibus-mozc because I can just type Hiragana and Katakana but no Kanji. Choosing the symbols from the drop down list works in Firefox, LibreOffice Writer and the Gnome Terminal. This is why I think it is a bug in gedit. It used to work in Ubuntu 14.04. Just updated to Ubuntu 14.10. Did a clean installation i.e. formated the entire disk before installation. Description: Ubuntu 14.10 Release: 14.10 gedit: Installed: 3.10.4-0ubuntu6 Candidate: 3.10.4-0ubuntu6 Version table: *** 3.10.4-0ubuntu6 0 500 http://ftp.uni-stuttgart.de/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1385738/+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 1438128] Re: gedit crashed with SIGSEGV in gtk_action_group_get_action()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1438128 Title: gedit crashed with SIGSEGV in gtk_action_group_get_action() Status in gedit package in Ubuntu: Expired Bug description: just opened two tabs with text in gedit ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gedit 3.10.4-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 30 13:36:37 2015 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2015-03-27 (2 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcCmdline: gedit /home/username/Desktop/gpuintel SegvAnalysis: Segfault happened at: 0x7f8764f5796c : cmp%rax,0x0(%rbp) PC (0x7f8764f5796c) ok source "%rax" ok destination "0x0(%rbp)" (0x4) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: gtk_action_group_get_action () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in gtk_action_group_get_action() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1438128/+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 1248814] Re: gedit kill, maybe segmentation fault
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1248814 Title: gedit kill, maybe segmentation fault Status in gedit package in Ubuntu: Expired Bug description: text document, (1) ctrl-c -> (2) ctrl-v -> (3) change to korean input(= Hangul ?) -> (4) when enter key, then kill ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gedit 3.8.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 7 12:35:01 2013 InstallationDate: Installed on 2013-01-19 (291 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gedit UpgradeStatus: Upgraded to saucy on 2013-11-01 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1248814/+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 1249764] Re: Doesn't respond to scroll (almost); restarting fixes the issue
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1249764 Title: Doesn't respond to scroll (almost); restarting fixes the issue Status in gedit package in Ubuntu: Expired Bug description: Up to now it has happened to me only once: - I opened a file (a .js file) in Gedit by double clicking in nautilus - Gedit would not respond to scroll, or it would respond with HUGE slowness, i.e. several seconds after moving the scroll bar or mouse wheel it would actually scroll - Closing and restarting Gedit fixed the issue (I've opened the same file and it works fine). The file is not especially big nor does it have especially long lines. I think this was totally random. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Sun Nov 10 13:21:06 2013 InstallationDate: Installed on 2013-10-11 (29 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1249764/+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 1247469] Re: gedit launched from terminal: On closing preferences window, Gtk-CRITICAL **: gtk_tree_selection_get_selected: assertion `GTK_IS_TREE_SELECTION (selection)' failed
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1247469 Title: gedit launched from terminal: On closing preferences window, Gtk- CRITICAL **: gtk_tree_selection_get_selected: assertion `GTK_IS_TREE_SELECTION (selection)' failed Status in gedit package in Ubuntu: Expired Bug description: When I start gedit from the terminal, and go to Edit --> Preferences, and then close the Preferences window, I get the error message "Gtk- CRITICAL **: gtk_tree_selection_get_selected: assertion `GTK_IS_TREE_SELECTION (selection)' failed" in the terminal window. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Nov 2 16:19:12 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1247469/+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 1297265] Re: gedit crashed with SIGSEGV in gtk_tree_model_filter_row_deleted()
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1297265 Title: gedit crashed with SIGSEGV in gtk_tree_model_filter_row_deleted() Status in gedit package in Ubuntu: Expired Bug description: I tried to open a document... ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Mon Mar 24 13:57:41 2014 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-06-18 (280 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcCmdline: gedit SegvAnalysis: Segfault happened at: 0x7fb3745ef031:cmpq $0x0,0x38(%rbp) PC (0x7fb3745ef031) ok source "$0x0" ok destination "0x38(%rbp)" (0x0038) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke (closure=0x2c78c60, return_value=0x0, n_param_values=2, param_values=0x7fff0804eb10, invocation_hint=0x7fff0804eab0) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x2255c10, detail=detail@entry=0, instance=instance@entry=0x20f0490, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff0804eb10) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3584 g_signal_emit_valist (instance=0x20f0490, signal_id=, detail=0, var_args=var_args@entry=0x7fff0804ed68) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3328 g_signal_emit (instance=, signal_id=, detail=) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3384 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1297265/+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 1553202] Re: Firefox 44 breaks fontconfig (yet again)
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1553202 Title: Firefox 44 breaks fontconfig (yet again) Status in firefox package in Ubuntu: Expired Bug description: I have a fontconfig setup to use TeX Gyre family fonts (and related) instead of the Microsoft fonts from ttf-core-fonts, and I have successfully used such a setup until some of the Firefox updates in the past broke it. I played with my config and found a fix, and it worked until Firefox 44, when that broke again. See the screenshots for the reference. Non-Latin characters are displayed using the wrong font, even a serif one, which isn't even close to what I have in the config. Importantly, no other apps broke. Any ideas how can that be fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1553202/+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 1698152] Re: loopback.io with wrong visualization on scroll
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1698152 Title: loopback.io with wrong visualization on scroll Status in firefox package in Ubuntu: Expired Bug description: scrolling on the website loopback.io is broken ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 54.0+build3-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: enrico 2655 F...m pulseaudio /dev/snd/controlC0: enrico 2655 F pulseaudio BuildID: 20170612122310 Channel: Unavailable CurrentDesktop: Unity Date: Thu Jun 15 16:11:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-12-03 (193 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.42.254 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.42.0/24 dev wlp58s0 proto kernel scope link src 192.168.42.136 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=54.0/20170612122310 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1698152/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Also affects: ubuntu-core-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide
Ghetolay You can place the dock on all displays or pick the one you want it on in settings > dock I've just tested it and it allows you to open at the left edge of both monitors (not what I want as it also sticks the mouse briefly and i don't like the central dock). -- 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/1726464 Title: Can't easily move the cursor between monitors when the dock is set to auto-hide Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The sticky edge thing between monitors is very annoying as the cursor never ends up where it should when it's moved over to the other screen. It's annoying to the degree that I feel like I can not use multiple monitors with standard Ubuntu anymore. Unity had an option to disable this, please add one to Gnome as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726464/+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 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide
Im not sure if its barrier or sticky that comes into play. I was able to disable it on 16.04 as described above. Multi screen (two) Dock on Primary monitor only Left Side Auto Hide Issue, Mouse sticks at monitor join edge. It occurs only when moving the mouse from primary to secondary at the top of the screen. Could it be the desired effect to prevent passing by the system dropdown (sorry dont know what else to call it). In any case, its quite annoying when you just want to move across because you have to remember to drop the cursor below the stick/barrier to get to the second screen. I am not sure how it can become acceptable, a delay barrier all the way down while frustrating would become expected and so tolerable but the small barrier with dead stop makes it so that you just happen to hit it inadvertently which means its virtually impossible predict and so find yourself looking around the screen for the cursor. -- 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/1726464 Title: Can't easily move the cursor between monitors when the dock is set to auto-hide Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The sticky edge thing between monitors is very annoying as the cursor never ends up where it should when it's moved over to the other screen. It's annoying to the degree that I feel like I can not use multiple monitors with standard Ubuntu anymore. Unity had an option to disable this, please add one to Gnome as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726464/+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 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation
Sorry, the combination of ssh-agent and "log out and log back in" made me immediately think of bug 1789523. ** Package changed: gnome-session (Ubuntu) => openssh (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-agent fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
** Attachment added: "dpkgl.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/+attachment/5231871/+files/dpkgl.txt -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1813076] Re: goa crashes when trying to authenticate against google & DUO
Wait a second - is goa based on Safari code? Is that why it's being shut-out from DUO? And, I'm not suggesting that anyone lie - I suspect that DUO is misreading goa as Safari. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1813076 Title: goa crashes when trying to authenticate against google & DUO Status in gnome-online-accounts package in Ubuntu: New Bug description: My google eMAIL account is managed by my organisation. They recently required everyone to validate their sign-ons (sign-ins) via a central authentication server (CAS) using the 2FA from DUO. When attempting to connect using goa, I am now re-directed to my organisation's CAS and when the DUO login page refreshes, it states that login could not proceed because I am using a SAFARI browser that is more than one year out of date. Of course, I'm not using SAFARI, but rather goa. Is there a way to deed the proper header (a more recent version of SAFARI in goa) to be able to complete 2FA with DUO? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-online-accounts 3.28.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 23 15:20:45 2019 InstallationDate: Installed on 2019-01-15 (8 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1813076/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812359/+attachment/5231870/+files/dmesg.txt -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/+attachment/5231873/+files/lspcik.txt -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1812359/+attachment/5231872/+files/journalctl.txt -- 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/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1813076] Re: goa crashes when trying to authenticate against google & DUO
Excellent question. If we lie about the version of Safari it might cause other tools to emit HTML etc that it can't parse. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1813076 Title: goa crashes when trying to authenticate against google & DUO Status in gnome-online-accounts package in Ubuntu: New Bug description: My google eMAIL account is managed by my organisation. They recently required everyone to validate their sign-ons (sign-ins) via a central authentication server (CAS) using the 2FA from DUO. When attempting to connect using goa, I am now re-directed to my organisation's CAS and when the DUO login page refreshes, it states that login could not proceed because I am using a SAFARI browser that is more than one year out of date. Of course, I'm not using SAFARI, but rather goa. Is there a way to deed the proper header (a more recent version of SAFARI in goa) to be able to complete 2FA with DUO? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-online-accounts 3.28.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 23 15:20:45 2019 InstallationDate: Installed on 2019-01-15 (8 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1813076/+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 1812407] Re: Dock resize on hover and on window focus and is displayed on lock screen
I think this is a combination of bug 1769383, and some other hover/resize bug that is also mentioned in bug 1812996 and bug 1812998. So let's make this about just the hover/resize bug. ** This bug is no longer a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1812407 Title: Dock resize on hover and on window focus Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Dock resize on hover and on window focus. Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 16:15:18 2019 InstallationDate: Installed on 2018-09-17 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812407/+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 1812407] Re: Dock resize on hover and on window focus and is displayed on lock screen
** Tags added: cosmic ** Summary changed: - Dock resize on hover and on window focus and is displayed on lock screen + Dock resize on hover and on window focus ** Description changed: - Dock resize on hover and on window focus. Displayed on lock screen. See - attachment. - - udp (2019-01-19): - Same situation on my home PC. Suppose appear after firs screen lock and can be related somehow to datetime-format extension (https://extensions.gnome.org/extension/1173/datetime-format/) + Dock resize on hover and on window focus. Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 16:15:18 2019 InstallationDate: Installed on 2018-09-17 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1812407 Title: Dock resize on hover and on window focus Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Dock resize on hover and on window focus. Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 16:15:18 2019 InstallationDate: Installed on 2018-09-17 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812407/+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 1812998] Re: Dock change size and windows positions when focus
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 ** This bug is no longer a duplicate of bug 1812996 Dock focus bug with Virtualbox ** This bug has been marked a duplicate of bug 1812407 Dock resize on hover and on window focus and is displayed on lock screen -- 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/1812998 Title: Dock change size and windows positions when focus Status in gnome-shell package in Ubuntu: New Bug description: sometimes (but can't find when), the focus on dock change its size and move all the windows opened (see screen capture) Ubuntu 18.10 x 64 EDIT: see content of last entries of journalctl: janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: Failed to create XFIXES cursor: Failed to get cursor image janv. 23 16:26:54 jerome-PC gnome-shell[3335]: Failed to create XFIXES cursor: Failed to get cursor image janv. 23 16:26:53 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a5c not in stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812998/+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 1812996] Re: Dock focus bug with Virtualbox
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 Found it in bug 1812407. ** This bug has been marked a duplicate of bug 1812407 Dock resize on hover and on window focus and is displayed on lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1812996 Title: Dock focus bug with Virtualbox Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: There is a graphical bug with Dock/virtualbox when other apps like Chrome are displayed on full screen. Virtualbox icon on dock continuously switch between 1 or 2 windows (even if No VM is launched) , resulting in modification of icons/dock size this disappear if I reduce the Chrome window See screen capture to have an idea of the visual output. Ubuntu 18.10 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812996/+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 1812407] Re: Dock resize on hover and on window focus and is displayed on lock screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1812407 Title: Dock resize on hover and on window focus Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Dock resize on hover and on window focus. Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.1 Candidate: 0.9.1ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 16:15:18 2019 InstallationDate: Installed on 2018-09-17 (123 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812407/+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 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
Also, I notice you seem to be using this Bluetooth adapter: Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Unfortunately we do find that brand (Cambridge Silicon Radio) of Bluetooth adapter to be unreliable and buggy. So please also try a different Bluetooth adapter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+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 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
Can you please run this command and send us the output? dpkg -s pulseaudio ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+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 1812998] Re: Dock change size and windows positions when focus
*** This bug is a duplicate of bug 1812996 *** https://bugs.launchpad.net/bugs/1812996 ** This bug has been marked a duplicate of bug 1812996 Dock focus bug with Virtualbox -- 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/1812998 Title: Dock change size and windows positions when focus Status in gnome-shell package in Ubuntu: New Bug description: sometimes (but can't find when), the focus on dock change its size and move all the windows opened (see screen capture) Ubuntu 18.10 x 64 EDIT: see content of last entries of journalctl: janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a6a not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a63 not in stack janv. 23 16:26:54 jerome-PC gnome-shell[3335]: Failed to create XFIXES cursor: Failed to get cursor image janv. 23 16:26:54 jerome-PC gnome-shell[3335]: Failed to create XFIXES cursor: Failed to get cursor image janv. 23 16:26:53 jerome-PC gnome-shell[3335]: STACK_OP_RAISE_ABOVE: sibling window 0x2200a5c not in stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812998/+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 1812996] Re: Dock focus bug with Virtualbox
I saw someone else report a similar bug with the Ubuntu Dock recently. It was changing size when it should not. Can't find that other bug right now though. ** Tags added: cosmic ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- 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/1812996 Title: Dock focus bug with Virtualbox Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: There is a graphical bug with Dock/virtualbox when other apps like Chrome are displayed on full screen. Virtualbox icon on dock continuously switch between 1 or 2 windows (even if No VM is launched) , resulting in modification of icons/dock size this disappear if I reduce the Chrome window See screen capture to have an idea of the visual output. Ubuntu 18.10 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1812996/+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 1812918] Re: Bluetooth Sound disjoined 18.04
Wow, OK. That is indeed disjoint/disjoined. ** Summary changed: - Bluetooth Sound disjoined 18.04 + Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+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 1812359] Re: Login screen not appearing in bionic [Intel Atom D425]
daisyd, Please: 1. Run: dmesg > dmesg.txt 2. Run: journalctl > journalctl.txt 3. Run: lspci -k > lspcik.txt 4. Run: dpkg -l > dpkgl.txt 5. Send us all the above text files. ** Summary changed: - Login screen not appearing in bionic [SSD Intel Atom] + Login screen not appearing in bionic [Intel Atom D425] ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1812359 Title: Login screen not appearing in bionic [Intel Atom D425] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've tried the solution mentioned here https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72 but it did not solve my issue. $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter 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/1812359/+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 1813097] Re: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813097 Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36ec] InstallationDate: Installed on 2014-12-08 (1507 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Supermicro X10SRA-F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=7439bd5c-2c10-4e9d-8ccc-144a158d3318 ro radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 audio=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: X10SRA-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd01/28/2016:svnSupermicro:pnX10SRA-F:pvr0123456789:rvnSupermicro:rnX10SRA-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1813097/+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 1813097] [NEW] package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of packag
Public bug reported: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36ec] InstallationDate: Installed on 2014-12-08 (1507 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Supermicro X10SRA-F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=7439bd5c-2c10-4e9d-8ccc-144a158d3318 ro radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 audio=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: X10SRA-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd01/28/2016:svnSupermicro:pnX10SRA-F:pvr0123456789:rvnSupermicro:rnX10SRA-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813097 Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard:
[Desktop-packages] [Bug 1795200] Re: nautilus hangs when copying mp3 audio file
Sorry, can't reproduce it. But if it happens again, I will remember. -- 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/1795200 Title: nautilus hangs when copying mp3 audio file Status in nautilus package in Ubuntu: Incomplete Bug description: having two windows of nautilus open copy file with from one window past file with to other window progress bar appears, runs, but stops (see attached) file appears to have been copied correctly, because it plays correctly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 30 14:13:56 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'enable-delete' b'true' b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+45+24'" b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 'size']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2017-12-13 (290 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2018-08-28 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795200/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This fixed the bug for me.
I did not enable -proposed, just downloaded and upgraded this packages:
{{{
$ dpkg -l \*cairo\* | grep ^ii | grep 1.15.10
ii libcairo-gobject2:amd641.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library (GObject library)
ii libcairo-script-interpreter2:amd64 1.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library (script interpreter)
ii libcairo2:amd641.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library
ii libcairo2-dev:amd641.15.10-2ubuntu0.1 amd64
Development files for the Cairo 2D graphics library
}}}
Thanks!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1560286
Title:
Evince displays pdf file fine, but prints colors inverted
Status in cairo package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
Fix Committed
Status in cairo source package in Cosmic:
Fix Committed
Bug description:
* Impact
In some files images are printed with inverted colors
* Test case
open
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
in evince, click on the print preview, the colors should be right
* Regression potential
it's a change in the code dealing with specific adobe file, test opening the
example in different document viewer and try with some other files (the bug has
several example), they should display the correct image/colors
I have several pdf files that when opened by evince, they appear to be fine
until I try to print them. When I do, they print with the colors inverted (the
printout looks like a photograph negative). This color inversion also occurs
when viewed in the print preview screen. If I click on File > Properties, I
get some information...
Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
Creator : Adobe Acrobat 15.10
...
Format : PDF-1.6
...
I am running ubuntu 14.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu10.2
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 21 21:01:45 2016
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2012-07-24 (1336 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1812735] Re: Andyrock has to update this placeholder bug :)
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1812735 Title: Andyrock has to update this placeholder bug :) Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Something in OSK doesn't work, he knows about it! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1812735/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: apache2 (Ubuntu) Status: New => Triaged ** Changed in: anope (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
Yes, that wouldn't be a problem. Steps: 1 - Open the GNOME Control Center (Ubuntu Settings, or Configurations); 2 - Select "Network" on the left sidebar; 3 - Press the small cog-wheel (Network Configurations); 4 - Select the IPv6 tab; 5 - On IPv6 Method, select disabled (on my system, it is on Automatic); After that, GOA doesn't load the login screens that I've detailed on earlier comments. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account Status in gnome-initial-setup package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: New Bug description: After the first boot up of Ubuntu 18.10, it invites me to log-in into several accounts, including Google and Microsoft accounts. After I log-in into Ubuntu One, my next step is to log in my Google Account, but the log-in page never loads, and when it does (after a couple of minutes), and I insert my log in credentials, it fails the log-in process, all of this happens with the Microsoft account too. The Ubuntu One account logs-in without a hitch, but the rest does not. 1) Description: Ubuntu 18.10 Release: 18.10 2) gnome-initial-setup: Instalado: 3.30.0-1ubuntu3 Candidato: 3.30.0-1ubuntu3.1 Tabela de versão: 3.30.0-1ubuntu3.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.0-1ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-initial-setup 3.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 11:12:31 2018 ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup InstallationDate: Installed on 2018-11-27 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1805426/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
libslang2-modules is in universe although it's built from the slang2 source. I guess that means we can mark it invalid here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
quagga was another false Build-Depends so I filed a Debian bug requesting they drop the pcre3 Build-Depends. ** Changed in: quagga (Ubuntu) Status: Incomplete => Invalid ** Description changed: + https://people.canonical.com/~ubuntu- + archive/transitions/html/pcre2-main.html + demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. - aide - apache2 - apr-util - clamav - exim4 - freeradius - git - glib2.0 - grep - haproxy - libpam-mount - libselinux - nginx - nmap - php7.2 - postfix - python-pyscss - quagga - rasqal - slang2 - sssd - wget - zsh - -- - - For clarification: pcre2 is actually newer than pcre3. pcre3 is just - poorly named (according to jbicha). + For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Also affects: anope (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package clamav - 0.100.2+dfsg-2ubuntu1 --- clamav (0.100.2+dfsg-2ubuntu1) disco; urgency=medium * Sync with Debian. Remaining change: - clamav-daemon may fail to start due to options removed in new version and manually edited configuration file. (LP: #1783632) + debian/patches/Deprecate-unused-options-instead-of-removing-it.patch: add patch from Debian stretch to simply warn about removed options. * Dropped change: - Build-Depend on pcre3-dev (pcre2 is now in Ubuntu main) (LP: #1792544) clamav (0.100.2+dfsg-2) unstable; urgency=medium * Increase clamd socket command read timeout to 30 seconds (Closes: #915098) clamav (0.100.2+dfsg-1) unstable; urgency=medium * Import new upstream - Bump symbol version due to new version. - CVE-2018-15378 (Closes: #910430). * add NEWS.md and README.md from upstream * Fix infinite loop in dpkg-reconfigure, Patch by Santiago Ruano Rincón (Closes: #905044). -- Jeremy Bicha Wed, 23 Jan 2019 12:08:48 -0500 ** Changed in: clamav (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15378 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1051726] Re: WebDav broken, Nautilus sends data on a closed TCP connection!
Sorry, I have stopped using Nautilus when Gnome decided it should be a tablet tool instead of a PC program, and withdraw all interesting functions from it (like F3 to open a double pane). I am now using Nemo, which might still have the bug since it forked Nautilus before its emasculation, but I am also not using WebDAV anymore. As far as I am concerned, you can leave this bug to "low" importance, or even close it. "Close" I am not quite sure because it could affect others... Many thanks for the reply though! -- 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/1051726 Title: WebDav broken, Nautilus sends data on a closed TCP connection! Status in nautilus package in Ubuntu: Incomplete Bug description: ENVIRONMENT: - Precise 64 Nautilus 3.4.2 $ uname -a && nautilus --version Linux zakhar-desktop 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux GNOME nautilus 3.4.2 WEBDAV: I set up a local Apache WebDAV with standard options. No SSL Basic authentication (it is for local use) When I instruct Nautilus to go to my WebDAV (dav://127.0.0.1/webdav/) I get an error. After a few hours of investigation, I discovered the bug: Nautilus sends data to a closed TCP connection! WHAT HAPPENS: -- When you hit "Enter" after the address (dav://127.0.0.1/webdav/), Nautilus issues a plain request to the server. Then, of course, the server replies 401: Authorisation required. Having this response, Nautilus shows the box where you can enter user/password. ... the trouble is... if it takes you more than 5 seconds to type the password, the default keepalive of Apache being 5 seconds, the connection will be closed. Then, once you have entered both username and password, Nautilus re- issues the same request with the Authorization header. ... but this is done on a closed connection!.. PROOF: -- This is the Wireshark summary trace from a second PC (client is 192.168.0.132, server is 192.168.0.130) No. TimeSourceDestination Protocol Length Info 1 0.00192.168.0.132 192.168.0.130 TCP 74 38035 > http [SYN] Seq=0 Win=14600 Len=0 MSS=1460 2 0.40192.168.0.130 192.168.0.132 TCP 74 http > 38035 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 3 0.000246192.168.0.132 192.168.0.130 TCP 66 38035 > http [ACK] Seq=1 Ack=1 Win=14656 Len=0 4 0.000534192.168.0.132 192.168.0.130 HTTP 230 OPTIONS /webdav HTTP/1.1 5 0.000555192.168.0.130 192.168.0.132 TCP 66 http > 38035 [ACK] Seq=1 Ack=165 Win=15552 Len=0 6 0.001226192.168.0.130 192.168.0.132 HTTP 727 HTTP/1.1 401 Authorization Required (text/html) 7 0.001698192.168.0.132 192.168.0.130 TCP 66 38035 > http [ACK] Seq=165 Ack=662 Win=15936 Len=0 8 5.003870192.168.0.130 192.168.0.132 TCP 66 http > 38035 [FIN, ACK] Seq=662 Ack=165 Win=15552 Len=0 9 5.042256192.168.0.132 192.168.0.130 TCP 66 38035 > http [ACK] Seq=165 Ack=663 Win=15936 Len=0 10 7.873829192.168.0.132 192.168.0.130 HTTP 273 OPTIONS /webdav HTTP/1.1 11 7.873866192.168.0.130 192.168.0.132 TCP 54 http > 38035 [RST] Seq=663 Win=0 Len=0 12 7.873872192.168.0.132 192.168.0.130 TCP 66 38035 > http [FIN, ACK] Seq=372 Ack=663 Win=15936 Len=0 13 7.873881192.168.0.130 192.168.0.132 TCP 54 http > 38035 [RST] Seq=663 Win=0 Len=0 As you can see, packet 8 occurs around 5 second after the packet 7, and is a FIN from the server (5 seconds of inactivity). I spent almost 8 seconds typing username/password, and then at 7.8 sec, the second request with the Authorization goes out... WITHOUT reopening the connection. Of course, the server is not happy with that and issues a RST, and subsequently Nautilus says that there is an error. To check that it is indeed the source of the bug, I bumped the keep-alive time-out in my Apache config to 30 seconds, and this time, all was fine (of course I typed the user/password in less than 30 secs). GUESSING: - With previous versions of Nautilus where you had to enter in a windows the address of the server, the protocol, the username and password... THEN hit enter, I imagine such things didn't show as it was 'fast enough' not to be in that situation. Having removed this windows, the bug shows. It is bad because my workaround (timeout to 30 secs) is
[Desktop-packages] [Bug 1173558] Re: folder expand arrows are missing
the issue seems resolved in newer versions ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released -- 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/1173558 Title: folder expand arrows are missing Status in nautilus package in Ubuntu: Fix Released Bug description: in the latest Nautilus release 3.6.3 the functionality to expand folders with the small arrows is missing. this was a very important feature for me and it seems to be a bug because there is an empty space where the arrows are in earlier versions of Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1173558/+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 1183383] Re: statusbar is gone!
the current version has a floating status bar which is the upstream design ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/1183383 Title: statusbar is gone! Status in nautilus package in Ubuntu: Fix Released Bug description: after update the new Nautilus doesn't have a statusbar anymore even the option to activate it isn't there anymore statusbar is really important to see the folder or partition size on first glance or to see how much files are marked... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1183383/+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 425736] Re: nautilus segfaults
the bug has got no activity nor reports in years, closing ** Changed in: nautilus (Ubuntu) Status: Triaged => Invalid -- 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/425736 Title: nautilus segfaults Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus Upgraded system from jaunty to karmic alpha 5. Gnome does not work anymore (no panel, etc shows up just my custom background), I've reported this bug as bug #424435 but I managed to launch gnome-panel, metacity, etc "by hand" from an xterm. However nautilus segfaults all the time just after I start it: Initializing nautilus-open-terminal extension ** Message: Initializing gksu extension... ** (nautilus:15448): WARNING **: No marshaller for signature of signal 'UploadFinished' ** (nautilus:15448): WARNING **: No marshaller for signature of signal 'DownloadFinished' Initializing nautilus-gdu extension Initializing nautilus-image-converter extension Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00 *** glibc detected *** nautilus: double free or corruption (fasttop): 0x0a23ce70 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0x365f091] /lib/tls/i686/cmov/libc.so.6[0x3660792] /lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x366383d] /usr/lib/libglib-2.0.so.0(g_free+0x36)[0x63a0c6] /usr/lib/libglib-2.0.so.0[0x65c94a] /lib/tls/i686/cmov/libpthread.so.0[0x13f2ef] /lib/tls/i686/cmov/libpthread.so.0[0x13f81c] /lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0x36c081e] === Memory map: 0011-0012e000 r-xp 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0012e000-0012f000 r--p 0001e000 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0012f000-0013 rw-p 0001f000 08:03 404362 /usr/lib/libdbus-glib-1.so.2.1.0 0013-00138000 r-xp 08:03 9396 /usr/lib/libXrender.so.1.3.0 00138000-00139000 r--p 7000 08:03 9396 /usr/lib/libXrender.so.1.3.0 00139000-0013a000 rw-p 8000 08:03 9396 /usr/lib/libXrender.so.1.3.0 0013a000-0015 r-xp 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 0015-00151000 r--p 00015000 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 00151000-00152000 rw-p 00016000 08:03 8027 /lib/tls/i686/cmov/libpthread-2.10.1.so 00152000-00154000 rw-p 00:00 0 00154000-0016e000 r-xp 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0016e000-0016f000 r--p 0001a000 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0016f000-0017 rw-p 0001b000 08:03 397806 /usr/lib/libgdk_pixbuf-2.0.so.0.1710.0 0017-00173000 r-xp 08:03 77036 /lib/libuuid.so.1.3.0 00173000-00174000 r--p 3000 08:03 77036 /lib/libuuid.so.1.3.0 00174000-00175000 rw-p 4000 08:03 77036 /lib/libuuid.so.1.3.0 00175000-0017c000 r-xp 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017c000-0017d000 r--p 6000 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017d000-0017e000 rw-p 7000 08:03 66639 /usr/lib/libXrandr.so.2.2.0 0017e000-00186000 r-xp 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00186000-00187000 r--p 8000 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00187000-00188000 rw-p 9000 08:03 398598 /usr/lib/libstartup-notification-1.so.0.0.0 00188000-0018a000 r-xp 08:03 9384 /usr/lib/libXinerama.so.1.0.0 0018a000-0018b000 rw-p 1000 08:03 9384 /usr/lib/libXinerama.so.1.0.0 0018b000-0018d000 r-xp 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018d000-0018e000 r--p 1000 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018e000-0018f000 rw-p 2000 08:03 9571 /usr/lib/libXcomposite.so.1.0.0 0018f000-001b5000 r-xp 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b5000-001b6000 r--p 00025000 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b6000-001b7000 rw-p 00026000 08:03 398665 /usr/lib/libgnome-desktop-2.so.11.4.0 001b7000-00262000 r-xp 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00262000-00264000 r--p 000ab000 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00264000-00265000 rw-p 000ad000 08:03 397805 /usr/lib/libgdk-x11-2.0.so.0.1710.0 00265000-002a9000 r-xp 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002a9000-002aa000 r--p 00044000 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002aa000-002ab000 rw-p 00045000 08:03 36938 /usr/lib/libgobject-2.0.so.0.2105.0 002ab000-002bf000 r-xp 08:03 11570 /lib/libz.so.1.2.3.3 002bf000-002c r--p 00013000 08:03 11570 /lib/libz.so.1.2.3.3 002c-002c1000 rw-p 00014000
[Desktop-packages] [Bug 1260208] Re: malious pdf causes segementation fault
the issue seems to not apply to newer versions
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Invalid
--
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/1260208
Title:
malious pdf causes segementation fault
Status in nautilus package in Ubuntu:
Invalid
Bug description:
Hi together,
I found an interesting bug today. After compiling attached errornous latex
code attached in my home directory, nautilus crashes a second after start with
segmentation fault. Ouptut is:
** (nautilus:4779): WARNING **: Couldn't register with accessibility bus: Did
not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
Initializing nautilus-open-terminal extension
sys:1: Warning: g_object_set: assertion 'G_IS_OBJECT (object)' failed
** (nautilus:4779): CRITICAL **: nautilus_menu_provider_get_background_items:
assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Nautilus-Share-Message: Called "net usershare info" but it failed: »net
usershare« gab den Fehler 255 zurück: Ignoring unknown parameter "server role"
Ignoring unknown parameter "server services"
Ignoring unknown parameter "dcerpc endpoint servers"
net usershare: cannot open usershare directory /var/lib/samba/usershares.
Error Datei oder Verzeichnis nicht gefunden
Please ask your system administrator to enable user sharing.
** (nautilus:4779): CRITICAL **: nautilus_menu_provider_get_background_items:
assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Syntax Warning: May not be a PDF file (continuing anyway)
Syntax Error: Couldn't find trailer dictionary
Syntax Error: Couldn't read xref table
Error loading document: File type Einfaches Textdokument (text/plain) is not
supported
(nautilus:4779): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_close:
assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed
(nautilus:4779): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_get_pixbuf:
assertion 'GDK_IS_PIXBUF_LOADER (loader)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Speicherzugriffsfehler
("Datei oder Verzeichnis nicht gefunden" means "file or directory not found",
"Speicherzugriffsfehler" means segmentation fault).
I have no idea why the produces pdf is malious, but it shouldn't matter
because nautilus should be able to handle such files by ignoring them somehow.
Removing the pdf file from my home diretory fixes the issue, compiling it
again makes it reproducible.
I'm running nautilus 3.8.2 on Ubuntu 13.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1260208/+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 751232] Re: wrong icon mounting micro sd with card reader
Is that still an issue in newer Ubuntu versions? ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/751232 Title: wrong icon mounting micro sd with card reader Status in nautilus package in Ubuntu: Incomplete Bug description: Binary package hint: nautilus During test of Natty Beta 1 I encountered this little bug while testing the card reader: When I insert the micro SD in the card reader, the icon on the desktop is not a red SD icon but a USB key icon. It's not an important and blocking bug, but I thought useful to report it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu11 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Tue Apr 5 13:04:39 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/751232/+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 1074753] Re: error mounting encrypted volume/keychain error/volume not mounted
Is that still an issue in newer Ubuntu versions? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1074753 Title: error mounting encrypted volume/keychain error/volume not mounted Status in nautilus package in Ubuntu: Incomplete Bug description: When mounting a LUKS encrypted drive from nautilus (example /dev/sda1 is not automatically mounted at startup), an error is reported upon successful entering of passphrase that "keychain cannot be updated at this time." The device then disappears altogether from the nautilus window and seems to have vanished, but actually the mapper object has been created and can be mounted manually from the command line. This leaves the user potentially believing the device was never mounted but in actuality the mapper object is sitting there with their encrypted drive just waiting to be mounted. Furthermore, this leaves the user with no way to remove the mapped drive unless through the command window which, of course, means the user needs to know the mapped object was created in the first place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1074753/+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 1045528] Re: Not able to SHIFT click when renaming a file.
That's fixed in the current nautilus version ** Changed in: nautilus Status: New => Fix Released ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- 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/1045528 Title: Not able to SHIFT click when renaming a file. Status in One Hundred Papercuts: Fix Released Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: If you press CTRL + L to bring up the address field, left click in one spot, then hold SHIFT and left click in another spot. It will highlight the text between the two selections. You are unable to do this when renaming a file. It makes highlighting large portions of a name very tedious and should be fixed. Running Ubuntu 12.10 and also on 12.04 both with the latest version from the repos. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1045528/+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 1041930] Re: Cannot navigate in nautilius using touchscreen of Asus Slate ep121
Is there still an issue in newer versions? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/1041930 Title: Cannot navigate in nautilius using touchscreen of Asus Slate ep121 Status in nautilus package in Ubuntu: Incomplete Bug description: Touching (with a finger) once the screen making it imposible to navigate within nautilus, even with a conventional mouse. (became alreadya problem after upgrading from 11.10 to 12.04). The sidebar still works, but I can't navigate by double-clicking on the "big" Icons in the main-panel. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Sun Aug 26 14:59:20 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+49+24'" InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821) ProcEnviron: LANGUAGE=de_DE:de PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1041930/+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 1019995] Re: gksu nautilus will not display icons correctly or at all
** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- 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/1019995 Title: gksu nautilus will not display icons correctly or at all Status in nautilus package in Ubuntu: Invalid Bug description: nautulus 3.5.3 will not display icons when using gksu nautilus in terminal http://ubuntuforums.org/showthread.php?t=2014450 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4 Uname: Linux 3.5.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.2.5-0ubuntu1 Architecture: i386 Date: Mon Jul 2 04:50:02 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1019995/+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 1027743] Re: Multi-monitor - When using two displays, nautilus window jumps to other display after clicking link on Bookmarks side panel
The issue there is deprecated in newer versions ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- 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/1027743 Title: Multi-monitor - When using two displays, nautilus window jumps to other display after clicking link on Bookmarks side panel Status in nautilus package in Ubuntu: Invalid Bug description: When using two displays (single X11 session), nautilus file-manager window jumps from second to the first display after clicking folder link on Bookmarks side panel. Ubuntu 12.04 Gnome 3.4.1 Kernel Linux 3.2.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1027743/+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 1069381] Re: nautilus got frozen on handeling mounted archive
Do you still get the issue in newer Ubuntu versions? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1069381 Title: nautilus got frozen on handeling mounted archive Status in nautilus package in Ubuntu: Incomplete Bug description: I have used nautilus to mount a .iso with the archive mounter. During browsing the mounted .iso and cleanding up by the way the trash folder(unity action taken -> the symbol in the unity panel), nautilus got frozen. Steps to reproduce: 1.Choose a .iso file 2.click in nautilus with the right mouse button on it 3. choose archive mounter to mount the file 4.Switch in nautilus in the mounted .iso 5.Use in mean time the trash icon on unity panel with -> right mouse click -> option : clean up 6. See nautilus window on the mounted .iso freezing Reproducability: Not tested. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4 Uname: Linux 3.6.2-030602-generic x86_64 ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Sun Oct 21 15:19:03 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'910x674+65+65'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'283' InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722) MarkForUpload: True ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (update-notifier:3035): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (update-notifier:3035): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (tracker-miner-fs:2549): Tracker-WARNING **: Could not find parent node for URI:'archive://file%253A%252F%252F%252Fhome%252Fuser%252FIsos%252FBlender_Fortgeschrittene.iso/' (tracker-miner-fs:2549): Tracker-WARNING **: NOTE: URI themes other than 'file://' are not supported currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1069381/+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
