[Touch-packages] [Bug 1676000] Re: neverball opens a second black window, maximizing the window crashes unity8
there are more bugs in this bug report, 1. the black window 2. neverball window is transparent 3. if you resize the window it doesn't resize well 4. if you resize/close the black window it crashes unity8 ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: libsdl2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676000 Title: neverball opens a second black window, maximizing the window crashes unity8 Status in Canonical System Image: New Status in libsdl2 package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Ubuntu 17.04 Unity8 neverball opens a second black window, maximizing the window crashes unity8 start neverball without Xmir (it's an SDL2 app i think) you'll now see a black window behind the neverball window titled "OpenGL test" (see screenshot), now try to maximize that black window, here it just crashes unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676000/+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 1676002] [NEW] Xorg freeze
Public bug reported: The system freezes randomly since I installed Ubuntu 16.04. I think there's a problem with nvidia drivers. The graphic card is Nvidia GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used Ubuntu 12.04 without problems for almost 5 years with 173 Nvidia driver (which it's recommended), but it's not avaliable. Now when I try to use privete drivers the only avaliable driver is Nvidia 304.xx, but it causes a black screen at start the PC. I can use the terminal to uninstall the nvidia drivers and login, but then the system freezes very frecuently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 25 08:11:57 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C73 [GeForce 7050 / nForce 610i] [1043:82ae] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=5edf19ce-c17b-4661-bfff-4b32af86a9e4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N73-AM ACPI BIOS Revision 0201 dmi.board.name: P5N73-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N73-AMACPIBIOSRevision0201:bd06/11/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N73-AM:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 08:05:47 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu xenial -- 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/1676002 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: The system freezes randomly since I installed Ubuntu 16.04. I think there's a problem with nvidia drivers. The graphic card is Nvidia GeForce 7050/NForce 610i. I use the nouveau driver. Before this I used Ubuntu 12.04 without problems for almost 5 years with 173 N
[Touch-packages] [Bug 1676004] [NEW] tiled - enabling hardware accelerated drawing spawns new windows/instances forever
Public bug reported: ubuntu 17.04 unity8 tiled - enabling hardware accelerated drawing spawns new windows/instances forever if you don't have tiled install (it's a qt5 app) "apt install tiled" launch tiled without Xmir from Preferences enable Hardware accelerated drawing (OpenGL) see screenshot should now start to spawn multiple instances/windows for ever. if it doesn't click on new project (should be the same) in unity7 seems to work fine ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20170325_102119148.png" https://bugs.launchpad.net/bugs/1676004/+attachment/4845348/+files/screenshot20170325_102119148.png ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676004 Title: tiled - enabling hardware accelerated drawing spawns new windows/instances forever Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 tiled - enabling hardware accelerated drawing spawns new windows/instances forever if you don't have tiled install (it's a qt5 app) "apt install tiled" launch tiled without Xmir from Preferences enable Hardware accelerated drawing (OpenGL) see screenshot should now start to spawn multiple instances/windows for ever. if it doesn't click on new project (should be the same) in unity7 seems to work fine To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676004/+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 1676007] [NEW] package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error
Public bug reported: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.handoff=7 SourcePackage: libxrandr Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RCK3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3450:pvr:rvnDellInc.:rn0RCK3X:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 09:44:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3~trusty1 ** Affects: libxrandr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 Status in libxrandr package in Ubuntu: New Bug description: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quie
[Touch-packages] [Bug 1676007] Re: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error ex
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1676007 Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 Status in libxrandr package in Ubuntu: New Bug description: 安装wine出错 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 25 16:34:01 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libxrandr2:2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz]:subprocess new post-removal script returned error exit status 127 ErrorMessage: subprocess new post-removal script returned error exit status 127 GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0631] Subsystem: Dell Device [1028:0631] InstallationDate: Installed on 2016-03-02 (387 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=6b99940d-5057-4776-99ae-b97c37448fd5 ro quiet splash vt.handoff=7 SourcePackage: libxrandr Title: package libxrandr2 2:1.4.2-1 [modified: usr/share/doc/libxrandr2/changelog.Debian.gz] failed to install/upgrade: subprocess new post-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RCK3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/18/2015:svnDellInc.:pnLatitude3450:pvr:rvnDellInc.:rn0RCK3X:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 25 09:44:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1676007/+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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)
** Changed in: mir Status: New => In Progress ** Changed in: mir Milestone: None => 1.0.0 ** Also affects: mir/0.26 Importance: Undecided Status: New ** Changed in: mir/0.26 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir/0.26 Status: New => In Progress ** Changed in: mir/0.26 Milestone: None => 0.26.3 ** Changed in: mir/0.26 Importance: Undecided => High ** Description changed: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. - Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. + Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. + + This applies to all currently pressed buttons. I.e. you can open an edit + field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch + to another VT. On return 'w' will be repeated indefinitely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675357 Title: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) Status in Canonical System Image: Triaged Status in Mir: In Progress Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub
[Touch-packages] [Bug 1476218] Re: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
*** This bug is a duplicate of bug 873551 *** https://bugs.launchpad.net/bugs/873551 The attached DpkgTerminalLog.gz contains the following error message at the end. update-default-wordlist: Question empty but elements installed for class "wordlist" dictionaries-common/default-wordlist: return code: "0", value: "" Choices: , Manual symlink setting shared/packages-wordlist: return code: "10" owners/error: "shared/packages-wordlist doesn't exist" Installed elements: american (American English), british (British English) Please see "/usr/share/doc/dictionaries-common/README.problems", section "Debconf database corruption" for recovery info. update-default-wordlist: Selected wordlist "" does not correspond to any installed package in the system and no alternative wordlist could be selected. dpkg: error processing package dictionaries-common (--configure): subprocess installed post-installation script returned error exit status 255 ** This bug has been marked a duplicate of bug 1310271 systemsettings not installing, dictionaries-common is getting error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1476218 Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in dictionaries-common package in Ubuntu: New Bug description: Errors were encountered while processing: dictionaries-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.2.0-87.125-generic 3.2.69 Uname: Linux 3.2.0-87-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Mon Jul 20 12:50:35 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2015-07-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1476218/+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 1310271] Re: systemsettings not installing, dictionaries-common is getting error
*** This bug is a duplicate of bug 873551 *** https://bugs.launchpad.net/bugs/873551 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dictionaries-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1310271 Title: systemsettings not installing, dictionaries-common is getting error Status in dictionaries-common package in Ubuntu: Confirmed Bug description: sudo apt-get install systemsettings Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: aspell aspell-en dictionaries-common enchant kde-runtime kdelibs5-plugins kubuntu-debug-installer libenchant1c2a qapt-batch Suggested packages: aspell-doc spellutils emacsen-common jed-extra djvulibre-bin libenchant-voikko The following NEW packages will be installed: aspell aspell-en dictionaries-common enchant kde-runtime kdelibs5-plugins kubuntu-debug-installer libenchant1c2a qapt-batch systemsettings 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3,605 kB of archives. After this operation, 16.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y Preconfiguring packages ... Selecting previously unselected package dictionaries-common. (Reading database ... 275477 files and directories currently installed.) Preparing to unpack .../dictionaries-common_1.20.5_all.deb ... Adding 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Unpacking dictionaries-common (1.20.5) ... Selecting previously unselected package aspell. Preparing to unpack .../aspell_0.60.7~20110707-1ubuntu1_i386.deb ... Unpacking aspell (0.60.7~20110707-1ubuntu1) ... Selecting previously unselected package aspell-en. Preparing to unpack .../aspell-en_7.1-0-1_all.deb ... Unpacking aspell-en (7.1-0-1) ... Selecting previously unselected package libenchant1c2a:i386. Preparing to unpack .../libenchant1c2a_1.6.0-10ubuntu1_i386.deb ... Unpacking libenchant1c2a:i386 (1.6.0-10ubuntu1) ... Selecting previously unselected package enchant. Preparing to unpack .../enchant_1.6.0-10ubuntu1_i386.deb ... Unpacking enchant (1.6.0-10ubuntu1) ... Selecting previously unselected package kdelibs5-plugins. Preparing to unpack .../kdelibs5-plugins_4%3a4.13.0-0ubuntu1_i386.deb ... Unpacking kdelibs5-plugins (4:4.13.0-0ubuntu1) ... Selecting previously unselected package kde-runtime. Preparing to unpack .../kde-runtime_4%3a4.13.0-0ubuntu1_i386.deb ... Unpacking kde-runtime (4:4.13.0-0ubuntu1) ... Selecting previously unselected package qapt-batch. Preparing to unpack .../qapt-batch_2.1.70-0ubuntu4_i386.deb ... Unpacking qapt-batch (2.1.70-0ubuntu4) ... Selecting previously unselected package kubuntu-debug-installer. Preparing to unpack .../kubuntu-debug-installer_13.10ubuntu1_i386.deb ... Unpacking kubuntu-debug-installer (13.10ubuntu1) ... Selecting previously unselected package systemsettings. Preparing to unpack .../systemsettings_4%3a4.11.8-0ubuntu6_i386.deb ... Unpacking systemsettings (4:4.11.8-0ubuntu6) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Setting up dictionaries-common (1.20.5) ... update-default-wordlist: Question empty but elements installed for class "wordlist" dictionaries-common/default-wordlist: return code: "0", value: "" Choices: , Manual symlink setting shared/packages-wordlist: return code: "10" owners/error: "shared/packages-wordlist doesn't exist" Installed elements: american (American English) Please see "/usr/share/doc/dictionaries-common/README.problems", section "Debconf database corruption" for recovery info. update-default-wordlist: Selected wordlist "" does not correspond to any installed package in the system and no alternative wordlist could be selected. dpkg: error processing package dictionaries-common (--configure): subprocess installed post-installation script returned error exit status 255 dpkg: dependency problems prevent configuration of aspell: aspell depends on dictionaries-common (>> 0.40); however: Package dictionaries-common is not configured yet. dpkg: error processing package aspell (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of aspell-en: aspell-en depends on aspell (>= 0.60.3-2); however: Package aspell
[Touch-packages] [Bug 1476218] Re: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
*** This bug is a duplicate of bug 873551 *** https://bugs.launchpad.net/bugs/873551 ** This bug is no longer a duplicate of bug 1310271 systemsettings not installing, dictionaries-common is getting error ** This bug has been marked a duplicate of bug 873551 dictionaries-common: debconf corruption -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1476218 Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in dictionaries-common package in Ubuntu: New Bug description: Errors were encountered while processing: dictionaries-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.2.0-87.125-generic 3.2.69 Uname: Linux 3.2.0-87-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Mon Jul 20 12:50:35 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2015-07-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1476218/+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 1310271] Re: systemsettings not installing, dictionaries-common is getting error
*** This bug is a duplicate of bug 873551 *** https://bugs.launchpad.net/bugs/873551 ** This bug has been marked a duplicate of bug 873551 dictionaries-common: debconf corruption -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1310271 Title: systemsettings not installing, dictionaries-common is getting error Status in dictionaries-common package in Ubuntu: Confirmed Bug description: sudo apt-get install systemsettings Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: aspell aspell-en dictionaries-common enchant kde-runtime kdelibs5-plugins kubuntu-debug-installer libenchant1c2a qapt-batch Suggested packages: aspell-doc spellutils emacsen-common jed-extra djvulibre-bin libenchant-voikko The following NEW packages will be installed: aspell aspell-en dictionaries-common enchant kde-runtime kdelibs5-plugins kubuntu-debug-installer libenchant1c2a qapt-batch systemsettings 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3,605 kB of archives. After this operation, 16.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y Preconfiguring packages ... Selecting previously unselected package dictionaries-common. (Reading database ... 275477 files and directories currently installed.) Preparing to unpack .../dictionaries-common_1.20.5_all.deb ... Adding 'diversion of /usr/share/dict/words to /usr/share/dict/words.pre-dictionaries-common by dictionaries-common' Unpacking dictionaries-common (1.20.5) ... Selecting previously unselected package aspell. Preparing to unpack .../aspell_0.60.7~20110707-1ubuntu1_i386.deb ... Unpacking aspell (0.60.7~20110707-1ubuntu1) ... Selecting previously unselected package aspell-en. Preparing to unpack .../aspell-en_7.1-0-1_all.deb ... Unpacking aspell-en (7.1-0-1) ... Selecting previously unselected package libenchant1c2a:i386. Preparing to unpack .../libenchant1c2a_1.6.0-10ubuntu1_i386.deb ... Unpacking libenchant1c2a:i386 (1.6.0-10ubuntu1) ... Selecting previously unselected package enchant. Preparing to unpack .../enchant_1.6.0-10ubuntu1_i386.deb ... Unpacking enchant (1.6.0-10ubuntu1) ... Selecting previously unselected package kdelibs5-plugins. Preparing to unpack .../kdelibs5-plugins_4%3a4.13.0-0ubuntu1_i386.deb ... Unpacking kdelibs5-plugins (4:4.13.0-0ubuntu1) ... Selecting previously unselected package kde-runtime. Preparing to unpack .../kde-runtime_4%3a4.13.0-0ubuntu1_i386.deb ... Unpacking kde-runtime (4:4.13.0-0ubuntu1) ... Selecting previously unselected package qapt-batch. Preparing to unpack .../qapt-batch_2.1.70-0ubuntu4_i386.deb ... Unpacking qapt-batch (2.1.70-0ubuntu4) ... Selecting previously unselected package kubuntu-debug-installer. Preparing to unpack .../kubuntu-debug-installer_13.10ubuntu1_i386.deb ... Unpacking kubuntu-debug-installer (13.10ubuntu1) ... Selecting previously unselected package systemsettings. Preparing to unpack .../systemsettings_4%3a4.11.8-0ubuntu6_i386.deb ... Unpacking systemsettings (4:4.11.8-0ubuntu6) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Setting up dictionaries-common (1.20.5) ... update-default-wordlist: Question empty but elements installed for class "wordlist" dictionaries-common/default-wordlist: return code: "0", value: "" Choices: , Manual symlink setting shared/packages-wordlist: return code: "10" owners/error: "shared/packages-wordlist doesn't exist" Installed elements: american (American English) Please see "/usr/share/doc/dictionaries-common/README.problems", section "Debconf database corruption" for recovery info. update-default-wordlist: Selected wordlist "" does not correspond to any installed package in the system and no alternative wordlist could be selected. dpkg: error processing package dictionaries-common (--configure): subprocess installed post-installation script returned error exit status 255 dpkg: dependency problems prevent configuration of aspell: aspell depends on dictionaries-common (>> 0.40); however: Package dictionaries-common is not configured yet. dpkg: error processing package aspell (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of aspell-en: aspell-en depends on aspell (>= 0.60.3-2); however: Package aspell is not configured yet. aspell-en depends on di
[Touch-packages] [Bug 1427203] Re: package dictionaries-common 1.20.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255
*** This bug is a duplicate of bug 873551 *** https://bugs.launchpad.net/bugs/873551 The attached VarLogDistupgradeApttermlog.txt.gz contains the following error message: Configurando dictionaries-common (1.20.5) ... update-default-wordlist: Question empty but elements installed for class "wordlist" dictionaries-common/default-wordlist: return code: "0", value: "" Choices: , Ajuste manual de enlaces simb√≥licos shared/packages-wordlist: return code: "10" owners/error: "shared/packages-wordlist doesn't exist" Installed elements: american (American English), british (British English) Please see "/usr/share/doc/dictionaries-common/README.problems", section "Debconf database corruption" for recovery info. update-default-wordlist: Selected wordlist "" does not correspond to any installed package in the system and no alternative wordlist could be selected. dpkg: error al procesar el paquete dictionaries-common (--configure): el subproceso instalado el script post-installation devolvi√≥ el c√≥digo de salida de error 255 ** This bug has been marked a duplicate of bug 1310271 systemsettings not installing, dictionaries-common is getting error ** This bug is no longer a duplicate of bug 1310271 systemsettings not installing, dictionaries-common is getting error ** This bug has been marked a duplicate of bug 873551 dictionaries-common: debconf corruption -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1427203 Title: package dictionaries-common 1.20.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255 Status in dictionaries-common package in Ubuntu: New Bug description: do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.2.0-59.90-generic 3.2.54 Uname: Linux 3.2.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Mon Mar 2 13:23:26 2015 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 255 InstallationDate: Installed on 2009-11-26 (1921 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 255 UpgradeStatus: Upgraded to trusty on 2015-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1427203/+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 1676011] [NEW] [unity8] minimize/unminimize animation is not pointing to the app in the launcher
Public bug reported: ubuntu 17.04 unity8 [unity8] minimize/unminimize animation is not pointing to the app in the launcher when you minimize/unminimize and app it just resizes and moves the window to a fixed location. in unity8 the UX is much better/more descriptive, it actually resizes the window towards the actuall app icon in the launcher. minimize/maximize apps in both u7/u8 ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1676011 Title: [unity8] minimize/unminimize animation is not pointing to the app in the launcher Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 [unity8] minimize/unminimize animation is not pointing to the app in the launcher when you minimize/unminimize and app it just resizes and moves the window to a fixed location. in unity8 the UX is much better/more descriptive, it actually resizes the window towards the actuall app icon in the launcher. minimize/maximize apps in both u7/u8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676011/+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 1648183] Re: Crackling and popping sound when using headphones
Same issue on HP Pavilion x360 u003ng. (Sorry for German output) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio Liste der Hardware-Geräte (PLAYBACK) Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC295 Analog [ALC295 Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 8: HDMI 2 [HDMI 2] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1676016] [NEW] the menu doesn't work if the window is smaller
Public bug reported: Ubuntu 17.04 unity8 the menu doesn't work if the window is smaller launch kate (without Xmir), resize the window until the menu is wider than the window (you'll see a down arrow that will expand the menu if pressed) see screenshot now try to open the expanded menu/submenus see screenshot ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20170325_114331283.png" https://bugs.launchpad.net/bugs/1676016/+attachment/4845426/+files/screenshot20170325_114331283.png ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1676016 Title: the menu doesn't work if the window is smaller Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Ubuntu 17.04 unity8 the menu doesn't work if the window is smaller launch kate (without Xmir), resize the window until the menu is wider than the window (you'll see a down arrow that will expand the menu if pressed) see screenshot now try to open the expanded menu/submenus see screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676016/+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
Re: [Touch-packages] [Bug 1674330] [NEW] Please consider dropping /etc/network/if-up.d/openssh-server
On Mon, Mar 20, 2017 at 05:14:07PM -, Perry E. Metzger wrote:
> And it isn't a "hack", this is exactly what ifup/down scripts are for.
They're useful for giving sysadmins the flexibility to do this sort of
thing locally without too much work, but doing service restarts on
if-{up,down} is an awfully big hammer that's generally better handled
some other way if possible.
Not being the maintainer and not using Ubuntu any more, you might be
unaware of how much work this hack has been to maintain over the years.
I'd certainly support removing it if it can be demonstrated to be safe
to do so (in which I do include your original use case). For example:
https://bugs.debian.org/502444
https://bugs.debian.org/756547
https://bugs.launchpad.net/bugs/1584393
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1674330
Title:
Please consider dropping /etc/network/if-up.d/openssh-server
Status in openssh package in Ubuntu:
New
Bug description:
The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1]
as a response to bug
103436. At least from today's perspective this isn't justified:
I can't seem to be able to actually reproduce that issue: I can start
a VM with no network interfaces, remove the above hack, then start
sshd, then bring up an ethernet interface, and I can connect to ssh
via ethernet just fine. Also, e. g. Fedora has no counterpart of this
hack, and these days a lot of people would complain if that would
cause problems, as hotpluggable/roaming network devices are
everywhere.
The hack introduces a race: you run into connection errors after
bringing up a new interface as sshd stops listening briefly while
being reloaded. That's the reason why I looked at it, as this
regularly happens in upstream's cockpit integration tests.
Also, /etc/network/if-up.d/ isn't being run when using
networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
this doesn't seem to have caused any issues.
I asked the original reporter of bug 103436 for some details, and to
check whether that hack is still necessary. There is actually a
proposed patch upstream [2] to use IP_FREEBIND, which is the modern
solution to listening to all "future" interfaces as well. But at least
for the majority of cases it seems to work fine without that even.
So I wonder if it's time to bury that hack?
[1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
[2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1674330/+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 1675685] Re: Click python namespace clashes with another Python project
I agree that this is an unfortunate situation. I did as much as I realistically could to mitigate it in versions 0.4.41+16.04.20151211-0ubuntu1 and 0.4.43+16.04.20160203-0ubuntu1. click is end-of-life, is now lacking a regular maintainer, is due to be replaced by snapd/snapcraft/etc., and will be removed once the migration has been complete; so the (non-trivial) effort to rename it wouldn't pay off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1675685 Title: Click python namespace clashes with another Python project Status in click package in Ubuntu: New Bug description: The click python library provided by Ubuntu uses the namespace `click` with conflicts with another project with the same name (http://click.pocoo.org/5/). This can (and has caused) serious issues. I spent several hours troubleshooting an Ubuntu 17.04 upgrade because I happened to have click installed with pip in /usr/local/. One of the two projects has to let go of the namespace and since the Ubuntu project isn't used for general programming, is much less widespread and isn't available in Pypi, this one should change its namespace to something else. I noticed this has been done with the deb package, named python3 -click-package (which conflicts with python3-click) but since click is also installable with pip, this is not enough to avoid issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1675685/+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 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server
** Bug watch added: Debian Bug tracker #502444 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502444 ** Bug watch added: Debian Bug tracker #756547 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756547 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1674330 Title: Please consider dropping /etc/network/if-up.d/openssh-server Status in openssh package in Ubuntu: New Bug description: The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] as a response to bug 103436. At least from today's perspective this isn't justified: I can't seem to be able to actually reproduce that issue: I can start a VM with no network interfaces, remove the above hack, then start sshd, then bring up an ethernet interface, and I can connect to ssh via ethernet just fine. Also, e. g. Fedora has no counterpart of this hack, and these days a lot of people would complain if that would cause problems, as hotpluggable/roaming network devices are everywhere. The hack introduces a race: you run into connection errors after bringing up a new interface as sshd stops listening briefly while being reloaded. That's the reason why I looked at it, as this regularly happens in upstream's cockpit integration tests. Also, /etc/network/if-up.d/ isn't being run when using networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far this doesn't seem to have caused any issues. I asked the original reporter of bug 103436 for some details, and to check whether that hack is still necessary. There is actually a proposed patch upstream [2] to use IP_FREEBIND, which is the modern solution to listening to all "future" interfaces as well. But at least for the majority of cases it seems to work fine without that even. So I wonder if it's time to bury that hack? [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6 [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1674330/+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 1086019] Re: cupsd crashes regularly (daily)
all users can't print from libreoffice (oodt) files - only PDF printing works -- 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/1086019 Title: cupsd crashes regularly (daily) Status in cups package in Ubuntu: Fix Released Status in cups-filters package in Ubuntu: Fix Released Status in cups source package in Quantal: Fix Released Status in cups-filters source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacB
[Touch-packages] [Bug 1676023] [NEW] apport leaks hostname
Public bug reported: Apport leaks the machine's hostname in the log files when uploading logs to Launchpad. File CurrentDmesg.txt has the line: [6.690523] systemd[1]: Set hostname to . File XorgLog.txt and XorgLogOld.txt has the line: [ 293.791] Current Operating System: Linux foo 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 x86_64 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sat Mar 25 11:21:04 2017 InstallationDate: Installed on 2013-12-26 (1184 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug privacy zesty ** Tags added: privacy -- 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/1676023 Title: apport leaks hostname Status in apport package in Ubuntu: New Bug description: Apport leaks the machine's hostname in the log files when uploading logs to Launchpad. File CurrentDmesg.txt has the line: [6.690523] systemd[1]: Set hostname to . File XorgLog.txt and XorgLogOld.txt has the line: [ 293.791] Current Operating System: Linux foo 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:26 UTC 2017 x86_64 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sat Mar 25 11:21:04 2017 InstallationDate: Installed on 2013-12-26 (1184 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1676023/+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 1676016] Re: Overflow menus don't work
** Summary changed: - the menu doesn't work if the window is smaller + Overflow menus don't work ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: canonical-devices-system-image Milestone: None => u8c-2 ** Changed in: qtubuntu (Ubuntu) Status: New => Triaged ** No longer affects: qtubuntu (Ubuntu) ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1676016 Title: Overflow menus don't work Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Ubuntu 17.04 unity8 the menu doesn't work if the window is smaller launch kate (without Xmir), resize the window until the menu is wider than the window (you'll see a down arrow that will expand the menu if pressed) see screenshot now try to open the expanded menu/submenus see screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676016/+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 1675138] Re: Please transition to Boost 1.62
** Changed in: mir (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675138 Title: Please transition to Boost 1.62 Status in Mir: Fix Committed Status in Mir 0.26 series: New Status in mir package in Ubuntu: Fix Committed Bug description: There is an ongoing transition to Boost 1.62 and mir is one of the last affected packages: http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1675138/+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 1567697] Re: libcurl is missing http2 support
time passes, new releases come, nothing changes silpol@lorry:~$ curl --http2 www.google.com curl: (1) Unsupported protocol silpol@lorry:~$ lsb_release -rd Description:Ubuntu 16.10 Release:16.10 silpol@lorry:~$ apt-cache policy libcurl3 libcurl3: Installed: 7.50.1-1ubuntu1.1 Candidate: 7.50.1-1ubuntu1.1 Version table: *** 7.50.1-1ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 7.50.1-1ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1567697 Title: libcurl is missing http2 support Status in curl package in Ubuntu: Confirmed Bug description: libcurl supports HTTP/2.0 through libnghttp2, but the package on Ubuntu is not compiled with it. Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good idea. See also: https://curl.haxx.se/docs/http2.html curl CLI tool should not need an update, as it already has the commandline switches, but when you use them it comes back with unsupported protocol. drwilco@eris:~$ curl --http2 www.google.com curl: (1) Unsupported protocol drwilco@eris:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@eris:~# apt-cache policy libcurl3 libcurl3: Installed: 7.47.0-1ubuntu2 Candidate: 7.47.0-1ubuntu2 Version table: *** 7.47.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1567697/+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 1567697] Re: libcurl is missing http2 support
from -V key it looks like current curl in Yakkety is built with GnuTLS silpol@lorry:~$ curl -V curl 7.50.1 (x86_64-pc-linux-gnu) libcurl/7.50.1 GnuTLS/3.5.3 zlib/1.2.8 libidn/1.33 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP UnixSockets -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1567697 Title: libcurl is missing http2 support Status in curl package in Ubuntu: Confirmed Bug description: libcurl supports HTTP/2.0 through libnghttp2, but the package on Ubuntu is not compiled with it. Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good idea. See also: https://curl.haxx.se/docs/http2.html curl CLI tool should not need an update, as it already has the commandline switches, but when you use them it comes back with unsupported protocol. drwilco@eris:~$ curl --http2 www.google.com curl: (1) Unsupported protocol drwilco@eris:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@eris:~# apt-cache policy libcurl3 libcurl3: Installed: 7.47.0-1ubuntu2 Candidate: 7.47.0-1ubuntu2 Version table: *** 7.47.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1567697/+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
Re: [Touch-packages] [Bug 1674330] [NEW] Please consider dropping /etc/network/if-up.d/openssh-server
On Sat, 25 Mar 2017 09:57:26 - Colin Watson
wrote:
> On Mon, Mar 20, 2017 at 05:14:07PM -, Perry E. Metzger wrote:
> > And it isn't a "hack", this is exactly what ifup/down scripts are
> > for.
>
> They're useful for giving sysadmins the flexibility to do this sort
> of thing locally without too much work, but doing service restarts
> on if-{up,down} is an awfully big hammer that's generally better
> handled some other way if possible.
So why don't you get a laptop and try it out? Using a virtual machine
will not tell you what the behavior is if the network address is
forcibly changed on the machine, and there are other confounding
circumstances here like loss of network carrier when you change
location etc. (It may be possible to conduct a principled experiment
with virtual machines but it will not be particularly easy.)
You will have to make sure that the daemon continues to permit remote
logins on every new address it acquires.
> Not being the maintainer and not using Ubuntu any more, you might be
> unaware of how much work this hack has been to maintain over the
> years.
Many things are unpleasant to maintain but provide necessary
functionality. Again, what you should do is conduct an actual test.
Perry
--
Perry E. Metzgerpe...@piermont.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1674330
Title:
Please consider dropping /etc/network/if-up.d/openssh-server
Status in openssh package in Ubuntu:
New
Bug description:
The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1]
as a response to bug
103436. At least from today's perspective this isn't justified:
I can't seem to be able to actually reproduce that issue: I can start
a VM with no network interfaces, remove the above hack, then start
sshd, then bring up an ethernet interface, and I can connect to ssh
via ethernet just fine. Also, e. g. Fedora has no counterpart of this
hack, and these days a lot of people would complain if that would
cause problems, as hotpluggable/roaming network devices are
everywhere.
The hack introduces a race: you run into connection errors after
bringing up a new interface as sshd stops listening briefly while
being reloaded. That's the reason why I looked at it, as this
regularly happens in upstream's cockpit integration tests.
Also, /etc/network/if-up.d/ isn't being run when using
networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
this doesn't seem to have caused any issues.
I asked the original reporter of bug 103436 for some details, and to
check whether that hack is still necessary. There is actually a
proposed patch upstream [2] to use IP_FREEBIND, which is the modern
solution to listening to all "future" interfaces as well. But at least
for the majority of cases it seems to work fine without that even.
So I wonder if it's time to bury that hack?
[1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
[2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1674330/+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 1551022] Re: mouse pointer leaves trail
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on a Intel J3160 processor. Connection is dual monitor VGA + HDMI What do you need qua logging or actions to solve this issue? ** Attachment added: "Mouse Pointer Trails" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+attachment/4845654/+files/MousePointerTrails.png -- 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/1551022 Title: mouse pointer leaves trail Status in xorg package in Ubuntu: Expired Bug description: In my desktop system Kubuntu 15.10 I have the integrated graphic card (Intel HD3000) and a discrete graphic card (Nvidia GTX 550). Some days ago I attached a monitor on the iGPU and enabled it, giving me a triple head system (two monitors on the Nvidia and one on the Intel). From that moment, the mouse pointer started to leave a trail when it pass over something that is animating. I'm using nouveau for the nvidia card. I tried to upgrade to Kubuntu 16.04, but it gives me the same glitch. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-02-24 01:06:09,804 DEBUG enabling apt cron job DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF116 [GeForce GTX 550 Ti] [19da:5194] InstallationDate: Installed on 2015-11-19 (106 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=679d8ad1-4664-4abd-a80a-3ac9339425bb ro quiet splash nomdmonddf nomdmonisw irqnodebug vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Tags: xenial ubuntu single-occurrence reproducible has-workaround Uname: Linux 4.4.0-10-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3707:bd07/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+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 1675206] Re: Bug when authenticating password
** Description changed: When you enter the wrong password, you will be prompted to enter the password again, and if you enter the wrong password three times, you will receive a warning. - But after updating the language-pack-en-base package, it introduces a bug, if you enter the wrong password is not asking you to enter the password again, simply the authentication screen disappears. Moving to another language works fine. + But after updating the language-pack-pt-base package, it introduces a bug, if you enter the wrong password is not asking you to enter the password again, simply the authentication screen disappears. Moving to another language works fine. This is a translation error in the sudoers.mo file. /usr/share/locale-langpack/pt_BR/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. /usr/share/locale-langpack/pt/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. OBS: I downloaded the Source and opened the PO file, I noticed that the line 6 when it is written (Sorry, try again) works without bug, when translated or write anything, it presents the error. EXEMPLE: If I write: ENPT or PT-BR Sorry, try again. --- Sinto muito, tente novamente. - bug Sorry, try again. --- aaa ddd rrr. -- bug Sorry, try again. --- xxx fff hhh. -- bug Sorry, try again. --- Sorry, try again.-- not bug I made a video to show the error: https://youtu.be/D22S7rTha9I Use Ubuntu 16.04 and Linux Mint 18.01 Base Ubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1675206 Title: Bug when authenticating password Status in language-pack-pt-base package in Ubuntu: New Bug description: When you enter the wrong password, you will be prompted to enter the password again, and if you enter the wrong password three times, you will receive a warning. But after updating the language-pack-pt-base package, it introduces a bug, if you enter the wrong password is not asking you to enter the password again, simply the authentication screen disappears. Moving to another language works fine. This is a translation error in the sudoers.mo file. /usr/share/locale-langpack/pt_BR/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. /usr/share/locale-langpack/pt/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. OBS: I downloaded the Source and opened the PO file, I noticed that the line 6 when it is written (Sorry, try again) works without bug, when translated or write anything, it presents the error. EXEMPLE: If I write: ENPT or PT-BR Sorry, try again. --- Sinto muito, tente novamente. - bug Sorry, try again. --- aaa ddd rrr. -- bug Sorry, try again. --- xxx fff hhh. -- bug Sorry, try again. --- Sorry, try again.-- not bug I made a video to show the error: https://youtu.be/D22S7rTha9I Use Ubuntu 16.04 and Linux Mint 18.01 Base Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1675206/+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 1586597] Re: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-setuptools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1586597 Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-setuptools package in Ubuntu: Confirmed Bug description: i installed the easy_install tool and i got this problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-pkg-resources 20.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 AptOrdering: python-pkg-resources: Install python-setuptools: Install python-pkg-resources: Configure python-setuptools: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat May 28 15:54:02 2016 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-setuptools Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1586597/+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 1675206] Re: Bug when authenticating password
close bug report: bug: https://github.com/linuxmint/libgksu/blob/acd6967a022709bf1ab74b3d7eb1eaabd91ce26f/libgksu/libgksu.c#L2599 Issues: https://github.com/linuxmint/libgksu/issues/6 ** Bug watch added: github.com/linuxmint/libgksu/issues #6 https://github.com/linuxmint/libgksu/issues/6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1675206 Title: Bug when authenticating password Status in language-pack-pt-base package in Ubuntu: New Bug description: When you enter the wrong password, you will be prompted to enter the password again, and if you enter the wrong password three times, you will receive a warning. But after updating the language-pack-pt-base package, it introduces a bug, if you enter the wrong password is not asking you to enter the password again, simply the authentication screen disappears. Moving to another language works fine. This is a translation error in the sudoers.mo file. /usr/share/locale-langpack/pt_BR/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. /usr/share/locale-langpack/pt/LC_MESSAGES/sudoers.mo LINE 6 - Sorry, try again. - Desculpe, tente novamente. OBS: I downloaded the Source and opened the PO file, I noticed that the line 6 when it is written (Sorry, try again) works without bug, when translated or write anything, it presents the error. EXEMPLE: If I write: ENPT or PT-BR Sorry, try again. --- Sinto muito, tente novamente. - bug Sorry, try again. --- aaa ddd rrr. -- bug Sorry, try again. --- xxx fff hhh. -- bug Sorry, try again. --- Sorry, try again.-- not bug I made a video to show the error: https://youtu.be/D22S7rTha9I Use Ubuntu 16.04 and Linux Mint 18.01 Base Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1675206/+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 1676076] [NEW] [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd
Public bug reported: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description:Ubuntu 16.10 Release:16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1676076 Title: [X556UB, Realtek ALC255, Speaker, Internal] flac files skips or sttuter, rhytmbox and mpd Status in alsa-driver package in Ubuntu: New Bug description: Flac Files skips (like an old record scratch) on rhytmbox or mpd server (via soundcard or a DAC). The skip is random. Description: Ubuntu 16.10 Release: 16.10 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: brujo 2424 F...m pulseaudio /dev/snd/controlC0: brujo 2424 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 25 12:11:59 2017 InstallationDate: Installed on 2017-01-30 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X556UB, Realtek ALC255, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1676076/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Done! See bug 1676081. Thanks Seth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Fix Released Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Won't Fix Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1676081] [NEW] No wifi connection after suspend with a MacBook Pro
Public bug reported: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: macbookpro network suspend-resume systemctl wifi ** Description changed: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 + Side effect: it closes the VPN connection if there was one. + # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1676081 Title: No wifi connection after suspend with a MacBook Pro Status in wpa package in Ubuntu: New Bug description: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1676081/+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 1653217] Re: stop job timeout loops forever
I have a similar problem on Linux Mint 18.1. -- 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/1653217 Title: stop job timeout loops forever Status in systemd package in Ubuntu: Confirmed Bug description: On my Ubuntu 16.04.1 LTS with the most recent software updates I regularly run into a situation where the reboot of the machine will hang with a message A stop job is running for ... (1min 23s / 1min 30s) which is already annoying by itself see e.g. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400 what is worse is that after 90 secs the message changes to A stop job is running for ... (1min 31s / 3min 0s) and so on which effectively means the machine will not reboot since this seems to go on for ever (I tried at least for 15 minutes ...) The reason for the stop job behavior seems to be a cifs mount from the machine to one of it's virtual machine. The shutdown sequence seems to be that the virtual machines are shutdown first than the try to unmount the CIFS share will obviously fail (which in fact would not be any big deal at all). First I'll now try to workaround this bug but this bug indeed has horrible consequences: - the machine will not properly reboot by itself any more needing human intervention - since the console is not accessible a hard reset is needed - the hard reset will cause a file system check since the cifs mounts are unmounted before the physical drives so the file systems on the physical drives are not shut down properl.y - on my machine there are several multi-terrabyte drives where the filesystem checks will take approx an hour - so each reboot at this time might take at least an hour and an ugly procedure - thats not what I expect from an OS in this century ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653217/+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 1653217] Re: stop job timeout loops forever
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1653217 Title: stop job timeout loops forever Status in systemd package in Ubuntu: Confirmed Bug description: On my Ubuntu 16.04.1 LTS with the most recent software updates I regularly run into a situation where the reboot of the machine will hang with a message A stop job is running for ... (1min 23s / 1min 30s) which is already annoying by itself see e.g. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400 what is worse is that after 90 secs the message changes to A stop job is running for ... (1min 31s / 3min 0s) and so on which effectively means the machine will not reboot since this seems to go on for ever (I tried at least for 15 minutes ...) The reason for the stop job behavior seems to be a cifs mount from the machine to one of it's virtual machine. The shutdown sequence seems to be that the virtual machines are shutdown first than the try to unmount the CIFS share will obviously fail (which in fact would not be any big deal at all). First I'll now try to workaround this bug but this bug indeed has horrible consequences: - the machine will not properly reboot by itself any more needing human intervention - since the console is not accessible a hard reset is needed - the hard reset will cause a file system check since the cifs mounts are unmounted before the physical drives so the file systems on the physical drives are not shut down properl.y - on my machine there are several multi-terrabyte drives where the filesystem checks will take approx an hour - so each reboot at this time might take at least an hour and an ugly procedure - thats not what I expect from an OS in this century ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653217/+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 1351939] Re: Sending USSD message does not work
Hello. My device is E3372. After sending any USSD i've get error: "GDBus.Error:org.freedesktop.ModemManader1.Error.Core.Failed: Invalid USSD response received: '^CCIN:2,0,"","",0'". Modem Manager GUI 0.0.18-3 Linux Mint 18.1 In the previous version of the USSD went sometimes and sometimes not. Please fix the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager: New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+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 1676088] [NEW] unity greeter logs-in when clicking password field
Public bug reported: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1676088 Title: unity greeter logs-in when clicking password field Status in lightdm package in Ubuntu: New Bug description: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1676088/+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 1676088] Re: unity greeter logs-in when clicking password field
** Description changed: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. - Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... + + I think this is also a security issue. I missed checking marking the + checkbox... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1676088 Title: unity greeter logs-in when clicking password field Status in lightdm package in Ubuntu: New Bug description: On Ubuntu 17.04 beta2 the unity greeter will log in immediately after clicking the password field. If I focus the password field using tab keys, I cannot type anything. The issue appears in both unity 7 and 8 options. I dont have activated auto login or login without password in my user settings. Maybe related: I face issues with passwords on sudo commands and similar. I changed my password with passwd (by booting from recovery mode). Since then, most sudo commands work with my new password, but some times I must type the old. For example after the automatic login in unity 7, a window asks me for my password (it says that it was not provided during login, which is true of course). This window would accepts only the old password... I think this is also a security issue. I missed checking marking the checkbox... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Mar 25 21:26:14 2017 InstallationDate: Installed on 2017-03-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1676088/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- 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: Unknown 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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
Comment 14 from https://bugs.kde.org/show_bug.cgi?id=303627 summarizes the current state of this bug. "I'm taking the liberty to close this report (it was "confirmed" by my vote in the first place). The fake mimetypes have been removed from kcoreaddons's kde5.xml file: https://github.com/KDE/kcoreaddons/commit/36ff1bf60c9b12c28ed4d7566abceac10cab345e They still are defined in the old kdelibs package, but we cannot remove them because it would break all the kde4 apps that are still using them. While kdelibs4 is still being released with new bugfixes, most of those kde4 apps are not." ** Package changed: kde4libs (Debian) => ubuntu ** No longer affects: ubuntu ** Bug watch added: KDE Bug Tracking System #303627 https://bugs.kde.org/show_bug.cgi?id=303627 ** Also affects: kdelibs via https://bugs.kde.org/show_bug.cgi?id=303627 Importance: Unknown Status: Unknown ** Changed in: kde4libs (Ubuntu) Status: Invalid => Confirmed ** Changed in: kde4libs (Ubuntu) Importance: Undecided => Low -- 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: Unknown 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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
It seems this was fixed upstream for KDE Frameworks 5. Not sure if we
can backport the fix because of the compatibility problems mentioned.
This is also mentioned in the porting notes for KDE Frameworks 5.
https://community.kde.org/Frameworks/Porting_Notes#Mime_Types
"The following fake MIME types have been removed and should be replaced
as follows:
all/allfiles ➙ application/octet-stream
all/all ➙ application/octet-stream+inode/directory
uri/{mms,mmst,mmsu,pnm,rtspt,rtsptu} ➙ x-scheme-handler/..."
--
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:
Unknown
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 193325] Re: "unknown media type" during update
** Project changed: nautilus => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Confirmed => New ** Changed in: ubuntu Remote watch: Debian Bug tracker #469833 => None ** No longer affects: ubuntu ** Bug watch removed: Debian Bug tracker #469833 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469833 ** Bug watch removed: freedesktop.org Bugzilla #16816 https://bugs.freedesktop.org/show_bug.cgi?id=16816 -- 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/193325 Title: "unknown media type" during update Status in shared-mime-info: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/193325/+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 1672111] Re: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1672111 Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: Confirmed Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016j-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Mar 11 18:38:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-15 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1672111/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
** Changed in: kdelibs Status: Unknown => Won't Fix ** Changed in: kdelibs Importance: Unknown => Low -- 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 1591524] Re: package openssh-client 1:7.2p2-4 failed to install/upgrade: package openssh-client is not ready for configuration cannot configure (current status 'half-installed')
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1591524 Title: package openssh-client 1:7.2p2-4 failed to install/upgrade: package openssh-client is not ready for configuration cannot configure (current status 'half-installed') Status in openssh package in Ubuntu: Expired Bug description: / ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-client 1:7.2p2-4 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 AptOrdering: python-apt: Install openssh-client: Configure python-apt: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 12 01:03:38 2016 DpkgTerminalLog: Preparing to unpack .../python-apt_1.1.0~beta1build1_amd64.deb ... Unpacking python-apt (1.1.0~beta1build1) ... dpkg: error processing package openssh-client (--configure): package openssh-client is not ready for configuration cannot configure (current status 'half-installed') DuplicateSignature: Unpacking python-apt (1.1.0~beta1build1) ... dpkg: error processing package openssh-client (--configure): package openssh-client is not ready for configuration ErrorMessage: package openssh-client is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-06-10 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:7.2p2-4 SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4, OpenSSL 1.0.2g-fips 1 Mar 2016 SourcePackage: openssh Title: package openssh-client 1:7.2p2-4 failed to install/upgrade: package openssh-client is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1591524/+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 1435988] Re: sometime right edge swip stop working on the lockscreen
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1435988 Title: sometime right edge swip stop working on the lockscreen Status in unity8 package in Ubuntu: Expired Status in unity8 package in Ubuntu RTM: Incomplete Bug description: Using rtm 256 on a bq phone, with a pin code set. Sometime the greeter/lock screen stops responding to right edge swipes (rather than dismissing the bg image+logo screen to display the pin code one, it does nothing). Right edge swipping works fine to trigger the switcher once the screen is unlocked though To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1435988/+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 1676115] [NEW] systemd-resolved spams the system log with useless “Processing query...” messages
Public bug reported: If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved: Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... This was fixed upstream in v233 by downgrading this message from log_info to log_debug: https://github.com/systemd/systemd/pull/5233 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #5233 https://github.com/systemd/systemd/issues/5233 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5233 Importance: Unknown Status: Unknown -- 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/1676115 Title: systemd-resolved spams the system log with useless “Processing query...” messages Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved: Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... This was fixed upstream in v233 by downgrading this message from log_info to log_debug: https://github.com/systemd/systemd/pull/5233 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1676115/+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 1676117] [NEW] tzdata-java 2017a package required
Public bug reported: Mongolia no longer observes DST. I can't find tzdata-java_2017a package. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1676117 Title: tzdata-java 2017a package required Status in systemd package in Ubuntu: New Bug description: Mongolia no longer observes DST. I can't find tzdata-java_2017a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676117/+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 1623666] Re: iOS device contents not displayed in Ubuntu
#28 and then #29 work perfectly for me, connecting an iPhone with iOS 10.2 to my laptop with Ubuntu 16.04 running on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages
Dont get your spam: oem@u64:~$ journalctl | grep query Mar 26 07:15:44 u64 geoclue[2802]: Failed to query location: Error resolving “location.services.mozilla.com”: Name or service not known and seems already been fixed: systemd (232-21) unstable; urgency=medium * resolved: Downgrade "processing query..." message to debug. It doesn't really add much value in normal operation and just spams the log. (Closes: #858197) -- Michael Biebl Tue, 21 Mar 2017 19:52:17 +0100 ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1676115 Title: systemd-resolved spams the system log with useless “Processing query...” messages Status in systemd: Unknown Status in systemd package in Ubuntu: Incomplete Bug description: If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved: Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... This was fixed upstream in v233 by downgrading this message from log_info to log_debug: https://github.com/systemd/systemd/pull/5233 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1676115/+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
