[Bug 1235532] Re: gconf still a depen because gconf-defaults file forgotten in tree
This is fixed in Ubuntu 16.04 LTS. It looks like it was fixed in https://launchpad.net/ubuntu/+source /gnome-user-share/3.0.4-0ubuntu2 I guess gconf-defaults no longer forces a gconf dependency. ** Changed in: gnome-user-share (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1235532 Title: gconf still a depen because gconf-defaults file forgotten in tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1235532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1332648] Re: Wrong bluetooth pairing PIN reported for Logitech K810
The solution is easy: Just grab the same code from hcidump. The implementation is hard, because ssems need an exception for this model. Any news about that? Someone posts this bug on Gnome Bugzilla? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1332648 Title: Wrong bluetooth pairing PIN reported for Logitech K810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1332648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1332648] Re: Wrong bluetooth pairing PIN reported for Logitech K810
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1332648 Title: Wrong bluetooth pairing PIN reported for Logitech K810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1332648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1611165] Re: Update to 3.20.2
Debian reverted the commits that required the newer freerdp: https://launchpad.net/ubuntu/+source/vinagre/3.22.0-1 ** Changed in: vinagre (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1611165 Title: Update to 3.20.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1611165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
I had a similar problem show up on Lubuntu 16.04 (i386). One thing that SEEMS to work (it actually made a Samsung phone reboot!) is 1) disable the "USB debugging" on the phone; 2) set the phone to Airplane mode (so it doesn't try to make a network connection). In my case, running `dmesg` it seems that Network Manager was trying to set a network connection: [ 1039.598665] cdc_acm 1-3:1.1: ttyACM0: USB ACM device HTH. -- 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/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629600] [NEW] Installed application from .deb does not appear unless Ubuntu is restarted
Public bug reported: I'm using Ubuntu 16.04 x64 and the installed version of gnome-software is 3.20.1 * I install a desktop application from a .deb package. I tried several methods (apt install, dpkg -i, xdg-open then click on install button). * After the installation, I control that the application is visible from the system: * The application appears correctly in the application list in Unity Dash * The application appears in the "Open With" menu list in Nautilus (because of registered mime types) * The package name of the application can be used as an argument of apt commands (apt show, apt remove...) and dpkg (dpkg -l, dpkg -L...) * I start gnome-software. * I click on the "installed" tab to get the list of installed applications. expected result: the freshly installed application is in the list actual result: the freshly installed application is not in the list. If I reboot my computer and start gnome-software, the installed application appears in the list. It looks like there is some kind of cache that is not refreshed at the right moment. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1629600 Title: Installed application from .deb does not appear unless Ubuntu is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1629600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1066658] Re: gedit opens on wrong screen
*** This bug is a duplicate of bug 874146 *** https://bugs.launchpad.net/bugs/874146 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1066658 Title: gedit opens on wrong screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1066658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
On Sat, Oct 01, 2016 at 01:53:56PM -, Martin Pitt wrote: > > To fix that, something like comment #3 is needed. Such as looping over > all 'active' units that are PartOf graphical-session.target and stopping > them all. > > I think we would only need to "systemctl stop graphical-session.target" > for this, otherwise a unit forgets the PartOf= and that loop would not > work anyway. I tried this, but I think that it might have only been before I worked out the below ExecStopPost issue - so it's worth testing again. > > > gnome-session needs a fix to its ExecStopPost to not kill the one we > just started. > > This is similar to waiting for "deactivating" units after > *-session.target goes down. On the systemd sprint we just figured out a > better scheme for this which solves that waiting, does not require this > session ID tracking, and also gets rid of the manual starting of > graphical-session-pre.target: Eventually we just want to declare in > *-session.target that it comes After=graphical-session-pre.target and > have this propagate to the dependencies > (https://github.com/systemd/systemd/issues/3750). Until then we can just > have a mini-generator do this for us. After we have the Requires/After > =graphical-session-pre.target, then "systemctl stop graphical-session- > pre.target" properly blocks until all "later" units are completely > stopped. I remember this problem. It would only solve this specific issue if it lets us get rid of the stop or restart in the session-runner script. If you ever end up stopping gnome-keyring from within a new session then its ExecStopPost kills the upstart session of this new one that we are starting up, *not* the previous one that it was started up under. That's a mismatch vs. session and user specific semantics of upstart and systemd --user. Hmm. Maybe this is saying that we should bind ubuntu-session.target to something else - like unity7? You can't log in again with an active unity7, so in theory (if stop is propagated down to graphical-session and graphical-session-pre) there wouldn't be a need to stop/restart in the script since everything would be stopped by definition if you're trying to start unity7 again. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548841] Re: Text Menus not displaying - org.gtk.vfs.Daemon
** Changed in: gvfs (Ubuntu) Status: Expired => Incomplete -- 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/1548841 Title: Text Menus not displaying - org.gtk.vfs.Daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1548841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1613916] Re: Unable to move a maximized window to an upper workspace
A little update on the bug: it also affects windows that are snapped to the sides of the desktop, and with programs running under WINE it does not work at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwnck in Ubuntu. https://bugs.launchpad.net/bugs/1613916 Title: Unable to move a maximized window to an upper workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck/+bug/1613916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629579] Re: Nautilus does not launch becuase it cannot find commons_comun
Fixed! If a nautilus python extension under /usr/share/nautilus- python/extensions/ cannot import a python module it crashes. It was a pushbullet problem. Please mark as closed, Thanks. -- 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/1629579 Title: Nautilus does not launch becuase it cannot find commons_comun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1629579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629579] [NEW] Nautilus does not launch becuase it cannot find commons_comun
Public bug reported: What i except to happen is nautilus launches and displays folders on the desktop. However, instead it crashes because it cannot find 'commons_comun' $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy nautilus nautilus: Installed: 1:3.20.3-1ubuntu2 Candidate: 1:3.20.3-1ubuntu2 Version table: *** 1:3.20.3-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Oct 1 10:55:10 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+1074'" InstallationDate: Installed on 2016-07-04 (89 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-09-30 (0 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 gnome-user-share 3.14.2-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1629579 Title: Nautilus does not launch becuase it cannot find commons_comun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1629579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315273] Re: Some characters with diacritics not displayed
** Changed in: evince Status: New => Unknown -- 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/1315273 Title: Some characters with diacritics not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1315273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
> To fix that, something like comment #3 is needed. Such as looping over all 'active' units that are PartOf graphical-session.target and stopping them all. I think we would only need to "systemctl stop graphical-session.target" for this, otherwise a unit forgets the PartOf= and that loop would not work anyway. > gnome-session needs a fix to its ExecStopPost to not kill the one we just started. This is similar to waiting for "deactivating" units after *-session.target goes down. On the systemd sprint we just figured out a better scheme for this which solves that waiting, does not require this session ID tracking, and also gets rid of the manual starting of graphical-session-pre.target: Eventually we just want to declare in *-session.target that it comes After=graphical-session-pre.target and have this propagate to the dependencies (https://github.com/systemd/systemd/issues/3750). Until then we can just have a mini-generator do this for us. After we have the Requires/After =graphical-session-pre.target, then "systemctl stop graphical-session- pre.target" properly blocks until all "later" units are completely stopped. ** Bug watch added: github.com/systemd/systemd/issues #3750 https://github.com/systemd/systemd/issues/3750 -- 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/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629548] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1628350 *** https://bugs.launchpad.net/bugs/1628350 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1628350, so 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1629548/+attachment/4752330/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752332/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752335/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752336/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752337/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752338/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1629548/+attachment/4752339/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1628350 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1629548 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1629548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
