[Touch-packages] [Bug 1361610] Re: libPCRE3 8.31 regex matching is not working
Arne, I compiled your code, got no warnings and got a different output!
Poco 0x01030600 on Linux 4.2.0-35-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? no
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes
System info
linux-vdso.so.1 => (0x7ffc9efc4000)
libboost_regex.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_regex.so.1.54.0 (0x7f87ad124000)
libPocoFoundation.so.9 => /usr/lib/libPocoFoundation.so.9
(0x7f87acdd8000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f87acb99000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f87ac895000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f87ac67f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f87ac2b9000)
libicuuc.so.52 => /usr/lib/x86_64-linux-gnu/libicuuc.so.52
(0x7f87abf4)
libicui18n.so.52 => /usr/lib/x86_64-linux-gnu/libicui18n.so.52
(0x7f87abb39000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f87ab91a000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f87ab701000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f87ab4fd000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f87ab2f4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f87aafee000)
/lib64/ld-linux-x86-64.so.2 (0x5582e37fc000)
libicudata.so.52 => /usr/lib/x86_64-linux-gnu/libicudata.so.52
(0x7f87a978)
inux ws004 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361610
Title:
libPCRE3 8.31 regex matching is not working
Status in pcre3 package in Ubuntu:
Invalid
Status in poco package in Ubuntu:
Confirmed
Bug description:
It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
handle regex matching alright. This also affects the libPocoFoundation
RegularExpression classes.
I attached a proof-of-concept which tests a good and bad heystack
string to a regex pattern with Poco, Boost and PCRE. I tested it on
two different machines with the following output:
Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
i686 i686 i686 GNU/Linux
Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT
Ubuntu 12.04.3 LTS 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.12 2011-01-15
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no --> OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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 1585020] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1585020 Title: Bluetooth not work Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: My bluetooth not work, before update incremental of ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 1588 F pulseaudio /dev/snd/controlC1: guilherme 1588 F pulseaudio CurrentDesktop: Unity Date: Mon May 23 23:46:56 2016 HibernationDevice: RESUME=UUID=a6865d25-3156-437d-aacf-017df3a88e6b InstallationDate: Installed on 2016-05-14 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Sony Corporation SVE14125CBB ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=2db3f6c7-ed97-44fd-8953-a7fb072c28a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0180D5:bd03/19/2013:svnSonyCorporation:pnSVE14125CBB:pvrC800D43W:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVE14125CBB dmi.product.version: C800D43W dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1585020/+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 1585020] Re: Bluetooth not work
Note the following line from your logs: Mai 23 23:43:58 username bluetoothd[2675]: Not enough free handles to register service I'm just guessing here but can you check the output of: sudo lsof -p `pidof bluetoothd` | wc -l Thanks ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1585020 Title: Bluetooth not work Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: My bluetooth not work, before update incremental of ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 1588 F pulseaudio /dev/snd/controlC1: guilherme 1588 F pulseaudio CurrentDesktop: Unity Date: Mon May 23 23:46:56 2016 HibernationDevice: RESUME=UUID=a6865d25-3156-437d-aacf-017df3a88e6b InstallationDate: Installed on 2016-05-14 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Sony Corporation SVE14125CBB ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=2db3f6c7-ed97-44fd-8953-a7fb072c28a1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0180D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0180D5:bd03/19/2013:svnSonyCorporation:pnSVE14125CBB:pvrC800D43W:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVE14125CBB dmi.product.version: C800D43W dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1585020/+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 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.
This issue seems to be no longer present on my system in Ubuntu 16.04. Wifi and VPN connect automatically without problems. -- 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/1323594 Title: vpn auto-connect works, but doesn't connect automatically when network is available. Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having is that with a connection set to auto-connect to a PPTP-vpn, it does not auto-connect when (wireless)-network becomes available. Syslog returns this error: [1401130450.367538] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. However it does connect when when connecting to the particular connection manually. e.g. I select the wireless network in the network-manager. This bug seems related to bugs: #280571 #1297849 #1247682 #1298047 The difference between my situation and the others is that vpn- autoconnect does work, it just doesn't work automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323594/+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 1361610] Re: libPCRE3 8.31 regex matching is not working
Additional info; when I change the linking order of pcre and poco I got
a different output:
$ g++ regex.cc -lPocoFoundation -lpcre
$ ./a.out
Poco 0x01030600 on Linux 4.2.0-35-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? no
Poco match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes
$ g++ regex.cc -lpcre -lPocoFoundation
$ ./a.out
Poco 0x01030600 on Linux 4.2.0-35-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes
Poco match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no
Our system uses heavily Poco's StringTokenizer and Regex classes which
are not working correctly on 14.04 and I'm most interested in a solution
to get it back working on 14.04 :)
I'm not familiar with LD_PRELOAD and the also do not fully understand
replies like 'Yoshiki Kanemoto (yocchiman) wrote on 2015-05-01' so if
anyone could tell we what the best approach here would be I would very
greatfull
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361610
Title:
libPCRE3 8.31 regex matching is not working
Status in pcre3 package in Ubuntu:
Invalid
Status in poco package in Ubuntu:
Confirmed
Bug description:
It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
handle regex matching alright. This also affects the libPocoFoundation
RegularExpression classes.
I attached a proof-of-concept which tests a good and bad heystack
string to a regex pattern with Poco, Boost and PCRE. I tested it on
two different machines with the following output:
Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
i686 i686 i686 GNU/Linux
Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT
Ubuntu 12.04.3 LTS 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.12 2011-01-15
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no --> OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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 1584945] Re: after reset password in /etc/passwd and set a new one, hash appears in /etc/passwd
A co-worker has reminded me that the 'x' in the passwd file is how the shadow suite annotates that the password should be stored in the shadow file: password field is blank. If the password field is a lower-case “x”, then the encrypted password is actually stored in the shadow(5) file instead; there must be a corresponding line in the /etc/shadow file, or else the user account is invalid. If the password field is any other (from passwd(5)) Once the 'x' was removed, that was the indicator that the password should be stored in the passwd file instead of the shadow file. So this is behaving as expected. Thanks ** Changed in: base-passwd (Ubuntu) Status: New => Invalid ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1584945 Title: after reset password in /etc/passwd and set a new one, hash appears in /etc/passwd Status in base-passwd package in Ubuntu: Invalid Bug description: After resetting a password in /etc/passwd (and /etc/shadow) and setting a new one, its hash appears in /etc/passwd. I forgot my pass :( and launched liveUSB with Ubuntu 16.04. 1st time I just used vi to edit /etc/passwd and remove "x" char in 2nd column. Reboot and I can change (maybe set) pass the usual way "passwd" etc. But password's hash appears in /etc/passwd. So strange. 2nd time I used "vipw" and "vipw -s" to clean the 2nd column. Reboot. And I can set NEW password. Password's hash appears in passwd and does not appear in shadow. I use Ubuntu 16.04 with latest update. anonym@ubu:~$ tail -1 /etc/passwd anonym:$6$IM9SWBps$DLKVpwPdlVLPh7kbGZSYxd7w9EpPNram4E.wHJ37evdJLbDWLnQwmELypgAjQppZul2LknTrSzzcxmZ1f8bAe1:1000:1000:ANONYMVS:/home/anonym:/bin/bash anonym@ubu:~$ sudo tail -1 /etc/shadow [sudo] пароль для anonym: anonym::16917:0:9:7::: anonym@ubu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" anonym@ubu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1584945/+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 1585084] [NEW] Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)
Public bug reported: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1585084 Title: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner) Status in pulseaudio package in Ubuntu: New Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1:
[Touch-packages] [Bug 1407921] Re: Indicator should give feedback when location-service is in use by apps
** Changed in: indicator-location (Ubuntu) Assignee: Bartosz Kosiorek (gang65) => Marcus Tomlinson (marcustomlinson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1407921 Title: Indicator should give feedback when location-service is in use by apps Status in Canonical System Image: In Progress Status in Indicator Location: New Status in Ubuntu theme: In Progress Status in Ubuntu UX: Triaged Status in indicator-location package in Ubuntu: In Progress Bug description: The only information the location indicator icon conveys currently is whether location detection is enabled at all, when more data could be interesting. Especially acquiring a GPS lock is often interesting, as this greatly impacts the location accuracy. Maybe the location icon should be dimmed when nothing is using it and blink when GPS lock is being acquired, bright when the lock is fine? The current spec is @ https://wiki.ubuntu.com/Location == Bug revision by charlesk 2016-01-24: The Location spec has been revised in this regard. The new text reads: > The indicator should appear in the status bar > whenever an app has accessed your location in > the past five minutes. It should list all apps > that have accessed your location in the past > five minutes, most recent first. Choosing any > app should switch to that app, so that you may > control whichever functions in that app are > accessing location. “Location Settings…” should > navigate to the “Location” screen of System > Settings. This bug is about the first part of that spec -- making the indicator visible when it's active -- and is (currently) blocked on location- service bug #1536774. The recent apps list component of the spec is covered in sibling bug #1235300. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407921/+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 1585087] [NEW] *.override files do not work for session jobs
Public bug reported: bamfdaemon ships a session job /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it should be possible to disable that with an override: $ cat /usr/share/upstart/sessions/bamfdaemon.override manual but this doesn't work, bamfdaemon is still started. I also tried to put "start on disabled" into the *.override file, no effect either. (Background: I'm trying to migrate jobs to systemd units one by one, thus for every systemd user unit that I add I need to disable the corresponding upstart job). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: upstart 1.13.2-0ubuntu23 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 24 09:23:36 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist upstart.upstart-event-bridge.log: upstart-event-bridge stop/pre-start, process 2537 upstart-event-bridge stop/pre-start, process 3444 upstart-event-bridge stop/pre-start, process 4582 ** Affects: upstart (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 upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585087 Title: *.override files do not work for session jobs Status in upstart package in Ubuntu: New Bug description: bamfdaemon ships a session job /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it should be possible to disable that with an override: $ cat /usr/share/upstart/sessions/bamfdaemon.override manual but this doesn't work, bamfdaemon is still started. I also tried to put "start on disabled" into the *.override file, no effect either. (Background: I'm trying to migrate jobs to systemd units one by one, thus for every systemd user unit that I add I need to disable the corresponding upstart job). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: upstart 1.13.2-0ubuntu23 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 24 09:23:36 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist upstart.upstart-event-bridge.log: upstart-event-bridge stop/pre-start, process 2537 upstart-event-bridge stop/pre-start, process 3444 upstart-event-bridge stop/pre-start, process 4582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585087/+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 1585087] Re: *.override files do not work for session jobs
Placing the *.override file into /usr/share/upstart/xdg/ also does not help. This is the $XDG_CONFIG_DIRS/upstart/ item in the "User Session Mode" man page section. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585087 Title: *.override files do not work for session jobs Status in upstart package in Ubuntu: New Bug description: bamfdaemon ships a session job /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it should be possible to disable that with an override: $ cat /usr/share/upstart/sessions/bamfdaemon.override manual but this doesn't work, bamfdaemon is still started. I also tried to put "start on disabled" into the *.override file, no effect either. (Background: I'm trying to migrate jobs to systemd units one by one, thus for every systemd user unit that I add I need to disable the corresponding upstart job). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: upstart 1.13.2-0ubuntu23 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 24 09:23:36 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist upstart.upstart-event-bridge.log: upstart-event-bridge stop/pre-start, process 2537 upstart-event-bridge stop/pre-start, process 3444 upstart-event-bridge stop/pre-start, process 4582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585087/+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 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition
As recommended workaround i get this: gsettings set org.freedesktop.Tracker.Miner.Files crawling-interval -2 gsettings set org.freedesktop.Tracker.Miner.Files enable-monitors false tracker-control -r This will disable the constant indexing and cleanup the indexers database. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/911981 Title: tracker-store uses 100% cpu and fills all the disk space in home partition Status in tracker package in Ubuntu: Confirmed Bug description: I recently noticed that several tracker related programs were using 100% cpu on my system and in particular tracker-store filled up completely all the available disk space in my home partition. I rerun tracker-preferences to make sure that indexing would not proceed if less than 20% of free space is available, but it seems that tracker-store ignores it. After I noticed that I had left only 44Kb free on the home partition, I deleted the cache from another program and I noticed that tracker-store filled up again the disk space that I freed few minutes before. This is the content of my .cache/tracker/ directory: totale 772068 -rw-r--r-- 1 eclipse eclipse 3072 2011-06-26 22:56 contents.db -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt -rw-r--r-- 1 eclipse eclipse 3072 2010-12-05 21:29 email-contents.db -rw-r--r-- 1 eclipse eclipse 3072 2009-05-06 19:16 email-fulltext.db -rw-r--r-- 1 eclipse eclipse 2359292 2011-06-26 22:54 email-index.db -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db -rw-r--r-- 1 eclipse eclipse 17062912 2011-06-26 19:30 file-contents.db -rw-r--r-- 1 eclipse eclipse 15014912 2010-01-12 20:26 file-fulltext.db -rw-r--r-- 1 eclipse eclipse 75609207 2011-06-26 22:54 file-index.db -rw-r--r-- 1 eclipse eclipse 37027840 2011-06-26 19:31 file-meta.db -rw--- 1 eclipse eclipse 1180048 2009-05-05 22:57 file-update-index.db -rw-r--r-- 1 eclipse eclipse 28376064 2011-10-20 09:34 fulltext.db -rw-r--r-- 1 eclipse eclipse 1024 2012-01-04 21:24 meta.db -rw-r--r-- 1 eclipse eclipse 4653056 2012-01-04 21:26 meta.db-shm -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 miner-applications-locale.txt -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb and this is how much space I have left on my home partition after I KILLED the tracker-store process: /dev/sda8 31G 30G 418M 99% /home --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 DistroRelease: Ubuntu 11.10 Package: tracker 0.10.24-1build2 PackageArchitecture: i386 ProcEnviron: LANGUAGE=it_IT:it:en_GB:en PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago) UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser pulse-access sambashare src video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+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 1576711] Re: [xenial] Enable arm64 build
** Changed in: qtmir-gles (Ubuntu) Status: New => Fix Released ** No longer affects: qtmir-gles (Ubuntu) ** No longer affects: qtubuntu-gles (Ubuntu) ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: qtubuntu-camera (Ubuntu) Status: New => Fix Released ** Changed in: qtubuntu-camera (Ubuntu) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1576711 Title: [xenial] Enable arm64 build Status in aethercast: New Status in Canonical System Image: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu: New Status in libhybris package in Ubuntu: Fix Released Status in qtubuntu-camera package in Ubuntu: Fix Released Status in qtubuntu-media package in Ubuntu: Fix Committed Status in qtubuntu-sensors package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: In Progress Bug description: Tracking bug for touch packages without arm64 enabled on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/aethercast/+bug/1576711/+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 1585087] Re: *.override files do not work for session jobs
strace shows that upstart *does* read /usr/share/upstart/sessions/bamfdaemon.override successfully. Also, if I replace the override with exec true then "true" is being executed, and the job loops because the *.conf has "restart" (i. e. expected). This opens the hypothesis that the job is being started through something else than the "start on" condition. But it is not being referenced by any other *.conf file. And indeed, even if I drop the "start on" from bamfdaemon.conf it still gets started. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585087 Title: *.override files do not work for session jobs Status in upstart package in Ubuntu: Invalid Bug description: bamfdaemon ships a session job /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it should be possible to disable that with an override: $ cat /usr/share/upstart/sessions/bamfdaemon.override manual but this doesn't work, bamfdaemon is still started. I also tried to put "start on disabled" into the *.override file, no effect either. (Background: I'm trying to migrate jobs to systemd units one by one, thus for every systemd user unit that I add I need to disable the corresponding upstart job). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: upstart 1.13.2-0ubuntu23 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 24 09:23:36 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist upstart.upstart-event-bridge.log: upstart-event-bridge stop/pre-start, process 2537 upstart-event-bridge stop/pre-start, process 3444 upstart-event-bridge stop/pre-start, process 4582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585087/+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 1585087] Re: *.override files do not work for session jobs
Got it -- bamfdaemon also installs /usr/share/dbus-1/services/org.ayatana.bamf.service which calls bamfdaemon-dbus-runner which does if [ -n "$UPSTART_SESSION" ]; then /sbin/initctl start bamfdaemon else /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon fi That explains why its upstart job is D-Bus activated and the "start on" condition is redundant (and disabling it doesn't work). Adding "manual" to e. g. im-config.override does work as expected. ** Changed in: upstart (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1585087 Title: *.override files do not work for session jobs Status in upstart package in Ubuntu: Invalid Bug description: bamfdaemon ships a session job /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it should be possible to disable that with an override: $ cat /usr/share/upstart/sessions/bamfdaemon.override manual but this doesn't work, bamfdaemon is still started. I also tried to put "start on disabled" into the *.override file, no effect either. (Background: I'm trying to migrate jobs to systemd units one by one, thus for every systemd user unit that I add I need to disable the corresponding upstart job). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: upstart 1.13.2-0ubuntu23 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 24 09:23:36 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist upstart.upstart-event-bridge.log: upstart-event-bridge stop/pre-start, process 2537 upstart-event-bridge stop/pre-start, process 3444 upstart-event-bridge stop/pre-start, process 4582 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585087/+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 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.
** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- 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/1323594 Title: vpn auto-connect works, but doesn't connect automatically when network is available. Status in network-manager package in Ubuntu: Fix Released Bug description: I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having is that with a connection set to auto-connect to a PPTP-vpn, it does not auto-connect when (wireless)-network becomes available. Syslog returns this error: [1401130450.367538] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. However it does connect when when connecting to the particular connection manually. e.g. I select the wireless network in the network-manager. This bug seems related to bugs: #280571 #1297849 #1247682 #1298047 The difference between my situation and the others is that vpn- autoconnect does work, it just doesn't work automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323594/+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 1584970] Re: Ubuntu tries to set up my USB wireless device on a wired connection
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- 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/1584970 Title: Ubuntu tries to set up my USB wireless device on a wired connection Status in network-manager package in Ubuntu: New Bug description: When I start up from a Ubuntu 16.04 Live CD, I do not get a wireless network connection, instead it seems to see my USB device (a Belkin F5D8053 N Wireless USB Adapter) as a "wired connection". If I do 'service network-manager restart', or unplug and replug the device, then it sets it up with the rt2800usb driver, gives it a wireless connection, and allows me to connect to wifi routers as normal. A potentially similar issue has been reported with a GB-WB867D-I card at http://askubuntu.com/questions/758422/ubuntu-16-04-seeing-my- wireless-card-as-wired ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 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 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Mon May 23 22:02:27 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: 10.42.0.0/24 dev enp0s25 proto kernel scope link src 10.42.0.1 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 d553ccd9-63fb-494a-8ec6-59adc51a67f6 802-3-ethernet 1464040759 Mon 23 May 2016 09:59:19 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/3 Wired connection 2 b35063c3-365d-4287-85b2-882e449f4d13 802-3-ethernet 1464040460 Mon 23 May 2016 09:54:20 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 d553ccd9-63fb-494a-8ec6-59adc51a67f6 /org/freedesktop/NetworkManager/ActiveConnection/3 wlx002275911486 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- 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/ubuntu/+source/network-manager/+bug/1584970/+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 1585094] [NEW] Random stuck keys on Lenovo Yoga 13
Public bug reported: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 24 08:57:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial xserver-xorg-input-evdev -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: New Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec.
[Touch-packages] [Bug 1522694] Re: Mouse acceleration gets faster (too fast) during and after dragging the Unity launcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1522694 Title: Mouse acceleration gets faster (too fast) during and after dragging the Unity launcher Status in Nux: New Status in Unity: New Status in nux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Mouse acceleration gets faster after dragging on Unity launcher (!) No idea why, but the mouse cursor moves too fast only during and shortly after dragging the Unity launcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20151102-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Dec 4 14:44:27 2015 InstallationDate: Installed on 2015-12-03 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1522694/+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 1522694] Re: Mouse acceleration gets faster (too fast) during and after dragging the Unity launcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1522694 Title: Mouse acceleration gets faster (too fast) during and after dragging the Unity launcher Status in Nux: New Status in Unity: New Status in nux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Mouse acceleration gets faster after dragging on Unity launcher (!) No idea why, but the mouse cursor moves too fast only during and shortly after dragging the Unity launcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20151102-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Dec 4 14:44:27 2015 InstallationDate: Installed on 2015-12-03 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1522694/+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 1585097] [NEW] webbrowser randomly crashes when downloading file
Public bug reported: Seems this only affects my Aquaris M10 - haven't experienced anything like that on my E4.5. When clicking on download-button webbrowser crashes quite often (like 1 in 3 times). Simply immediately closes. When reopening browser, I can see the download file is listed in Download-manager with 0% (and won't do anything). When retry downloading the same file, everything works - no crash until now. I've added crashed-log. Please ask if you need any more information. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: crash download m10 webbrowser ** Attachment added: "_usr_bin_webbrowser-app.32011.crash" https://bugs.launchpad.net/bugs/1585097/+attachment/4669213/+files/_usr_bin_webbrowser-app.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1585097 Title: webbrowser randomly crashes when downloading file Status in webbrowser-app package in Ubuntu: New Bug description: Seems this only affects my Aquaris M10 - haven't experienced anything like that on my E4.5. When clicking on download-button webbrowser crashes quite often (like 1 in 3 times). Simply immediately closes. When reopening browser, I can see the download file is listed in Download-manager with 0% (and won't do anything). When retry downloading the same file, everything works - no crash until now. I've added crashed-log. Please ask if you need any more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1585097/+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 1580577] Re: python2.7 crashes with SegFault when running Zope
On 17.05.2016 14:14, Ján Jockusch wrote:
> In the mean time, I have attempted to narrow the debian/patches/* files
> down so I can find which patch produces the problem.
it should be enough to disable the hg-updates patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when running Zope
Status in python2.7 package in Ubuntu:
Confirmed
Bug description:
Source package / Package:
python2.7_2.7.11-7ubuntu1
System:
Description: Ubuntu 16.04 LTS
Release: 16.04
This is a bug report originating from the findings documented in
https://github.com/zopefoundation/Zope/issues/56
The expected behaviour is this:
- Upon installing Zope2 in a virtualenv a default instance should work with
no issues.
What happens instead:
- The freshly installed Zope instance causes Python to SegFault after only a
few requests.
But Python should never SegFault.
The following program produces the error:
#!/bin/bash
set -e
# Call this testing script with an argument "setup" for the first time
# to build the testing case
#
# After that, the script only performs the test as described below.
#
# Requirements: apt-get install virtualenv python2.7-dbg
#
# This script needs internet access when running.
# The python version to test:
python=/usr/bin/python2.7-dbg
# This part builds the testing environment
if [ "$1" == "setup" ] ; then
# Virtual environment with the chosen python
virtualenv --python ${python} --no-site-packages zope-virtualenv
cd zope-virtualenv
# Basic Zope installation
./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
# Simplest possible Zope instance
./bin/mkzopeinstance --dir instance --user admin:admin
cd ..
fi
# THE TEST
# Run Zope instance in the background
zope-virtualenv/instance/bin/runzope &
# Give Zope some time to start up
sleep 3
# Call a few management URLs, nothing too fancy...
urls="
http://admin:admin@localhost:8080/Control_Panel/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
http://admin:admin@localhost:8080/manage
http://admin:admin@localhost:8080/acl_users/manage_main
http://admin:admin@localhost:8080/acl_users/manage_access
"
while true ; do
for url in ${urls} ; do
echo ${url}
curl -s $url -o /dev/null
done
done
# This test fails after about 10 requests with
# Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has
negative ref count -1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+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 1572943] Re: Token::isValid() returns true on invalid tokens
This bug was fixed in the package ubuntuone-credentials - 15.11+16.04.20160427 --- ubuntuone-credentials (15.11+16.04.20160427) xenial; urgency=medium [ Alberto Mardegan ] * Be more explicit about which headers are installed. Move the symbol export map to LINK_FLAGS on the target. * Complete the UbuntuOne authentication plugin * Make Token::isValid() return false on tokens created out of empty strings. (LP: #1572943) -- Rodney Dawes Wed, 27 Apr 2016 20:33:37 + ** Changed in: ubuntuone-credentials (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1572943 Title: Token::isValid() returns true on invalid tokens Status in Canonical System Image: Fix Committed Status in ubuntuone-credentials package in Ubuntu: Fix Released Bug description: Token token(QString(), QString(), QString(), QString()); token.isValid(); // prints true This is something which can obviously being worked around in the client code, but I think it would be nicer if Token would consider empty strings as missing data. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572943/+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 1167281] Re: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1167281 Title: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile Status in base-files package in Ubuntu: Confirmed Status in xen-3.1 package in Ubuntu: Invalid Bug description: Upstreaming from https://bugzilla.wikimedia.org/show_bug.cgi?id=46913 : This used to happen at the start of every Puppet run, because of the line "mesg n" in /root/.profile. The shell provisioner is actually invoked to fix the problem by changing it to "tty -s && mesg n". This fixes the problem for every subsequent run. Still, I'd like to prevent it from appearing even once. Ubuntu could fix this by adding a check to .profile. Also see https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/201884 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1167281/+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 1585094] Re: Random stuck keys on Lenovo Yoga 13
The rundom stuck key effect has been seen not only for arrow keys though. It happens also for ALT, CTRL and probably SHIFT and SUPPER -- it is not easy to recognize what special/control key gets stuck. The random stuck key effect never has been seen with alphabet and numeric keys though. Since I use Neo2 keyboard layout, the conventional arrow keys could be ignored and the Right AltGr+S,E,D,F could be used instead. Still, even if the AltGr combination is used the random stuck key effect happens with the same occasional rate. -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: New Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 24 08:57:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 864 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+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.
[Touch-packages] [Bug 1569653] Re: NetworkManager plugin for 'team' unavailable
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1569653] Re: NetworkManager plugin for 'team' unavailable
you need an extra plugin for that one, do you have it installed?
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1576247] Re: network manager does not find *.p12 files in Xenial
*** This bug is a duplicate of bug 1575614 *** https://bugs.launchpad.net/bugs/1575614 ** This bug has been marked a duplicate of bug 1575614 Can't select secret key for TLS auth on wired or wifi connection -- 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/1576247 Title: network manager does not find *.p12 files in Xenial Status in network-manager package in Ubuntu: Confirmed Bug description: I opened the network manager using Edit Connections from the pull down menu of the system tray network icon . Creating a new wifi connection, I chose WPA&WPA Enterprise in the wifi-security tab. Security: WPA & WPA2 Enterprise Authentication: TLS Identify: xxx User certificate: none CA certificate: xxx (I could chose from file manager) When opening the browser for the private key and navigating to the right directory, it does not show any *perm, *.p12 or *.der files although they are present in this directory Looks like this is a UI bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576247/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
I assumed it was because I had both synaptic and Ubuntu Software center open At the same time ?? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Ambasa: New Status in Debconf: New Status in aptdaemon package in Ubuntu: Confirmed Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+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 1583114] Re: Dhcpdiscover loops on interval until network-manager restart
thanks ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- 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/1583114 Title: Dhcpdiscover loops on interval until network-manager restart Status in network-manager package in Ubuntu: Triaged Bug description: UBUNTU VERSION: Ubuntu desktop 16.04 64bit, system is up to date to latest KERNEL: Linux RooTBooK 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux DHCPDISCOVER keeps looping on intervals until i restart network-manager, the loops are not happening at every boot, but only sometimes at boot WIFI CHIPSET: product: BCM4313 802.11bgn Wireless Network Adapter WIFI DRIVER: driver=wl0 driverversion=6.30.223.248 (r487574) ip=192.168.1.3 the problem gets solved on network-manager restart and can be reproduced. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 18 12:37:55 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-25 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp7s0 proto static metric 600 169.254.0.0/16 dev wlp7s0 scope link metric 1000 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.3 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp7s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 belkin7 1 1042ceaf-e9a0-4db1-96dd-897213b0c61c /org/freedesktop/NetworkManager/ActiveConnection/0 enp6s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/ubuntu/+source/network-manager/+bug/1583114/+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 1584965] Re: [browser] scrolling uneven and queues up
** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: New Status in Oxide: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+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 1569653] Re: NetworkManager plugin for 'team' unavailable
Hi Sebastien,
I tried to apt search keywords about plugins and team, but in vain.
What is the package name of the team plugin?
Thanks,
Jim
2016-05-24 16:23 GMT+08:00 Sebastien Bacher :
> you need an extra plugin for that one, do you have it installed?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1569653
>
> Title:
> NetworkManager plugin for 'team' unavailable
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> Versions:
> OS: 16.04 amd64 daily build
> nmcli 1.0.4
> network-manager: 1.0.4-0ubuntu
>
> Symptom:
> while creating a team connection with nmcli/nmtui, actions can be done
> but failed while activating team connection because no 'team' plugin
> avaulable.
>
> Reproduce the issue:
> $ nmcli c a type team ifname team0 con-name team0 config
> '{"runner":{"name":"lacp"}}'
> $ for dev in eno1 eno2 eno3 eno4; do
> nmcli c a type team-slave ifname $dev con-name teamport-$dev
> master team0
> done
> $ nmcli c up team0
>
> Error: Connection activation failed: NetworkManager plugin for 'team'
> unavailable
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+subscriptions
>
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1584965] Re: [browser] scrolling uneven and queues up
I can easily observe the same kind of issue with slashdot.org on my krillin running rc-proposed: - browse to slashdot.org, wait for the main page to be loaded - tap on an article headline to open it - wait for the page to be fully loaded, tap the back button - flick the page once It seems that if I wait long enough after the main page has been loaded back (a few seconds), then the issue cannot be reproduced, so I’m guessing this is linked to loading/rendering not being fully complete by the time the flick gesture is delivered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: New Status in Oxide: New Status in webbrowser-app package in Ubuntu: New Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+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 1585097] Re: webbrowser randomly crashes when downloading file
Unfortunately the attached crash file doesn’t have a core dump. Can you reproduce the crash with any file to download on any site, or is it specific to a given site/file type? Could you maybe link to a page where such a link triggers a crash, so I can try to reproduce on my device? ** Changed in: webbrowser-app (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1585097 Title: webbrowser randomly crashes when downloading file Status in webbrowser-app package in Ubuntu: Incomplete Bug description: Seems this only affects my Aquaris M10 - haven't experienced anything like that on my E4.5. When clicking on download-button webbrowser crashes quite often (like 1 in 3 times). Simply immediately closes. When reopening browser, I can see the download file is listed in Download-manager with 0% (and won't do anything). When retry downloading the same file, everything works - no crash until now. I've added crashed-log. Please ask if you need any more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1585097/+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 1576247] Re: network manager does not find *.p12 files in Xenial
*** This bug is a duplicate of bug 1575614 *** https://bugs.launchpad.net/bugs/1575614 I am facing the same problem. I tried to drag the key file as James Hewitt (jammy) suggested. But now I am getting bug # 1339607 https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1339607 -- 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/1576247 Title: network manager does not find *.p12 files in Xenial Status in network-manager package in Ubuntu: Confirmed Bug description: I opened the network manager using Edit Connections from the pull down menu of the system tray network icon . Creating a new wifi connection, I chose WPA&WPA Enterprise in the wifi-security tab. Security: WPA & WPA2 Enterprise Authentication: TLS Identify: xxx User certificate: none CA certificate: xxx (I could chose from file manager) When opening the browser for the private key and navigating to the right directory, it does not show any *perm, *.p12 or *.der files although they are present in this directory Looks like this is a UI bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576247/+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 1573536] Re: Content of the re-authentication dialog window
** Changed in: ubuntu-ux Assignee: (unassigned) => Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1573536 Title: Content of the re-authentication dialog window Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UX: New Status in ubuntuone-credentials package in Ubuntu: New Bug description: The bug is about finding the right content to present to the user when an online service requests a re-authentication. This scenario happens with Online Accounts. The user has created an OA account in the system, for example an Ubuntu One account. The related OAuth token may expire after a while, or the user may change his/her password. At this stage, the online service will require the user to re-authenticate and re-enter his/her password. When that happens, OA will show a password prompt and we are looking for the right information level to present to the user. The minimum input required is the username/password pair that will be sent back to the online service. Additionally we could present the service icon and name, and a short paragraph explaining that this service requests an identity confirmation. Note: this re-authentication happens at the system level, as opposed to being limited to a particular application. An app may trigger this process because it sends a request to the online service with outdated credentials. But the implication is beyond that particular app, as the re-authentication will allow all authorized apps to continue using the online service in question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1573536/+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 1542002] Re: [browser] opening multiple tabs causing major system slowdown or crash
That’s most likely because the behaviour of the mechanism to unload background tabs when running low on memory has recently been tweaked (see bug #1576639). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1542002 Title: [browser] opening multiple tabs causing major system slowdown or crash Status in The Avila project: New Status in Canonical Pocket Desktop: New Status in webapps-sprint: Incomplete Status in webbrowser-app package in Ubuntu: Invalid Bug description: the default browser constantly seems to crash when set up as pocket desktop. For example when viewing this page: http://www.digitaltrends.com/mobile/bq-aquaris-m10-ubuntu-edition-tablet-news Also when using google docs, and even launch pad. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1542002/+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 1388743] Re: iOS 8.1 - Could not start com.apple.mobile.installation_proxy!
This bug was fixed in the package libimobiledevice - 1.2.0+dfsg-3~ubuntu1 --- libimobiledevice (1.2.0+dfsg-3~ubuntu1) yakkety; urgency=medium * debian/patches/git_gnutls_proxy.patch: - Fix installation_proxy when using GnuTLS instead of OpenSSL (lp: #1388743) * debian/patches/git_local_socket.patch: - [security fix] Make sure sockets only listen locally -- Sebastien Bacher Mon, 23 May 2016 12:48:38 +0200 ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed => Fix Released -- 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/1388743 Title: iOS 8.1 - Could not start com.apple.mobile.installation_proxy! Status in ideviceinstaller package in Ubuntu: Invalid Status in libimobiledevice package in Ubuntu: Fix Released Bug description: * Impact When running ideviceinstaller -l, I get the following error: Could not start com.apple.mobile.installation_proxy! * Test case connect an iOS >8 device and try to use ideviceinstaller * Regression potential It's fixing code that was not working before, should create any new issue Pairing works and I can mount the phone using iFuse. iPhone 4S, iOS 8.1 libimobiledevice is probably outdated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ideviceinstaller 1.0.1-0.2build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Nov 3 09:33:21 2014 InstallationDate: Installed on 2014-11-02 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: ideviceinstaller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ideviceinstaller/+bug/1388743/+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 1407921] Re: Indicator should give feedback when location-service is in use by apps
** Changed in: ubuntu-themes Status: In Progress => Confirmed ** Changed in: ubuntu-themes Assignee: Bartosz Kosiorek (gang65) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1407921 Title: Indicator should give feedback when location-service is in use by apps Status in Canonical System Image: In Progress Status in Indicator Location: New Status in Ubuntu theme: Confirmed Status in Ubuntu UX: Triaged Status in indicator-location package in Ubuntu: In Progress Bug description: The only information the location indicator icon conveys currently is whether location detection is enabled at all, when more data could be interesting. Especially acquiring a GPS lock is often interesting, as this greatly impacts the location accuracy. Maybe the location icon should be dimmed when nothing is using it and blink when GPS lock is being acquired, bright when the lock is fine? The current spec is @ https://wiki.ubuntu.com/Location == Bug revision by charlesk 2016-01-24: The Location spec has been revised in this regard. The new text reads: > The indicator should appear in the status bar > whenever an app has accessed your location in > the past five minutes. It should list all apps > that have accessed your location in the past > five minutes, most recent first. Choosing any > app should switch to that app, so that you may > control whichever functions in that app are > accessing location. “Location Settings…” should > navigate to the “Location” screen of System > Settings. This bug is about the first part of that spec -- making the indicator visible when it's active -- and is (currently) blocked on location- service bug #1536774. The recent apps list component of the spec is covered in sibling bug #1235300. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407921/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt apps
I confirm this bug at Ubuntu 16.04 and kdenlive app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1436405 Title: Duplicate menu (both unity and in-app) for Qt apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: Confirmed Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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 1575152] Re: [SRU] gstreamer 1.8.1
I've that version installed on my main system, playing different type of videos in totem works fine, rhythmbox deals with music and CDs as it should, cheese is displaying live videos of the webcam, missing codec triggers the plugins install as they should, sound settings are working as they shoulds ... looks good, marking as verified! ** 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 gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1575152 Title: [SRU] gstreamer 1.8.1 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: Fix Committed Status in gstreamer1.0 source package in Xenial: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 26 13:16:04 2016 InstallationDate: Installed on 2015-06-05 (325 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1575152/+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 1584314] Re: Please merge xkeyboard-config 2.17-1 (main) from Debian unstable
This bug was fixed in the package xkeyboard-config - 2.17-1ubuntu1
---
xkeyboard-config (2.17-1ubuntu1) yakkety; urgency=medium
* Merge with Debian (LP: #1584314), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
xkb-data-i18n to be used by console-setup.
- xkb-data.postinst.in: Remove the xkb cache to make sure it gets
regenerated.
xkeyboard-config (2.17-1) unstable; urgency=medium
* New upstream release
* Use https instead of git for Vcs-Git.
-- Gunnar Hjalmarsson Mon, 23 May 2016 20:04:00
+0200
** Changed in: xkeyboard-config (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1584314
Title:
Please merge xkeyboard-config 2.17-1 (main) from Debian unstable
Status in libx11 package in Ubuntu:
In Progress
Status in xkeyboard-config package in Ubuntu:
Fix Released
Bug description:
Hi
My name is Rodrigo with my team we develop the Togo-Africa Keyboard Layout in
the Linux Distribution.
We want to include this keyboard in the Ubuntu distribution.
I've uploaded a keyboard to XKB:
https://cgit.freedesktop.org/xkeyboard-config/commit/?id=53452c901fcab08a43705c9aa79a5ec5642cca08
https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=3129c757f9da8586ab8b8654a56c8f687cc9ef5c
Here is the Keyboard
##
diff --git a/rules/base.xml.in b/rules/base.xml.in
index f495c8d..5e91717 100644
--- a/rules/base.xml.in
+++ b/rules/base.xml.in
@@ -5680,6 +5680,16 @@
+tg
+<_shortDescription>fr-tg
+<_description>French (Togo)
+
+ fra
+
+
+
+
+
ke
<_shortDescription>sw
diff --git a/symbols/Makefile.am b/symbols/Makefile.am
index 77ec0ff..3226d41 100644
--- a/symbols/Makefile.am
+++ b/symbols/Makefile.am
@@ -29,7 +29,7 @@ pc ph pk pl pt \
ro rs ru \
se si sk sn \
sy th \
-terminate \
+terminate tg \
tj tm tr tw tz \
ua us uz vn \
za \
diff --git a/symbols/tg b/symbols/tg
new file mode 100644
index 000..f7b2cb3
--- /dev/null
+++ b/symbols/tg
@@ -0,0 +1,68 @@
+default partial alphanumeric_keys
+xkb_symbols "basic" {
+
+include "fr(azerty)"
+
+name[Group1]="French (Togo)";
+
+// French AZERTY-Keyboard layout including symbols for Togolese local
languages
+// Created 2015 by Globalbility Togo (www.globalbility.org)
+// Authors: Issaka Ouro-Wétchiré, Caroline Riefstahl, Mats Blakstad
+//
+// LAYOUT OVERVIEW
+//
+// | 1 3| 1 = Shift, 3 = AltGr + Shift(AltGr is the right side alt key)
+// | 2 4| 2 = normal, 4 = AltGr
+//
+// ___
+// || 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0 | ° | + | <-- |
+// | ² | & | é ~| " #| ' {| ( [| - || è `| _ \| ç ^| à @| ) ]| = }| |
+//
+// | |<- | A | Z Ʒ| E Ɛ| R Ɗ| T | Y Ƴ| U Ʊ| I Ɩ| O Ɔ| P | ¨ | $ €| , |
+// | ->| | a | z ʒ| e ɛ| r ɗ| t | y ƴ| u ʊ| i ɩ| o ɔ| p | ^ ̌| £ ¤| <-'
|
+// ===¬|
+// | | Q Ǝ| S | D Ɖ| F Ƒ| G Ɣ| H Ĥ | J | K | L | M Ŋ| % | µ |
|
+// | MAJ | q ǝ| s | d ɖ| f ƒ| g ɣ| h ɦ| j | k | l | m ɲ| ù `| * ́|
|
+//
+// | ^ | > | W | X | C | V Ʋ| B Ɓ| N Ŋ| ? | . | / | § | | |
+// | | | < | w | x | c | v ʋ| b ɓ| n ŋ| , ~| ; ¯| : | ! | | |
+//
+// | | | | | | | | |
+// | Ctrl | Super| Alt | SpaceNobreakspace | AltGr | Super|Menu | Ctrl |
+// ¯¯ ¯¯ ¯¯ ¯¯¯ ¯¯¯ ¯¯ ¯ ¯¯
+// Togolese local languages use 8 tones markers.
+// Acute ( ´ ), Grave ( ` ), Circumflex ( ˆ ), Caron ( ˇ ), Macron ( ¯
), Tilde ( ~ ), Tilde + Acute ( ̃́ ), Tilde + Grave ( ̃̀ )
+// All vowels can have tones except "y" (which is not vowel in Togolese
local languages)
+// Nasal consonants ("m" and "n") can have have high tones.
+
+ // Modifications of the basic French Azerty layout, adding
symbols for Togolese local languages
+
+ // Second row
+ key { [ z, Z, ezh,
EZH ] };// U0292 = ʒ (small), U01B7 = Ʒ (capital)
+override key { [ e, E, U025B,
U0190 ] };// Replqce Eurosi
[Touch-packages] [Bug 1579221] Re: Hotspot not working with NM 1.2
This bug was fixed in the package indicator-network -
0.7.1+16.04.20160511-0ubuntu1
---
indicator-network (0.7.1+16.04.20160511-0ubuntu1) xenial; urgency=medium
[ Pete Woods ]
* Fix limitations property (LP: #1547194)
* Remember hotspot UUID
* Store information about which device we are using in a member
variable
* Wait for hotspot device to be ready, not just present (LP: #1579221)
* Wait for hotspot to finish activating
[ Tony Espy ]
* hotspot: Don't create NM ipv4 settings with empty values. (LP:
#1579221)
-- Tony Espy Wed, 11 May 2016 16:57:39
+
** Changed in: indicator-network (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1579221
Title:
Hotspot not working with NM 1.2
Status in Canonical System Image:
Fix Committed
Status in indicator-network package in Ubuntu:
Fix Released
Bug description:
While testing network-manager 1.1.93-0ubuntu1~vivid1 we noticed that
hotspot no longer worked on arale or krillin ( it's not enabled on
mako ).
The first issue was that if no NM connection file yet existed for the
hotspot, indicator-network would fail creating one due to a DBus
error:
void nmofono::HotspotManager::Priv::addConnection() Adding new hotspot
connection
Failed to add connection: "ipv4.dns: can't set property of type 'au' from
value of type 'as'"
This was due to indicator-network using the following code to set this
setting:
ipv4[QStringLiteral("dns")] = QVariant(QStringList());
My guess is that NM's re-factoring of it's DBus code to use gdbus
instead of dbus-glib, resulting in NM being a bit more strict in it's
parameter checking.
Removing this, and the same for the 'addresses' and 'routes' settings allows
indicator-network to create hotspot connection files once again.
See the associated branch for the update.
If a connection file already exists, or one is created with the fix
from the merge proposal, then the current problem is that when 'Start'
is pressed, the UI displays a spinner which is never dismissed.
Testing has shown that the hotspot is actually activated, can be seen
from other devices and connected to.
Testing has also shown that it's possible to activate the hotspot
using nmcli directly, and the result is usable from other clients.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579221/+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 1547194] Re: cannot connect to limitationsUpdated signal
This bug was fixed in the package indicator-network - 0.7.1+16.04.20160511-0ubuntu1 --- indicator-network (0.7.1+16.04.20160511-0ubuntu1) xenial; urgency=medium [ Pete Woods ] * Fix limitations property (LP: #1547194) * Remember hotspot UUID * Store information about which device we are using in a member variable * Wait for hotspot device to be ready, not just present (LP: #1579221) * Wait for hotspot to finish activating [ Tony Espy ] * hotspot: Don't create NM ipv4 settings with empty values. (LP: #1579221) -- Tony Espy Wed, 11 May 2016 16:57:39 + ** Changed in: indicator-network (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1547194 Title: cannot connect to limitationsUpdated signal Status in indicator-network package in Ubuntu: Fix Released Bug description: In connectivity.h, the limitationsUpdated signal is declared as such: void limitationsUpdated(const QVector&); When I use this syntax to connect: connect(ns.data(),SIGNAL(limitationsUpdated(const QVector&)), this,SLOT(limitationsUpdated(const QVector&)); I get this error when building: tstconnectivity.h:21:43: error: ‘Limitations’ was not declared in this scope void limitationsUpdated(const QVector&); When I try: connect(ns.data(),SIGNAL(limitationsUpdated(const QVector&)), this,SLOT(limitationsUpdated(const QVector&)); It builds, but I get this error when running: 2016-02-18T17:52:55 (unknown:0) - QObject::connect: No such signal connectivityqt::Connectivity::limitationsUpdated(const QVector&) The signal should probably be declared: void limitationsUpdated(const QVector&); with connectivityqt::Connectivity:: just as the statusUpdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1547194/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
This bug was fixed in the package indicator-network - 0.7.1+16.04.20160511-0ubuntu1 --- indicator-network (0.7.1+16.04.20160511-0ubuntu1) xenial; urgency=medium [ Pete Woods ] * Fix limitations property (LP: #1547194) * Remember hotspot UUID * Store information about which device we are using in a member variable * Wait for hotspot device to be ready, not just present (LP: #1579221) * Wait for hotspot to finish activating [ Tony Espy ] * hotspot: Don't create NM ipv4 settings with empty values. (LP: #1579221) -- Tony Espy Wed, 11 May 2016 16:57:39 + ** Changed in: indicator-network (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1485522] Re: Volume obtained is 100% in multimedia sink for sounds from app
This bug was fixed in the package qtmultimedia-opensource-src -
5.5.1-4ubuntu3
---
qtmultimedia-opensource-src (5.5.1-4ubuntu3) xenial; urgency=medium
* debian/patches/PulseAudio-change-the-way-volume-is-applied.patch:
- Backport from 5.6, change Pulseaudio volume control (LP: #1485522)
-- Timo Jyrinki Wed, 13 Apr 2016 10:41:46
+
** Changed in: qtmultimedia-opensource-src (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1485522
Title:
Volume obtained is 100% in multimedia sink for sounds from app
Status in Canonical System Image:
Fix Committed
Status in pulseaudio package in Ubuntu:
Invalid
Status in qtmultimedia-opensource-src package in Ubuntu:
Fix Released
Status in qtubuntu-media package in Ubuntu:
Invalid
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
Fix Released
Bug description:
I'm not sure 100% this is a bug but it is related to
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506
When the "Marron in trouble" games launches a sound the multimedia
sink it's updated and when reading the volume it's always 100%.
I'ts not 100% for other applications using the multimedia role, like
the music app or other games/apps. The volume in that case is in sync
with the volume that was previously set for it.
This is the code from the indicator-sound where we get the 100%
volume.
var props_variant = yield _pconn.call
("org.PulseAudio.Ext.StreamRestore1.RestoreEntry",
sink_input_objp,
"org.freedesktop.DBus.Properties", "Get",
new Variant ("(ss)",
"org.PulseAudio.Ext.StreamRestore1.RestoreEntry", "Volume"),
null, DBusCallFlags.NONE, -1);
Variant tmp;
props_variant.get ("(v)", out tmp);
uint32 type = 0, volume = 0;
VariantIter iter = tmp.iterator ();
iter.next ("(uu)", &type, &volume);
I did a workaround branch in the indicator-sound that reads the volume
at initilaization for every role and stores any change When the sink
is updated I read the volume in it that is already stored instead of
reading the volume from pulse.
I'm not convinced of that, and would like to know why I get 100%
volume only for this particular game.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1485522/+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 1562822] Re: Bluetooth Browse Files... not working
the setting part works, the indicator is going to be next ** 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 indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in unity-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth source package in Xenial: New Status in unity-control-center source package in Xenial: Fix Committed Bug description: * Impact The bluetooth settings include a non working "browse files..." items * Test case connect/pair a phone which does obex, open settings->bluetooth, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1585127] [NEW] Apps sometimes get stuck on splashscreen on the first run after upgrade
Public bug reported: Krillin, rc-proposed, r340 It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps). Steps to reproduce: 1) Update an application using System settings 2) As soon as it is updated, go to dash and tap on the application icon to run it 3) If the bug is reproduced, the app will now be stuck on the splashscreen Run the app a 2nd time to get it working again. Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful) https://pastebin.ubuntu.com/16652091/ Logs from unity8 http://pastebin.ubuntu.com/16652517/ syslog has rotated already (due to the high frequency spam on krillin) so I don't have that anymore ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Krillin, rc-proposed, r340 It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps). Steps to reproduce: 1) Update an application using System settings 2) As soon as it is updated, go to dash and tap on the application icon to run it 3) If the bug is reproduced, the app will now be stuck on the splashscreen Run the app a 2nd time to get it working again. Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful) https://pastebin.ubuntu.com/16652091/ - Logs from unity8 + Logs from unity8 http://pastebin.ubuntu.com/16652517/ + + syslog has rotated already (due to the high frequency spam on krillin) + so I don't have that anymore -- 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/1585127 Title: Apps sometimes get stuck on splashscreen on the first run after upgrade Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Krillin, rc-proposed, r340 It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps). Steps to reproduce: 1) Update an application using System settings 2) As soon as it is updated, go to dash and tap on the application icon to run it 3) If the bug is reproduced, the app will now be stuck on the splashscreen Run the app a 2nd time to get it working again. Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful) https://pastebin.ubuntu.com/16652091/ Logs from unity8 http://pastebin.ubuntu.com/16652517/ syslog has rotated already (due to the high frequency spam on krillin) so I don't have that anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1585127/+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 1585127] Re: Apps sometimes get stuck on splashscreen on the first run after upgrade
** Also affects: qtmir (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/1585127 Title: Apps sometimes get stuck on splashscreen on the first run after upgrade Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Krillin, rc-proposed, r340 It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps). Steps to reproduce: 1) Update an application using System settings 2) As soon as it is updated, go to dash and tap on the application icon to run it 3) If the bug is reproduced, the app will now be stuck on the splashscreen Run the app a 2nd time to get it working again. Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful) https://pastebin.ubuntu.com/16652091/ Logs from unity8 http://pastebin.ubuntu.com/16652517/ syslog has rotated already (due to the high frequency spam on krillin) so I don't have that anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1585127/+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 1585127] Re: Apps sometimes get stuck on splashscreen on the first run after upgrade
faenil: well that used to be the case and then the appscope was updated to auto refresh but still takes a little while to do that so the the blue bouncing bar was at the bottom when you tried to open it initially it might of still been updating the appscope which would mean you were using the old .desktop file for app which tends to lead to a spinner and eventually app closure then launching again would of given it time to complete davmor2: it is a possibility, sure. If it takes that long to update the scope faenil: it takes as long as it takes to refresh a scope, move to the apps scope pull down to refresh and wait for the blue bouncer to finish that will give you an idea when there are no changes -- 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/1585127 Title: Apps sometimes get stuck on splashscreen on the first run after upgrade Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Krillin, rc-proposed, r340 It happened to me with Telegram last evening, but after discussing a bit with other people, it seems I am not the only one to have experience this (even with other apps). Steps to reproduce: 1) Update an application using System settings 2) As soon as it is updated, go to dash and tap on the application icon to run it 3) If the bug is reproduced, the app will now be stuck on the splashscreen Run the app a 2nd time to get it working again. Logs from telegram (the run at 21:40 is the failing one, the run at 22:00 is successful) https://pastebin.ubuntu.com/16652091/ Logs from unity8 http://pastebin.ubuntu.com/16652517/ syslog has rotated already (due to the high frequency spam on krillin) so I don't have that anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1585127/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected
** Branch linked: lp:~ubuntu-art-pkg/ubuntu-themes/16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/762349 Title: [SRU] Difficult to distinguish which tab is selected Status in Ayatana Design: Fix Committed Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Committed Status in ubuntu-themes source package in Xenial: In Progress Bug description: [Impact] * When a user opens multiple tabs in GNOME terminal all tabs are styled in a *very* visually similar manner. This makes it very hard to distinguish between the current active tab and all the others and on a HiDPI screen pretty much impossible. * This fix has been ack'd by design and was targeted for X but didn't get reviewed and OK'd in time. Design team have approved this styling. * This bug is fixed by extending the CSS specifically for Terminal (i.e. no other applications are affected) giving the active tab a darker background colour (using only theme defined colours) and reworks the borders around the tabs to remove the graduated image borders that only look right on a light coloured background. Changes have been made for both Ambiance and Radiance. [Test Case] * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t) * Open five new tabs (ctrl-shift-t) * Click on the tab in the middle * Note that it is hard to see at a glance which tab is currently selected * Close Terminal and all open tabs. * Install the patched theme * Open Terminal and open five new tabs * Click on the tab in the middle and note that it takes on a dark grey background [Regression Potential] * The patch only addresses tabs that are placed at the top of the window. However this is the only option in Terminal, so should not cause any problems. * There is a work-around to match the "actions bar" (the bit with the dropdown selector and + button). This bug is supposed to be fixed in v3.20 and could be removed. This is commented in the CSS. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected
I uploaded this. ** Changed in: ubuntu-themes Status: In Progress => Fix Released ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/762349 Title: [SRU] Difficult to distinguish which tab is selected Status in Ayatana Design: Fix Committed Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Committed Status in ubuntu-themes source package in Xenial: In Progress Bug description: [Impact] * When a user opens multiple tabs in GNOME terminal all tabs are styled in a *very* visually similar manner. This makes it very hard to distinguish between the current active tab and all the others and on a HiDPI screen pretty much impossible. * This fix has been ack'd by design and was targeted for X but didn't get reviewed and OK'd in time. Design team have approved this styling. * This bug is fixed by extending the CSS specifically for Terminal (i.e. no other applications are affected) giving the active tab a darker background colour (using only theme defined colours) and reworks the borders around the tabs to remove the graduated image borders that only look right on a light coloured background. Changes have been made for both Ambiance and Radiance. [Test Case] * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t) * Open five new tabs (ctrl-shift-t) * Click on the tab in the middle * Note that it is hard to see at a glance which tab is currently selected * Close Terminal and all open tabs. * Install the patched theme * Open Terminal and open five new tabs * Click on the tab in the middle and note that it takes on a dark grey background [Regression Potential] * The patch only addresses tabs that are placed at the top of the window. However this is the only option in Terminal, so should not cause any problems. * There is a work-around to match the "actions bar" (the bit with the dropdown selector and + button). This bug is supposed to be fixed in v3.20 and could be removed. This is commented in the CSS. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1580792] Re: Unity8 on Intel Atoms performs poorly
Successful proof of concept fix in eglplasma! Just shortening the shaders to fit i915 makes the error go away, and everything renders orders of magnitude faster: https://code.launchpad.net/~vanvugt/mir/fix-1583532/+merge/295564 -- 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/1580792 Title: Unity8 on Intel Atoms performs poorly Status in unity8 package in Ubuntu: Confirmed Bug description: (problem forked from bug 1549455) Unity8 on Intel Pineview performs very poorly. Frame times appears to be up to 900ms, Qt's renderer thread using 100% CPU. Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors: http://paste.ubuntu.com/16344427/ Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like OpenGL features that Unity8 is hitting but mir-demos don't. So those gl calls are also good candidates for explaining poor performance, especially if Mesa is falling back to software rendering for them." Since Qt tends to perform just fine on that hardware in X11, something isn't right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1580792/+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 1585150] [NEW] cannot open kubuntu desktop nor xubuntu desktop
Public bug reported: i'm new in GPU computing and after i installed nvidia-361.28 and cuda-7.5 all the windows fell. wua...what a huge mess cannot even log in when i reboot my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.20 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: Tue May 24 18:27:31 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:362d] InstallationDate: Installed on 2015-12-08 (168 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic root=UUID=ab447542-e029-488c-92f4-58169f0b0af6 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/17/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B85M-D3V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2 xserver.bootTime: Tue May 24 18:22:03 2016 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install third-party-packages trusty ubuntu -- 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/1585150 Title: cannot open kubuntu desktop nor xubuntu desktop Status in xorg package in Ubuntu: New Bug description: i'm new in GPU computing and after i installed nvidia-361.28 and cuda-7.5 all the windows fell. wua...what a huge mess cannot even log in when i reboot my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.20 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: Tue May 24 18:27:31 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:362d] InstallationDate: Installed on 2015-12-08 (168 days ago) InstallationMedia:
[Touch-packages] [Bug 1584602] Re: internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336
** Changed in: gcc-4.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1584602 Title: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: When building samba package on trusty/arm64 with gcc-4.8, the following build crash can be observed, and it can be triggered with gcc-4.7 too. 01:07:10 runner /usr/bin/gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -- DSTATIC_LOCKING_MODULES=NULL -DSTATIC_LOCKING_MODULES_PROTO=extern void __LOCKINN G_dummy_module_proto(void) -MD -D_FORTIFY_SOURCE=2 -Idefault/source3 -I../sourcee 3 -Idefault/source3/include -I../source3/include -Idefault/source3/lib -I../sourr ce3/lib -Idefault/source4/heimdal/lib/com_err -I../source4/heimdal/lib/com_err -- Idefault/source4/heimdal/lib/krb5 -I../source4/heimdal/lib/krb5 -Idefault/sourcee 4/heimdal/lib/gssapi -I../source4/heimdal/lib/gssapi -Idefault/source4/heimdal_bb uild -I../source4/heimdal_build -Idefault/bin/default/source4/heimdal/lib/asn1 -- Idefault/source4/heimdal/lib/asn1 -Idefault/include/public -I../include/public -- Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib -I..// source4/lib -Idefault/source4/include -I../source4/include -Idefault/include -I.. ./include -Idefault/lib/replace -I../lib/replace -Idefault -I.. -Idefault/librpcc -I../librpc -Idefault/libcli/security -I../libcli/security -Idefault/source3/lii brpc -I../source3/librpc -Idefault/libcli/util -I../libcli/util -Idefault/lib/utt il/charset -I../lib/util/charset -Idefault/dynconfig -I../dynconfig -Idefault/lii b/compression -I../lib/compression -Idefault/libcli/nbt -I../libcli/nbt -Idefaull t/lib/crypto -I../lib/crypto -I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFII G_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../source3/locking/brlock.c -c -o default/source3/locking/brlock_92.o ../source3/smbd/notify.c: In function ‘change_notify_create’: ../source3/smbd/notify.c:297:1: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 ../source3/smbd/notify.c: In function ‘change_notify_create’: ../source3/smbd/notify.c:297:1: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 } ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+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 1584907] Re: Size set in Window{} is not respected in desktop mode
can you delete ~/.cache/unity/windowstatestorage.sqlite and try again?
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
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/1584907
Title:
Size set in Window{} is not respected in desktop mode
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
bq M10 rc-proposed r111
If I set width and height in Window component and run the app on tablet in
desktop mode, the window size is not as I set.
I set width and height to be units.gu 70x70 but the result is 60x47. See the
screenshot please. When I try the same app on my desktop running 16.04 the
result is correct (70x70).
Code I used:
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.2
Window {
id: root_window
visible: true
title: i18n.tr("My cool app's name")
width: units.gu(70)
height: units.gu(70)
minimumWidth: units.gu(40)
minimumHeight: units.gu(40)
MainView {
// Note! applicationName needs to match the "name" field of the click
manifest
applicationName: "windowsize.mivoligo"
anchors.fill: parent
Text {
id: window_size
text: "width = " + root_window.width / units.gu(1) + " height = "
+ root_window.height / units.gu(1)
anchors.centerIn: parent
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1584907/+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 1584907] Re: Size set in Window{} is not respected in desktop mode
Note that those values are only honored the first time an application
starts. if the user resizes it, that's what unity will remember.
--
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/1584907
Title:
Size set in Window{} is not respected in desktop mode
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
bq M10 rc-proposed r111
If I set width and height in Window component and run the app on tablet in
desktop mode, the window size is not as I set.
I set width and height to be units.gu 70x70 but the result is 60x47. See the
screenshot please. When I try the same app on my desktop running 16.04 the
result is correct (70x70).
Code I used:
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.2
Window {
id: root_window
visible: true
title: i18n.tr("My cool app's name")
width: units.gu(70)
height: units.gu(70)
minimumWidth: units.gu(40)
minimumHeight: units.gu(40)
MainView {
// Note! applicationName needs to match the "name" field of the click
manifest
applicationName: "windowsize.mivoligo"
anchors.fill: parent
Text {
id: window_size
text: "width = " + root_window.width / units.gu(1) + " height = "
+ root_window.height / units.gu(1)
anchors.centerIn: parent
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1584907/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected
This bug was fixed in the package ubuntu-themes - 14.04+16.04.20160426-0ubuntu2 --- ubuntu-themes (14.04+16.04.20160426-0ubuntu2) yakkety; urgency=medium [ Will Cooke ] * Adds Terminal specific CSS to change tab colours making it easier to distinguish the current selected tab from the others. Design have reviewed and ack'd. LP: #762349 -- Iain Lane Tue, 24 May 2016 10:21:12 +0100 ** Changed in: ubuntu-themes (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/762349 Title: [SRU] Difficult to distinguish which tab is selected Status in Ayatana Design: Fix Committed Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: In Progress Bug description: [Impact] * When a user opens multiple tabs in GNOME terminal all tabs are styled in a *very* visually similar manner. This makes it very hard to distinguish between the current active tab and all the others and on a HiDPI screen pretty much impossible. * This fix has been ack'd by design and was targeted for X but didn't get reviewed and OK'd in time. Design team have approved this styling. * This bug is fixed by extending the CSS specifically for Terminal (i.e. no other applications are affected) giving the active tab a darker background colour (using only theme defined colours) and reworks the borders around the tabs to remove the graduated image borders that only look right on a light coloured background. Changes have been made for both Ambiance and Radiance. [Test Case] * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t) * Open five new tabs (ctrl-shift-t) * Click on the tab in the middle * Note that it is hard to see at a glance which tab is currently selected * Close Terminal and all open tabs. * Install the patched theme * Open Terminal and open five new tabs * Click on the tab in the middle and note that it takes on a dark grey background [Regression Potential] * The patch only addresses tabs that are placed at the top of the window. However this is the only option in Terminal, so should not cause any problems. * There is a work-around to match the "actions bar" (the bit with the dropdown selector and + button). This bug is supposed to be fixed in v3.20 and could be removed. This is commented in the CSS. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1584602] Re: internal compiler error: in fixup_reorder_chain, , at cfgrtl.c:3336
I've raised https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1585174 to highlight the issue and suggest using the "-fno-if-conversion" option that Matthias has identifed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1584602 Title: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: When building samba package on trusty/arm64 with gcc-4.8, the following build crash can be observed, and it can be triggered with gcc-4.7 too. 01:07:10 runner /usr/bin/gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -- DSTATIC_LOCKING_MODULES=NULL -DSTATIC_LOCKING_MODULES_PROTO=extern void __LOCKINN G_dummy_module_proto(void) -MD -D_FORTIFY_SOURCE=2 -Idefault/source3 -I../sourcee 3 -Idefault/source3/include -I../source3/include -Idefault/source3/lib -I../sourr ce3/lib -Idefault/source4/heimdal/lib/com_err -I../source4/heimdal/lib/com_err -- Idefault/source4/heimdal/lib/krb5 -I../source4/heimdal/lib/krb5 -Idefault/sourcee 4/heimdal/lib/gssapi -I../source4/heimdal/lib/gssapi -Idefault/source4/heimdal_bb uild -I../source4/heimdal_build -Idefault/bin/default/source4/heimdal/lib/asn1 -- Idefault/source4/heimdal/lib/asn1 -Idefault/include/public -I../include/public -- Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib -I..// source4/lib -Idefault/source4/include -I../source4/include -Idefault/include -I.. ./include -Idefault/lib/replace -I../lib/replace -Idefault -I.. -Idefault/librpcc -I../librpc -Idefault/libcli/security -I../libcli/security -Idefault/source3/lii brpc -I../source3/librpc -Idefault/libcli/util -I../libcli/util -Idefault/lib/utt il/charset -I../lib/util/charset -Idefault/dynconfig -I../dynconfig -Idefault/lii b/compression -I../lib/compression -Idefault/libcli/nbt -I../libcli/nbt -Idefaull t/lib/crypto -I../lib/crypto -I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFII G_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../source3/locking/brlock.c -c -o default/source3/locking/brlock_92.o ../source3/smbd/notify.c: In function ‘change_notify_create’: ../source3/smbd/notify.c:297:1: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 ../source3/smbd/notify.c: In function ‘change_notify_create’: ../source3/smbd/notify.c:297:1: internal compiler error: in fixup_reorder_chain,, at cfgrtl.c:3336 } ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1584602/+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 1574826] Re: Kubuntu 16.04 LTS network connection (VPN, and WPA2 WLAN) fails: "connection.gateway-ping-timeout: cannot set property: value of "###" of type 'guint' is invalid or
*** This bug is a duplicate of bug 1569674 *** https://bugs.launchpad.net/bugs/1569674 It works! -- 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/1574826 Title: Kubuntu 16.04 LTS network connection (VPN, and WPA2 WLAN) fails: "connection.gateway-ping-timeout: cannot set property: value of "###" of type 'guint' is invalid or out of range for property type 'gateway- ping-timeout' of type 'guint'" Status in network-manager package in Ubuntu: Confirmed Bug description: Just freshly installed Kubuntu 16.04. When trying to create a VPN in the network manager settings, the following error occurs: "connection.gateway-ping-timeout: cannot set property: value of "###" of type 'guint' is invalid or out of range for property type 'gateway- ping-timeout' of type 'guint' " "###" is sometimes a different value and sometimes repeating. The issue happens for PPTP VPN as well as OpenConnect VPN (network-manager-openconnect was installed for this). It seems to be currently not possible to use Kubuntu 16.04 with a VPN, due to this bug. Therefore, it is quite critical for mobile usage (laptop) in public WLANs. $ apt-show-versions | grep network-manager network-manager:amd64/xenial 1.1.93-0ubuntu4 uptodate network-manager:i386 not installed network-manager-openconnect:amd64/xenial 1.0.2-1build1 uptodate network-manager-openconnect:i386 not installed network-manager-pptp:amd64/xenial 1.1.93-1ubuntu1 uptodate network-manager-pptp:i386 not installed Other users seem to have the problem as well: - https://askubuntu.com/questions/761646/intermittent-networkmanager-error-on-importing-ovpn-files-or-editing-such-conne - http://ubuntuforums.org/showthread.php?t=2321553 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 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 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 25 21:28:45 2016 InstallationDate: Installed on 2016-04-25 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IpRoute: default via 172.31.255.254 dev wlp3s0 proto static metric 600 default dev enp0s25 scope link metric 1002 linkdown 169.254.0.0/16 dev enp0s25 proto kernel scope link src 169.254.13.163 linkdown 172.31.255.0/24 dev wlp3s0 proto kernel scope link src 172.31.255.121 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Forskningsnettverk Sognsvann 2bbff8c3-4a62-43e1-8bca-11af323eead6 802-11-wireless 1461612320 Mo 25 Apr 2016 21:25:20 CEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Forskningsnettverk Sognsvann 2bbff8c3-4a62-43e1-8bca-11af323eead6 /org/freedesktop/NetworkManager/ActiveConnection/0 enp0s25 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- 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/ubuntu/+source/network-manager/+bug/1574826/+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 1584907] Re: Size set in Window{} is not respected in desktop mode
This was the very first start. :)
I deleted the database and tried again just now and the result is the same
60x47.
--
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/1584907
Title:
Size set in Window{} is not respected in desktop mode
Status in unity8 package in Ubuntu:
Triaged
Bug description:
bq M10 rc-proposed r111
If I set width and height in Window component and run the app on tablet in
desktop mode, the window size is not as I set.
I set width and height to be units.gu 70x70 but the result is 60x47. See the
screenshot please. When I try the same app on my desktop running 16.04 the
result is correct (70x70).
Code I used:
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.2
Window {
id: root_window
visible: true
title: i18n.tr("My cool app's name")
width: units.gu(70)
height: units.gu(70)
minimumWidth: units.gu(40)
minimumHeight: units.gu(40)
MainView {
// Note! applicationName needs to match the "name" field of the click
manifest
applicationName: "windowsize.mivoligo"
anchors.fill: parent
Text {
id: window_size
text: "width = " + root_window.width / units.gu(1) + " height = "
+ root_window.height / units.gu(1)
anchors.centerIn: parent
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1584907/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: aptdaemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apturl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Yakkety (proposed) now has been updated to packagekit 1.1.1-1ubuntu1 But there are some conflicts when trying to upgrade: sudo apt-get install gir1.2-packagekitglib-1.0 [sudo] password for oem: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED aptdaemon apturl language-selector-gnome nautilus-share python3-aptdaemon python3-aptdaemon.gtk3widgets python3-aptdaemon.pkcompat sessioninstaller software-properties-gtk system-config-printer-gnome The following packages will be upgraded: gir1.2-packagekitglib-1.0 1 to upgrade, 0 to newly install, 10 to remove and 1 not to upgrade. Need to get 21.5 kB of archives. After this operation, 3,412 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ** Tags added: yakkety ** Also affects: apturl (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus-share (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus-share (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: packagekit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1580577] Re: python2.7 crashes with SegFault when running Zope
Yes, that was exactly the one I wanted to keep out. Sadly, it's not that
simple. Later patches depend on this one. If I also disable those, the
build fails. That's why it's taking so much time...
On 05/24/2016 10:14 AM, Matthias Klose wrote:
> On 17.05.2016 14:14, Ján Jockusch wrote:
>> In the mean time, I have attempted to narrow the debian/patches/* files
>> down so I can find which patch produces the problem.
> it should be enough to disable the hg-updates patch.
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when running Zope
Status in python2.7 package in Ubuntu:
Confirmed
Bug description:
Source package / Package:
python2.7_2.7.11-7ubuntu1
System:
Description: Ubuntu 16.04 LTS
Release: 16.04
This is a bug report originating from the findings documented in
https://github.com/zopefoundation/Zope/issues/56
The expected behaviour is this:
- Upon installing Zope2 in a virtualenv a default instance should work with
no issues.
What happens instead:
- The freshly installed Zope instance causes Python to SegFault after only a
few requests.
But Python should never SegFault.
The following program produces the error:
#!/bin/bash
set -e
# Call this testing script with an argument "setup" for the first time
# to build the testing case
#
# After that, the script only performs the test as described below.
#
# Requirements: apt-get install virtualenv python2.7-dbg
#
# This script needs internet access when running.
# The python version to test:
python=/usr/bin/python2.7-dbg
# This part builds the testing environment
if [ "$1" == "setup" ] ; then
# Virtual environment with the chosen python
virtualenv --python ${python} --no-site-packages zope-virtualenv
cd zope-virtualenv
# Basic Zope installation
./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
# Simplest possible Zope instance
./bin/mkzopeinstance --dir instance --user admin:admin
cd ..
fi
# THE TEST
# Run Zope instance in the background
zope-virtualenv/instance/bin/runzope &
# Give Zope some time to start up
sleep 3
# Call a few management URLs, nothing too fancy...
urls="
http://admin:admin@localhost:8080/Control_Panel/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
http://admin:admin@localhost:8080/manage
http://admin:admin@localhost:8080/acl_users/manage_main
http://admin:admin@localhost:8080/acl_users/manage_access
"
while true ; do
for url in ${urls} ; do
echo ${url}
curl -s $url -o /dev/null
done
done
# This test fails after about 10 requests with
# Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has
negative ref count -1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1584907] Re: Size set in Window{} is not respected in desktop mode
** Changed in: unity8 (Ubuntu)
Status: Incomplete => 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/1584907
Title:
Size set in Window{} is not respected in desktop mode
Status in unity8 package in Ubuntu:
Triaged
Bug description:
bq M10 rc-proposed r111
If I set width and height in Window component and run the app on tablet in
desktop mode, the window size is not as I set.
I set width and height to be units.gu 70x70 but the result is 60x47. See the
screenshot please. When I try the same app on my desktop running 16.04 the
result is correct (70x70).
Code I used:
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.2
Window {
id: root_window
visible: true
title: i18n.tr("My cool app's name")
width: units.gu(70)
height: units.gu(70)
minimumWidth: units.gu(40)
minimumHeight: units.gu(40)
MainView {
// Note! applicationName needs to match the "name" field of the click
manifest
applicationName: "windowsize.mivoligo"
anchors.fill: parent
Text {
id: window_size
text: "width = " + root_window.width / units.gu(1) + " height = "
+ root_window.height / units.gu(1)
anchors.centerIn: parent
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1584907/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- 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/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: language-selector (Ubuntu) Status: New => Confirmed -- 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/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sessioninstaller (Ubuntu) Status: New => Confirmed -- 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/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1496292] Re: Needs to be ported to packagekit 1
** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Also affects: sessioninstaller (Ubuntu) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1568772] Re: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
Adding sleep 10 in /etc/rc.local before alsactl restore does not help. Contrary to what I said in my previous email in my last try running in terminal "sudo alsactl restore" did not manage to restore the mixer settings (even though there were no warnings or error messages) but "alsactl restore" (no sudo) did. -- 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/1568772 Title: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl, on a fresh xenial 64 bits installed from mini.iso and sharing a /home partition with a wily installation. No third party package, only genuine default install. Note that sound has no trouble; only this logged. There is no sound card on this system, only a mobo chipset. systemd-udevd[412]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Maybe its related to the 'i' aka '--no-init-fallback' found here: http://manpages.ubuntu.com/manpages/wily/man1/alsactl.1.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1755 F pulseaudio /dev/snd/pcmC0D0p: oem1755 F...m pulseaudio /dev/snd/controlC0: oem1755 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 11 13:50:55 2016 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772/+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 54948] Re: Unnecessary tab positions in "unsaved changes" dialog
** Changed in: gedit Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/54948 Title: Unnecessary tab positions in "unsaved changes" dialog Status in gedit: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Bug description: If you have unsaved changed in a document when you try to close gedit, you get an "unsaved changes" dialog warning: Save the changes to document "Unsaved Document 2" before closing? If you don't save, changes from the last minute and 46 seconds will be permanently lost. [ Close without Saving ] [ Cancel ] [ Save ] If you try to use tab to navigate between buttons, you'll find that the focus also goes to the first text paragraph (before the S) and the second text paragraph (before the I). This is, of course, entirely useless, as the text is unchangable. The tab focus should only go between the 3 buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/54948/+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 1540168] Re: Update OpenCV version for 16.04
There is another pressing issue. When I tried to compile OpenCV 3.1.0 from source, it complains that GCC versions later than 4.9 are not supported. The version of GCC that ships with Ubuntu 16.04 is 5.3.1 I think, which is nice. So the fact that OpenCV doesn't support it is a real shame. I desperately need OpenCV 3.x for my work and this is a massive setback. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1540168 Title: Update OpenCV version for 16.04 Status in opencv package in Ubuntu: Confirmed Status in opencv package in Debian: Fix Released Bug description: The Ubuntu 16.04 alpha still only contains OpenCV 2.4. It would be really good to update to OpenCV 3.1 for a distribution to be released in 2016, as the 2.4 series is getting quite old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1540168/+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 1361610] Re: libPCRE3 8.31 regex matching is not working
I was afraid so.
You could try using the pcre.h header from the embedded pcre in Poco
(apt-get source libPoco-dev, poco-1.3.6p1/Foundation/src/pcre.h), that
I've attached as pocopcre.h and not linking to the system pcre (just g++
regex.cc -lPocoFoundation).
That seems to work for me:
Poco POCO_VERSION on Linux 3.13.0-24-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes
Poco match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 7.8 2008-09-05
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no
If you need a more recent pcre you need to change Poco somehow to not
expose the pcre functions, for example by renaming them, adding a
namespace or using __attribute__ ((visibility ("hidden"))). Maybe the
poco developers can help you with that.
** Attachment added: "pocopcre.h"
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+attachment/4669359/+files/pocopcre.h
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361610
Title:
libPCRE3 8.31 regex matching is not working
Status in pcre3 package in Ubuntu:
Invalid
Status in poco package in Ubuntu:
Confirmed
Bug description:
It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
handle regex matching alright. This also affects the libPocoFoundation
RegularExpression classes.
I attached a proof-of-concept which tests a good and bad heystack
string to a regex pattern with Poco, Boost and PCRE. I tested it on
two different machines with the following output:
Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
i686 i686 i686 GNU/Linux
Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT
Ubuntu 12.04.3 LTS 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.12 2011-01-15
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no --> OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration
Upower patch has been applied upstaream. Debdiff for the ubuntu package
updated.
** Patch removed: "upower-always-get-kbd-brightness.debdiff"
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+attachment/440/+files/upower-always-get-kbd-brightness.debdiff
** Patch added: "upower-always-get-kbd-brightness.debdiff"
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+attachment/4669360/+files/upower-always-get-kbd-brightness.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1583861
Title:
Keyboard backlight isn't properly restored after idle on systems with
hardwired configuration
Status in Dell Sputnik:
New
Status in Upower:
Unknown
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in unity-settings-daemon package in Ubuntu:
Triaged
Status in upower package in Ubuntu:
Triaged
Status in gnome-settings-daemon source package in Xenial:
New
Status in unity-settings-daemon source package in Xenial:
New
Status in upower source package in Xenial:
New
Bug description:
In Dell or ThinkPad (for these you need a kernel which includes fix
for lp:1574498) notebooks with keyboard backlight, the keybindings to
control the keyboard backlight don't emit any event to the userland,
about the state change, nor they request userland to change it (as it
happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
events), this causes unity/gnome-settings daemon not to restore the
proper backlight after idle.
Steps to reproduce:
0) ensure your keyboard backlight is on, and
gdbus call --system --dest org.freedesktop.UPower \
--object-path /org/freedesktop/UPower/KbdBacklight \
--method org.freedesktop.UPower.KbdBacklight.GetBrightness
returns a value != from 0. If not, just call the SetBrightness
method with a positive value, to turn on the backlight.
Now turn off the keyboard backlight (or set it to another level)
using the laptop keys, and run:
gsettings set org.gnome.desktop.session idle-delay 1
to make things easier to test.
2) Wait one second and the screensaver should start. Wait the screen to
be turned off. If you just changed the brightness level at the step above,
once the screen is turned off, also the keyboard backlight should be
turned off too.
3) Now press a key or move the mouse.
Expected behavior:
4) The keyboard backlight should be set back to the previous level (so it
should stay off
or go back to the level you set before the idle timeout happened).
Actual behavior:
5) The backlight is set to the level it had at point 0).
To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 54948] Re: Unnecessary tab positions in "unsaved changes" dialog
** Changed in: gtk+2.0 (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/54948 Title: Unnecessary tab positions in "unsaved changes" dialog Status in gedit: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Bug description: If you have unsaved changed in a document when you try to close gedit, you get an "unsaved changes" dialog warning: Save the changes to document "Unsaved Document 2" before closing? If you don't save, changes from the last minute and 46 seconds will be permanently lost. [ Close without Saving ] [ Cancel ] [ Save ] If you try to use tab to navigate between buttons, you'll find that the focus also goes to the first text paragraph (before the S) and the second text paragraph (before the I). This is, of course, entirely useless, as the text is unchangable. The tab focus should only go between the 3 buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/54948/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration
** Also affects: gnome-settings-daemon (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: upower (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unity-settings-daemon (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1583861
Title:
Keyboard backlight isn't properly restored after idle on systems with
hardwired configuration
Status in Dell Sputnik:
New
Status in Upower:
Unknown
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in unity-settings-daemon package in Ubuntu:
Triaged
Status in upower package in Ubuntu:
Triaged
Status in gnome-settings-daemon source package in Xenial:
New
Status in unity-settings-daemon source package in Xenial:
New
Status in upower source package in Xenial:
New
Bug description:
In Dell or ThinkPad (for these you need a kernel which includes fix
for lp:1574498) notebooks with keyboard backlight, the keybindings to
control the keyboard backlight don't emit any event to the userland,
about the state change, nor they request userland to change it (as it
happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
events), this causes unity/gnome-settings daemon not to restore the
proper backlight after idle.
Steps to reproduce:
0) ensure your keyboard backlight is on, and
gdbus call --system --dest org.freedesktop.UPower \
--object-path /org/freedesktop/UPower/KbdBacklight \
--method org.freedesktop.UPower.KbdBacklight.GetBrightness
returns a value != from 0. If not, just call the SetBrightness
method with a positive value, to turn on the backlight.
Now turn off the keyboard backlight (or set it to another level)
using the laptop keys, and run:
gsettings set org.gnome.desktop.session idle-delay 1
to make things easier to test.
2) Wait one second and the screensaver should start. Wait the screen to
be turned off. If you just changed the brightness level at the step above,
once the screen is turned off, also the keyboard backlight should be
turned off too.
3) Now press a key or move the mouse.
Expected behavior:
4) The keyboard backlight should be set back to the previous level (so it
should stay off
or go back to the level you set before the idle timeout happened).
Actual behavior:
5) The backlight is set to the level it had at point 0).
To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration
Uplaoded upower fix to yakkety and to xenial-proposed.
** Changed in: upower (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: upower (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1583861
Title:
Keyboard backlight isn't properly restored after idle on systems with
hardwired configuration
Status in Dell Sputnik:
New
Status in Upower:
Unknown
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in unity-settings-daemon package in Ubuntu:
Triaged
Status in upower package in Ubuntu:
Fix Committed
Status in gnome-settings-daemon source package in Xenial:
New
Status in unity-settings-daemon source package in Xenial:
New
Status in upower source package in Xenial:
In Progress
Bug description:
In Dell or ThinkPad (for these you need a kernel which includes fix
for lp:1574498) notebooks with keyboard backlight, the keybindings to
control the keyboard backlight don't emit any event to the userland,
about the state change, nor they request userland to change it (as it
happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
events), this causes unity/gnome-settings daemon not to restore the
proper backlight after idle.
Steps to reproduce:
0) ensure your keyboard backlight is on, and
gdbus call --system --dest org.freedesktop.UPower \
--object-path /org/freedesktop/UPower/KbdBacklight \
--method org.freedesktop.UPower.KbdBacklight.GetBrightness
returns a value != from 0. If not, just call the SetBrightness
method with a positive value, to turn on the backlight.
Now turn off the keyboard backlight (or set it to another level)
using the laptop keys, and run:
gsettings set org.gnome.desktop.session idle-delay 1
to make things easier to test.
2) Wait one second and the screensaver should start. Wait the screen to
be turned off. If you just changed the brightness level at the step above,
once the screen is turned off, also the keyboard backlight should be
turned off too.
3) Now press a key or move the mouse.
Expected behavior:
4) The keyboard backlight should be set back to the previous level (so it
should stay off
or go back to the level you set before the idle timeout happened).
Actual behavior:
5) The backlight is set to the level it had at point 0).
To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 1496292] Re: Needs to be ported to packagekit 1
FWIW, just making Aptdaemon stop to pretend to be PackageKit and then adjust the dependent packages to not require the compat layer explicitly should also do the job. (we did that at Debian, and right now, only one package still explicitly depends on Aptd (but that one is using Aptd-specific API) -- 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/1496292 Title: Needs to be ported to packagekit 1 Status in aptdaemon package in Ubuntu: Confirmed Status in apturl package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in nautilus-share package in Ubuntu: Confirmed Status in packagekit package in Ubuntu: Confirmed Status in sessioninstaller package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding aptdaemon. This problem was most recently seen with version 1.1.1+bzr982-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/0cbdb94861b90a2bf18c183fb3031ed81f6bb5a7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1496292/+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 1428591] Re: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page
** Changed in: webapps-sprint Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1428591 Title: Dash crashes when trying to authenticate soundcloud scope with google, empty auth page Status in Canonical System Image: Confirmed Status in Unity SoundCloud Scope: New Status in webapps-sprint: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: 1. Go to Soundcloud scope 2. Hit Log-in to SoundCloud button 3. Choose 'Sign in with Google' on the SoundCloud auth page 4. Fill in google account credentials, confirm soundcloud permissions Result: a blank page with 'Cancel' button, no way to navigate back, hitting it crashes the dash (I couldn't get a usable backtrace). NB, this works fine when authenticating using a genuine Soundcloud account. It seems like authenticating via Google is causing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1428591/+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 1585202] [NEW] Network Manager Fails to Automatically Connect to VPN After User Login
Public bug reported: Ubuntu 16.04 (Unity) with Ethernet connection set to automatically connect to VPN in Network Manager after user login (to Ubuntu desktop). Network Manager does not automatically connect to VPN after login. Manually selecting the VPN connection from Network Manager in the system tray after login results in normal connection. Changing "password-flags=1" to "password-flags=0" in the VPN configuration file in /etc/NetworkManager/system-connections, Network- Manager adds "password=" to that configuration file where is VPN connection password in plain text. This change allow Network Manager to connect to VPN automatically after user login. Having to store VPN password in plain text in order for Network Manager to automatically connect is not secure. It appears Network Manager cannot obtain VPN password from Seahorse after user login. ** Affects: network-manager (Ubuntu) Importance: Low Status: New ** Tags: autoconnect network-manager vpn -- 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/1585202 Title: Network Manager Fails to Automatically Connect to VPN After User Login Status in network-manager package in Ubuntu: New Bug description: Ubuntu 16.04 (Unity) with Ethernet connection set to automatically connect to VPN in Network Manager after user login (to Ubuntu desktop). Network Manager does not automatically connect to VPN after login. Manually selecting the VPN connection from Network Manager in the system tray after login results in normal connection. Changing "password-flags=1" to "password-flags=0" in the VPN configuration file in /etc/NetworkManager/system-connections, Network- Manager adds "password=" to that configuration file where is VPN connection password in plain text. This change allow Network Manager to connect to VPN automatically after user login. Having to store VPN password in plain text in order for Network Manager to automatically connect is not secure. It appears Network Manager cannot obtain VPN password from Seahorse after user login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585202/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
On Tue, May 24, 2016 at 08:27:41AM -, Greg Rickson wrote: > I assumed it was because I had both synaptic and Ubuntu Software center > open At the same time ?? That is certainly the sort of thing that could lead to this locking problem, yes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Ambasa: New Status in Debconf: New Status in aptdaemon package in Ubuntu: Confirmed Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]
Hi Gerry, I'm sorry if I'm not very experienced, but could you explain the full procedure to download it and run? I am interested in trying it -- 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/1549455 Title: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"] Status in Mir: Invalid Status in qtubuntu: In Progress Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Qt clients are failing to create an egl context when running on Intel Pineview systems under Mir. eglCreateContext fails with a EGL_BAD_MATCH error code. When it fails, Qt tries to delete & recreate the context, which then crashes the client (bug 1580118) === Original bug description === This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1569653] Re: NetworkManager plugin for 'team' unavailable
Sorry, it looks like that plugin is part of the main package but Ubuntu
is building without it because the library is in universe...
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1585202] Re: Network Manager Fails to Automatically Connect to VPN After User Login
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- 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/1585202 Title: Network Manager Fails to Automatically Connect to VPN After User Login Status in network-manager package in Ubuntu: New Bug description: Ubuntu 16.04 (Unity) with Ethernet connection set to automatically connect to VPN in Network Manager after user login (to Ubuntu desktop). Network Manager does not automatically connect to VPN after login. Manually selecting the VPN connection from Network Manager in the system tray after login results in normal connection. Changing "password-flags=1" to "password-flags=0" in the VPN configuration file in /etc/NetworkManager/system-connections, Network- Manager adds "password=" to that configuration file where is VPN connection password in plain text. This change allow Network Manager to connect to VPN automatically after user login. Having to store VPN password in plain text in order for Network Manager to automatically connect is not secure. It appears Network Manager cannot obtain VPN password from Seahorse after user login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585202/+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 1565772] Re: Allow plugins to decide which username to set on new accounts
Version 0.13+16.04.20160405-0ubuntu1 which fixes this bug is in Yakkety. ** Also affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Changed in: account-plugins (Ubuntu) Status: New => In Progress ** Changed in: account-plugins (Ubuntu) Importance: Undecided => Critical ** Changed in: account-plugins Status: In Progress => Fix Released ** Changed in: gnome-control-center-signon Status: In Progress => Fix Released ** Also affects: gnome-control-center-signon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center-signon (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center-signon (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1565772 Title: Allow plugins to decide which username to set on new accounts Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Committed Status in Online Accounts: GNOME Control Center: Fix Released Status in webapps-sprint: Fix Committed Status in account-plugins package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: In Progress Bug description: This bug is related to bug 1547647, even though it makes sense in any case. Currently, the ApOAuthPlugin class in libaccount-plugin gets the username from the SignonIdentity, which in turn gets it from signon- ui, which in the current WebKit1 implementation gets it from the DOM of the login webpage. This is a hack, it's fragile, not trivial to port to the Oxide web engine, and possibly against some providers' guidelines. We should retrieve the username using some REST API provided by the service, and in order to do so we need to extend libaccounts-plugin with some hooks which subclasses can use to get the username. Once we fix this we can also get rid of the files /etc/signon-ui /webkit-options.d/, which are conflicting with those installed by the KDE account plugins packages. SRU information === [Impact] The same file /etc/signon-ui/webkit- options.d/www.facebook.com.conf is installed by the account-plugin- facebook package (used by Unity) and by kaccount-providers (used by KDE). See this bug's duplicates to see actual bug reports. [Test Case] Install both account-plugin-facebook and kaccount- providers and you'll get the conflict. [Regression Potential] Users running KDE will be completely unaffected by this. Users running Unity might see a change when creating accounts in System Settings->Online Accounts: with this bugfix, the account's display name is obtained by making a REST API call to the remote service, rather than by scrapping the DOM of the server webpages (which is a hack, and prone to errors if the providers' webpage changes). The new way of retrieving the username is the proper one, and it's been tested to work reliably. In any case, the worst thing that might happen is that accounts get created with an empty display name, which is mostly an aesthetic problem (the display name is used only for UI purposes). To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1540168] Re: Update OpenCV version for 16.04
UPDATE, it's not directly OpenCV's fault that GCC versions later than 4.9 are not supported. It's actually CUDA 7.5 that doesn't support GCC versions later than 4.9. There is a proposed solution at https://gist.github.com/wangruohui/679b05fcd1466bb0937f but I haven't tried it yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1540168 Title: Update OpenCV version for 16.04 Status in opencv package in Ubuntu: Confirmed Status in opencv package in Debian: Fix Released Bug description: The Ubuntu 16.04 alpha still only contains OpenCV 2.4. It would be really good to update to OpenCV 3.1 for a distribution to be released in 2016, as the 2.4 series is getting quite old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1540168/+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 1563398] Re: Set the front camera as the default for video media requests
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1563398 Title: Set the front camera as the default for video media requests Status in Canonical System Image: In Progress Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: At the moment, the selected camera (in form factors having multiple ones) defaults to the back camera which does not work very well for cases like hangouts, the container and the browser should default to the front camera. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563398/+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 1470309] Re: The e-mail icon is no response after tap on it
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1470309 Title: The e-mail icon is no response after tap on it Status in address-book-app: Invalid Status in The Webapps-core project: In Progress Status in webapps-sprint: Triaged Status in address-book-app package in Ubuntu: Invalid Bug description: $ system-image-cli -i current build number: 41 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-06-30 06:35:30 version version: 41 version ubuntu: 20150630 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Reproduce Steps: Reproduce steps: Prerequistes: There should be a contact in the contacts app,and it's need contains e-mail address 1,Enter the contacts app 2,Tap on the contact to enter the detail of contact 3,Tap on the e-mail icon Expect Result : It's can be open the gmail application Actual Result : The button is no response after tap on it To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1470309/+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 1488364] Re: [Qt 5.5] OxideQSslCertificate::issuer doesn't work in Qml
This bug was fixed in the package qtdeclarative-opensource-src - 5.5.1-2ubuntu7 --- qtdeclarative-opensource-src (5.5.1-2ubuntu7) yakkety; urgency=medium [ Timo Jyrinki ] * debian/patches/QML-do-not-wrap-property-values-of-type-QVariant.patch: - Make certain QVariant properties accessible from QML. A backport from Qt 5.6.0. (LP: #1488364) [ Jon Boden ] * Update symbols for ubuntuBSD (LP: #1579350) -- Timo Jyrinki Thu, 19 May 2016 11:44:07 + ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New => Fix Released -- 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/1488364 Title: [Qt 5.5] OxideQSslCertificate::issuer doesn't work in Qml Status in Canonical System Image: Fix Committed Status in Oxide: Triaged Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: With older Qt versions, we use private APIs (QQmlValueType and friends) for exposing value types. However, with the built-in gadget support in Qt5.5, OxideQSslCertificate::issuer() is no longer working correctly. - When OxideQSecurityStatus::certificate() returns a null QVariant, the value gets converted to null in Qml. When it returns a QVariant containing OxideQSslCertificate, this gets correctly converted to a value type in Qml. - The QVariant returned from OxideQSslCertificate::issuer() gets converted to an object in Qml (verified with typeof), and calling toString() on the object gives "QVariant(QVariant): undefined". To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488364/+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 1564351] Re: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable.
This bug was fixed in the package unity8 - 8.12+16.04.20160518.1-0ubuntu1 --- unity8 (8.12+16.04.20160518.1-0ubuntu1) xenial; urgency=medium [ CI Train Bot ] * Resync trunk. [ Daniel d'Andrada, Michał Sawicz ] * Move prompt surfaces from MirSurface to Application -- Nick Dedekind Wed, 18 May 2016 11:20:04 + ** Changed in: unity8 (Ubuntu) Status: Fix Committed => Fix Released -- 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/1564351 Title: Unity8 stuck on hint "Long swipe from the left edge to open the Today scope" and can't close it. Desktop left unusable. Status in Canonical System Image: Fix Committed Status in unity8 package in Ubuntu: Fix Released Bug description: Can not unlock my desktop, swipe is not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.12+16.04.20160330-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 31 19:29:50 2016 InstallationDate: Installed on 2016-03-11 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1564351/+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 1574165] Re: Dash forces use of landscape mode on tablet
*** This bug is a duplicate of bug 1465331 *** https://bugs.launchpad.net/bugs/1465331 This bug was fixed in the package unity8 - 8.12+16.04.20160518.1-0ubuntu1 --- unity8 (8.12+16.04.20160518.1-0ubuntu1) xenial; urgency=medium [ CI Train Bot ] * Resync trunk. [ Daniel d'Andrada, Michał Sawicz ] * Move prompt surfaces from MirSurface to Application -- Nick Dedekind Wed, 18 May 2016 11:20:04 + ** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Released -- 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/1574165 Title: Dash forces use of landscape mode on tablet Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: I each the M10 tablet on OTA10.1, and today only displays in landscape, so if I am holding it portrait I have to turn it. Since it only works in portrait on the phone it must know how. I expect it to honor the orientation. To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1574165/+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 1422711] Re: SIM pin notification breaks notification positioning
** Changed in: unity8 (Ubuntu) Assignee: Albert Astals Cid (aacid) => Lukáš Tinkl (lukas-kde) ** Branch linked: lp:~lukas-kde/unity8/fullscreenNotifications-lp1581498 -- 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/1422711 Title: SIM pin notification breaks notification positioning Status in unity8 package in Ubuntu: In Progress Bug description: Using a PIN protected SIM card that produces the SIM PIN notification breaks positioning of notifications. Once the SIM PIN notification has been shown, subsequent notifications hide the panel like this: http://i.imgur.com/cVnOPma.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1422711/+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 1572588] Re: Toolkit should use new orange #e95420
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-html5-theme in Ubuntu. https://bugs.launchpad.net/bugs/1572588 Title: Toolkit should use new orange #e95420 Status in webapps-sprint: New Status in ubuntu-html5-theme package in Ubuntu: New Bug description: this toolkit uses #dd4814 as the colour orange. css/sass/constants.scss:26:$ubuntu_orange: #dd4814; css/appTemplate.css:1033: background: #dd4814; css/appTemplate.css:1168: background: #dd4814; css/appTemplate.css:1440: color: #dd4814; this has apparently been intentionally changed to #E95420 in the QML toolkit so this should probably be updated to match. Now I am really not sure if that should entail a version number bump from 0.1 to something else. There were previous discussions about symlinking a "current" pointer to a theme but these don't appear to have been implemented. As this is a fairly subtle change it is probably not going to break anything to update it in place without a version number bump. see https://lists.ubuntu.com/archives/ubuntu-community-team/2016-April/date.html for further discussion on the change. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1572588/+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 1567619] Re: webapp-container crashes at exit on desktop
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1567619 Title: webapp-container crashes at exit on desktop Status in webapps-sprint: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: There is a non systematic but consistent crash in the container when it is being closed: Thread 1 "webapp-containe" received signal SIGSEGV, Segmentation fault. 0x00f52630 in ?? () (gdb) bt #0 0x00f52630 in ?? () #1 0x76c746c2 in QQmlType::SingletonInstanceInfo::destroy(QQmlEngine*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #2 0x76c4c220 in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #3 0x76c4c349 in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x00473d60 in BrowserApplication::~BrowserApplication() () #5 0x0046af28 in WebappContainer::~WebappContainer() () #6 0x004671bf in main () To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1567619/+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 1517470] Re: Crash in logging cleanup
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1517470 Title: Crash in logging cleanup Status in webapps-sprint: Incomplete Status in webbrowser-app package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding webbrowser-app. This problem was most recently seen with version 0.23+16.04.20151103bzr1264pkg0vivid5107+autopilot0, the problem page at https://errors.ubuntu.com/problem/8140ac614184b545ddcd30185930f36215a649cf contains more details. Rank 2 on errors.u.c for rc-proposed/meizu.en/arale The amount of crash reports increased significantly with webapp- container 0.23+15.04.20151103-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1517470/+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 1577373] Re: Don't use deprecatd GSimpleAsyncResult API
** Changed in: webapps-sprint Milestone: sprint-22 => sprint-23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1577373 Title: Don't use deprecatd GSimpleAsyncResult API Status in webapps-sprint: Confirmed Status in libaccounts-glib package in Ubuntu: Confirmed Status in libsignon-glib package in Ubuntu: Confirmed Bug description: The GSimpleAsyncResult API has been deprecated in favour of GTask. We should migrate our code to use the new API. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1577373/+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 1361610] Re: libPCRE3 8.31 regex matching is not working
Arne,
Thank you for your quick reply but I don't think this solves my problem.
It only solves it for the proof-of-concept which I made to proof, the
bug in Poco regex functionality.
Our system does not even link against libPCRE but uses Poco. If I change
the proof-of-concept to a Poco only solution (see attachment) I still
have the problem of a non functioning regex.
$ g++ regex.cc -lPocoFoundation
$ ./a.out
Poco 0x01030600 on Linux 4.2.0-35-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? no
Poco match 123456789 to pattern ^[0-9]{10} matches? no
$ ldd ./a.out
linux-vdso.so.1 => (0x7ffe94177000)
libPocoFoundation.so.9 => /usr/lib/libPocoFoundation.so.9
(0x7f14dd744000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f14dd44)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f14dd229000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f14dce64000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f14dcc46000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f14dca07000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f14dc7ee000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f14dc5ea000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f14dc3e1000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f14dc0db000)
/lib64/ld-linux-x86-64.so.2 (0x55cbc9c93000)
$ LD_PRELOAD=/lib/x86_64-linux-gnu/libpcre.so.3 ./a.out
Poco 0x01030600 on Linux 4.2.0-35-generic @ x86_64
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes
Poco match 123456789 to pattern ^[0-9]{10} matches? no
$ LD_PRELOAD=/lib/x86_64-linux-gnu/libpcre.so.3 ldd ./a.out
linux-vdso.so.1 => (0x7ffed2c4f000)
/lib/x86_64-linux-gnu/libpcre.so.3 (0x7f34efa89000)
libPocoFoundation.so.9 => /usr/lib/libPocoFoundation.so.9
(0x7f34ef722000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f34ef41d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f34ef207000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f34eee42000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f34eec23000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f34eea0a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f34ee806000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f34ee5fd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f34ee2f7000)
/lib64/ld-linux-x86-64.so.2 (0x564cbde41000)
** Attachment added: "regex.cc"
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+attachment/4669408/+files/regex.cc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1361610
Title:
libPCRE3 8.31 regex matching is not working
Status in pcre3 package in Ubuntu:
Invalid
Status in poco package in Ubuntu:
Confirmed
Bug description:
It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
handle regex matching alright. This also affects the libPocoFoundation
RegularExpression classes.
I attached a proof-of-concept which tests a good and bad heystack
string to a regex pattern with Poco, Boost and PCRE. I tested it on
two different machines with the following output:
Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013
i686 i686 i686 GNU/Linux
Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.31 2012-07-06
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT
Ubuntu 12.04.3 LTS 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
Poco match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
Poco match 123456789 to pattern ^[0-9]{10} matches? no
Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
Boost match 123456789 to pattern ^[0-9]{10} matches? no
PCRE 8.12 2011-01-15
PCRE match 1234567890 to pattern ^[0-9]{10} matches? yes
PRCE match 123456789 to pattern ^[0-9]{10} matches? no --> OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1361610/+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
