[Bug 1392616] Re: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
*** This bug is a duplicate of bug 1055197 *** https://bugs.launchpad.net/bugs/1055197 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 #1055197, 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/1392616/+attachment/4260373/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260375/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260376/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260377/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260378/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260379/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1392616/+attachment/4260380/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1055197 ** 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 rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1392616 Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1392616/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392637] [NEW] Cannot boot with newly installed systemd if /tmp/ is filled with files
Public bug reported: On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version). After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached). I then tried init=/lib/systemd/systemd in grub without quiet and splash and found that it was blocking on a start job is running for Create Volatile files and directories. A search on the internet later, I found that the problem was solved by this approach : http://forums.debian.net/viewtopic.php?f=10t=118008 So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works! While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?) This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: dpkg.log https://bugs.launchpad.net/bugs/1392637/+attachment/4260400/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392637 Title: Cannot boot with newly installed systemd if /tmp/ is filled with files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392640] [NEW] package libpam-systemd:amd64 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: while installin update I get this error ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Nov 14 11:41:38 2014 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu8.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2014-06-24 (143 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392640 Title: package libpam-systemd:amd64 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1067301] Re: ssh-add: Error reading response length from authentication socket.
The same symptoms seem to still be present in 14.04.1 LTS at least for ed25519 keys. RSA keys seem to work ok. $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 $ apt-cache policy gnome-keyring gnome-keyring: Installed: 3.10.1-1ubuntu4.1 Candidate: 3.10.1-1ubuntu4.1 Version table: *** 3.10.1-1ubuntu4.1 0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1067301 Title: ssh-add: Error reading response length from authentication socket. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1067301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392642] [NEW] Daemons are restarted in the current session cgroups
Public bug reported: (forwarded from the relevant bug report raised in Debian BTS and adapted for upstart as PID1) Daemons which are not spawned via an upstart job (eg. those with initscripts, ifupdown hooks and similar) are not detached from the current logind session cgroups. This causes the session to linger in the closing state until the background processes are either terminated or manually moved by root into the root cgroups, so seat ACLs are not released. A (very crude) workaround on Debian Jessie is using cgm movepidabs / $$ to break out of the current session before performing any administrative action which could result in a daemon (re)start, but cgmanager is not installed by default on Trusty and the version of cgm shipped with it lacks the movepidabs subcommand (even though the MovePidAbs method in the DBus interface does exist). Note that this affects anything that uses service, invoke-rc.d, ifupdown hooks (like ifup on PPPoE links) or initscripts directly. Upstart jobs are not affected because they inherit their cgroup set from PID1 (which lives in the root cgroup). Nota bene: I'm raising the issue on systemd-shim on advice from its maintainer, even though it's unclear at what level this behavior should be addressed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-shim 6-2bzr1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 14 10:36:01 2014 InstallationDate: Installed on 2012-09-30 (774 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: systemd-shim UpgradeStatus: Upgraded to trusty on 2014-08-18 (87 days ago) ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Affects: systemd-shim (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug trusty ** Bug watch added: Debian Bug tracker #769483 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769483 ** Also affects: systemd-shim (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769483 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1392642 Title: Daemons are restarted in the current session cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1392642/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392637] Re: Cannot boot with newly installed systemd if /tmp/ is filled with files
** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392637 Title: Cannot boot with newly installed systemd if /tmp/ is filled with files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1362765] Re: Location service should persist property states
** Changed in: location-service (Ubuntu) Importance: Undecided = Critical ** Changed in: location-service (Ubuntu) Status: Confirmed = In Progress ** Branch linked: lp:~thomas-voss/location-service/make-engine-state- persistent-across-boots-and-otas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1362765 Title: Location service should persist property states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1362765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1061195] Re: Can't create EWS or MAPI account
I have the same problem. The workarounds from the last two bug reports worked for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Can't create EWS or MAPI account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1061195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292282] Re: background transparency is not working on gnome terminal
seems fixed in vivid ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed = Fix Released -- 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/1292282 Title: background transparency is not working on gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1362765] Re: Location service should persist property states
** Also affects: location-service (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: location-service (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: location-service (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: location-service (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1362765 Title: Location service should persist property states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1362765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Also affects: trust-store (Ubuntu) Importance: Undecided Status: New ** Changed in: trust-store Importance: Undecided = Critical ** Changed in: trust-store Status: New = Confirmed ** Changed in: trust-store (Ubuntu) Status: New = Confirmed ** Changed in: trust-store (Ubuntu) Importance: Undecided = Critical ** Also affects: trust-store (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: trust-store (Ubuntu RTM) Status: New = Confirmed ** Changed in: trust-store (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: trust-store (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: location-service (Ubuntu) Status: Confirmed = Invalid ** Changed in: location-service (Ubuntu) Assignee: Thomas Voß (thomas-voss) = (unassigned) ** Changed in: trust-store Assignee: (unassigned) = Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Changed in: trust-store (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Branch linked: lp:~thomas-voss/trust-store/fix-1387734 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392399] Re: Enabling/Disabling the GPS provider does not reliably enforce the provider to be stopped
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1392399 Title: Enabling/Disabling the GPS provider does not reliably enforce the provider to be stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1392399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1362765] Re: Location service should persist property states
** Description changed: - Thus preserving user choices across reboots. + Thus preserving user choices across reboots and otas ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1362765 Title: Location service should persist property states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1362765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292282] Re: background transparency is not working on gnome terminal
Will it be backported to LTS? -- 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/1292282 Title: background transparency is not working on gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392717] [NEW] directory picker failure
Public bug reported:
Steps:
1) in a empty directory, create 2 (or more) directories with the same prefix
(e.g. '2014', '2015')
2) start a directory picker in any application that use it : nautilus, gthumb,
...
3) click on the 'Type a file name' button (the pen on the top left)
4) use the directory picker to select one of these directories ('2014')
5) you can't - there's still the prefix ('201')
screencast available here:
http://youtu.be/FxEMTHe_k1o
This bug won't happen if :
- there is a directory which doesn't share the same prefix
- you don't use the 'Type a file name' button. Once you have use it, it will be
activated for every directory chooser you start.
standard 14.04.1 installation (unity), last updates
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty
** Package changed: shotwell (Ubuntu) = nautilus (Ubuntu)
** Description changed:
Steps:
- 1) in a empty directory, create 2 (or more) directory with the same prefix
(e.g. '2014', '2015')
+ 1) in a empty directory, create 2 (or more) directories with the same prefix
(e.g. '2014', '2015')
2) start a directory picker in any application that use it : nautilus,
gthumb, ...
3) click on the 'Type a file name' button (the pen on the top left)
4) use the directory picker to select one of these directories ('2014')
5) you can't - there's still the prefix ('201')
screencast available here:
http://youtu.be/FxEMTHe_k1o
This bug won't happen if :
- there is a directory which doesn't share the same prefix
- you don't use the 'Type a file name' button. Once you have use it, it will
be activated for every directory chooser you start.
standard 14.04.1 installation (unity), last updates
--
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/1392717
Title:
directory picker failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1392717/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
This is CVE-2014-1422 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-1422 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1270251] Re: package shotwell 0.15.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/shotwell/ui/collection.ui', which is also in package shotwell-common 0.15.0-0ubuntu1
** Changed in: shotwell Status: Unknown = Fix Released ** Changed in: shotwell Importance: High = Medium -- 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/1270251 Title: package shotwell 0.15.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/shotwell/ui/collection.ui', which is also in package shotwell-common 0.15.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1270251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335102] Re: Stopping positioning updates/the gps provider should release wake lock
** Changed in: location-service (Ubuntu RTM) Status: New = In Progress ** Changed in: location-service (Ubuntu RTM) Importance: Undecided = High ** Changed in: location-service (Ubuntu) Status: In Progress = Invalid ** Changed in: location-service (Ubuntu RTM) Status: In Progress = Invalid ** Also affects: platform-api (Ubuntu) Importance: Undecided Status: New ** Also affects: platform-api (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: location-service (Ubuntu) Assignee: Thomas Voß (thomas-voss) = (unassigned) ** Changed in: platform-api (Ubuntu) Importance: Undecided = High ** Changed in: platform-api (Ubuntu RTM) Importance: Undecided = High ** Changed in: platform-api (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: platform-api (Ubuntu RTM) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: platform-api (Ubuntu) Status: New = In Progress ** Changed in: platform-api (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1335102 Title: Stopping positioning updates/the gps provider should release wake lock To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1335102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335102] Re: Stopping positioning updates/the gps provider should release wake lock
** Branch linked: lp:~thomas-voss/platform-api/fix-1335102 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1335102 Title: Stopping positioning updates/the gps provider should release wake lock To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1335102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335102] Re: Stopping positioning updates/the gps provider should release wake lock
** Also affects: location-service (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1335102 Title: Stopping positioning updates/the gps provider should release wake lock To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1335102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
** Description changed: The bug occurs after removing location access authorization to an application. The location is still available to the application, despite the user having revoked access from within USS Privacy Location. To reproduce: 1. Open a map application, like Here map 2. Allow access to location 3. Switch to System Settings Privacy Location 4. Disable location access for Maps 5. Kill Here map, and restart it What should happen: you should not have access anymore (and should not see a prompt) What happens instead: the app still has access to your location, as shown in the logs: I1030 16:15:38.167752 3100 cached_agent_glog_reporter.cpp:32] CachedAgent::authenticate_request_with_parameters: Application pid: 27975 Application uid: 32011 Application id: com.nokia.heremaps_here Cached request: Request(from: com.nokia.heremaps_here, feature: 0, when: 1414682114882519283, answer: granted) I confirmed that the trust store had recorded the authorization change as in: phablet@ubuntu-phablet:~$ sqlite3 ~/.local/share/UbuntuLocationService/trust.db select * from requests 1|unconfined|0|1414098093331252474|1 2|com.nokia.heremaps_here|0|1414682114882519283|1 3|com.nokia.heremaps_here|0|1414682131206341515|0 + + From a user's perspective: Despite having explicitly rejected trust to + an application, the app would still be able to access services. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1335102] Re: Stopping positioning updates/the gps provider should release wake lock
** Description changed: The GPS provider implementation takes a wake-lock on behalf of the GPS chipset driver whenever the positioning engine is enabled. We have to make sure that the wake-lock is released as early and as aggressively as possible such that we do not prevent the device from going to deep sleep. + + From a user's perspective: Battery life is likely to suffer as we do not + ensure on this level that the respective wake lock is given up. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1335102 Title: Stopping positioning updates/the gps provider should release wake lock To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1335102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1059107] Re: recipient address: comma inserted when pressing AltGr
*** This bug is a duplicate of bug 943104 *** https://bugs.launchpad.net/bugs/943104 ** This bug has been marked a duplicate of bug 943104 recipient address: comma inserted when pressing AltGr -- 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/1059107 Title: recipient address: comma inserted when pressing AltGr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1059107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app
This will need an update to utopic-security as well (for when rtm syncs back up). ** Also affects: location-service (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: trust-store (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: location-service (Ubuntu Vivid) Importance: Critical Status: Invalid ** Also affects: trust-store (Ubuntu Vivid) Importance: Critical Assignee: Thomas Voß (thomas-voss) Status: Confirmed ** Changed in: location-service (Ubuntu Utopic) Status: New = Invalid ** Changed in: trust-store (Ubuntu Utopic) Status: New = Confirmed ** Changed in: trust-store (Ubuntu Utopic) Importance: Undecided = Critical ** Changed in: trust-store (Ubuntu Utopic) Assignee: (unassigned) = Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387734 Title: Location service uses the cached authorization, even if the user denied location access to an app To manage notifications about this bug go to: https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392728] [NEW] Vinagre terminate on connection loss
Public bug reported: It would be nice if vinagre had the option to terminate when the connection is lost. Thus, if started from commandline, the window closes automatically when the connection is lost. ** Affects: vinagre (Ubuntu) Importance: Undecided Status: New -- 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/1392728 Title: Vinagre terminate on connection loss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1392728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
I guess I don't fully get your response. This has been noted as a bug since saucy and has never had a patch or workaround associated with it (other than using bluman instead of gnome-bluetooth). Is there a better bug list for gnome specific problems than here? -- 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/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392785] [NEW] Chat messages with no formatting when using Ubuntu theme
Public bug reported: Please see the attached image. The third conversation box is not formatted and the contact name does not appear. This is happening with many different contacts. But it seems to happen only when the default Ubuntu theme is set. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 14 13:41:50 2014 InstallationDate: Installed on 2014-08-05 (101 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: empathy.png https://bugs.launchpad.net/bugs/1392785/+attachment/4260551/+files/empathy.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/1392785 Title: Chat messages with no formatting when using Ubuntu theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1392785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392600] [NEW] Unable to rename folders/files in Nautilus
You have been subscribed to a public bug: This is weird. After restarting my machine I can rename folders or files in Nautilus for the first few minutes. After that I cannot rename them anymore. When I hit F2 on a folder the whole folder name is highlighted and selected. Then, when I type, no changes become visible. It just does not react at all on my keyboard input. Really weird and bad. I have to go into the terminal to rename files/folders with the `mv` command :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael-heuberger 2289 F pulseaudio /dev/snd/controlC1: michael-heuberger 2289 F pulseaudio /dev/snd/controlC0: michael-heuberger 2289 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 14 19:15:54 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (14 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug nautilus third-party-packages utopic -- Unable to rename folders/files in Nautilus https://bugs.launchpad.net/bugs/1392600 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392600] Re: Unable to rename folders/files in Nautilus
** Package changed: linux (Ubuntu) = nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: Confirmed = New -- 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/1392600 Title: Unable to rename folders/files in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1392600/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
apt-mark lightdm hold apt-get dist-upgrade reboot Indeed, logins are fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
Hmm, as 1.13.0-0ubuntu1 just showed up in vivid, it broke my login in the follow way. Note that I always try devel channel updates in a VM with a snapshotted disk so I'm able to revert and do some further investigating. Looking at the dist-upgrade packages, I suspect the lightdm changes are affecting me, but I'm going to continue to investigate. So, when I log in, I do get several warnings in a dialog. Most are because I use `source` instead of `.` to source other shell files. What shell is lightdm using these days? Still, even with the warnings, I can log in just fine. Anyway, when I change them all to `.` I still get one warning about my use of shopt, but I'll just ignore that for now. However, logins are now completely broken. I see the screen blank and then I'm thrown back to the login screen. ~/.xsession-errors is empty and I can find no other log file either in $HOME or /var/log that contains any information about what's going wrong. I'm going to pin lightdm and dist-upgrade everything else just to verify that the lightdm update is causing my problems. How can I debug the login crash after I fix my login scripts? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
pay-service crashed, leaving a core file and the following in .xsesssion.old. Not sure if this is related. upstart: pay-service main process (6149) killed by ABRT signal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
For now I'll keep the hold on lightdm, but if Robert or someone else wants to debug in real-time, ping me on irc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390224] Re: Enable gnome-shell search provider
This bug was fixed in the package gnome-terminal - 3.14.1-1ubuntu1 --- gnome-terminal (3.14.1-1ubuntu1) vivid; urgency=medium [ Iain Lane ] * Merge with Debian, remaining changes: - debian/patches/50_add_unity_quicklist.patch: Add Unity quicklist menu item. - debian/patches/52_support_apturl.patch: Support apt: urls. - debian/patches/60_add_lp_handler.patch: Add a handler for launchpad bug URLs. - debian/patches/0001-Restore-transparency.patch: Restore transparency support, dropped upstream. Patch from Debarishi Ray, modified by Iain Lane to support a 'theme' default value. - Add 61_cwd_fallback.patch: Provide fallback for reading current directory if OSC 7 fails. * debian/patches/0001-window-Make-the-drawing-robust-across-all-themes.patch: Make sure the window always draws a background, even when transparency is on. * Disable shell provider, we don't want to build-dep on gnome-shell. [ Tim Lunn ] * Add gnome-shell_search_provider.patch: provide a local copy of the dbus interface so can build shell search provider without depending on gnome-shell which is in universe (LP: #1390224) gnome-terminal (3.14.1-1) unstable; urgency=medium * New upstream release. gnome-terminal (3.14.0-1) unstable; urgency=medium * New upstream release. * Bump build-depencencies according to configure.ac changes: + libgtk-3-dev (= 3.10.0), + libvte-2.91-dev (= 0.38.0), * Drop libgtk2.0-dev build-dependency. * Make debian/patches/01_onlyshowin.patch apply again. * Have quilt refresh remaining patches. * Upload to unstable. gnome-terminal (3.13.90-1) experimental; urgency=medium [ Simon McVittie ] * Be Multi-Arch: foreign so gnome-terminal:amd64 can satisfy a dependency from, e.g., steam:i386 (Closes: #698957) [ Sjoerd Simons ] * New upstream release * Add valac (= 0.24) to b-d gnome-terminal (3.12.3-2) unstable; urgency=medium * Team upload. * When we ask the system theme how to draw a TerminalScreen widget, if it answers black text on a black background (like the built-in fallback theme in Gtk 3.14, Raleigh), instead draw black text on a white background like the GNOME default theme Adwaita does. (Closes: #683744) * Tell dh_makeshlibs that the libterminal-nautilus.so plugin is not a shared library (workaround for #204975) gnome-terminal (3.12.3-1) unstable; urgency=medium * New upstream release. * Bump libvte-2.90-dev build-dependency to = 1:0.36.3 - as required by configure.ac * Bump Standards-Version to 3.9.5 -- Iain Lane iain.l...@canonical.com Fri, 14 Nov 2014 16:39:19 + ** Changed in: gnome-terminal (Ubuntu) Status: Fix Committed = Fix Released -- 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/1390224 Title: Enable gnome-shell search provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1390224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1362840] Re: Unable to access “640 GB Volume”
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- 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/1362840 Title: Unable to access “640 GB Volume” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1362840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
Hi Barry!
On 2014-11-14 17:56, Barry Warsaw wrote:
So, when I log in, I do get several warnings in a dialog. Most are
because I use `source` instead of `.` to source other shell files.
What shell is lightdm using these days?
It has always been using Bourne shell, so source is not understood.
You have obliviously been running your system without the configuration
in those other shell files.
Anyway, when I change them all to `.` I still get one warning about
my use of shopt,
Another bash command, not understood by dash.
However, logins are now completely broken. I see the screen blank and
then I'm thrown back to the login screen. ~/.xsession-errors is
empty and I can find no other log file either in $HOME or /var/log
that contains any information about what's going wrong.
This is the code in /usr/sbin/lightdm-session which triggers those
warning dialogs:
code
# temporary storage of error messages
ERR=$(mktemp --tmpdir config-err-XX)
source_with_error_check () {
CONFIG_FILE=$1
if sh -n $CONFIG_FILE 2$ERR; then
echo Loading $CONFIG_FILE;
. $CONFIG_FILE 2$ERR
if [ -s $ERR ]; then
SYNTAX=false
. /usr/lib/lightdm/config-error-dialog.sh
fi
else
SYNTAX=true
. /usr/lib/lightdm/config-error-dialog.sh
fi
cat $ERR /dev/stderr
truncate -s 0 $ERR
}
# Load profile
for file in /etc/profile $HOME/.profile \
/etc/xprofile $HOME/.xprofile; do
if [ -f $file ]; then
source_with_error_check $file
fi
done
/code
I find it hard to believe that that code itself is causing the problem
you describe. Considering that you could log in just fine before you
changed the occurrences of source to ., I would look for the cause
in the code which unlike before is now sourced by lightdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 678421] Re: Error message for a faulty ~/.profile script
Hi Gunnar. On Nov 14, 2014, at 07:07 PM, Gunnar Hjalmarsson wrote: It has always been using Bourne shell, so source is not understood. You have obliviously been running your system without the configuration in those other shell files. Sure, it's entirely possibly that my login has been silently ignoring the non-sh syntax errors, so in that respect, getting notification of them now is a good thing. I still wonder what in my shell code could be causing lightdm to exit back to the login screen and where those errors would be logged so that I can view them and debug them. Cheers. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
Being thrown back indicates a syntax error. One thing you could do is testing each one of your sourced files like this: sh -n file The files must pass that test, or else you won't be able to log in. This is what the new lightdm code does, but it does not work recursively... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
On 2014-11-14 20:43, Barry Warsaw wrote: Sure, it's entirely possibly that my login has been silently ignoring the non-sh syntax errors, so in that respect, getting notification of them now is a good thing. The use of commands unknown to sh is one kind of error that was silently ignored. However, that's not a syntax error. Syntax errors was not ignored. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote: Being thrown back indicates a syntax error. Are those errors logged anywhere permanently? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
On 2014-11-14 21:45, Barry Warsaw wrote: On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote: Being thrown back indicates a syntax error. Are those errors logged anywhere permanently? I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile are logged in ~/.xsession-errors both with the latest lightdm version and with previous versions, but I don't know whether syntax errors in files which are sourced from those files are logged anywhere. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 09:59 PM, Gunnar Hjalmarsson wrote: I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile are logged in ~/.xsession-errors both with the latest lightdm version and with previous versions, but I don't know whether syntax errors in files which are sourced from those files are logged anywhere. I guess they aren't because ~/.xsession-errors is empty when lightdm exits back to the login screen. :( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
I created the file /etc/profile.d/wrong.sh with a sh syntax error. With lightdm 1.12.1-0ubuntu1 the reason for the login failure is logged in ~/.xsession-errors, but with the latest lightdm version it's not. So there is a regression with the fix of this bug. The reason is that stderr is temporarily redirected to /tmp/config-err- XX. Actually, if you are thrown back to the login screen and log in via a console to investigate the reason, you can find the error message in that /tmp file. OTOH, that's not documented anywhere... Right now I don't know how to best deal with this issue. Any advice appreciated. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote: Right now I don't know how to best deal with this issue. Any advice appreciated. Probably use tee(1) to get the output both into the temp file and ~/.xsession-errors. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392915] [NEW] Misssing header files from c++/usr/include/c++/4.8/
Public bug reported: For some reason, /usr/include/c++/4.8/string is missing from Ubuntu 14.04 by installing ii gcc-4.8-base4.8.2-15 ii libc6-dev 2.17-97 ii libgcc-4.8-dev 4.8.2-15 ii libstdc++6 4.8.2-15 it shuold have provided string but it does not 'find /usr/include/c++ -name string' returns nothing. dpkg-query -L libstdc++-4.8-dev | grep string /usr/include/c++/4.8/debug/string /usr/include/c++/4.8/cstring /usr/include/c++/4.8/ext/pb_ds/detail/trie_policy/trie_string_access_traits_imp.hpp /usr/include/c++/4.8/ext/string_conversions.h /usr/include/c++/4.8/ext/rc_string_base.h /usr/include/c++/4.8/ext/vstring.h /usr/include/c++/4.8/ext/sso_string_base.h /usr/include/c++/4.8/ext/vstring_fwd.h /usr/include/c++/4.8/ext/vstring_util.h /usr/include/c++/4.8/ext/vstring.tcc /usr/include/c++/4.8/string /usr/include/c++/4.8/bits/stringfwd.h /usr/include/c++/4.8/bits/basic_string.h /usr/include/c++/4.8/bits/basic_string.tcc string did not get installed for some reason ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 13 21:25:02 2014 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-10-14 (30 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1392915 Title: Misssing header files from c++/usr/include/c++/4.8/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1392915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 487908] Re: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/487908 Title: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/487908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 487908] Re: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pavucontrol (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/487908 Title: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/487908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 487908] Re: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
** Also affects: gedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/487908 Title: freeze Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/487908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 678421] Re: Error message for a faulty ~/.profile script
On 2014-11-15 00:49, Barry Warsaw wrote: On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote: Right now I don't know how to best deal with this issue. Any advice appreciated. Probably use tee(1) to get the output both into the temp file and ~/.xsession-errors. Yeah.. But I fear that would make the code much more complicated. Or do you have an idea, given the current code as shown in comment #33? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390490] Re: Race between connectivity-api and network-manager
** Branch linked: lp:ubuntu/ubuntu-location-provider-here -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1390490 Title: Race between connectivity-api and network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-location-provider-here/+bug/1390490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390490] Re: Race between connectivity-api and network-manager
** Branch linked: lp:ubuntu/location-service -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1390490 Title: Race between connectivity-api and network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-location-provider-here/+bug/1390490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1059767] Re: Empathy wrong background color selection in kubuntu
** Changed in: empathy Status: Incomplete = New -- 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/1059767 Title: Empathy wrong background color selection in kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1059767/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392955] [NEW] [Feature request] Edit link target of a symbolic link
*** This bug is a duplicate of bug 154954 *** https://bugs.launchpad.net/bugs/154954 Public bug reported: ## Explanation I'd like to change the target of a symbolic link from absolute path to relative path, but I failed to find the option in file properties UI. ## Upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=46306 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 15 15:20:59 2014 GsettingsChanges: InstallationDate: Installed on 2014-11-10 (4 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Bug watch added: GNOME Bug Tracker #46306 https://bugzilla.gnome.org/show_bug.cgi?id=46306 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=46306 Importance: Unknown Status: Unknown -- 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/1392955 Title: [Feature request] Edit link target of a symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1392955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1392955] Re: [Feature request] Edit link target of a symbolic link
*** This bug is a duplicate of bug 154954 *** https://bugs.launchpad.net/bugs/154954 ** This bug has been marked a duplicate of bug 154954 [wishlist] simlink target should be editable -- 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/1392955 Title: [Feature request] Edit link target of a symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1392955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
