[Touch-packages] [Bug 1772629] Re: Automatic logout when resuming from suspend on Xubuntu 18.04
Bug #1776887 indicated that Xorg crashes because of a problem in blk- core.c. A patch and a workaround were presented, as well as a test from blktests. It took a long for the patch to reach the kernel, and it was finally included with 4.15.0-31-generic. And here the bug hit a snag because: 1. If the workaround is put in place, the problem doesn't happen 2. Without the workaround, with just the patched kernel, the problem still happens It seems to indicate that either the patch doesn't actually solve the root problem, and that the workaround doesn't seem to be related to the patch. In any case, it definitely has nothing to do with systemd. -- 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/1772629 Title: Automatic logout when resuming from suspend on Xubuntu 18.04 Status in systemd package in Ubuntu: Incomplete Bug description: When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind automatically logs out of the current session if the laptop has stayed suspended for more than a couple of hours. If the interval between suspend and resume is short, it doesn't log out. I still haven't discovered how long this interval has to be in order to cause the logout. I enabled debug on the systemd-logind.service, creating file _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_: [Service] Environment=SYSTEMD_LOG_LEVEL=debug which causes systemd-logind to log all D-Bus messages it handles, but couldn't spot anything that might have caused the logout. I scanned all systemd journal messages (`journalctl`) before systemd- logind starts killing the current session, investigated all that looked suspicious but couldn't find anything that might influence an automatic logout. Here are some of the messages that striked me as suspicious (they are not sequential, but pulled from different occasions): upowerd[1600]: unhandled action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0 polkitd(authority=local)[840]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.46, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) wpa_supplicant[811]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none at-spi-bus-launcher[7031]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[7031]: after 30333 requests (30333 known processed) with 0 events remaining. systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager handles these events) pid=8611 uid=1000 mode=block stopped systemd-logind[779]: Electing new display for user paulo systemd-logind[779]: Ignoring session c8 logind config doesn't have anything that might cause this: paulo:~$ loginctl show-session EnableWallMessages=no NAutoVTs=6 KillUserProcesses=no RebootToFirmwareSetup=no IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key DelayInhibited=sleep InhibitDelayMaxUSec=5s HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=ignore HoldoffTimeoutUSec=30s IdleAction=ignore IdleActionUSec=30min PreparingForShutdown=no PreparingForSleep=no Docked=no RemoveIPC=yes RuntimeDirectorySize=615313408 InhibitorsMax=8192 NCurrentInhibitors=5 SessionsMax=8192 NCurrentSessions=1 UserTasksMax=10813 I can't find any anything that might cause an automatic logout after a time interval. I'm really stumped. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 07:36:59 2018 InstallationDate: Installed on 2018-04-28 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08FDW5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:
[Touch-packages] [Bug 1782567] Re: apt changelog outputs "usage: which [-as] program ..." if variable PAGER doesn't exist
The bug was present in 1.6.3, but it seems to have been fixed in 1.6.3ubuntu0.1. If you roll back to 1.6.3, it's easy to reproduce it: $ PAGER= $ apt changelog apt It shows this error message: usage: which [-as] program ... and then goes on to show the changelog for apt. Whether apt called which or not, it was a bug nonetheless. The changelog for apt doesn't mention fixing this, but it has been fixed because it cannot be reproduced on 1.6.3ubuntu0.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1782567 Title: apt changelog outputs "usage: which [-as] program ..." if variable PAGER doesn't exist Status in apt package in Ubuntu: Invalid Bug description: When variable PAGER isn't in the environment, apt changelog always outputs this message: usage: which [-as] program ... but it goes on and shows the changelog with less. Most certainly it's running: which $PAGER without checking first if PAGER is empty. sensible-browser has the same bug, but with variable BROWSER: bug #1782447 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 19 09:35:46 2018 InstallationDate: Installed on 2018-04-28 (81 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1782567/+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 1782908] [NEW] Package gtk-3-examples doesn't include icon gtk3-icon-browser
Public bug reported: gtk3-icon-browser.desktop in package gtk-3-examples references icon gtk3 -icon-browser: paulo:~$ grep ^Icon /usr/share/applications/gtk3-icon-browser.desktop Icon=gtk3-icon-browser but the packages doesn't include it: paulo:~$ dpkg -L gtk-3-examples | grep gtk3-icon-browser /usr/bin/gtk3-icon-browser /usr/share/applications/gtk3-icon-browser.desktop /usr/share/man/man1/gtk3-icon-browser.1.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gtk-3-examples 3.22.30-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jul 21 10:52:17 2018 InstallationDate: Installed on 2018-04-28 (84 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782908 Title: Package gtk-3-examples doesn't include icon gtk3-icon-browser Status in gtk+3.0 package in Ubuntu: New Bug description: gtk3-icon-browser.desktop in package gtk-3-examples references icon gtk3-icon-browser: paulo:~$ grep ^Icon /usr/share/applications/gtk3-icon-browser.desktop Icon=gtk3-icon-browser but the packages doesn't include it: paulo:~$ dpkg -L gtk-3-examples | grep gtk3-icon-browser /usr/bin/gtk3-icon-browser /usr/share/applications/gtk3-icon-browser.desktop /usr/share/man/man1/gtk3-icon-browser.1.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gtk-3-examples 3.22.30-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jul 21 10:52:17 2018 InstallationDate: Installed on 2018-04-28 (84 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1782908/+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 1782570] [NEW] nohup is not preventing jobs from receiving SIGHUP when the shell ends
Public bug reported: nohup seems to have stopped working, not sure since when. It's easy to reproduce: 1. Close your default browser 2. Run: nohup sensible-browser & 3. Wait for the browser to open 4. Close the terminal emulator The browser is terminated. I have discovered that, instead of running nohup, the job has to be removed from the job table: sensible-browser & disown ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 19 10:21:56 2018 InstallationDate: Installed on 2018-04-28 (82 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1782570 Title: nohup is not preventing jobs from receiving SIGHUP when the shell ends Status in coreutils package in Ubuntu: New Bug description: nohup seems to have stopped working, not sure since when. It's easy to reproduce: 1. Close your default browser 2. Run: nohup sensible-browser & 3. Wait for the browser to open 4. Close the terminal emulator The browser is terminated. I have discovered that, instead of running nohup, the job has to be removed from the job table: sensible-browser & disown ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 19 10:21:56 2018 InstallationDate: Installed on 2018-04-28 (82 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1782570/+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 1782567] [NEW] apt changelog outputs "usage: which [-as] program ..." if variable PAGER doesn't exist
Public bug reported: When variable PAGER isn't in the environment, apt changelog always outputs this message: usage: which [-as] program ... but it goes on and shows the changelog with less. Most certainly it's running: which $PAGER without checking first if PAGER is empty. sensible-browser has the same bug, but with variable BROWSER: bug #1782447 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 19 09:35:46 2018 InstallationDate: Installed on 2018-04-28 (81 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1782567 Title: apt changelog outputs "usage: which [-as] program ..." if variable PAGER doesn't exist Status in apt package in Ubuntu: New Bug description: When variable PAGER isn't in the environment, apt changelog always outputs this message: usage: which [-as] program ... but it goes on and shows the changelog with less. Most certainly it's running: which $PAGER without checking first if PAGER is empty. sensible-browser has the same bug, but with variable BROWSER: bug #1782447 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 19 09:35:46 2018 InstallationDate: Installed on 2018-04-28 (81 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1782567/+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 1782447] [NEW] If BROWSER isn't set, sensible-browser outputs: "usage: which [-as] program ..."
Public bug reported: If environment variable BROWSER isn't set, sensible-browser always shows this error message: usage: which [-as] program ... even though it goes on and opens the browser. It's easy to reproduce: $ unset BROWSER $ sensible-browser http://example.com The bug is right at the beginning: # Prevent recursive loops, where these values are set to this script p="$(which sensible-browser)" [ "$(which $BROWSER || true)" = "$p" ] && BROWSER= It could be fixed with: [ -n "$BROWSER" -a "$(which "$BROWSER")" = "$p" ] && BROWSER= ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sensible-utils 0.0.12 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jul 18 20:21:36 2018 Dependencies: InstallationDate: Installed on 2018-04-28 (81 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: sensible-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sensible-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1782447 Title: If BROWSER isn't set, sensible-browser outputs: "usage: which [-as] program ..." Status in sensible-utils package in Ubuntu: New Bug description: If environment variable BROWSER isn't set, sensible-browser always shows this error message: usage: which [-as] program ... even though it goes on and opens the browser. It's easy to reproduce: $ unset BROWSER $ sensible-browser http://example.com The bug is right at the beginning: # Prevent recursive loops, where these values are set to this script p="$(which sensible-browser)" [ "$(which $BROWSER || true)" = "$p" ] && BROWSER= It could be fixed with: [ -n "$BROWSER" -a "$(which "$BROWSER")" = "$p" ] && BROWSER= ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sensible-utils 0.0.12 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jul 18 20:21:36 2018 Dependencies: InstallationDate: Installed on 2018-04-28 (81 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: sensible-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1782447/+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 1775593] [NEW] X server crashes with SIGBUS when resuming from suspend
Public bug reported: Every night I suspend my laptop and resume it in the morning. At least once a week, the X server crashes with SIGBUS when resuming from suspend. I scoured systemd journals and all logs under /var/log, and this was the only suspicious message I found: [ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied As my graphics card uses driver i915, I installed xserver-xorg-video- intel-dbg but couldn't find any package with debugging symbols for xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded this: Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGBUS, Bus error. #0 0x5631c45681f1 in ?? () [Current thread is 1 (LWP 1016)] (gdb) bt #0 0x5631c45681f1 in ?? () #1 0x0001 in ?? () #2 0x5631c5a03350 in ?? () #3 0x0001 in ?? () #4 0x5631c4596ec5 in ?? () #5 0x7f5f0974e2a0 in ?? () #6 0x7f5f093e5977 in ?? () #7 0x in ?? () I'm attaching apport's crash report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jun 7 08:56:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b0] InstallationDate: Installed on 2018-04-28 (39 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash systemd.legacy_systemd_cgroup_controller=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08FDW5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "apport crash report when X crashed with SIGBUS" https://bugs.launchpad.net/bugs/1775593/+attachment/5149744/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775593 Title: X server crashes with SIGBUS when resuming from suspend Status in xorg package in Ubuntu: New Bug description: Every night I suspend my laptop and resume it in the morning. At least once a week, the X server crashes with SIGBUS when resuming from suspend. I scoured systemd journals and all logs under /var/log, and this was the only suspicious message I found: [ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied As my graphics card uses driver i915, I installed xserver-xorg-video- intel-dbg but couldn't find any package with debugging symbols for xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded this: Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGBUS, Bus error. #0 0x5631c45681f1 in ?? () [Current thread is 1 (LWP 1016)] (gdb) bt #0 0x5631c45681f1 in ?? () #1 0x0001 in ?? () #2 0x5631c5a03350 in ?? () #3 0x0001 in ?? () #4 0x5631c4596ec5 in ?? () #5 0x7f5f0974e2a0 in ?? () #6
[Touch-packages] [Bug 1775392] [NEW] at-spi-bus-launcher makes Xorg crash when resuming from suspend
Public bug reported: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Tags: crash sigbus xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: New Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1775043] [NEW] bash completion not working: uses deprecated have()
Public bug reported: bash completion, defined in /usr/share/bash-completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1775043 Title: bash completion not working: uses deprecated have() Status in ufw package in Ubuntu: New Bug description: bash completion, defined in /usr/share/bash- completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1775043/+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 1772629] Re: Automatic logout when resuming from suspend on Xubuntu 18.04
I have discovered that the automatic logout was caused by the Xorg server crashing with SIGBUS. So this bug may and should be closed. -- 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/1772629 Title: Automatic logout when resuming from suspend on Xubuntu 18.04 Status in systemd package in Ubuntu: New Bug description: When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind automatically logs out of the current session if the laptop has stayed suspended for more than a couple of hours. If the interval between suspend and resume is short, it doesn't log out. I still haven't discovered how long this interval has to be in order to cause the logout. I enabled debug on the systemd-logind.service, creating file _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_: [Service] Environment=SYSTEMD_LOG_LEVEL=debug which causes systemd-logind to log all D-Bus messages it handles, but couldn't spot anything that might have caused the logout. I scanned all systemd journal messages (`journalctl`) before systemd- logind starts killing the current session, investigated all that looked suspicious but couldn't find anything that might influence an automatic logout. Here are some of the messages that striked me as suspicious (they are not sequential, but pulled from different occasions): upowerd[1600]: unhandled action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0 polkitd(authority=local)[840]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.46, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) wpa_supplicant[811]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none at-spi-bus-launcher[7031]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[7031]: after 30333 requests (30333 known processed) with 0 events remaining. systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager handles these events) pid=8611 uid=1000 mode=block stopped systemd-logind[779]: Electing new display for user paulo systemd-logind[779]: Ignoring session c8 logind config doesn't have anything that might cause this: paulo:~$ loginctl show-session EnableWallMessages=no NAutoVTs=6 KillUserProcesses=no RebootToFirmwareSetup=no IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key DelayInhibited=sleep InhibitDelayMaxUSec=5s HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=ignore HoldoffTimeoutUSec=30s IdleAction=ignore IdleActionUSec=30min PreparingForShutdown=no PreparingForSleep=no Docked=no RemoveIPC=yes RuntimeDirectorySize=615313408 InhibitorsMax=8192 NCurrentInhibitors=5 SessionsMax=8192 NCurrentSessions=1 UserTasksMax=10813 I can't find any anything that might cause an automatic logout after a time interval. I'm really stumped. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 07:36:59 2018 InstallationDate: Installed on 2018-04-28 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08FDW5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1772629/+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 1772629] [NEW] Automatic logout when resuming from suspend on Xubuntu 18.04
Public bug reported: When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind automatically logs out of the current session if the laptop has stayed suspended for more than a couple of hours. If the interval between suspend and resume is short, it doesn't log out. I still haven't discovered how long this interval has to be in order to cause the logout. I enabled debug on the systemd-logind.service, creating file _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_: [Service] Environment=SYSTEMD_LOG_LEVEL=debug which causes systemd-logind to log all D-Bus messages it handles, but couldn't spot anything that might have caused the logout. I scanned all systemd journal messages (`journalctl`) before systemd- logind starts killing the current session, investigated all that looked suspicious but couldn't find anything that might influence an automatic logout. Here are some of the messages that striked me as suspicious (they are not sequential, but pulled from different occasions): upowerd[1600]: unhandled action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0 polkitd(authority=local)[840]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.46, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) wpa_supplicant[811]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none at-spi-bus-launcher[7031]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[7031]: after 30333 requests (30333 known processed) with 0 events remaining. systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager handles these events) pid=8611 uid=1000 mode=block stopped systemd-logind[779]: Electing new display for user paulo systemd-logind[779]: Ignoring session c8 logind config doesn't have anything that might cause this: paulo:~$ loginctl show-session EnableWallMessages=no NAutoVTs=6 KillUserProcesses=no RebootToFirmwareSetup=no IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key DelayInhibited=sleep InhibitDelayMaxUSec=5s HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchDocked=ignore HoldoffTimeoutUSec=30s IdleAction=ignore IdleActionUSec=30min PreparingForShutdown=no PreparingForSleep=no Docked=no RemoveIPC=yes RuntimeDirectorySize=615313408 InhibitorsMax=8192 NCurrentInhibitors=5 SessionsMax=8192 NCurrentSessions=1 UserTasksMax=10813 I can't find any anything that might cause an automatic logout after a time interval. I'm really stumped. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 07:36:59 2018 InstallationDate: Installed on 2018-04-28 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08FDW5 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: automatic logout systemd-logind -- 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/1772629 Title: Automatic logout when resuming from suspend on Xubuntu 18.04 Status in systemd package in Ubuntu: New Bug description: When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind automatically logs out of the current session if the laptop has stayed suspended for more than a couple of hours. If the interval between suspend and resume is short, it doesn't log out. I still haven't discovered how long this interval has to be in order to cause the logout. I enabled debug on the systemd-logind.service, creating file _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_: [Service] Environment=SYSTEMD_LOG_LEVEL=debug whic
[Touch-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
In xubuntu 17.10, kdelibs5-data 4.14.34-0ubuntu2, file /usr/share/mime/packages/kde.xml still includes MIME types all/all and all/allfiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Won't Fix Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user
This is fixed in xdg-util's current upstream release 1.1.2+ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1721948 Title: gvfs-open/xdg-open shows message about 'gio open' which confuses user Status in Apport: Fix Released Status in gvfs: Fix Released Status in apport package in Ubuntu: Triaged Status in gvfs package in Ubuntu: Invalid Status in python3.6 package in Ubuntu: Triaged Status in xdg-utils package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Try to report bug with Apport by terminal command `apport-bug apport` Expected results: apport-bug reports bug silently Actual results: get output in the terminal $ apport-bug apport This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 13:50:23 2017 InstallationDate: Installed on 2017-08-26 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1721948/+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 1434647] Re: 'file -i' reports application/octet-stream for mp3 files
This error was introduced with version 5.19-1ubuntu1.2. Version 5.19-1ubuntu1.1 was correctly reporting the MIME type of mp3 files as 'audio/mpeg'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1434647 Title: 'file -i' reports application/octet-stream for mp3 files Status in file package in Ubuntu: New Bug description: 'file -i' reports 'application/octet-stream' for mp3 files, when it should be 'audio/mpeg'. It can be reproduced with any mp3 file: file -i To get the correct mime type: xdg-mime query filetype ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: file 1:5.19-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 20 14:54:25 2015 InstallationDate: Installed on 2014-11-25 (115 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1434647/+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 1434647] [NEW] 'file -i' reports application/octet-stream for mp3 files
Public bug reported: 'file -i' reports 'application/octet-stream' for mp3 files, when it should be 'audio/mpeg'. It can be reproduced with any mp3 file: file -i To get the correct mime type: xdg-mime query filetype ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: file 1:5.19-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 20 14:54:25 2015 InstallationDate: Installed on 2014-11-25 (115 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1434647 Title: 'file -i' reports application/octet-stream for mp3 files Status in file package in Ubuntu: New Bug description: 'file -i' reports 'application/octet-stream' for mp3 files, when it should be 'audio/mpeg'. It can be reproduced with any mp3 file: file -i To get the correct mime type: xdg-mime query filetype ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: file 1:5.19-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 20 14:54:25 2015 InstallationDate: Installed on 2014-11-25 (115 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1434647/+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@lists.launchpad.net
Public bug reported: If the message body contains the character ampersand (&), notify-send shows the title, but not the message body. It's easily reproduced running it with any message body containing &, for instance: notify-send teste 'this & that' See the screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libnotify-bin 0.7.6-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 21 17:29:27 2015 InstallationDate: Installed on 2014-11-25 (88 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: libnotify UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libnotify (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "1_002.jpg" https://bugs.launchpad.net/bugs/1424243/+attachment/4324137/+files/1_002.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1424243 Title: notify-send doesn't show message body which contains ampersand (&) Status in libnotify package in Ubuntu: New Bug description: If the message body contains the character ampersand (&), notify-send shows the title, but not the message body. It's easily reproduced running it with any message body containing &, for instance: notify-send teste 'this & that' See the screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libnotify-bin 0.7.6-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 21 17:29:27 2015 InstallationDate: Installed on 2014-11-25 (88 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: libnotify UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1424243/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
It is still happening in Xubuntu 14.10. After coming back from suspend (closed the laptop lid), NetworkManager is asleep: RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep enabled enabledenabled disabled This workaround works for me: created script /etc/pm/sleep.d/49network- manager: #!/bin/sh # # work around a NetworkManager bug, waking it up after resume (sometimes it # stays sleeping after resume) # case "$1" in suspend|hibernate) ;; resume|thaw) nmcli nm status nmcli dev status state=`nmcli -t -f STATE nm status` if [ "$state" = "asleep" ]; then echo "waking up NetworkManager" nmcli nm sleep false nmcli nm status fi ;; esac exit 0 I had removed it to test whether the problem had gone away, but put it back when confirmed it hadn't been solved yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Confirming: I installed Xubuntu Utopic 2 days ago, and this bug is also biting me. However, I noticed that it depends on the time interval between suspend and resume: the bug only happens when I resume 2+ hours after I suspend (it always happens in the morning when I first open the laptop lid). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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
