[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
See for workaround: - https://wiki.ubuntuusers.de/ecryptfs/Einrichten/#Problembehebung - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854#107 -- 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/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
** Bug watch added: Debian Bug tracker #765854 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 ** Also affects: ecryptfs-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 Importance: Unknown Status: Unknown -- 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/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862617] [NEW] Whoopsie sends non-existent crash
Public bug reported: apport-cli says: Keine aktuellen Absturzberichte. (Means: No crash report.) But Whoopsie insist on sending a report on every re-boot. Das nervt!!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 10 12:06:21 2020 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-10-22 (475 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1862617 Title: Whoopsie sends non-existent crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1862617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
I get this error from the sessiom of GDM3: $ journalctl -b -u user-120.slice -p 0..6 | grep -e gdm -e icc Aug 19 16:28:21 lieselotte systemd[1]: Created slice User Slice of gdm. Aug 19 16:28:21 lieselotte systemd[911]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Aug 19 16:28:41 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung Aug 19 16:28:42 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung gsd-color from user id 120 trys reading a private file of user id 1000. That seems wrong by design. It's a security fault. -- 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/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80220] Re: ability to print several images
** Tags added: xenial ** Tags removed: xenial ** Tags added: trusty ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/80220 Title: ability to print several images To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/80220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1568491] [NEW] rhythmbox crashed with SIGSEGV in g_value_object_collect_value()
> Rhythmbox Version 3.3, package version 3.3-1ubuntu6. > Upgrade to package version 3.3-1ubuntu7. Still crashes. -- 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/1568491 Title: rhythmbox crashed with SIGSEGV in g_value_object_collect_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1568491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1556924] Re: rhythmbox crashed with SIGSEGV in tracker_evt_update_orphan_item_cb() (when grilo media tracker is enabled)
*** This bug is a duplicate of bug 1568491 *** https://bugs.launchpad.net/bugs/1568491 ** This bug has been marked a duplicate of bug 1568491 rhythmbox crashed with SIGSEGV in g_value_object_collect_value() -- 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/1556924 Title: rhythmbox crashed with SIGSEGV in tracker_evt_update_orphan_item_cb() (when grilo media tracker is enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1556924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1568491] Re: rhythmbox crashed with SIGSEGV in g_value_object_collect_value()
Am Montag, den 11.04.2016, 14:42 + schrieb Sebastien Bacher: > Thank you for your bug report. Do you have cross-fading enable in the > preferences? Does it work if you disable it? Cross-fading was not enabled. En-/disable this option does not help. All plugins except grilo disabled, selecting Radio France crashes Rhythmbox. Jamendo works as expected. -- 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/1568491 Title: rhythmbox crashed with SIGSEGV in g_value_object_collect_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1568491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568491] Re: rhythmbox crashed with SIGSEGV in g_value_object_collect_value()
** Information type changed from Private to Public -- 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/1568491 Title: rhythmbox crashed with SIGSEGV in g_value_object_collect_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1568491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 973295] Re: Enable grilo plugin
Need grilo support backported to current LTS version (trusty, 14.04) ! -- 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/973295 Title: Enable grilo plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
@#22: Seth Arnold, I agree that there must be better solution. The easiest may be just changing in network-manager the configuration for dnsmasq by omitting the option --cache-size=0. But: I am not package maintainer or developer for whoopsie, network-manager or dnsmasq and I do not fully understand your technical hints. I am just an Ubuntu user affected by this annoying bug open for more than 2 1/2 years. I do not know why whoppsie must look at DNS every minute and why network-manager starts a caching DNS forwarder without cache. I just want get rid of this dammed traffic. As far as I can see, my wrapper script helps. I will use it until the package maintainers and developers for whoopsie, network-manager or dnsmasq provide a better solution of their choice. -- 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/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
More experiments, results and proposed solution: 1) On a system with whoopsie running network-manager NOT running, but network interface initialized via /etc/network/interfaces dnsmask running with network-managers configuration for dnsmasq IPv6 aktivated I see the annoying repetive DNS-traffic for daisy.ubuntu.com. One or more packets per minute. This proves network-manager itself is not the bad guy! 2) Network-manager provides a configuration to dnsmask which disabled cache (--cache-size=0). Removing this option from dnsmasq configuration reduces traffic rate to 1 packet per 10 minutes. This corresponds to the lifetime for the DNS record of daisy.ubuntu.com which is set to 600 seconds. 3) Running network-manager again and dnsmasq started from network- manager, but with the modified configuration shows same result as #2. 4) HOWTO modify configuration for dnsmasq: Network-manager provides the option --cache-size=0 as argument on command line. This cannot be overriden by config-files, but you can use a wrapper script which is called by network-manager instead of real dnsmasq. The fake dnsmask purges the option --cache-size=0 and calls the real dnsmasq. I provide this wrapper script as attachment. Place it in /usr/local/sbin (this directory is searched before /usr/sbin), name it dnsmasq, set owner and group to root and set execute bits. Use at own risk. Enjoy! ** Attachment added: wrapper script for dnsmasq, purges option --cache-size=0 https://bugs.launchpad.net/whoopsie/+bug/991481/+attachment/4276624/+files/dnsmasq -- 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/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
I did some experiments on an Ubuntu GNOME 14.04 LTS desktop standard installation. There are 4 (!) components involved in this annoying traffic: whoopsie network manager dnsmasq (started by network manager) IPv6 The repeated DNS-requests for daisy.ubuntu.com stop when de-activating anyone of these! You (as root) may use these recipes as workarounds: Workaround #1: De-activate whoopsie: #initctl stop whoopsie #echo 'manual' /etc/init/whoopsie.override Or workaround #2: De-activate Network Manager: #initctl stop network-manager #echo 'manual' /etc/init/network-manager.override - Bring up network interface through config lines in file /etc/network/interfaces, e.g. iface eth0 inet dhcp auto eth0 #ifup eth0 Or workaround #3: Disable dnsmasq - Edit file /etc/NetworkManager/NetworkManager.conf and change line with dns=dnsmasq to #dns=dnsmasq - Restart Network Manager: # initctl restart network-manager Or workaround #4: Disable IPv6: #sysctl -w net/ipv6/conf/all/disable_ipv6=1 #echo 'net/ipv6/conf/all/disable_ipv6=1' /etc/sysctl.d/10-ipv6-off -- 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/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1330430] [NEW] apparmor profile needs review/improvement
Public bug reported: Apparmor rules for evince forbid opening a PDF from an external drive mounted under /media/… unless its filename ends in '.pdf'. Same file will be opened if it is copied to /home/… or renamed to a filename tailing in '.pdf' on the external drive. See bugs #1096837 and #1327161. On a GNU/Linux system like Ubuntu these rules are useless because filetype is not determined by an extension. Checking the filename adds no security. It smells like snakeoil to me. Please review the apparmor profile. On an GNU/Linux system opening a PDF should not denied on filename. This bug affects Ubuntu versions 14.04 LTS, 12.04 LTS and 10.04 LTS. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Description changed: Apparmor rules for evince forbid opening a PDF from an external drive mounted under /media/… unless its filename ends in '.pdf'. Same file will be opened if it is copied to /home/… or renamed to a filename tailing in '.pdf' on the external drive. See bugs #1096837 and #1327161. On a GNU/Linux system like Ubuntu these rules are useless because filetype ist not determined by an extension. Checking the filename adds - no security. It smels like snakeoil to me. + no security. It smells like snakeoil to me. Please review the apparmor profile. On an GNU/Linux system opening a PDF should not denied on filename. This bug affects Ubuntu versions 14.04 LTS, 12.04 LTS and 10.04 LTS. ** Information type changed from Private Security to Public ** Description changed: Apparmor rules for evince forbid opening a PDF from an external drive mounted under /media/… unless its filename ends in '.pdf'. Same file will be opened if it is copied to /home/… or renamed to a filename tailing in '.pdf' on the external drive. See bugs #1096837 and #1327161. On a GNU/Linux system like Ubuntu these rules are useless because - filetype ist not determined by an extension. Checking the filename adds + filetype is not determined by an extension. Checking the filename adds no security. It smells like snakeoil to me. Please review the apparmor profile. On an GNU/Linux system opening a PDF should not denied on filename. This bug affects Ubuntu versions 14.04 LTS, 12.04 LTS and 10.04 LTS. -- 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/1330430 Title: apparmor profile needs review/improvement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1330430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1096837] Re: [apparmor] Evince does not save files to external disks unless I rename them with the .pdf extension
This is not an issue of the evince program, but the apparmor rules for evince. Checking by trying this procedure on Ubuntu 10.04, 12.04 or 14.04: Be carefull, these modifications will be permanent and survive reboot! 1. Install apparmor-utils. 2. In a terminal check apparmor status with this command: sudo aa-status evince should be in enforce mode. 3. Set evince to complain mode in apparmor with this command: sudo aa-complain evince 4. Try opening a PDF without tailing '.pdf' on a filesystem mounted under /media/… It should proceed without error. You can also save a file from evince without '.pdf' now on an external media. 5. You can undo with this command: sudo aa-enforce evince I do not recommend using step 3 as a workaround for this bug. It is a hint that evince need its apparmor rules to be improved. I will file a separate bug against package evince-common, which contains a profile for apparmor. -- 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/1096837 Title: [apparmor] Evince does not save files to external disks unless I rename them with the .pdf extension To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1096837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1096837] Re: [apparmor] Evince does not save files to external disks unless I rename them with the .pdf extension
I can confirm this bug, see #1327161. Even worse, it affects also opening a file without a tailing '.pdf' on a drive mounted under /media/… This bug exist for a long time. I see it under Ubuntu 10.04 LTS (evince 2.30.3-0ubuntu1.3, under Ubuntu 12.04 LTS (evince 3.4.0-0ubuntu1.7 and under 14.04 LTS (evince 3.10.3-0ubuntu10). -- 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/1096837 Title: [apparmor] Evince does not save files to external disks unless I rename them with the .pdf extension To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1096837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1327161] [NEW] evince cannot open PDF on removeable drive
Public bug reported: I am using evince 3.10.3 from Ubuntu GNOME 14.04 LTS. evince will not open a normal PDF with a filename not ending in '.pdf' on a drive mounted under /media/... unless the file is renamed and ends with '.pdf'. Error message: „Keine Berechtigung“ (german), maybe 'missing permission'. I am sure I have sufficient permissions for opening the file. When I rename filename to filename.pdf evince will open it. I tried with different files copied from /home/... to /media/... This occurres only on drives mounted under /media/... ! A PDF on /home/... will be opened by evince even it doesn't end with '.pdf'. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1327161 Title: evince cannot open PDF on removeable drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1327161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 519935] Re: unable to eject cd-rom after burning disk
I am using brasero 3.4.1 from package 3.4.1-0ubuntu1.1 on ubuntu 12.04 LTS i386 32 bit. The problem is NOT fixed! I still have to eject manually. Burned CDs are OK if ejected before closing the window but sometimes corrupted when ejected after closing the window. After closing the window with the hint Please eject manually … brasero does not terminate. In order to burn another ISO to CD I first must kill the old brasero process with sudo killall brasero. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/519935 Title: unable to eject cd-rom after burning disk To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-utils/+bug/519935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
