[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash
Tested 8.59+17.10.20170606-0ubuntu2.20.10.1 on groovy and the test scenario outlined in the description is working now. The auth dialog no longer crashes singond. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Committed Status in signon source package in Groovy: Fix Committed Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
Also uploaded to groovy and focal as 8.59+17.10.20170606-0ubuntu2.20.10.1 and 8.59+17.10.20170606-0ubuntu2.20.04.1 respectively ** Changed in: signon (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: signon (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: In Progress Status in signon source package in Groovy: In Progress Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
** Description changed: - I'm reporting this bug upstream from where I found it, since I've - learned that the signond package in KDE Neon is sourced from Ubuntu - focal. + [Impact] + + Without the patch users are unable to add google accounts because signond crashes. + This prevents users from using KDE's online accounts feature for google. + The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. + + [Test Case] + + - in a plasma session + - install kio-gdrive + - run `systemsettings5 kcm_kaccounts` + - add a new account + - click on google + - wait for login window to appear + - signond shouldn't be crashing + + [Where problems could occur] + + Cannot think of any. It simply adds type info to the objects. Also + upstream has rtti disabled for months and I'm not aware of any problems. + + [Other Info] + + This is a fairly grave issue as far as user experience is concerned. + + + + + + I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) - Expected behaviour: + Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. - Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 ** Also affects: signon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: New Status in signon source package in Focal: New Status in signon source package in Groovy: New Status in signon source package in Hirsute: New Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to:
[Touch-packages] [Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
Was there a question in there? I did also see this on installed kubuntu systems, it's just far harder to reproduce there because of the racy nature of the issue. In fact, the only reason I know about the issue is because the colors are just so far off that they tripped up our openqa tests and flaked every so often. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: Incomplete Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1777994] Re: the header xcb/xinput.h is missing
uploaded bionic SRU libxcb_1.13-1.1 by Jonathan Riddell ** Description changed: - I suspect this means there should be another package, libxcb-xinput-dev - perhaps? + [Impact] + Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. + + [Test Case] + Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. + + [Regression Potential] + None that I can see, it's just packaging a few new header files. + + + + + I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:3802] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. - Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. - Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. + Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. + Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Changed in: libxcb (Ubuntu Bionic) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: In Progress Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita
[Touch-packages] [Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
** Patch added: "setvtrgb.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+attachment/5167040/+files/setvtrgb.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: New Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1783283] [NEW] setvtrgb.service incorrectly ordered [with patchy]
Public bug reported: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: New Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown
As explained in Bug #1761478 that would still leave timing issues. With --ping not blocking anymore casper-stop can shoot right past the prompt code on account of --ping coming back !0 (if plymouth isn't quick enough to start anyway). Meaning the user doesn't get told to remove the installation medium. e.g. this is what I get in a VM now http://people.ubuntu.com/~apachelogger/screencasts/vokoscreen-2018-04-06_13-40-13.mkv -- 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/1760598 Title: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown Status in ubuntu-mate: Invalid Status in casper package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-mate-welcome package in Ubuntu: Invalid Bug description: ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs to be cached for display of the shutdown message. We really should be using shutdown initramfs on the livecd -- Tested in Virtualbox VM. Ubuntu MATE works after force-reboot, but after I click on "restart now" after completing the installation, the screen shows me this: req_error: I/O error, dev sr0, sector 1488792 And the above message loops a couple times, and wont turn off the computer to restart. No error happens after force reboot, and the OS boots properly, but I'm curious as to what's causing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1760598/+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 1612669] Re: wrong PPA series used if system name not Ubuntu
Works as expected. 16:56:54 /etc/apt/sources.list.d $ sudo add-apt-repository ppa:alexlarsson/flatpak Linux application sandboxing and distribution framework (formerly xdg-app) More info: https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak Press [ENTER] to continue or ctrl-c to cancel adding it gpg: keyring `/tmp/tmpcsb45r2b/secring.gpg' created gpg: keyring `/tmp/tmpcsb45r2b/pubring.gpg' created gpg: requesting key FA577F07 from hkp server keyserver.ubuntu.com gpg: /tmp/tmpcsb45r2b/trustdb.gpg: trustdb created gpg: key FA577F07: public key "Launchpad PPA for Alexander Larsson" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 16:56:58 /etc/apt/sources.list.d $ cat alexlarsson-ubuntu-flatpak-xenial.list deb http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu xenial main # deb-src http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu xenial main 16:57:21 /etc/apt/sources.list.d $ sudo add-apt-repository -r ppa:alexlarsson/flatpak Linux application sandboxing and distribution framework (formerly xdg-app) More info: https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak Press [ENTER] to continue or ctrl-c to cancel removing it 16:57:26 /etc/apt/sources.list.d $ file alexlarsson-ubuntu-flatpak-xenial.list alexlarsson-ubuntu-flatpak-xenial.list: empty ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1612669 Title: wrong PPA series used if system name not Ubuntu Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: In Progress Status in software-properties source package in Yakkety: Fix Released Bug description: If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt- repositories will use the latest series of the PPA even if the DISTRIB_CODENAME would match with what is available in the PPA. # Test Case - change lsb-release to say DISTRIB_ID=yolo - copy /usr/share/python-apt/templates/Ubuntu.info to /usr/share/python-apt/templates/yolo.info - sudo add-apt-repository ppa:graphics-drivers/ppa - should add xenial to sources.list.d # Regression potential The current behavior of using the latest series is last ditch effort at come up with anything valid. The proposed change simply extends the acceptable deviation from 100 match. # Other info Change has been used in production in KDE neon for months now. No side effects observed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1612669/+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 1612669] Re: wrong PPA series used if system name not Ubuntu
Uploading software-properties_0.96.20.4_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1612669 Title: wrong PPA series used if system name not Ubuntu Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: In Progress Status in software-properties source package in Yakkety: Fix Released Bug description: If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt- repositories will use the latest series of the PPA even if the DISTRIB_CODENAME would match with what is available in the PPA. # Test Case - change lsb-release to say DISTRIB_ID=yolo - copy /usr/share/python-apt/templates/Ubuntu.info to /usr/share/python-apt/templates/yolo.info - sudo add-apt-repository ppa:graphics-drivers/ppa - should add xenial to sources.list.d # Regression potential The current behavior of using the latest series is last ditch effort at come up with anything valid. The proposed change simply extends the acceptable deviation from 100 match. # Other info Change has been used in production in KDE neon for months now. No side effects observed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1612669/+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 1612669] [NEW] wrong PPA series used if system name not Ubuntu
Public bug reported: If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt- repositories will use the latest series of the PPA even if the DISTRIB_CODENAME would match with what is available in the PPA. # Test Case - change lsb-release to say DISTRIB_ID=yolo - copy /usr/share/python-apt/templates/Ubuntu.info to /usr/share/python-apt/templates/yolo.info - sudo add-apt-repository ppa:graphics-drivers/ppa - should add xenial to sources.list.d # Regression potential The current behavior of using the latest series is last ditch effort at come up with anything valid. The proposed change simply extends the acceptable deviation from 100 match. # Other info Change has been used in production in KDE neon for months now. No side effects observed. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Affects: software-properties (Ubuntu Yakkety) Importance: Undecided Status: Fix Released ** Also affects: software-properties (Ubuntu Yakkety) Importance: Undecided Status: In Progress ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Xenial) Status: New => In Progress ** Changed in: software-properties (Ubuntu Yakkety) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1612669 Title: wrong PPA series used if system name not Ubuntu Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: In Progress Status in software-properties source package in Yakkety: Fix Released Bug description: If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt- repositories will use the latest series of the PPA even if the DISTRIB_CODENAME would match with what is available in the PPA. # Test Case - change lsb-release to say DISTRIB_ID=yolo - copy /usr/share/python-apt/templates/Ubuntu.info to /usr/share/python-apt/templates/yolo.info - sudo add-apt-repository ppa:graphics-drivers/ppa - should add xenial to sources.list.d # Regression potential The current behavior of using the latest series is last ditch effort at come up with anything valid. The proposed change simply extends the acceptable deviation from 100 match. # Other info Change has been used in production in KDE neon for months now. No side effects observed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1612669/+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 1612669] Re: wrong PPA series used if system name not Ubuntu
fixed in yakkety as per https://launchpad.net/ubuntu/+source/software- properties/0.96.24.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1612669 Title: wrong PPA series used if system name not Ubuntu Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: In Progress Status in software-properties source package in Yakkety: Fix Released Bug description: If the DISTRIB_ID in /etc/lsb-release is not 'ubuntu' add-apt- repositories will use the latest series of the PPA even if the DISTRIB_CODENAME would match with what is available in the PPA. # Test Case - change lsb-release to say DISTRIB_ID=yolo - copy /usr/share/python-apt/templates/Ubuntu.info to /usr/share/python-apt/templates/yolo.info - sudo add-apt-repository ppa:graphics-drivers/ppa - should add xenial to sources.list.d # Regression potential The current behavior of using the latest series is last ditch effort at come up with anything valid. The proposed change simply extends the acceptable deviation from 100 match. # Other info Change has been used in production in KDE neon for months now. No side effects observed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1612669/+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 1450137] Re: Qt5 applications crash when switching screens
Tried it, doesn't fix plasmashell exploding (not in the particular test case presented anyway). A bit of research suggests that this type of issue has multiple causes and is in fact only fixed by a combination of multiple commits (see the code review tabs on the bug reports below). The last bug in particular seems to carry the majority of relevant patches. https://bugreports.qt.io/browse/QTBUG-32973 https://bugreports.qt.io/browse/QTBUG-32681 https://bugreports.qt.io/browse/QTBUG-42985 I am not sure how to proceed on this. The additional patches seem to only affect qxcb such that they could only regress !phone apps (e.g. kubuntu-desktop). They are however numerous making this more work and more likely to cause regressions in other parts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1450137 Title: Qt5 applications crash when switching screens Status in qtdeclarative-opensource-src package in Ubuntu: Incomplete Status in qtdeclarative-opensource-src source package in Vivid: Confirmed Status in qtdeclarative-opensource-src source package in Wily: Incomplete Bug description: # Impact When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. # Test Case * Have two screens. One plugged-in one not * Run plasma 5 * Plug-in second screen and wait 10 seconds * Unplug and wait 10 seconds * Plug-in and wait 10 seconds * Unplug and wait 10 seconds * ... # Regression Potential Worst case scenario an application using qquickscreen would slow down because of erroneous screen change singals being emitted too often per second. This would however only reveal a lower level issue in the foundations that ultimately needs to be fixed anyway. # Other Info The upstream code review [1] explains the issue and solution pretty well. https://codereview.qt-project.org/#/c/00/ - original report --- When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. This makes my laptop unusable, since I do that very frequently. The problem has already been described here: https://bugs.kde.org/show_bug.cgi?id=341497 Apparently it is fixed in Qt 5.5 I am running Kubuntu 15.04 64bit and libqt5gui5 5.4.1+dfsg-2ubuntu4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137/+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 1450137] Re: Qt5 applications crash when switching screens
** No longer affects: plasma-workspace (Ubuntu) ** No longer affects: kwin (Ubuntu) ** Package changed: qtbase-opensource-src (Ubuntu) = qtdeclarative- opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1450137 Title: Qt5 applications crash when switching screens Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Status in qtdeclarative-opensource-src source package in Vivid: Confirmed Bug description: When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. This makes my laptop unusable, since I do that very frequently. The problem has already been described here: https://bugs.kde.org/show_bug.cgi?id=341497 Apparently it is fixed in Qt 5.5 I am running Kubuntu 15.04 64bit and libqt5gui5 5.4.1+dfsg-2ubuntu4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137/+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 1450137] Re: Qt5 applications crash when switching screens
** Description changed: + # Impact + When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. + + # Test Case + * Have two screens. One plugged-in one not + * Run plasma 5 + * Plug-in second screen and wait 10 seconds + * Unplug and wait 10 seconds + * Plug-in and wait 10 seconds + * Unplug and wait 10 seconds + * ... + + # Regression Potential + Worst case scenario an application using qquickscreen would slow down because of erroneous screen change singals being emitted too often per second. This would however only reveal a lower level issue in the foundations that ultimately needs to be fixed anyway. + + # Other Info + The upstream code review [1] explains the issue and solution pretty well. + + https://codereview.qt-project.org/#/c/00/ + + + - original report --- + When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. This makes my laptop unusable, since I do that very frequently. The problem has already been described here: https://bugs.kde.org/show_bug.cgi?id=341497 Apparently it is fixed in Qt 5.5 I am running Kubuntu 15.04 64bit and libqt5gui5 5.4.1+dfsg-2ubuntu4. ** Also affects: qtdeclarative-opensource-src (Ubuntu Wily) Importance: Medium Assignee: Timo Jyrinki (timo-jyrinki) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1450137 Title: Qt5 applications crash when switching screens Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Status in qtdeclarative-opensource-src source package in Vivid: Confirmed Status in qtdeclarative-opensource-src source package in Wily: Confirmed Bug description: # Impact When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. # Test Case * Have two screens. One plugged-in one not * Run plasma 5 * Plug-in second screen and wait 10 seconds * Unplug and wait 10 seconds * Plug-in and wait 10 seconds * Unplug and wait 10 seconds * ... # Regression Potential Worst case scenario an application using qquickscreen would slow down because of erroneous screen change singals being emitted too often per second. This would however only reveal a lower level issue in the foundations that ultimately needs to be fixed anyway. # Other Info The upstream code review [1] explains the issue and solution pretty well. https://codereview.qt-project.org/#/c/00/ - original report --- When switching screens (e. g. when putting the laptop onto the docking station the notebook screen is turned off and the external one is turned on) Qt5 applications (including plasmashell) quite often crash. This makes my laptop unusable, since I do that very frequently. The problem has already been described here: https://bugs.kde.org/show_bug.cgi?id=341497 Apparently it is fixed in Qt 5.5 I am running Kubuntu 15.04 64bit and libqt5gui5 5.4.1+dfsg-2ubuntu4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137/+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 1436328] [NEW] FFe apport-kde qt5 port
Public bug reported: https://code.launchpad.net/~kubuntu-packagers/apport/qt5/+merge/254082 integrating the qt5 port would allow kubuntu to attempt dropping python- kde4 from the ISO reducing the oversizing quite a bit test by Jonathan Riddell and me and works very well. functionally nothing changed as far as the UI is concerned and under the hood all the happened was an almost straight qt4-qt5 port along with replacing now obsolete kde dependencies with their qt5 counterpart ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1436328 Title: FFe apport-kde qt5 port Status in apport package in Ubuntu: New Bug description: https://code.launchpad.net/~kubuntu-packagers/apport/qt5/+merge/254082 integrating the qt5 port would allow kubuntu to attempt dropping python-kde4 from the ISO reducing the oversizing quite a bit test by Jonathan Riddell and me and works very well. functionally nothing changed as far as the UI is concerned and under the hood all the happened was an almost straight qt4-qt5 port along with replacing now obsolete kde dependencies with their qt5 counterpart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1436328/+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 1424957] Re: Fix crash in quassel when hovering links
*** This bug is a duplicate of bug 1424256 *** https://bugs.launchpad.net/bugs/1424256 ** This bug has been marked a duplicate of bug 1424256 quassel crashes on clicking a link posted in chat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1424957 Title: Fix crash in quassel when hovering links Status in qtbase-opensource-src package in Ubuntu: New Bug description: https://codereview.qt-project.org/#/c/106409/ fixes crashes in quassel when hovering links Patch is accepted upstream and will be part of Qt 5.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1424957/+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 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc
patch attached selectively disabling pch on amd64 and powerpc ** Patch added: disablepch.patch https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1395661/+attachment/4282005/+files/disablepch.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1395661 Title: Qt Webkit fails to build against Qt 5.4.0 on amd64 and powerpc Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: There's a problem with Qt WebKit (5.4.0 beta) failing to build against Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157 /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta- 0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz and on powerpc: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-005/+build/6649444/+files /buildlog_ubuntu-vivid-powerpc.qtwebkit-opensource- src_5.4.0-0ubuntu1%7Evivid1%7Etest2_FAILEDTOBUILD.txt.gz It seems to be related to pre-compiled headers. Qttools requires qtwebkit for the documentation. In the test PPA I've disabled qttools' qtwebkit requirement in order to have more amd64 builds done in general. More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1395661/+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 1370170] Re: knetworkmanager is starting with --no-hosts
** Package changed: knetworkmanager (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1370170 Title: knetworkmanager is starting with --no-hosts Status in “network-manager” package in Ubuntu: New Bug description: Distribution Kubuntu 12.04.5 knetworkmanager 0.9.4.0 After years I gave Networkmanager again a chance and kicked it out again immediately. Why is it starting dnsmasq with --no-hosts? I found nothing to disable this misbeave. I can't see any reason for doing this. It sucks only when I can not add names to /etc/hosts. Crutches like a wrapper script filtering out --host are not a really acceptable solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370170/+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 1369220] Re: lightdm: PAM adding faulty module: pam_kwallet.so
You'd get the same message if gnome-keyring wasn't installed. From what I understand this is really more of a PAM thing really, as PAM decides to be verbose when optional modules are not found (which IMHO makes a lot of sense). ** Package changed: pam-kwallet (Ubuntu) = pam (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1369220 Title: lightdm: PAM adding faulty module: pam_kwallet.so Status in “pam” package in Ubuntu: New Bug description: Latest /var/log/auth.log, on that fresh stock installation: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user oem ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 14 09:16:06 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1369220/+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
