[Touch-packages] [Bug 1020048] Re: after certain time printing to cups stops working
I have to confirm this bug. 300 seconds timeout. CUPS does not reopen connections again. Notifiers are shutdown. The workaround is to enable the web interface. But this should not be necessary. CUPS should work without the web interface, as that is the default behaviour defined by upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1020048 Title: after certain time printing to cups stops working Status in LibreOffice: Invalid Status in cups package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Invalid Status in cups source package in Precise: Fix Released Status in libreoffice source package in Precise: Invalid Bug description: SRU justification: [Impact] * When the CUPS client connects to a remote cupsd over TCP, the server closes an idle connection after 5 minutes and the client does not reconnect. * LibreOffice is affected because it keeps a CUPS connection open. The effect is that printing to a remote cupsd is no longer possible after LibreOffice has been open for 5 minutes. [Test Case] * This can be reproduced on a desktop system. You don't need a separate CUPS server. * You need at least one print queue in CUPS. If you don't have a printer, install "cups-pdf". * Optional, configure CUPS with a shorter timeout for testing: sudo cupsctl Timeout=30 # seconds sudo restart cups * Configure the CUPS client to use a TCP socket: mkdir ~/.cups echo ServerName 127.0.0.1 > ~/.cups/client.conf * Open LibreOffice. Press Ctrl-P to open the Print dialog. Press Esc to dismiss the dialog. Wait long enough for the timout to elapse (5 minutes by default, or as per the Timeout setting). * Try to print. With cups in precise, the job simply vanishes and is never seen by the server. With the proposed patch, printing works normally. [Regression Potential] * The patch changes a library linked by many programs. An incorrect change might result in those programs misbehaving or crashing. * The patch is minimal, only adding a branch to handle a case that was previously not handled. The behaviour in other cases should be unchanged. [Other Info] * A workaround is to set the cupsd Timeout to a high value such as 8 hours. This works on a server with few users, but on a busy server more and more connections are opened and eventually cupsd isn't able to accept new clients. Original description: == Problem == In our institution we are running only printers through a cups server. while freshly opened document prints well, after some time (few minutes) clicking "print file directly" and menu item "print" do not work any more. after close and open again, thing prints correctly. i have checked what exactly is going on in such cases and logs on the cups server don't show any submissions and/or errors so that the thing is obviously stopped at the level of libreoffice. == Analysis == LibreOffice loses it's TCP connection to CUPS after exactly 5 minutes of inactivity and does not manage to reconnect. To reproduce: print something (to a real printer or cups-pdf), wait 6 minutes not printing anything, and print again. Then, nothing is printed. You can watch the TCP connection using netstat -tpn | grep soffice While it's working, it looks like this: tcp0 0 127.0.0.1:48810 127.0.0.1:631 ESTABLISHED 13976/soffice.bin After 5 minutes, that connection is gone permanently. WORKAROUND: To set the timeout to 24 hours add this line to the top of /etc/cups/cupsd.conf : Timeout 62400 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1020048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
I attach the error_log file with debug logging mode. The CUPS notifier closes after a while. That might be the problem. When I open the KDE printer dialog, the D-BUS system bus dumps these messages calling the Notifier method. Opening the printing dialog from LibreOffice writer does not print anything, not even in the session bus: method call time=1520971612.523540 sender=:1.364 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method return time=1520971612.523567 sender=org.freedesktop.DBus -> destination=:1.364 serial=1 reply_serial=1 string ":1.364" signal time=1520971612.523580 sender=org.freedesktop.DBus -> destination=(null destination) serial=19 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.364" string "" string ":1.364" signal time=1520971612.523598 sender=org.freedesktop.DBus -> destination=:1.364 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.364" method call time=1520971612.524056 sender=:1.364 -> destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='ServerStarted'" method call time=1520971612.524213 sender=:1.364 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='ServerStopped'" method call time=1520971612.524295 sender=:1.364 -> destination=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='ServerRestarted'" method call time=1520971612.524399 sender=:1.364 -> destination=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='ServerAudit'" method call time=1520971612.524514 sender=:1.364 -> destination=org.freedesktop.DBus serial=6 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterAdded'" method call time=1520971612.524595 sender=:1.364 -> destination=org.freedesktop.DBus serial=7 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterModified'" method call time=1520971612.524690 sender=:1.364 -> destination=org.freedesktop.DBus serial=8 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterDeleted'" method call time=1520971612.524760 sender=:1.364 -> destination=org.freedesktop.DBus serial=9 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterStateChanged'" method call time=1520971612.524814 sender=:1.364 -> destination=org.freedesktop.DBus serial=10 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterStopped'" method call time=1520971612.524876 sender=:1.364 -> destination=org.freedesktop.DBus serial=11 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterShutdown'" method call time=1520971612.524922 sender=:1.364 -> destination=org.freedesktop.DBus serial=12 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterRestarted'" method call time=1520971612.524986 sender=:1.364 -> destination=org.freedesktop.DBus serial=13 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='PrinterMediaChanged'" method call time=1520971612.525034 sender=:1.364 -> destination=org.freedesktop.DBus serial=14 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/org/cups/cupsd/Notifier',interface='org.cups.cupsd.Notifier',member='JobState'" method call time=1520971612.525087 sender=:1.364 -> destination=org.freedesktop.DBus serial=15 path=/org/freedesktop/DBus;
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
I am on Kubuntu 17.10 and I am suffering this bug. I do not have the web interface enabled but I have an IPP printer. I have attached the cupsd.conf on my system. I think this is the relevant part of the file: # Only listen for connections from the local machine. Listen localhost:631 Listen /var/run/cups/cups.sock # Show shared printers on the local network. Browsing Off BrowseLocalProtocols dnssd ** Attachment added: "cupsd.conf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+attachment/5078523/+files/cupsd.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Released Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. [Regression in Pending SRU page] * Regression in autopkgtest for c2esp (armhf): test log This autopkgtest seems always fails : http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf c2esp [xenial/armhf] Version TriggersDateDurationResult 27-2 cups/2.1.3-4ubuntu0.3 2017-08-23 04:07:44 UTC 2h 50m 13s faillog artifacts ♻ 27-2 cups/2.1.3-4ubuntu0.2 2017-08-14 23:31:50 UTC 2h 50m 11s faillog artifacts ♻ 27-2 cups/2.1.3-4ubuntu0.2 2017-07-17 20:17:10 UTC 2h 50m 52s faillog artifacts ♻ 27-2 cups/2.1.3-4ubuntu0.1 2017-01-20 12:00:41 UTC 2h 49m 29s faillog artifacts ♻ Additionally look at Till comment : https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129 * Regression in autopkgtest for libreoffice (i386): test log It's a known issue, A regression in the kernel, which breaks libreoffice with java enabled on i386 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772 ... so until this is fixed upstream in the kernel and backported in an ubuntu kernel, I'm afraid the only option is to just ignore the failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile
I have removed the proposal for merging, as I want to check the profile with KDE 5 on Kubuntu 17.04. I am removing also the patch tag as suggested by the bot, because it is not a patch to anything available already in the repository. ** Tags removed: patch ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Raúl Vidal (raulvior-bcn) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667963 Title: QuiteRSS AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile
Uh, sorry. This is the modification patch (see attachment). ** Patch added: "usr.bin.quiterss.patch" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+attachment/4958867/+files/usr.bin.quiterss.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667963 Title: QuiteRSS AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile
Yes, no problem. But since I uploaded the profile to launchpad I made a slight modification. See attached profile. ** Attachment added: "usr.bin.quiterss" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+attachment/4958853/+files/usr.bin.quiterss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667963 Title: QuiteRSS AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
Yes please. I am struggling with systemd-resolved. It sucks. I am getting these messages: Jun 15 15:34:19 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.8.8. Jun 15 15:34:19 n53sn systemd-resolved[1503]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.8.8. Jun 15 15:34:20 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.4.4. Jun 15 15:34:24 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::. Jun 15 15:34:24 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::8844. Jun 15 15:34:24 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.8.8. Jun 15 15:34:24 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.4.4. Jun 15 15:34:25 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::. Jun 15 15:34:25 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::8844. Jun 15 15:34:25 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.8.8. Jun 15 15:34:29 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.4.4. Jun 15 15:34:29 n53sn systemd-resolved[1503]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.4.4. Jun 15 15:34:30 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::. Jun 15 15:34:30 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::8844. Jun 15 15:34:30 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.8.8. Jun 15 15:34:31 n53sn systemd-resolved[1503]: Switching to fallback DNS server 8.8.4.4. Jun 15 15:34:34 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::. Jun 15 15:34:34 n53sn systemd-resolved[1503]: Switching to fallback DNS server 2001:4860:4860::8844. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
I installed Ubuntu 17.04 as a VirtualBox guest and I have the same problem: syslog output: systemd-resolved[947]: DNSSEC validation failed for question . in DNSKEY: missing-key systemd-resolved[947]: DNSSEC validation failed for question com in DS: missing-key systemd-resolved[947]: DNSSEC validation failed for question com in DNSKEY: missing-key systemd-resolved[947]: DNSSEC validation failed for question ubuntu.com in DS: missing-key systemd-resolved[947]: DNSSEC validation failed for question ubuntu.com in SOA: missing-key systemd-resolved[947]: DNSSEC validation failed for question apps.ubuntu.com in DS: missing-key systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in DS: missing-key systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in SOA: missing-key systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in A: missing-key -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) Status in network-manager package in Ubuntu: Confirmed Bug description: Access to local ethernet is possible (e.g. ping 192.168.2.2), access to internet is not possible: ping: ports.ubuntu.com: Name or service not known ping: www.google.com: Name or service not known It does not matter if my PowerBook G4 is connected via WLAN or ethernet, the effect is the same. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0 Uname: Linux 4.9.0-11-powerpc-smp ppc ApportVersion: 2.20.4-0ubuntu1 Architecture: powerpc CasperVersion: 1.379 Date: Thu Nov 3 18:13:07 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlP1p17s0 proto static metric 600 169.254.0.0/16 dev wlP1p17s0 scope link metric 1000 192.168.3.0/24 dev wlP1p17s0 proto kernel scope link src 192.168.3.2 metric 600 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218) NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 802-11-wireless 1478196808 Thu 03 Nov 2016 06:13:28 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlP1p17s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 Wired connection 1 1a0d2e10-42f2-3154-b4f6-dfbec067bff3 802-3-ethernet 1478196172 Thu 03 Nov 2016 06:02:52 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlP1p17s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 /org/freedesktop/NetworkManager/ActiveConnection/4 enP2p36s15f0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670394] Re: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all
If you add options snd-hda-intel model=inv-dmic option to /etc/modprobe.d/alsa-base.conf, works. There seems to be a problem with this laptop. I never needed to add that option to get the headphone jack to work. But on bug https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099 a user reported that using that option in Ubuntu 14.04 LTS fixed the problem. But as I said, I didn't need it before. Whatever changes do to the kernel, they broke something in the driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1670394 Title: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound. Anything. PulseAudio Volume Control shows sound going through it (sound level bar moves), but jack does not output anything. Old bugs which had the same problem with the same laptop: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360641 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099 These bugs occurred on old kernel versions from 12.04 LTS and 14.04 LTS. The laptop I'm working on is on Ubuntu 16.04 LTS, upgraded from Ubuntu 14.04.5 LTS which was updated from Ubuntu 12.04 LTS itself. I have tried running the LiveCDs of Ubuntu 16.04.2 LTS and Ubuntu 16.10 and still the laptop has no sound in the headphones jack. So, the issue remains unsolved with newer kernels or in a fresh environment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 6 16:15:45 2017 InstallationDate: Installed on 2012-07-22 (1688 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite Pro P200 dmi.product.version: PSPB7E-00Q00HCE dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-03-05T21:14:03.997095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670394] [NEW] [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all
Public bug reported: No sound. Anything. PulseAudio Volume Control shows sound going through it (sound level bar moves), but jack does not output anything. Old bugs which had the same problem with the same laptop: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360641 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099 These bugs occurred on old kernel versions from 12.04 LTS and 14.04 LTS. The laptop I'm working on is on Ubuntu 16.04 LTS, upgraded from Ubuntu 14.04.5 LTS which was updated from Ubuntu 12.04 LTS itself. I have tried running the LiveCDs of Ubuntu 16.04.2 LTS and Ubuntu 16.10 and still the laptop has no sound in the headphones jack. So, the issue remains unsolved with newer kernels or in a fresh environment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 6 16:15:45 2017 InstallationDate: Installed on 2012-07-22 (1688 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite Pro P200 dmi.product.version: PSPB7E-00Q00HCE dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-03-05T21:14:03.997095 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1670394 Title: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound. Anything. PulseAudio Volume Control shows sound going through it (sound level bar moves), but jack does not output anything. Old bugs which had the same problem with the same laptop: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1360641 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099 These bugs occurred on old kernel versions from 12.04 LTS and 14.04 LTS. The laptop I'm working on is on Ubuntu 16.04 LTS, upgraded from Ubuntu 14.04.5 LTS which was updated from Ubuntu 12.04 LTS itself. I have tried running the LiveCDs of Ubuntu 16.04.2 LTS and Ubuntu 16.10 and still the laptop has no sound in the headphones jack. So, the issue remains unsolved with newer kernels or in a fresh environment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 6 16:15:45 2017 InstallationDate: Installed on 2012-07-22 (1688 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2165 F pulseaudio /dev/snd/controlC1: antonio2165 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Satellite Pro P200, Realtek ALC268, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90
[Touch-packages] [Bug 1670193] [NEW] No audio on headphone ubuntu 16.04
Public bug reported: I upgraded from Ubuntu 14.04 LTS to Ubuntu 16.04 and I lost audio on the headphone jack. Speakers work fine though. I installed pavucontrol and that program has a sound level bar which moves while playing sound with the headphones plugged in. So, PulseAudio effectively detects sound. In addition to the files attached by the ubuntu-bug program I have attached the output of alsa-info.sh. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2172 F pulseaudio /dev/snd/controlC1: antonio2172 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 5 21:39:08 2017 InstallationDate: Installed on 2012-07-22 (1687 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite Pro P200 dmi.product.version: PSPB7E-00Q00HCE dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/bugs/1670193/+attachment/4831990/+files/alsa-info.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1670193 Title: No audio on headphone ubuntu 16.04 Status in pulseaudio package in Ubuntu: New Bug description: I upgraded from Ubuntu 14.04 LTS to Ubuntu 16.04 and I lost audio on the headphone jack. Speakers work fine though. I installed pavucontrol and that program has a sound level bar which moves while playing sound with the headphones plugged in. So, PulseAudio effectively detects sound. In addition to the files attached by the ubuntu-bug program I have attached the output of alsa-info.sh. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio2172 F pulseaudio /dev/snd/controlC1: antonio2172 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 5 21:39:08 2017 InstallationDate: Installed on 2012-07-22 (1687 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite Pro P200 dmi.product.version: PSPB7E-00Q00HCE dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1670193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669800] Re: Liferea AppArmor profile
Updated AppArmor Liferea profile with an additional member for the MountTracker. ** Attachment added: "usr.bin.liferea" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1669800/+attachment/4830845/+files/usr.bin.liferea -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1669800 Title: Liferea AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Load Liferea from the unity launcher 2. Add new RSS feed. 3. Check for updates. 4. Read an entry of a feed. 5. Open entry in tab. 6. Open entry in browser. 7. Open entry in external browser. 8. Close window. 9. Open window from the message notifications. 10. Export OPML RSS feed. 11. Import OPML RSS feed. 12. Close window. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 3 15:14:29 2017 InstallationDate: Installed on 2015-07-31 (580 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noht SourcePackage: apparmor UpgradeStatus: Upgraded to yakkety on 2016-11-01 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.base: 2017-02-25T03:27:12.649925 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.java: 2017-02-26T19:05:27.563689 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.ubuntu-integration: 2017-02-20T21:15:58.771432 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.user-files: 2017-02-18T19:33:07.157766 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-unity7-base: 2017-02-23T22:37:50.022685 mtime.conffile..etc.apparmor.d.tunables.xdg-user-dirs: 2017-02-22T02:08:02.499216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1669800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669800] [NEW] Liferea AppArmor profile
Public bug reported: Test plan: 1. Load Liferea from the unity launcher 2. Add new RSS feed. 3. Check for updates. 4. Read an entry of a feed. 5. Open entry in tab. 6. Open entry in browser. 7. Open entry in external browser. 8. Close window. 9. Open window from the message notifications. 10. Export OPML RSS feed. 11. Import OPML RSS feed. 12. Close window. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 3 15:14:29 2017 InstallationDate: Installed on 2015-07-31 (580 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noht SourcePackage: apparmor UpgradeStatus: Upgraded to yakkety on 2016-11-01 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.base: 2017-02-25T03:27:12.649925 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.java: 2017-02-26T19:05:27.563689 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.ubuntu-integration: 2017-02-20T21:15:58.771432 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.user-files: 2017-02-18T19:33:07.157766 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-unity7-base: 2017-02-23T22:37:50.022685 mtime.conffile..etc.apparmor.d.tunables.xdg-user-dirs: 2017-02-22T02:08:02.499216 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Apparmor liferea rules" https://bugs.launchpad.net/bugs/1669800/+attachment/4830762/+files/usr.bin.liferea -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1669800 Title: Liferea AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Load Liferea from the unity launcher 2. Add new RSS feed. 3. Check for updates. 4. Read an entry of a feed. 5. Open entry in tab. 6. Open entry in browser. 7. Open entry in external browser. 8. Close window. 9. Open window from the message notifications. 10. Export OPML RSS feed. 11. Import OPML RSS feed. 12. Close window. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 3 15:14:29 2017 InstallationDate: Installed on 2015-07-31 (580 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noht SourcePackage: apparmor UpgradeStatus: Upgraded to yakkety on 2016-11-01 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.base: 2017-02-25T03:27:12.649925 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.java: 2017-02-26T19:05:27.563689 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.ubuntu-integration: 2017-02-20T21:15:58.771432 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-browsers.d.user-files: 2017-02-18T19:33:07.157766 mtime.conffile..etc.apparmor.d.abstractions.ubuntu-unity7-base: 2017-02-23T22:37:50.022685 mtime.conffile..etc.apparmor.d.tunables.xdg-user-dirs: 2017-02-22T02:08:02.499216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1669800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667963] [NEW] QuiteRSS AppArmor profile
Public bug reported: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Attachment added: "usr.bin.quiterss" https://bugs.launchpad.net/bugs/1667963/+attachment/4826650/+files/usr.bin.quiterss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667963 Title: QuiteRSS AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
