[Bug 2068539] Re: tiling operation triggers assertion in gnome-shell
** Description changed: Ubuntu 24.04 LTS gnome-shell-extension-ubuntu-tiling-assistant 46-1ubuntu1 gnome-shell 46.0-0ubuntu5.1 I am at a very stock X11 session with a i915 laptop. I move a firefox window from my primary monitor to my secondary monitor and make it full screen. I am running, I guess, tile(...) in tilingWindowManager.js and I am exactly at - const workArea = new + const workArea = new Rect(window.get_work_area_for_monitor(monitor)); I trigger this: - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ../../../gobject/gsignal.c:2685: instance '0x5886a5604300' has no handler with id '456691' - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ** - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: Bail out! libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: GNOME Shell crashed with signal 6 - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: == Stack trace for context 0x5886994827c0 == - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #0 58869954f460 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:157 (3b1b8336e> - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #1 58869954f3a0 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:264 (3b1b8319240 @ 495) - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #2 58869954f318 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:233 (3b1b83191f0 @ 48) - jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #3 58869954f288 i resource:///org/gnome/shell/ui/init.js:21 (2cdb70270bf0 @ 48) - jun 06 00:31:55 MY-LAPTOP polkitd[1385]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.97, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale e> - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=6/ABRT - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Failed with result 'core-dump'. - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies. - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Consumed 11min 13.038s CPU time. - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1. - jun 06 00:31:55 MY-LAPTOP systemd[3137]: Started gnome-session-failed.service - GNOME Session Failed lockdown screen (user). - jun 06 00:31:55 MY-LAPTOP systemd[3137]: Reached target gnome-session-failed.target - GNOME Session Failed. - jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (Conditi> - jun 06 00:31:55 MY-LAPTOP systemd[3137]: Starting org.gnome.Shell@x11.service - GNOME Shell on X11... - jun 06 00:31:55 MY-LAPTOP gnome-shell[64176]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ../../../gobject/gsignal.c:2685: instance '0x5886a5604300' has no handler with id '456691' + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ** + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: Bail out! libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: GNOME Shell crashed with signal 6 + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: == Stack trace for context 0x5886994827c0 == + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #0 58869954f460 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:157 (3b1b8336e> + jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #1 58869954f3a0 i
[Bug 2068539] [NEW] tiling operation triggers assertion in gnome-shell
Public bug reported: Ubuntu 24.04 LTS gnome-shell-extension-ubuntu-tiling-assistant 46-1ubuntu1 gnome-shell 46.0-0ubuntu5.1 I am at a very stock X11 session with a i915 laptop. I move a firefox window from my primary monitor to my secondary monitor and make it full screen. I am running, I guess, tile(...) in tilingWindowManager.js and I am exactly at const workArea = new Rect(window.get_work_area_for_monitor(monitor)); I trigger this: jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ../../../gobject/gsignal.c:2685: instance '0x5886a5604300' has no handler with id '456691' jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: ** jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: Bail out! libmutter:ERROR:../src/core/window.c:5444:meta_window_get_workspaces: code should not be reached jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: GNOME Shell crashed with signal 6 jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: == Stack trace for context 0x5886994827c0 == jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #0 58869954f460 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:157 (3b1b8336e> jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #1 58869954f3a0 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:264 (3b1b8319240 @ 495) jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #2 58869954f318 i file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:233 (3b1b83191f0 @ 48) jun 06 00:31:53 MY-LAPTOP gnome-shell[3609]: #3 58869954f288 i resource:///org/gnome/shell/ui/init.js:21 (2cdb70270bf0 @ 48) jun 06 00:31:55 MY-LAPTOP polkitd[1385]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.97, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale e> jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=6/ABRT jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Failed with result 'core-dump'. jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies. jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Consumed 11min 13.038s CPU time. jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1. jun 06 00:31:55 MY-LAPTOP systemd[3137]: Started gnome-session-failed.service - GNOME Session Failed lockdown screen (user). jun 06 00:31:55 MY-LAPTOP systemd[3137]: Reached target gnome-session-failed.target - GNOME Session Failed. jun 06 00:31:55 MY-LAPTOP systemd[3137]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (Conditi> jun 06 00:31:55 MY-LAPTOP systemd[3137]: Starting org.gnome.Shell@x11.service - GNOME Shell on X11... jun 06 00:31:55 MY-LAPTOP gnome-shell[64176]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager I get the "Oh No! Something has gone wrong and the system can't recover" screen from gnome-shell. The session is lost. It has already happened to me a handful of times. This time I could find the crash in the journal, it seems to be happening inside tiling-assistant ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2068539 Title: tiling operation triggers assertion in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068539/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036595] Re: vulnerability in libcue affects tracker-extract (GHSL-2023-197)
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libcue in Ubuntu. https://bugs.launchpad.net/bugs/2036595 Title: vulnerability in libcue affects tracker-extract (GHSL-2023-197) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcue/+bug/2036595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland
Ubuntu 22.04.3 on Wayland, bug still exists -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1923033 Title: Archive manager drag to extract doesn't work on Gnome with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1923033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023688] Re: error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023688 Title: error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012184] Re: Black screen after logout and login in wayland session.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012184 Title: Black screen after logout and login in wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993874] Re: Settings and Quick Menu apply Dark style differently
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. As @Batwam say's the Appearance tab ob the Settings app is involved. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993874 Title: Settings and Quick Menu apply Dark style differently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991494] Re: dark mode sometimes works
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. See this others bugs I think are related: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878 https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1993874 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1991494 Title: dark mode sometimes works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993878] Re: Dark mode from the drop down menu turning off on it's own
Hi! For me the way to reproduce this its simple, 1. With dark mode/theme selected. 2. Open the settings app and select "Appearance". 3. The shell change to light/white theme. 4. Select any ascent color. 5. The shell change to dark theme again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993878 Title: Dark mode from the drop down menu turning off on it's own To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993878/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1984041] Re: 界面卡死
Thanks for taking the time to report this bug and helping to make Ubuntu better. Your bug report is more likely to get attention if it is made in English, since this is the language understood by the majority of Ubuntu developers. Additionally, please only mark a bug as "security" if it shows evidence of allowing attackers to cross privilege boundaries or to directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1984041 Title: 界面卡死 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1984041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982422] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
Hi Luis, as part of the sponsoring/updating process, you have to run tests and inform us about its results and instructions. Testing an update is important. At a minimum, be sure to: 1. build in a clean build environment 2. verify the package still installs 3. verify the package upgrades cleanly 4. verify the package still functions properly 5. use public exploits and Proof of Concept(s) (PoC) (if available) to verify the bug is fixed 6. run any test suites available for such package -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1982422 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1982422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
Recently, I noticed that, from time to time, efivars values are automatically restored to default thus making necessary to redo all the steps in the aforementioned solution. Does anyone know if it is possible to change this behavior? Thank you. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
Confirmed that Kieran Clancy's solution (supplemented by ThOR27) works on Samsung NP9005XT notebook. Thank you. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925409] Re: the screen just blink. somewhat look crash
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1925409 Title: the screen just blink. somewhat look crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1925409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923544] Re: GNU Crashed
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1923544 Title: GNU Crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1923544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925101] Re: GIMP segfault
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1925101 Title: GIMP segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1925101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906301] Re: Natural Scrolling doesn't persist after close and open the laptop lid
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 Thanks! Yes I uncheck the "Hide duplicate" now I can see the bugs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906301 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906186] Re: Natural Scrolling doesn't persist after close and open the laptop lid
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 Thanks Gunner Indeed the "Hide duplicates" check prevent me for finding the bugs I report! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906186 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906186] Re: Natural Scrolling doesn't persist after close and open the laptop lid
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 Thanks Gunnar I wasn't able to find this bug report, don't know why did show on my reported bug page neither searching for it! Thanks again -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906186 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906301] Re: Natural Scrolling doesn't persist after close and open the laptop lid
Hi Gunnar Sorry I was try to find the report that I did yesterday but I couldn't find it, I search for it and didnt find the report. I thought he hadn't reported Sorry my bad this can be deleted or closed The strange thing is that the previous report doesn't show on my launchpad page so I couldn't track was going on. Again sorry, I'm new to launchpad -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906301 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906301] [NEW] Natural Scrolling doesn't persist after close and open the laptop lid
Public bug reported: Hi! Sometimes when close and open the laptop lid, the mouse natural scrolling get reset to disable (default). Im using a thinkpad T460 with the trackpoint with the mouse natural scrolling turn on so when I use the scroll in the trackpoint (middle bottom) I get the same movement as the touchpad. So when I close and open the laptop lid and the natural scrolling stop working, what I do is going to the settings and turn off - on the natural scrolling so start working again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 30 13:03:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-11-23 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906301 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906186] [NEW] Natural Scrolling doesn't persist after close and open the laptop lid
Public bug reported: Hi! I'm using a Lenovo thinkpad t460 with Ubuntu 20.10, I like to use the mouse natural scrolling with the trackpoint, but recently I noticed that when I close and open the lip of the laptop, sometimes the natural scrolling in the trackpoint revert to the default (disable) but the UI in the control center setting for the mouse does not change, so what I have to do is, turn off and on the setting and then the natural scrolling start working again ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 29 15:24:24 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-11-23 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1906186 Title: Natural Scrolling doesn't persist after close and open the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1900694] Re: package gdm3 3.36.3-0ubuntu0.20.04.1 failed to install/upgrade: end of file on stdin at conffile prompt
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1900694 Title: package gdm3 3.36.3-0ubuntu0.20.04.1 failed to install/upgrade: end of file on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1900694/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.
Hi @ahasenack, @seb128 I saw you've both have dealt with smb issues. Could you please take a look on this issue? Thanks! ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881780 Title: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885393] Re: Dark theme
Thanks for taking the time to report this bug and helping to make Ubuntu better. Your bug report is more likely to get attention if it is made in English, since this is the language understood by the majority of Ubuntu developers. Additionally, please only mark a bug as "security" if it shows evidence of allowing attackers to cross privilege boundaries or to directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885393 Title: Dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1885393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)
Thank you Daniel! Enabling animations again with Gnome tweaks fixed the issue. In order for this not to impact future users, - could you and the team please still look into it before the 20.04 release? Thank you very much! Eduardo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866899 Title: Snap Store can't install or remove snaps on 20.04 (password prompt issue?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)
Hi Marc, Thank you very much for your quick response! Eduardo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866899 Title: Snap Store can't install or remove snaps on 20.04 (password prompt issue?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856698] Re: I can see the password as I type into the password field after I reboot my PC
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1856698 Title: I can see the password as I type into the password field after I reboot my PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847960] Re: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1847960 Title: After returning from suspend the screen content (with all previously opened programs, like code editor) is shown for 1 second before displaying login form To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1847960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835213] Re: CVE-2019-13132
Thanks Luca for all the help and contribution, the fix is released. Feel free to contact us in case of new issues. ** Changed in: zeromq3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1835213 Title: CVE-2019-13132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1835213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821957] Re: Turning off a monitor unlocks the computer
** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1821957 Title: Turning off a monitor unlocks the computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1821957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821957] Re: Turning off a monitor unlocks the computer
** Information type changed from Private Security to Public Security ** Changed in: ubuntubudgie Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1821957 Title: Turning off a monitor unlocks the computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1821957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811531] Re: remote execution vulnerability
Thanks Luca, The packages are being uploaded and should be available in the archive in a few minutes. Thanks ** Changed in: zeromq3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809045] Re: Dash - "See more results" shortcut doesn't lead to more results
advised to change this to gnome-shell ** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809045 Title: Dash - "See more results" shortcut doesn't lead to more results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809045/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805715]
Daniel, since you are dealing with many reports on screensavers/screenlockers, have you seen this before? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in calculator input box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805715] Re: password exposed in calculator input box
Hi Peter, are you still experiencing this issue? ** Changed in: gnome-screensaver (Ubuntu) Status: New => Invalid ** Changed in: gnome-screensaver (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in calculator input box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805614] Re: screensaver crashed on wake up
*** 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. Please continue to report any other bugs you may find ** Information type changed from Private Security to Public Security ** 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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805614 Title: screensaver crashed on wake up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805614/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1804949]
*** 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. Please 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 Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1804949 Title: Screen locking issue data leak~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1804949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806285] Re: Dock is visible on lock screen
*** 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 and marked as public-security. Please continue to report any other bugs you may find. ** Information type changed from Private Security to Public Security ** 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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806285 Title: Dock is visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797707] Re: system friert ständig ein, 18.04.1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1797707 Title: system friert ständig ein, 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1797707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Thanks a lot, it works very well in Ubuntu 18.04 with Xiaomi Air 13 Really appreciated :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792702] [NEW] gnome-shell filling /var/log/syslog
Public bug reported: My Ubuntu 18.04 installation is killing my disk space. It is filling /var/log/syslog with about 5gb of messages per day. I did a tail on it: PS: already upgraded to the latest packages lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages tail of /var/log/syslog: Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493ee54c50), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3717c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e00d150), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2f7ef0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f4a1ac0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e428090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e466470), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e401fc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2086c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2a8dc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f9d8e00), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e349860), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e1f57f0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3d5e90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e417050), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fa7f490), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fa81550), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fbf3370), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f8f8640), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ed5fc90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e264330), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fcab090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2e9830), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fce7880), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fcf4190), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ffa3890), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f955050), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ffe2670), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x5649400a7fd0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493f34dca0), has been already finalized. Impossible to set any property to it.
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
** Attachment added: "dpkg -l" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+attachment/5183107/+files/dpkg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+attachment/5183106/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
OK, I have the three files. I hope to give useful information. The last time I had the bug, I saw that the graphical session switched automatically to the "alt+ctrl+F1" virtual console and after returned to "alt+ctrl+F2" virtual console. ** Attachment added: "journalctl -b" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+attachment/5183105/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789749] Re: Virtual desktops are shown in the middle of screen in GNOME Shell
Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789749 Title: Virtual desktops are shown in the middle of screen in GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789749] Re: Virtual desktops are shown in the middle of screen in GNOME Shell
It seems I didn't do a good explanation. With the "I think is a general bug" sentence I tried to say that it doesn't mind the GPU configuration. I don't see the same flaw in Fedora 28, that uses the same version of GNOME. The only thing you have to do to reproduce the bug is to "smack" the top left corner with a file, dragging it with mouse cursor, in gnome-session of activating the hot corner with tweak tools y Ubuntu session. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789749 Title: Virtual desktops are shown in the middle of screen in GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789749] [NEW] Virtual desktops are shown in the middle of screen in GNOME Shell
Public bug reported: Hi, since I use Ubuntu 18.04 with GNOME Shell I see that the virtual desktops panel is shown in the middle of screen when I drag a file to the Activities corner. I didn't see this behavior in 17.10, so it's really strange for me. I really like gnome-session, but I drag a lot of files through Activities, so to not see the bug I'm forced to use the Ubuntu session (now communitheme). Yes, it's really annoying. I share a file to show how is the bug. I'm using: -Ubuntu 18.04 64-bit. -GNOME 3.28.2 (provided by official repos). -Linux 4.15.0-33-generic (but I saw the bug in all previous kernels released Ubuntu 18.04). I saw the bug in two different GPUs: -[AMD/ATI] RV630/M76 [Mobility Radeon HD 2600] with Mesa and free Radeon driver provided by official repos. -MSI NVIDIA GTX 1050 with official proprietary driver. I think is a general bug. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Virtual desktops panel in the middle of screen using GNOME Shell" https://bugs.launchpad.net/bugs/1789749/+attachment/5182356/+files/Captura%20de%20pantalla%20de%202018-08-29%2023-36-22.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1789749 Title: Virtual desktops are shown in the middle of screen in GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
OK. I will try to reproduce the error. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
When the screen turns black I'm using the GNOME session as usual. I'm working with my common apps (Dropbox, LibreOffice, Visual Studio Code and/or Audacious... ) normally until the screen suddenly turns black without any previous warning. After the screen turn black, I switch to a virtual console that works as usual, and after I come back to the console where the graphical session is loaded and everything is in the same place that before the black screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
Sorry, but I forgot one thing. When the screen turns black, I can recover the graphical session switching between a virtual console and the console that is supporting the graphical session with alt+control+f5 and alt+control+f2 or alt+control+f1. No issues with nomodeset so far. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1785834/+attachment/5173862/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
apport information ** Tags added: apport-collected ** Description changed: Hi, Daniel van Vugt asked me to fill a new bug for the problem I have after he replied me in this old problem with GDM. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369 First, I will show the basic configuration of my desktop computer: -Motherboard: ROG STRIX X370-F GAMING. -CPU: Ryzen 7 1700. -GPU: GTX 1050 2GB from MSI. -Sound: Xonar DSX with ALC1220 of the motherboard deactivated. Well, the problem I have ocurrs randomly and I saw it in Ubuntu 17.10 and 18.04. In the prior version I get the typical “stopping user manager for uid” message, but in the most recent version I only see some information about storage I always see in the system boot, nothing apparently bad. I always use the official NVIDIA blob driver from the Proprietary GPU Drivers PPA, but the I also saw the bug in drivers provided by Ubuntu’s repositories. I used Linux Mint 19 for one month and I didn’t see the bug, so I think that origin is from Ubuntu’s stack. I suspect of two components and three possibilities: -GDM. -NVIDIA Prime. -Both combinanted. I’m trying a workaround setting nomodeset in the file “/etc/default/grub”. The line: - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" - Is now: - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" - After modify the file I executed the “sudo update-grub” command. Until now I didn’t see the bug again, but it’s too early to make sure. If I don’t see the bug again in two months I will declare the bug solved for me, but this is not the "out of the box" behavior you expect from a system like Ubuntu. Sorry if my English is hard to understand. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: communitheme:ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + GsettingsChanges: + b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' + 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-07-26 (14 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1785834/+attachment/5173861/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] [NEW] Screen randomly turns black minutes after successfully login with GDM
Public bug reported: Hi, Daniel van Vugt asked me to fill a new bug for the problem I have after he replied me in this old problem with GDM. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369 First, I will show the basic configuration of my desktop computer: -Motherboard: ROG STRIX X370-F GAMING. -CPU: Ryzen 7 1700. -GPU: GTX 1050 2GB from MSI. -Sound: Xonar DSX with ALC1220 of the motherboard deactivated. Well, the problem I have ocurrs randomly and I saw it in Ubuntu 17.10 and 18.04. In the prior version I get the typical “stopping user manager for uid” message, but in the most recent version I only see some information about storage I always see in the system boot, nothing apparently bad. I always use the official NVIDIA blob driver from the Proprietary GPU Drivers PPA, but the I also saw the bug in drivers provided by Ubuntu’s repositories. I used Linux Mint 19 for one month and I didn’t see the bug, so I think that origin is from Ubuntu’s stack. I suspect of two components and three possibilities: -GDM. -NVIDIA Prime. -Both combinanted. I’m trying a workaround setting nomodeset in the file “/etc/default/grub”. The line: - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" - Is now: - GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" - After modify the file I executed the “sudo update-grub” command. Until now I didn’t see the bug again, but it’s too early to make sure. If I don’t see the bug again in two months I will declare the bug solved for me, but this is not the "out of the box" behavior you expect from a system like Ubuntu. Sorry if my English is hard to understand. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Hi, this is the basic configuration of my desktop: -Motherboard: ROG STRIX X370-F GAMING. -CPU: Ryzen 7 1700. -GPU: GTX 1050 2GB from MSI. I don't know if the bug I have is this one, but sometimes, after successfully login, the screen goes black in the first 10 minutes. On Ubuntu 17.10 I could see a message about "stopping user manager for uid", but on 18.04 I only see information about storage I always get in the boot process, nothing apparently bad. I used different versions of the NVIDIA blob driver without getting different results, but the error didn't appear in almost one month using Linux Mint, so I think the problem is from Ubuntu's stack. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I forgot to say I will try with nomodeset in my Grub config first. If that doesn't work, I will switch from GDM to LightDM. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768176] Re: Unable to suspend computer
Hi Tom-lorinthe... I'm not so sure what is your suggestion. I should add "acpi_rev_override=1" after GRUB_CMDLINE_LINUX_DEFAULT="splash acpi_rev_override=1 nouveau.runpm=0"?? In my case, when I run that command that line is commented as GRUB_CMDLINE_LINUX_DEFAULT="quiet splash". I am running Ubuntu 18.04, fresh install from April 26th on a Lenovo e11. Everything works fine but the suspend feature; not with all windows closed, not at all, period. Some guidance would be grateful. Cheers. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1768176 Title: Unable to suspend computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1768176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
+1, using Ubuntu 18.04-beta here and it's not there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685647] Re: Upgrade to 17 doesn't work, gnome-terminal doesn't work
Duplicate of 1694454? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685647 Title: Upgrade to 17 doesn't work, gnome-terminal doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
I also encountered the same problem for Ubuntu 16.04, I've tried everything and nothing works. I hope they fix it soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717634] [NEW] Logging in regular Gnome displays classical
Public bug reported: I'm running Ubuntu 17.04. I changed to Gnome classic in the login screen, then logged in, logged out and chose regular Gnome, but I keep logging in Gnome classic every time. A workaround is to run "gnome-shell --mode=user -r" after every login. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717634 Title: Logging in regular Gnome displays classical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717634/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
** No longer affects: gnome-shell (Ubuntu) ** Also affects: gjs Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
It seems the last backtrace is from another bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
It seems the bug is not fully patched yet. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
It seems that the patch is now available. https://bugzilla.gnome.org/show_bug.cgi?id=781799#c90 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=781799 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
It seems that the patch will arrive soon. https://bugzilla.gnome.org/show_bug.cgi?id=781799#c57 ** Bug watch added: GNOME Bug Tracker #781799 https://bugzilla.gnome.org/show_bug.cgi?id=781799 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696112] [NEW] Visual Studio Code hanged installation at 51% and it got stuck indefenitely. I had to restart to install other software....
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 After restarting, the OS popped-up some crash report window... whatever. Using Ubuntu 17.04 from Virtual Box machine on Windows 10. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jun 6 08:53:12 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-06 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1696112 Title: Visual Studio Code hanged installation at 51% and it got stuck indefenitely. I had to restart to install other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1696112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"]
Reading Wayland events even on Xorg? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 ["(EE) failed to read Wayland events: Broken pipe"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04
** Tags removed: gnome-17.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell
** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1491787 Title: System language isn't applied to gnome-control-center in Gnome-Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04
** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] Re: GNOME Shell crashes randomly on Ubuntu GNOME 17.04
** Tags added: gnome-shell ** Tags added: gjs gnome-17.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695720] [NEW] GNOME Shell crashes randomly on Ubuntu GNOME 17.04
Public bug reported: https://bugzilla.gnome.org/show_bug.cgi?id=781799 https://bugzilla.redhat.com/show_bug.cgi?id=1451914 Hi, I'm experiencing the bug showed in the two links put above on Ubuntu GNOME 17.04. I just want to ask if the Ubuntu team or Ubuntu GNOME team will apply the patch for this bug on Ubuntu GNOME 17.04 (and the whole Ubuntu stack, obviously). The bug it's very difficult to reproduce, and I see that on Ubuntu GNOME is harder than on Manjaro GNOME. Nonetheless, I hope that you will consider to apply the patch when it's available, because the bug is really annoying. If there is some way to collect the info of the bug when it happens, I want to know it, because apport-gtk doesn't appear when it happens. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1695720 Title: GNOME Shell crashes randomly on Ubuntu GNOME 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string
@johnwang I guess you meant $ sudo mv /etc/apt/apt.conf.d/50appstream /etc/apt/apt.conf.d/50appstream.disabled -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs due to strdup on non-NULL terminated string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string
Removing appstreamcli seems to do the trick. I'm not aware of side effects sudo rm /usr/bin/appstreamcli Source: http://trastetes.blogspot.com/2016/02/solucion-al-error-e-then- appstreamcli.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs due to strdup on non-NULL terminated string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string
Neither can I install any update, even after disabling third-party repositories. appstreamcli hangs refreshing with 100% cpu use apt update hangs after 'Fetched XXX kb in Xs (XXX kb/s)' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs due to strdup on non-NULL terminated string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534672] [NEW] package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: the package cannot be reinstaled nor eliminated by apt-get ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shotwell-common 0.18.0-0ubuntu4.4 ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Jan 13 11:39:23 2016 DuplicateSignature: package:shotwell-common:0.18.0-0ubuntu4.4:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-10 (96 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: shotwell Title: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1534672 Title: package shotwell-common 0.18.0-0ubuntu4.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1534672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272001] Re: Evolution black background in mail display
pato01's fix also working with Bluebird -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1272001 Title: Evolution black background in mail display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
Got the same error when opening files with Sublime text 2 from the console (sublime_text:15984): GLib-CRITICAL **: Source ID 1231 was not found when attempting to remove it -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1264368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1182205] Re: totem freezes after changing/disabling subtitle on mp4 files.
Running Linux Mint 16 Petra Cinnamon, same problem here. Just realized that it freezes when you try to switch off subtitles from the context menu (right click on movie screen) but not from the view menu on the toolbar. Also doesn't freeze when you switch from one to another subtitle. Hope it helps. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1182205 Title: totem freezes after changing/disabling subtitle on mp4 files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1182205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1050358] Re: emesene crashed with SIGSEGV in tupledealloc.24592()
** Changed in: emesene (Ubuntu) Assignee: (unassigned) = eduardo (lalo7america) ** Changed in: pygobject-2 (Ubuntu) Assignee: (unassigned) = eduardo (lalo7america) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1050358 Title: emesene crashed with SIGSEGV in tupledealloc.24592() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
The same problem in the ThinkPad L530 with Ubuntu 13.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1239218] Re: [regression] Rhythmbox crashes with segfault when playing next track
Looks like the problem gets triggered when catching the EOS signal on the backend player: self.__eos_id = backend_player.connect(eos, self.on_backend_eos) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1239218 Title: [regression] Rhythmbox crashes with segfault when playing next track To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1239218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1242806] Re: Rhytmbox 2.99.1 bug
After crashing with the same error as the one reported, I used to not be able to run rhythmbox again at all. Therefore, I have been using rhythmbox --disable-plugins to do so, but no plugins though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1242806 Title: Rhytmbox 2.99.1 bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1242806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246794] Re: rhythmbox crashed with SIGSEGV in sem_post() when trying to change tracks frequently
*** This bug is a duplicate of bug 1193525 *** https://bugs.launchpad.net/bugs/1193525 ** This bug is no longer a duplicate of private bug 1234645 ** This bug has been marked a duplicate of bug 1193525 rhythmbox crashed with SIGSEGV in sem_post() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1246794 Title: rhythmbox crashed with SIGSEGV in sem_post() when trying to change tracks frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1246794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 622004] Re: Rhythmbox does not remember column width
** Changed in: hundredpapercuts Assignee: Eduardo Carneiro (edu1910) = (unassigned) ** Changed in: hundredpapercuts Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/622004 Title: Rhythmbox does not remember column width To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1078693] [NEW] Can't add any account
Public bug reported: I have no accounts and when I try to add one, the drop-down list is empty next to the question What kind of chat account do you have?. Screenshot is attached. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Attachment added: empathy_blank_accounts.png https://bugs.launchpad.net/bugs/1078693/+attachment/3433109/+files/empathy_blank_accounts.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1078693 Title: Can't add any account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1078693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1078693] Re: Can't add any account
Installing the missing telepathy dependency solved it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1078693 Title: Can't add any account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1078693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 622004] Re: Rhythmbox does not remember column width
** Changed in: hundredpapercuts Assignee: Papercuts Ninja (papercuts-ninja) = Eduardo Carneiro (edu1910) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/622004 Title: Rhythmbox does not remember column width To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 622004] Re: Rhythmbox does not remember column width
** Changed in: hundredpapercuts Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/622004 Title: Rhythmbox does not remember column width To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819304] Re: gvfsd-cdda crashed with signal 5 in _g_dbus_oom()
I'm using gvs Version: 1.12.1-0ubuntu1.1 and the bug persists -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/819304 Title: gvfsd-cdda crashed with signal 5 in _g_dbus_oom() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/819304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405432] Re: gvfsd-metadata crashed with SIGSEGV in copy_tree_to_builder()
With me whenever I was creating a folder named data, an emblem of note was being created onto it, and Nautilus was crashing when opening this folder. rm -rf ~/.local/share/gvfs-metadata/ as Vlad pointed out solved it for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/405432 Title: gvfsd-metadata crashed with SIGSEGV in copy_tree_to_builder() To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/405432/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1028670] [NEW] Open file window bigger than the vertical resolution
Public bug reported: When you use some function as Open file (exemple: Open file inside LibreOffice), the window to choose the file sometimes is bigger than the monitor vertical resolution. This behavior is not necessary. Just show all the folders in the right side (places). Today, when you click Open file in any place (web, local applications, etc), sometimes, is needed to resize window. My resolution monitor is 1366x768 and the Open window takes almost all vertical size. In virtul machines with less than this vertical resolution (720px), is needed to resize window to reach the Open button. Solution: Make the open file window with fixed size instead to wait the user resize the window to reach the Open button. Maybe, smaller and centralized. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Tue Jul 24 20:07:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '1062x715+50+24' org.gnome.nautilus.window-state sidebar-width 174 org.gnome.nautilus.window-state start-with-status-bar true InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1028670 Title: Open file window bigger than the vertical resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1028670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1028670] Re: Open file window bigger than the vertical resolution
** Attachment added: Open File window in Ubuntu 12.04 + LibreOffice https://bugs.launchpad.net/bugs/1028670/+attachment/3234598/+files/Open01.jpeg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1028670 Title: Open file window bigger than the vertical resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1028670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1028176] Re: package shared-mime-info 1.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1028176 Title: package shared-mime-info 1.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1028176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1028176] [NEW] package shared-mime-info 1.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: none ProblemType: Package DistroRelease: Ubuntu 12.04 Package: shared-mime-info 1.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 23 17:49:14 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: shared-mime-info Title: package shared-mime-info 1.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1028176 Title: package shared-mime-info 1.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1028176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 972311] Re: Accessing a MTP device like the Galaxy Nexus fails
This makes me restart the pc on WIndows just to perform this task and then restart back on Ubuntu. It is very annoying at least. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/972311 Title: Accessing a MTP device like the Galaxy Nexus fails To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/972311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1010290] [NEW] package libglib2.0-0 2.24.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: I have tried to instal glib2.0 with a newer version manually without good results, I have tried to restore the system successfully but the auto updates for this package will not work fine since the last crash of my sistem. I think this is not exactly a bug but an non-expert administrator error. Do you know how to fix this error? Thanks! -- Information requested: 1) Ubuntu release: Ubuntu 10.04 LTS - the Lucid Lynx 2) Package information: libglib2.0-0: Installed: 2.24.1-0ubuntu1 Candidate: 2.24.1-0ubuntu1 Version table: *** 2.24.1-0ubuntu1 0 500 http://cr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.24.0-0ubuntu4 0 500 http://cr.archive.ubuntu.com/ubuntu/ lucid/main Packages 3) Auto-updates to work fine. 4) Auto-update of this package has crashed and did not happen. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libglib2.0-0 2.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-41.89-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic i686 NonfreeKernelModules: wl AptOrdering: libgio-fam: Install libgio-fam: Configure Architecture: i386 Date: Thu Jun 7 11:08:38 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: glib2.0 Title: package libglib2.0-0 2.24.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1010290 Title: package libglib2.0-0 2.24.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1010290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1010290] Re: package libglib2.0-0 2.24.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1010290 Title: package libglib2.0-0 2.24.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1010290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
