[Touch-packages] [Bug 1397225] [NEW] [SB-XFi - Creative X-Fi, playback] No sound at all
Public bug reported: pas de son dans le haut-parleur droit no sound in the right speaker ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: isabelle 1781 F pulseaudio /dev/snd/controlC0: isabelle 1781 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 08:37:14 2014 InstallationDate: Installed on 2014-11-26 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: QuickCam Communicate STX - USB Device 0x46d:0x8d7 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: isabelle 1781 F pulseaudio /dev/snd/controlC0: isabelle 1781 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0FJ030 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/03/2006:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0FJ030:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1397225 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: pas de son dans le haut-parleur droit no sound in the right speaker ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: isabelle 1781 F pulseaudio /dev/snd/controlC0: isabelle 1781 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 08:37:14 2014 InstallationDate: Installed on 2014-11-26 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: QuickCam Communicate STX - USB Device 0x46d:0x8d7 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: isabelle 1781 F pulseaudio /dev/snd/controlC0: isabelle 1781 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0FJ030 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/03/2006:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0FJ030:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1397225/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
kill -9 $(pidof unity8) $(pidof unity8-dash) does not help at all in my PC at all. -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1379836] Re: dialer and messaging app show unlocked pin as locked
Should be fixed starting on vivid image #34 (mako). ** Changed in: ofono (Ubuntu) Status: Triaged => Fix Committed -- 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/1379836 Title: dialer and messaging app show unlocked pin as locked Status in the base for Ubuntu mobile products: Confirmed Status in Telepathy Ofono: In Progress Status in indicator-network package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Committed Status in telepathy-ofono package in Ubuntu: Fix Released Status in telepathy-ofono package in Ubuntu RTM: Confirmed Bug description: Ubuntu System Settings and ofono say it's unlocked but trying to use the dialer and messaging app is blocked by thinking the PIN is locked. $ system-image-cli -i current build number: 81 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-10 15:33:48 version version: 81 version ubuntu: 20141010.1 version device: 20140929.1 version custom: mako-0.7 $ phablet-shell /home/sergiusens/.ssh/known_hosts updated. Original contents retained as /home/sergiusens/.ssh/known_hosts.old Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ lis^C phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_0 ] Features = gprs ussd net sms rat sim Model = Fake Modem Model Powered = 1 Emergency = 0 Online = 1 Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring org.ofono.CallSettings org.ofono.SupplementaryServices org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager org.ofono.CallVolume org.ofono.VoiceCallManager Revision = M9615A-CEFWMAZM-2.0.1701.03 Type = hardware Manufacturer = Fake Manufacturer Serial = 355136052657866 Lockdown = 0 [ org.ofono.ConnectionManager ] Bearer = hspa RoamingAllowed = 0 Suspended = 0 Powered = 1 Attached = 1 [ org.ofono.CallBarring ] VoiceIncoming = disabled VoiceOutgoing = disabled [ org.ofono.CallSettings ] CallingLineRestriction = off HideCallerId = default ConnectedLinePresentation = unknown ConnectedLineRestriction = unknown CallingLinePresentation = enabled CallingNamePresentation = unknown CalledLinePresentation = disabled VoiceCallWaiting = enabled [ org.ofono.SupplementaryServices ] State = idle [ org.ofono.NetworkRegistration ] Mode = auto Name = Personal LocationAreaCode = 394 Status = registered CellId = 14122637 MobileCountryCode = 722 Technology = umts Strength = 61 MobileNetworkCode = 34 [ org.ofono.CallForwarding ] VoiceNotReachable = +541151009255 VoiceNoReplyTimeout = 25 VoiceUnconditional = VoiceNoReply = +541151009255 ForwardingFlagOnSim = 0 VoiceBusy = +541151009255 [ org.ofono.SmartMessaging ] [ org.ofono.PushNotification ] [ org.ofono.MessageManager ] Alphabet = default UseDeliveryReports = 0 ServiceCenterAddress = +541151740055 Bearer = cs-preferred [ org.ofono.NetworkTime ] [ org.ofono.MessageWaiting ] VoicemailWaiting = 0 VoicemailMailboxNumber = *555 VoicemailMessageCount = 0 [ org.ofono.RadioSettings ] TechnologyPreference = umts ModemTechnologies = gsm umts FastDormancy = 0 [ org.ofono.SimManager ] CardIdentifier = 89543421113404033941 ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = '*2582' [Personal] = '+810' [At. Clientes] = '*111' Retries = FixedDialing = 0 SubscriberIdentity = 722341240403394 MobileCountryCode = 722 BarredDialing = 0 PinRequired = none LockedPins = SubscriberNumbers = Present = 1 PreferredLanguages = es en pt it MobileNetworkCode = 34 [ org.ofono.CallVolume ] MicrophoneVolume = 0 Muted = 1 SpeakerVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image
[Touch-packages] [Bug 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
I enable virtuallization in BIOS and then it works ! We definitely need to check if visualization is properly enable before run it. Thanks for suggestion from Rex, I install package cpu-checker and run command kvm-ok can show whether cpu support visualization and if it's enable in BIOS. If cpu support it and it's enable in bios, it show result (in utopic) == INFO: /dev/kvm exists KVM acceleration can be used == If cpu support it and it's NOT enable in bios, it show result (run as non-root in utopic) == INFO: /dev/kvm does not exist HINT: sudo modprobe kvm_intel INFO: For more detailed results, you should run this as root HINT: sudo /usr/sbin/kvm-ok == If cpu support it and it's NOT enable in bios, it show result (run as root in utopic) == INFO: /dev/kvm does not exist HINT: sudo modprobe kvm_intel INFO: Your CPU supports KVM extensions INFO: KVM (vmx) is disabled by your BIOS HINT: Enter your BIOS setup and enable Virtualization Technology (VT), and then hard poweroff/poweron your system KVM acceleration can NOT be used = -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Hi, Michal The PES mainstream team identified that it has a higher probability happend, if the user runing the emulator on a virtualzation disabled machine. The user does not even get the panel / welcome screen / greeter, the whole "screen" of the emulator is blank. It comes back *sometimes* if restart unity8 by $ kill -9 $(pidof unity8) $(pidof unity8-dash) Here is my theory - When disabled virtualzation in emulator, the system will be running very slow, and it's possible incrase odds for a race condition of the unity8/unity8-dash. Reference - The developer need to have VT-X/AMD-V hardware for the emulator, and it need to be enabled from BIOS to have better emulator performance. The developer can check with the following command - # check if the hardware support virtualzation $ grep -e svm -e vmx /proc/cpuinfo # check if it's enabled from BIOS $ sudo apt-get install cpu-checker && kvm-ok -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1190344] Re: lightdm is leaking FDs -fix
** Tags removed: leak
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Precise:
Triaged
Status in lightdm source package in Trusty:
Triaged
Status in lightdm source package in Utopic:
Fix Committed
Status in lightdm source package in Vivid:
Fix Released
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes. This means each session that is created leaks two file
descriptors eventually leading to the system stopping it from creating new
pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1397178] Re: kubuntu 14.10 plasma 5 spins up PowerMizer
Sorry, I see that this bug is a duplicate of 1394856 which has already been transferred to xorg. -- 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/1397178 Title: kubuntu 14.10 plasma 5 spins up PowerMizer Status in xorg package in Ubuntu: New Bug description: I have installed 14.10 Plasma 5 on my laptop, which is a vintage 2011 System 76. Of greatest significance is that it has an nvidia 560M graphics card in it. When I first installed 14.04, I noticed that the PowerMizer report of the NVIDIA X Server Settings would report that the graphics chip's clock was more or less constantly spun up to its highest clock rate. Heat and power use were very high, and I constantly heard the fan running. I found there were two ways to fix this: (1) Add a file called 05-nvidia.conf to /usr/share/X11/xorg.conf.d containing the lines: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x; PowerMizerDefault=0x3; PowerMizerDefaultAC=0x3" EndSection This pegged the graphics card at its lowest possible clock rate, which was adequate for most things but sometimes led to bad playback on some videos. See: https://forums.opensuse.org/showthread.php/410089-nvidia- powermizer-how-tweak (2) Revert to the 304 driver. This still spun up to high clock rates a bit more often than it seemed to need to, but was fairly reasonable otherwise. I expected that this would soon be rectified, since I saw that version 337.25 of the driver allegedly fixed some issue with performance in KDE: http://www.nvidia.com/download/driverResults.aspx/76278/en-us Jump ahead to yesterday when I installed 14.10 plasma 5 - I noticed that even with the 304 driver the PowerMizer reported the clock at its highest rate. With nothing moving on the screen at all and my not touching the mouse, it was pegged. I found that even installing the xorg-edgers driver (340 I believe) had no effect. Furthermore, 340 did not respond to the xorg.conf settings file above. The only way I can get plasma 5 to run reasonably on this machine is to revert to 304 and *also* put the settings file in. This is of course not optimal. Is there some way to determine what exactly is happening that causes the graphics clock to spin up so high? Nothing much is happening. Just scrolling a window in firefox is sufficient to start it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Fri Nov 28 00:00:27 2014 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1397178/+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 1397178] [NEW] kubuntu 14.10 plasma 5 spins up PowerMizer
Public bug reported: I have installed 14.10 Plasma 5 on my laptop, which is a vintage 2011 System 76. Of greatest significance is that it has an nvidia 560M graphics card in it. When I first installed 14.04, I noticed that the PowerMizer report of the NVIDIA X Server Settings would report that the graphics chip's clock was more or less constantly spun up to its highest clock rate. Heat and power use were very high, and I constantly heard the fan running. I found there were two ways to fix this: (1) Add a file called 05-nvidia.conf to /usr/share/X11/xorg.conf.d containing the lines: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x; PowerMizerDefault=0x3; PowerMizerDefaultAC=0x3" EndSection This pegged the graphics card at its lowest possible clock rate, which was adequate for most things but sometimes led to bad playback on some videos. See: https://forums.opensuse.org/showthread.php/410089-nvidia- powermizer-how-tweak (2) Revert to the 304 driver. This still spun up to high clock rates a bit more often than it seemed to need to, but was fairly reasonable otherwise. I expected that this would soon be rectified, since I saw that version 337.25 of the driver allegedly fixed some issue with performance in KDE: http://www.nvidia.com/download/driverResults.aspx/76278/en-us Jump ahead to yesterday when I installed 14.10 plasma 5 - I noticed that even with the 304 driver the PowerMizer reported the clock at its highest rate. With nothing moving on the screen at all and my not touching the mouse, it was pegged. I found that even installing the xorg-edgers driver (340 I believe) had no effect. Furthermore, 340 did not respond to the xorg.conf settings file above. The only way I can get plasma 5 to run reasonably on this machine is to revert to 304 and *also* put the settings file in. This is of course not optimal. Is there some way to determine what exactly is happening that causes the graphics clock to spin up so high? Nothing much is happening. Just scrolling a window in firefox is sufficient to start it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Fri Nov 28 00:00:27 2014 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397178 Title: kubuntu 14.10 plasma 5 spins up PowerMizer Status in xorg package in Ubuntu: New Bug description: I have installed 14.10 Plasma 5 on my laptop, which is a vintage 2011 System 76. Of greatest significance is that it has an nvidia 560M graphics card in it. When I first installed 14.04, I noticed that the PowerMizer report of the NVIDIA X Server Settings would report that the graphics chip's clock was more or less constantly spun up to its highest clock rate. Heat and power use were very high, and I constantly heard the fan running. I found there were two ways to fix this: (1) Add a file called 05-nvidia.conf to /usr/share/X11/xorg.conf.d containing the lines: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x; PowerMizerDefault=0x3; PowerMizerDefaultAC=0x3" EndSection This pegged the graphics card at its lowest possible clock rate, which was adequate for most things but sometimes led to bad playback on some videos. See: https://forums.opensuse.org/showthread.php/410089-nvidia- powermizer-how-tweak (2) Revert to the 304 driver. This still spun up to high clock rates a bit more often than it seemed to need to, but was fairly reasonable otherwise. I expected that this would soon be rectified, since I saw that version 337.25 of the driver allegedly fixed some issue with performance in KDE: http://www.nvidia.com/download/driverResults.aspx/76278/en-us Jump ahead to yesterday when I installed 14.10 plasma 5 - I noticed that even with the 304 driver the PowerMizer reported the clock at its highest rate. With nothing moving on the screen at all and my not touching the mouse, it was pegged. I found that even installing the xorg-edgers driver (340 I believe) had no effect. Furthermore, 340 did not respond to the xorg.conf settings file above. The only way I can get plasma 5 to run reasonably on this machine is to revert to
[Touch-packages] [Bug 1342981] Re: Korean layout for Ubuntu Touch
@danielholm Thanks I'll contact the people who committed for Serbian keyboard. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1342981 Title: Korean layout for Ubuntu Touch Status in Ubuntu Keyboard: Confirmed Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: Ubuntu Touch currently lacks Korean keyboard layout. As Korean translation for Ubuntu Touch is almost done, Korean keyboard layout is the only obstacle to mass deployment of Ubuntu Touch in Korea. It is assumed that Korean layout in 'Onboard' (in Ubuntu Desktop) may be handy for devs to base off the new Korean mobile keyboard layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1342981/+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 1397172] [NEW] kubuntu 14.10 plasma 5 iso doesn't start X
Public bug reported: This is easy to reproduce: Burn a kubuntu 14.10 plasma 5 ISO, downloaded from here: http://www.kubuntu.org/news/kubuntu-14.10 Boot from it. X will not start, and the machine falls to a command prompt. Typing startx starts everything and it's possible to proceed. I should note that that my machine has an nvidia 560M graphics card in it, and is running the nouveau driver on the ISO. Rick Timmis on the kubuntu-developer list notes: > I can confirm, same problem install fails on init-rcd scriot, and complains > about saned, and drops to command prompt. I> too typed startx, and was off and running again, amd64 iso, which is 1.2Gd a DVD image. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 27 23:28:00 2014 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397172 Title: kubuntu 14.10 plasma 5 iso doesn't start X Status in “xorg” package in Ubuntu: New Bug description: This is easy to reproduce: Burn a kubuntu 14.10 plasma 5 ISO, downloaded from here: http://www.kubuntu.org/news/kubuntu-14.10 Boot from it. X will not start, and the machine falls to a command prompt. Typing startx starts everything and it's possible to proceed. I should note that that my machine has an nvidia 560M graphics card in it, and is running the nouveau driver on the ISO. Rick Timmis on the kubuntu-developer list notes: > I can confirm, same problem install fails on init-rcd scriot, and complains about saned, and drops to command prompt. I> too typed startx, and was off and running again, amd64 iso, which is 1.2Gd a DVD image. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 27 23:28:00 2014 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1397172/+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 1363421] Re: Unity Doesn't Start on 14.10 System
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1363421] Re: Unity Doesn't Start on 14.10 System
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363421/+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 1374133] Re: Mouse unusable when Plantronics W710 USB headset connected via USB
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1374133 Title: Mouse unusable when Plantronics W710 USB headset connected via USB Status in “xorg” package in Ubuntu: Expired Bug description: If I plug in my Plantronics W710 USB headset to a USB port, the mouse can move on the screen, but, cannot click anything ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 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: Thu Sep 25 16:20:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0984] InstallationDate: Installed on 2014-06-10 (107 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=f6dcf642-7422-4950-8b4b-13cb4cc6e761 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20e dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD3H 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.:bvrF20e:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 25 07:31:13 2014 xserver.configfile: default xserver.errors: [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1374133/+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.
[Touch-packages] [Bug 1397166] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all
Public bug reported: the dell is connected to a stereo amp with speakers and sub-woofer. it plays sounds for Rythnmbox, email and system, but did not play sound of the dvd. it did play the video. not familar with SPDIF. last ran FreeBSD servers and workstation, no music or dvds. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavanas2396 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 27 22:19:25 2014 InstallationDate: Installed on 2014-11-25 (2 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavanas2396 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-11-26 (2 days ago) dmi.bios.date: 08/04/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0DR845 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1397166 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “pulseaudio” package in Ubuntu: New Bug description: the dell is connected to a stereo amp with speakers and sub-woofer. it plays sounds for Rythnmbox, email and system, but did not play sound of the dvd. it did play the video. not familar with SPDIF. last ran FreeBSD servers and workstation, no music or dvds. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavanas2396 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 27 22:19:25 2014 InstallationDate: Installed on 2014-11-25 (2 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pavanas2396 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-11-26 (2 days ago) dmi.bios.date: 08/04/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0DR845 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1397166/+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 1397158] Re: Sound file recorded by arecord has noises.
** Attachment added: "Alsa codec." https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1397158/+attachment/4269943/+files/card1-codec%230 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1397158 Title: Sound file recorded by arecord has noises. Status in “alsa-utils” package in Ubuntu: New Bug description: Type command "arecord test.wav" in terminal, recording a sound, then pressing "ctrl+c" to end the recording. Using "aplay test.wav" to play itl, find the sounds record play has noises. Adjust input volume (even by alsamixer) dose not help to the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1397158/+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 1397158] [NEW] Sound file recorded by arecord has noises.
Public bug reported: Type command "arecord test.wav" in terminal, recording a sound, then pressing "ctrl+c" to end the recording. Using "aplay test.wav" to play itl, find the sounds record play has noises. Adjust input volume (even by alsamixer) dose not help to the issue. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Attachment added: "test.wav" https://bugs.launchpad.net/bugs/1397158/+attachment/4269942/+files/test.wav -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1397158 Title: Sound file recorded by arecord has noises. Status in “alsa-utils” package in Ubuntu: New Bug description: Type command "arecord test.wav" in terminal, recording a sound, then pressing "ctrl+c" to end the recording. Using "aplay test.wav" to play itl, find the sounds record play has noises. Adjust input volume (even by alsamixer) dose not help to the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1397158/+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 1371159] Re: MacBookPro 11, 1 (Haswell, retina) fails to both suspend and hibernate with ubuntu 14.04
While I'd love to try out the new kernel, I do not know how to install the proprietary wireless driver Broadcomm 802.11 along with that kernel. Is there perhaps a guide somewhere that details all the necessary commands? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1371159 Title: MacBookPro 11,1 (Haswell, retina) fails to both suspend and hibernate with ubuntu 14.04 Status in “pm-utils” package in Ubuntu: Confirmed Bug description: Cannot make a MacBookPro 11,1 suspend. 1. When putting the lid down, acpi_listen prints: $ acpi_listen button/lid LID close button/lid LID open ... so the lid is signalling correctly. Upon opening, the screensaver prompt is present, and typing in the password brings me back to the desktop. Nothing is found in dmesg. 2. When choosing "suspend" from the top-right power menu, the screen goes black and shortly lights up again, showing the screensaver login prompt. Typing in the password brings me back to the desktop as if nothing had happened. 3. To remark that the power menu in the System Settings shows sometimes "Suspend" as greyed out, and hibernate is not listed. Perhaps this is related to the suspend process taking very long (minutes) as reported in other bugs, but I have never waited so long to find out. 4. When attempting to hibernate instead, using: $ sudo pm-hibernate ... something similar to triggering a suspend happens, but this time dmesg lists one error: [ 1434.487141] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed register before writing to 2030 The whole relevant part of the dmesg is below, containing the sequence towards hibernation and then the sequence towards power up, cropped at the CPUs. [ 1434.121698] init: anacron main process (6746) killed by TERM signal [ 1434.160094] PM: Syncing filesystems ... done. [ 1434.164415] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 1434.166115] PM: Marking nosave pages: [mem 0x00058000-0x00058fff] [ 1434.166116] PM: Marking nosave pages: [mem 0x0008f000-0x0008] [ 1434.166117] PM: Marking nosave pages: [mem 0x0009f000-0x000f] [ 1434.166119] PM: Marking nosave pages: [mem 0x8ad14000-0x8ad52fff] [ 1434.166121] PM: Marking nosave pages: [mem 0x8ad62000-0x8ad75fff] [ 1434.166122] PM: Marking nosave pages: [mem 0x8ad77000-0x8ad8efff] [ 1434.166123] PM: Marking nosave pages: [mem 0x8af4b000-0x8afe4fff] [ 1434.166125] PM: Marking nosave pages: [mem 0x8b00-0x] [ 1434.166977] PM: Basic memory bitmaps created [ 1434.167010] PM: Preallocating image memory... done (allocated 872683 pages) [ 1434.484991] PM: Allocated 3490732 kbytes in 0.31 seconds (11260.42 MB/s) [ 1434.484993] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 1434.486307] Suspending console(s) (use no_console_suspend to debug) [ 1434.487014] mei_me :00:16.0: H_RDY is not cleared 0x80141418 [ 1434.487141] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed register before writing to 2030 [ 1435.603939] PM: freeze of devices complete after 1118.720 msecs [ 1435.604106] PM: late freeze of devices complete after 0.166 msecs [ 1435.604950] PM: noirq freeze of devices complete after 0.843 msecs [ 1435.605211] ACPI: Preparing to enter system sleep state S4 [ 1435.605985] PM: Saving platform NVS memory [ 1435.606140] Disabling non-boot CPUs ... [ 1435.607323] kvm: disabling virtualization on CPU1 [ 1435.607606] smpboot: CPU 1 is now offline [ 1435.608996] kvm: disabling virtualization on CPU2 [ 1435.710785] smpboot: CPU 2 is now offline [ 1435.712130] kvm: disabling virtualization on CPU3 [ 1435.814678] smpboot: CPU 3 is now offline [ 1435.815042] PM: Creating hibernation image: [ 1435.994507] PM: Need to copy 871520 pages [ 1435.994508] PM: Normal pages needed: 871520 + 1024, available pages: 3299080 [ 1436.710789] PM: Hibernation image created (871520 pages copied) [ 1435.816195] Enabling non-boot CPUs ... [ 1435.816221] x86: Booting SMP configuration: [ 1435.816222] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 1435.828025] kvm: enabling virtualization on CPU1 [ 1435.830204] CPU1 is up [ 1435.830216] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 1435.842013] kvm: enabling virtualization on CPU2 [ 1435.844227] CPU2 is up [ 1435.844239] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 1435.856037] kvm: enabling virtualization on CPU3 [ 1435.858227] CPU3 is up [ 1435.861484] ACPI: Waking up from system sleep state S4 Any hints towards getting suspend or hibernate working would be very appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 No
[Touch-packages] [Bug 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)
** Changed in: gnome-bluetooth Status: Unknown => New ** Changed in: gnome-bluetooth Importance: Unknown => Medium -- 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/1035431 Title: bluetooth-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in “bluez” package in Ubuntu: Fix Released Status in “gnome-bluetooth” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Triaged Status in “gnome-bluetooth” source package in Precise: Triaged Status in “bluez” source package in Trusty: In Progress Status in “gnome-bluetooth” source package in Trusty: In Progress Bug description: [Impact] * Fixes issues connecting bluetooth devices using SSP (Simple Secure Pairing); which does include many newer bluetooth devices, especially keyboards. [Test Case] * Try to connect a bluetooth keyboard using the wizard; especially one of the following models: Logitech Bluetooth Keyboard K760 Logitech Bluetooth Keyboard K810 HP Bluetooth Keyboard K4000 [Regression Potential] * It must be ensured that keyboards that could already be paired successfully still work properly; specifically, especially for keyboards but for any other devices, that pairing still works despite changes to the SSP code. [Other Info] --- When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1397149] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all
Public bug reported: No sound from Rythembox only. Sound ok with everything else. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gman 2034 F pulseaudio /dev/snd/pcmC0D0p: gman 2034 F...m pulseaudio CurrentDesktop: X-Cinnamon CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Nov 27 20:16:58 2014 InstallationDate: Installed on 2014-11-21 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gman 2034 F pulseaudio /dev/snd/pcmC0D0p: gman 2034 F...m pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0HC416 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/01/2006:svnDellInc.:pnMXC051:pvr:rvnDellInc.:rn0HC416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXC051 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty -- 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/1397149 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: No sound from Rythembox only. Sound ok with everything else. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gman 2034 F pulseaudio /dev/snd/pcmC0D0p: gman 2034 F...m pulseaudio CurrentDesktop: X-Cinnamon CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Nov 27 20:16:58 2014 InstallationDate: Installed on 2014-11-21 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gman 2034 F pulseaudio /dev/snd/pcmC0D0p: gman 2034 F...m pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0HC416 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd01/01/2006:svnDellInc.:pnMXC051:pvr:rvnDellInc.:rn0HC416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXC051 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1397149/+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 1020414] Re: Update to 1.7
** Changed in: libopenobex (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1020414 Title: Update to 1.7 Status in “libopenobex” package in Ubuntu: Triaged Status in “libopenobex” package in Debian: New Bug description: Update to 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1020414/+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 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)
** Bug watch added: GNOME Bug Tracker #740829 https://bugzilla.gnome.org/show_bug.cgi?id=740829 ** Changed in: gnome-bluetooth Importance: Undecided => Unknown ** Changed in: gnome-bluetooth Status: New => Unknown ** Changed in: gnome-bluetooth Remote watch: None => GNOME Bug Tracker #740829 ** Bug watch added: GNOME Bug Tracker #740829 https://bugzilla.gnome.org/show_bug.cgi?id=740829 -- 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/1035431 Title: bluetooth-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in “bluez” package in Ubuntu: Fix Released Status in “gnome-bluetooth” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Triaged Status in “gnome-bluetooth” source package in Precise: Triaged Status in “bluez” source package in Trusty: In Progress Status in “gnome-bluetooth” source package in Trusty: In Progress Bug description: [Impact] * Fixes issues connecting bluetooth devices using SSP (Simple Secure Pairing); which does include many newer bluetooth devices, especially keyboards. [Test Case] * Try to connect a bluetooth keyboard using the wizard; especially one of the following models: Logitech Bluetooth Keyboard K760 Logitech Bluetooth Keyboard K810 HP Bluetooth Keyboard K4000 [Regression Potential] * It must be ensured that keyboards that could already be paired successfully still work properly; specifically, especially for keyboards but for any other devices, that pairing still works despite changes to the SSP code. [Other Info] --- When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
The workaround to put export SSH_AUTH_SOCK=0 in my .bashrc also for me on 14.04 with the following versions: $ ssh -V OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 $ uname -a Linux mycomputer 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1390645] Re: Window contents sometimes not in right position to window frame
** Tags added: new-decorations -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390645 Title: Window contents sometimes not in right position to window frame Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: in Ubuntu 14.10, Window contents go out of position (not centered properly), and it affects several applications on my system (such as chromium/chrome, several emulators [such as visualboyadvance and fceux], and processing to name a couple To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390645/+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 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
I have the sam problem with Ubuntu 14.10 on a Thinkpad S540. I did a fresh install of Ubuntu, I am running Ubuntu only, no Dual Boot. -- 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/1320020 Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I can get perfect sound through headphones, and the kernel recognizes the internal speaker, but nothing is ever played through it. I have personally tested a pair of earbuds to make sure that sound could play through the headphone port, and that isn't a problem. The sound driver just refuses to recognize the existence of the speaker, even though the kernel does. I wouldn't be surprised if the last upstream update had something to do with it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio CurrentDesktop: GNOME Date: Thu May 15 18:07:52 2014 InstallationDate: Installed on 2014-01-29 (106 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago) dmi.bios.date: 03/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0M7CYJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1470 dmi.product.version: A05123 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
OK, the only symptom I saw is the *dash* not being there, not the whole unity8 UI, and that would be bug #1394208 -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
I just installed fresh utopic and followed the steps, everything worked fine here. To clarify: you don't even get the panel / welcome screen / greeter, the whole "screen" of the emulator is blank? Is that permanent? If you go "sudo stop lightdm; sudo start lightdm", does it come back? How about "stop unity8; start unity8"? If you *do* see the panel, just no dash, does "restart unity8-dash" help? I'll be trying a few more times here, recreating the emulator and starting it multiple times, maybe I'll get somewhere. -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1346734] Re: Unprivileged LXC containers don't work under systemd
The above patches are included in https://launchpad.net/ubuntu/+source/systemd/215-6ubuntu2, but they still don't work quite right: They seem to work well through VT logins and ssh, but not through lightdm. There's some race condition somewhere which removes PIDs from the session cgroup controllers again and moves them back to either or /user.slice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1346734 Title: Unprivileged LXC containers don't work under systemd Status in “systemd” package in Ubuntu: In Progress Bug description: With systemd 208, unprivileged containers stop working when running under systemd (working fine under upstart with cgmanager). Quoting Stephane Graber: In this setup, things don't work nearly as well. On login I'm only placed into the name=systemd cgroup and not in any of the others, which means that unprivileged LXC isn't usable. Martin suggested setting JoinControllers in /etc/systemd/system.conf but upon closer inspection, this isn't at all what we want. This setting is used to tell systemd what controllers to co-mount, by default this is set to cpu,cpuset (which caused the earlier cgmanager breakage). Even though this option isn't helpful for what we want (i.e. setting the list of cgroup controllers the first PID of a user session should be added to), we should nonetheless set it to an empty string which should instruct systemd not to co-mount any controller, therefore giving us a more reliable behavior (identical to what we have in the upstart world and unlikely to confuse lxc and other stuff doing direct cgroup access). Additionally, we need to find an equivalent to our good old "Controllers" logind.conf option, or re-introduce it or just patch logind so that it will always join all the controllers (similar to what the shim does). == Actions == * Update systemd.conf to set JoinControllers to an empty value. * Make it so new user sessions are joined to all the available controllers by doing one of the following: - Find the magic undocumented config variable - Re-introduce the "Controllers" option in logind.conf - Patch logind to have it always join all available controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346734/+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 1356840] Re: compiz+gedit mouse curser disappearing
BTW, the bug is still the same in Ubuntu 14.10. It also affects systems with i915 video driver (13" Macbook Pro with Intel Iris Graphics). -- 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/1356840 Title: compiz+gedit mouse curser disappearing Status in “xorg” package in Ubuntu: Confirmed Bug description: After typing some text in gedit, the mouse curser does not appear. After switching to another window and back, everything is normal again. I use Ubuntu 14.04 with Unity, with the included free driver for AMD video cards. No related costumized packages installed. I have no idea whether it is gedit or compiz or Xorg, I could not reproduce the bug with other programs (text boxes in browser, libreoffice etc.). My other computer (Thinkpad X60 with Intel video card) does not show this behavior. I made a screencast to demonstrate the phenomenon: - First few seconds: Curser is fine - After typing some characters: Curser hardly visible - After switching windows: Everything fine again Please try to reproduce the behavior. The bug has been around for some months, not only the latest version, but now I got really annoyed by not being able to use the mouse to select text. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Thu Aug 14 13:32:23 2014 DistUpgraded: 2014-04-23 10:07:08,892 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-26-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-33-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e174] InstallationDate: Installed on 2011-10-18 (1030 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic root=UUID=427dcfbf-6f4e-49e5-abe1-1b50a9d37e88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-23 (113 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-V EVO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 14 13:12:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1356840/+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 1020414] Re: Update to 1.7
** Bug watch added: Debian Bug tracker #717459 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717459 ** Also affects: libopenobex (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717459 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1020414 Title: Update to 1.7 Status in “libopenobex” package in Ubuntu: Triaged Status in “libopenobex” package in Debian: Unknown Bug description: Update to 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1020414/+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 1396270] Re: specifying AppArmorProfile doesn't result in processes launched under the named profile
This bug was fixed in the package systemd - 215-6ubuntu2
---
systemd (215-6ubuntu2) vivid; urgency=medium
[ Martin Pitt ]
* Merge fixes from Debian master.
* Put user slices into all cgroup controllers. This makes unprivileged user
LXC containers work under systemd. (LP: #1396270)
* boot-and-services autopkgtest: Test AppArmor confined units (LP #1396270)
[ Marc Deslauriers ]
* Build-depend on libapparmor-dev to enable AppArmor support. (LP: #1396270)
systemd (215-7) UNRELEASED; urgency=medium
[ Martin Pitt ]
* Add myself to Uploaders.
* Add boot-and-services autopkgtest: Check booting with systemd-sysv and
that the most crucial services behave as expected.
* logind autopkgtest: Fix stderr output in waiting loop for scsi_debug.
* Add nspawn test to boot-and-services autopkgtest.
* Make systemd-nspawn@.service work out of the box: (Closes: #770275)
- Pre-create /var/lib/container with a secure mode (0700) via tmpfiles.d.
- Add new try-{guest,host} modes for --link-journal to silently skip
setting up the guest journal if the host has no persistant journal.
- Extend boot-and-services autopkgtest to cover systemd-nspawn@.service.
* Cherry-pick upstream patch to fix SELinux unit access check (regression
in 215).
[ Jon Severinsson]
* Add /run/shm -> /dev/shm symlink in debian/tmpfiles.d/debian.conf. This
avoids breakage in Jessie for packages which still refer to /run/shm, and
while https://wiki.debian.org/ReleaseGoals/RunDirectory is still official.
(LP: #1320534, Closes: #674755).
-- Martin PittThu, 27 Nov 2014 16:38:55 +0100
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1396270
Title:
specifying AppArmorProfile doesn't result in processes launched under
the named profile
Status in “systemd” package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce
1. grab attached tarball and unpack in /tmp:
tar -zxvf /tmp/test.tar.gz
2. cd /tmp/test
3. Load the apparmor profile:
sudo apparmor_parser -r ./apparmor.profile
4. verify you see 'test-service' profile is loaded via 'sudo aa-status'. Eg:
$ sudo aa-status
apparmor module is loaded.
6 profiles are loaded.
6 profiles are in enforce mode.
...
test-service
...
5. enable the systemd service file:
$ cat ./test.service
[Unit]
Description=test webserver
[Service]
Environment=PYTHONDONTWRITEBYTECODE=1
ExecStart=/tmp/test/bin/webserver
Restart=on-failure
WorkingDirectory=/tmp/test/www
AppArmorProfile=test-service
[Install]
WantedBy=multi-user.target
$ sudo cp ./test.service /etc/systemd/system/
$ sudo systemctl enable test.service
6. start the service
$ sudo systemctl start test.service
$ sudo systemctl --no-pager status test.service
● test.service - test webserver
Loaded: loaded (/etc/systemd/system/test.service; enabled)
Active: active (running) since Tue 2014-11-25 17:33:51 UTC; 4min 8s ago
Main PID: 1246 (webserver)
CGroup: /system.slice/test.service
└─1246 /usr/bin/python3 /tmp/test/bin/webserver
Nov 25 17:33:51 localhost.localdomain systemd[1]: Started test
webserver.
7. verify that the service is confined (use Main PID from the last step. You
can also use aa-status):
$ ps -Z 1246
LABEL PID TTY STAT TIME COMMAND
unconfined 1246 ?Ss 0:00 /usr/bin/python3
/tmp/test/bin/webserver
Because the service file uses 'AppArmorProfile=test-service' and the
'test-service' profile is already loaded into the kernel, I would
expect /tmp/test/bin/webserver to be running under the 'test-service'
label, not 'unconfined'.
Note: you can manually start the webserver under apparmor using aa-exec. Eg:
$ sudo aa-exec -p test-service /tmp/test/bin/webserver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1396270/+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 1390645] Re: Window contents sometimes not in right position to window frame
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Changed in: unity Status: Incomplete => Confirmed ** Changed in: unity Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390645 Title: Window contents sometimes not in right position to window frame Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: in Ubuntu 14.10, Window contents go out of position (not centered properly), and it affects several applications on my system (such as chromium/chrome, several emulators [such as visualboyadvance and fceux], and processing to name a couple To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390645/+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 1392552] Re: Minimize or hide all windows for a tile from the launcher tile context menu
** Changed in: unity Importance: Low => Wishlist ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** 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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1392552 Title: Minimize or hide all windows for a tile from the launcher tile context menu Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Wishlist: Just as there is a "Quit" option in the right-click context menu for every active tile, I would like to see a "Minimize [all]" or "Hide [all]" option from this context menu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1392552/+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 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
** Changed in: linux-mako (Ubuntu) Assignee: Colin Ian King (colin-king) => Paolo Pisati (p-pisati) ** Changed in: linux-mako (Ubuntu RTM) Assignee: Colin Ian King (colin-king) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: Confirmed Status in “android” package in Ubuntu RTM: Fix Released Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: Fix Released Status in “linux-mako” package in Ubuntu RTM: Confirmed Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh" The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1310598] Re: AppArmor python tools fail to parse mounts with UTF-8 non-ascii characters
After some months where it didn't seem to crash -or at least apport
didn't report anything-, now this is crashing again with the same stack
trace about reading my UTF-8/non-ascii mounts.
I'm sending new apports automatic crash reports.
Although, Christian, I would find it normal that it crashes with
LANG=C aa-status
... because that defaults to english/ASCII, and then you should NOT have
non-ascii mounts.
If I do
aa-status (implied with my locale fr_FR.UTF-8) it works fine and says:
apparmor module is loaded.
22 profiles are loaded.
22 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/evince
/usr/bin/evince-previewer
/usr/bin/evince-previewer//sanitized_helper
/usr/bin/evince-thumbnailer
/usr/bin/evince-thumbnailer//sanitized_helper
/usr/bin/evince//sanitized_helper
/usr/bin/vidalia
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/lib/cups/backend/cups-pdf
/usr/lib/lightdm/lightdm-guest-session
/usr/lib/lightdm/lightdm-guest-session//chromium
/usr/lib/telepathy/mission-control-5
/usr/lib/telepathy/telepathy-*
/usr/lib/telepathy/telepathy-*//pxgsettings
/usr/lib/telepathy/telepathy-*//sanitized_helper
/usr/lib/telepathy/telepathy-ofono
/usr/sbin/cups-browsed
/usr/sbin/cupsd
/usr/sbin/tcpdump
system_tor
0 profiles are in complain mode.
4 processes have profiles defined.
4 processes are in enforce mode.
/sbin/dhclient (1375)
/usr/lib/telepathy/mission-control-5 (2551)
/usr/sbin/cups-browsed (1371)
/usr/sbin/cupsd (2606)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
Thus, although there is a crash reported at startup, it seems that I still have
app-armor up an running.
The bug might then be at startup. Could be that when aa is run at
startup the language is not yet defined, thus it is running with default
LANG=C and failing (which is then kind of "normal situation" as the
mounts can use any encoding they see fit!).
I'll try to investigate a little bit more around that idea.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1310598
Title:
AppArmor python tools fail to parse mounts with UTF-8 non-ascii
characters
Status in AppArmor Linux application security framework:
Triaged
Status in “apparmor” package in Ubuntu:
Triaged
Bug description:
Version:
14.04 Fresh Install.
$ uname -a
Linux alain-Desktop 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
AppArmor crashes with this stack trace:
PythonArgs: ['/usr/sbin/aa-status']
Traceback:
Traceback (most recent call last):
File "/usr/sbin/aa-status", line 194, in
commands[cmd]()
File "/usr/sbin/aa-status", line 17, in cmd_enabled
if get_profiles() == {}:
File "/usr/sbin/aa-status", line 82, in get_profiles
apparmorfs = find_apparmorfs()
File "/usr/sbin/aa-status", line 137, in find_apparmorfs
for p in open("/proc/mounts").readlines():
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1200:
ordinal not in range(128)
That is because I have a UTF-8 non-Ascii character in one of my mounts:
$ mount
/dev/sdb1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
(...)
/dev/sda6 on /home/alain/Vidéos type ext4 (rw,relatime,errors=remount-ro)
(...)
The Python code of aastatus near line 135 shows:
def find_apparmorfs():
'''Finds AppArmor mount point'''
for p in open("/proc/mounts").readlines():
if p.split()[2] == "securityfs" and \
os.path.exists(os.path.join(p.split()[1], "apparmor")):
return os.path.join(p.split()[1], "apparmor")
return False
So if I do:
$ cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
(...)
/dev/sda6 /home/alain/Vidéos ext4 rw,relatime,errors=remount-ro,data=ordered
0 0
(...)
There is indeed a line with a 'é'
UTF-8 code of the 'é' is 0xC3 0xA9
But apparently the call to .readlines() is set as ASCII and hence does
NOT support the 0xC3 (first byte of the 'é' in UTF-8) and then it
crashes.
I assume the solution could be to correctly read as UTF-8 as there are
some non-Americans/English out there!
Sorry my knowledge of Python is just enough to understand the bug, and
not enough to submit a patch.
Regards.
Alain
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1310598/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscr
[Touch-packages] [Bug 1396166] Re: [webapps-container] Stops prematurely for all default webapp on desktop
This bug was fixed in the package webbrowser-app - 0.23+15.04.20141126.1-0ubuntu1 --- webbrowser-app (0.23+15.04.20141126.1-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Alexandre Abreu ] * Fix desktop web container with local webapp install on desktop (LP: #1396166) * Adds a click hook for webapps that currently handles uninstall cleanup options -- Ubuntu daily releaseWed, 26 Nov 2014 15:55:49 + ** Changed in: webbrowser-app (Ubuntu) Status: New => Fix Released -- 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/1396166 Title: [webapps-container] Stops prematurely for all default webapp on desktop Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: In Vivid, the container now fails to properly lookup webapps and exists prematurely when no homepage is provided (which is the case for default installed webapps). To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1396166/+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 1356840] Re: compiz+gedit mouse curser disappearing
I knew I wasn't the only one! Very annoying bug -- 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/1356840 Title: compiz+gedit mouse curser disappearing Status in “xorg” package in Ubuntu: Confirmed Bug description: After typing some text in gedit, the mouse curser does not appear. After switching to another window and back, everything is normal again. I use Ubuntu 14.04 with Unity, with the included free driver for AMD video cards. No related costumized packages installed. I have no idea whether it is gedit or compiz or Xorg, I could not reproduce the bug with other programs (text boxes in browser, libreoffice etc.). My other computer (Thinkpad X60 with Intel video card) does not show this behavior. I made a screencast to demonstrate the phenomenon: - First few seconds: Curser is fine - After typing some characters: Curser hardly visible - After switching windows: Everything fine again Please try to reproduce the behavior. The bug has been around for some months, not only the latest version, but now I got really annoyed by not being able to use the mouse to select text. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Thu Aug 14 13:32:23 2014 DistUpgraded: 2014-04-23 10:07:08,892 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-26-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-33-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e174] InstallationDate: Installed on 2011-10-18 (1030 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic root=UUID=427dcfbf-6f4e-49e5-abe1-1b50a9d37e88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-23 (113 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-V EVO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 14 13:12:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1356840/+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 1356840] Re: compiz+gedit mouse curser disappearing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1356840 Title: compiz+gedit mouse curser disappearing Status in “xorg” package in Ubuntu: Confirmed Bug description: After typing some text in gedit, the mouse curser does not appear. After switching to another window and back, everything is normal again. I use Ubuntu 14.04 with Unity, with the included free driver for AMD video cards. No related costumized packages installed. I have no idea whether it is gedit or compiz or Xorg, I could not reproduce the bug with other programs (text boxes in browser, libreoffice etc.). My other computer (Thinkpad X60 with Intel video card) does not show this behavior. I made a screencast to demonstrate the phenomenon: - First few seconds: Curser is fine - After typing some characters: Curser hardly visible - After switching windows: Everything fine again Please try to reproduce the behavior. The bug has been around for some months, not only the latest version, but now I got really annoyed by not being able to use the mouse to select text. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Thu Aug 14 13:32:23 2014 DistUpgraded: 2014-04-23 10:07:08,892 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-26-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-33-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e174] InstallationDate: Installed on 2011-10-18 (1030 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic root=UUID=427dcfbf-6f4e-49e5-abe1-1b50a9d37e88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-23 (113 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-V EVO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 14 13:12:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1356840/+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 1393024] Re: Graphical corruption with hidpi scaling
Can you provide a screenshot showing the glitch? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1393024 Title: Graphical corruption with hidpi scaling Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: With a hidpi scaling greater or equal than 2 there is graphical corruption of the window borders in gtk3 apps. Steps to reproduce: 1. Set hidpi scaling to 2. 2. Enlarge a window for nautilus or eye of gnome. Probably it is necessary to do resize the window more than one time to spot the problem. 3. See corrupted window border on the right and/or the bottom. Expected behavior: Clean rendering Ubuntu 14.10 64 Bit Compiz 0.9.12+14.10.20140918-0ubuntu1 Unity 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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: Sat Nov 15 16:36:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e] InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=2a652086-a4da-44ed-ae7f-7b994401ef8b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-990FXA-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 15:00:14 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1393024/+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 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
> \o/
Thanks again :)
> That is in most cases the *desired* behavior,
On today's systems, I don't think so. Debian and Ubuntu run a dnsmasq
instance by default, with the only nameserver in /etc/resolv.conf being
127.0.1.1. Rather than overwrite this local caching server with any
remote one, it makes more sense to reconfigure *it* to include/remove
the new nameservers. Not only can you continue to benefit from the
cache, but it's smart enough to route lookups to different servers
depending on the domain. That's a benefit because:
> since only the VPN nameservers have name information about both the VPN and
> the Internet.
> Also, under what circumstances do you not trust the VPN with your DNS traffic?
Well, if you work at home and connect to an employer's VPN, what earthly
reason is there to send them all your Internet DNS lookups? It's far
preferable to only use their nameservers just for employer.com and 99.10
.in-addr.arpa, or whatever. Not only that, but if you have a local
nameserver that provides local names, you really don't want to wait for
the remote to time out before querying those, either.
That's exactly what NetworkManager does, simply by sending dnsmasq a
DBus message with the new servers, and (optionally) what zones to use
them for. However, it only works if the specific plugin in use is
excluded from resolvconf's ppp/ip-up script.
Come to think of it, there's a growing number of NM VPN plugins in the
repos nowadays. There has to be a better way of handling this than
excluding every one specifically...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
Status in “resolvconf” package in Ubuntu:
Confirmed
Bug description:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part
of Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
< nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
> nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP
one as well so that it can work out of the box on Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+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 1394737] Re: Launcher: Window list, provide close window option
** Changed in: unity Status: New => Opinion ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1394737 Title: Launcher: Window list, provide close window option Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: When one right clicks on a launcher icon in unity, you see the options and a list of open windows of the application with title. What would be great would be a way to quick close windows from there, e.g. be pressing ctrl and clicking on the window (maybe also keep the menu open in case one wants to close more than one window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1394737/+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 1397065] Re: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1397065 Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “dbus” package in Ubuntu: New Bug description: I don't know what it is, my computer said to report the bug and I did it. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 27 18:32:47 2014 DuplicateSignature: package:dbus:1.8.8-1ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (264 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: dbus Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1397065/+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 1397065] [NEW] package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I don't know what it is, my computer said to report the bug and I did it. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 27 18:32:47 2014 DuplicateSignature: package:dbus:1.8.8-1ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (264 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: dbus Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-27 (60 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1397065 Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “dbus” package in Ubuntu: New Bug description: I don't know what it is, my computer said to report the bug and I did it. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 27 18:32:47 2014 DuplicateSignature: package:dbus:1.8.8-1ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (264 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: dbus Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1397065/+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 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
We've been exercising the rtm images that include the latest workaround now for a considerable amount of time repeating the test that originally triggered the issue. On mako, 2 devices running: device #1, 329 iterations - no corruption observed device #2, 251 iterations - no corruption observed And also on another spare device using rtm image, device #3, 176 iterations, - no corruption observed I can continue running these for another few days if need be, but I think it is fairly conclusive that the data=journal change prevents the apparmor metadata from ending up on the /var/lib/apparmor/profiles/* files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: Confirmed Status in “android” package in Ubuntu RTM: Fix Released Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: Fix Released Status in “linux-mako” package in Ubuntu RTM: Confirmed Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh"
[Touch-packages] [Bug 1395118] Re: ActionSelectionPopover does not handle the 'visible' property of actions properly
** Also affects: ubuntu-ui-toolkit (Ubuntu RTM)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1395118
Title:
ActionSelectionPopover does not handle the 'visible' property of
actions properly
Status in File Manager application for Ubuntu devices:
New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
New
Status in “ubuntu-ui-toolkit” package in Ubuntu RTM:
New
Bug description:
When setting the 'visible' property of an action in an ActionList of
an ActionSelectionPopover to false, the delegate will not be hidden
but instead be shown at the top of the list behind the first visible
delegate. (Check out the screenshot.)
Demo code (containing an outcommented workaround):
import QtQuick 2.3
import Ubuntu.Components 1.1
import Ubuntu.Components.Popups 1.0
import Ubuntu.Components.ListItems 1.0
MainView {
width: units.gu(50)
height: units.gu(75)
Page {
title: i18n.tr("ActionSelectionPopover Fix")
Button {
id: button
width: parent.width
text: i18n.tr("Show popover")
onClicked: {
PopupUtils.open(actionSelectionPopoverComponent, button)
}
}
Component {
id: actionSelectionPopoverComponent
ActionSelectionPopover {
actions: ActionList {
Action {
text: "Action one"
}
Action {
text: "Action two"
}
Action {
text: "Hidden action"
visible: false
}
}
// Uncomment the following for a temporary workaround:
//delegate: Empty {
//id: listItem
//Label {
//text: listItem.text
//anchors {
//verticalCenter: parent.verticalCenter
//horizontalCenter: parent.horizontalCenter
//}
//wrapMode: Text.Wrap
//color: Theme.palette.normal.overlayText
//}
///*! \internal */
//onTriggered: popover.hide()
//visible: enabled && ((action === undefined) ||
action.visible)
//height: visible ? implicitHeight : 0
//}
}
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1395118/+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 1369510] Re: dutch keyboard layout lacks a .com option
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1369510 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1369510 Title: dutch keyboard layout lacks a .com option Status in “ubuntu-keyboard” package in Ubuntu: Triaged Status in “ubuntu-keyboard” package in Ubuntu RTM: New Bug description: In terms of popularity I would think that when entering an email address .com is a popular option. A lot of people use services like hotmail.com or gmail.com, so the ubuntu-keyboard should have an option for entering .com quickly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1369510/+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 1342981] Re: Korean layout for Ubuntu Touch
It is actually quite easy to add support. You could look at this MR which was for adding a Serbian keyboard and do something similar for Korean: https://code.launchpad.net/~danilo/ubuntu-keyboard/serbian-layout/+merge/229876 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1342981 Title: Korean layout for Ubuntu Touch Status in Ubuntu Keyboard: Confirmed Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: Ubuntu Touch currently lacks Korean keyboard layout. As Korean translation for Ubuntu Touch is almost done, Korean keyboard layout is the only obstacle to mass deployment of Ubuntu Touch in Korea. It is assumed that Korean layout in 'Onboard' (in Ubuntu Desktop) may be handy for devs to base off the new Korean mobile keyboard layout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1342981/+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 1389792] Re: theme not found when using a user-defined theme
Jamie, for now the application can set the theme in the MainView, in Component.Completed. See examples/customtheme application from the branch attached to the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1389792 Title: theme not found when using a user-defined theme Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Status in “ubuntu-ui-toolkit” package in Ubuntu RTM: In Progress Bug description: This bugs makes it so that developers cannot update the theming, which can be pretty important for some people and also important for working around color scheme issues in the theming (I've filed other bugs on this). Attached is a very simple application that tries to define the Foo theme which is derived from the SuruDark theme. $ tar -zxvf ./theme-test.tar.gz ./theme-test/ ./theme-test/themes/ ./theme-test/themes/Foo/ ./theme-test/themes/Foo/parent_theme ./theme-test/themes/Foo/Palette.qml ./theme-test/themes/Foo/MainViewStyle.qml ./theme-test/main.qml $ cd theme-test/ $ qmlscene ./main.qml "Theme not found: " "themes.Foo" QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:330:9: QML AppHeader: Warning: Style PageHeadStyle.qml not found in theme themes.Foo file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:202:5: QML StyledItem: Warning: Style MainViewStyle.qml not found in theme themes.Foo QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:70:5: QML Binding: Binding loop detected for property "target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1389792/+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 1396062] Re: [SDK] Default appearance for text field
TextInput and TextEdit are the basic QtQuick components, TextField and TextArea are the components in our UI Toolkit based on them. The fact that they look and behave very different is not a bug. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1396062 Title: [SDK] Default appearance for text field Status in Ubuntu UX bugs: Triaged Status in “ubuntu-ui-toolkit” package in Ubuntu: Invalid Bug description: Default appearance for Text Input is different than the one displayed in the SDK. Currently it looks as it is disabled, rather than enabled. https://www.dropbox.com/sh/7fnssmbsyuc6c8l/AADiZ5i- pZbDcPaFBUKPmjaUa?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1396062/+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 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
** Branch linked: lp:~mardy/ubuntu-system-settings-online-accounts/rtm-
fixes
--
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/1376445
Title:
Addition of signon-apparmor-extension causes token lookup problems
Status in go-onlineaccounts:
Incomplete
Status in The Savilerow project:
Invalid
Status in ACL for signond, AppArmor backend:
Fix Released
Status in Online Accounts setup for Ubuntu Touch:
In Progress
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
In Progress
Status in “ubuntuone-credentials” package in Ubuntu:
Confirmed
Status in “signon-apparmor-extension” package in Ubuntu RTM:
Triaged
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu RTM:
New
Status in “ubuntuone-credentials” package in Ubuntu RTM:
Confirmed
Bug description:
As of image ~264 of ubuntu-touch, the signon-apparmor-extension
package is included. As a result, apps like pay-ui cannot find the
token any longer, and are not being notified that they are not allowed
to access the token. The following error appears in the payui log
file:
2014-10-01 19:15:51,550 - DEBUG -
../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
"Client has insuficient permissions to access the
service.Method:getAuthSessionObjectPath")
To manage notifications about this bug go to:
https://bugs.launchpad.net/go-onlineaccounts/+bug/1376445/+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 1394669] Re: 'Switch to default SIM' dialog is confusing
What happens if you tap "No" is that the system setting is switched to "Always ask". If you try now to make a phone call, you will be prompted with an other popup to select a SIM card. You can do this by tapping on one of the items beneath the header. However, I understand the confusion and I think the journey needs a UX refinement. ** Tags added: ota-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1394669 Title: 'Switch to default SIM' dialog is confusing Status in Ubuntu UX bugs: Triaged Status in “dialer-app” package in Ubuntu: New Bug description: If I press 'No' on that dialog, there is no way for this dialog to appear again, even changing the setting in system-settings has no effect. 0. Clean flash device. 1. Start dialer 2. A dialog appears to select default sim 3. Tap on 'No' button 4. Go to system settings and select 'Ask me each time' for outgoing calls. What happens: The sim prompt dialog never appears, no matter I toggle that setting. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: dialer-app 0.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 17:18:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394669/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
** Project changed: initramfs-tools => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in “initramfs-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Triaged Status in “os-prober” package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong uf
[Touch-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in “initramfs-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Triaged Status in “os-prober” package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|u
[Touch-packages] [Bug 1397029] [NEW] [USB-Audio - Plantronics C420, recording] Headphone Mic do not appear after connect
Public bug reported: When connecting external USB headphones, only headphones speakers appear as an option to output audio, but Microphone only appears internal. After executing "pulsaudio -k" microphone appears. Sometimes (could be unrelated) when external HDMI connector the audio HDMI output do not appear. I once solve it Suspending the laptop and bringing it back again, then the correct Audio Output options appear. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 27 09:06:40 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-31 (179 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:C420 successful Symptom_Card: Plantronics C420 - Plantronics C420 Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:C420 failed Symptom_Type: Only some of inputs are working Title: [USB-Audio - Plantronics C420, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0845MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0845MX:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1397029 Title: [USB-Audio - Plantronics C420, recording] Headphone Mic do not appear after connect Status in “alsa-driver” package in Ubuntu: New Bug description: When connecting external USB headphones, only headphones speakers appear as an option to output audio, but Microphone only appears internal. After executing "pulsaudio -k" microphone appears. Sometimes (could be unrelated) when external HDMI connector the audio HDMI output do not appear. I once solve it Suspending the laptop and bringing it back again, then the correct Audio Output options appear. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 27 09:06:40 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-31 (179 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:C420 successful Symptom_Card: Plantronics C420 - Plantronics C420 Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:C420 failed Symptom_Type: Only some of inputs are working Title: [USB-Audio - Plantronics C420, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0845MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0845MX:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1397029/+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 1277647] Re: Changing theme from Ambiance to SuruDark or SuruGradient in MainView's completion causes binding loops.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Zsombor Egri (zsombi)
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming
--
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/1277647
Title:
Changing theme from Ambiance to SuruDark or SuruGradient in MainView's
completion causes binding loops.
Status in Address Book App:
Fix Released
Status in “address-book-app” package in Ubuntu:
Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
In Progress
Bug description:
The following code snippet reproduces the error:
import QtQuick 2.0
import Ubuntu.Components 0.1
MainView {
width: units.gu(40)
height: units.gu(71)
Component.onCompleted: Theme.name = "Ubuntu.Components.Themes.SuruDark"
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1277647/+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 1374759] [NEW] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
You have been subscribed to a public bug: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 576.843535] hfs: can't find a HFS filesystem on dev sda4 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-18-generic 3.16.0-18.25 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2117 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 27 10:39:43 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-0
[Touch-packages] [Bug 1356779] Re: MainView.backgroundColor is not usable any more
It has been confirmed that this is caused when gradient background is set of the application, which loads SuruGradient theme. The theme is deprecated, and SuruDark or Ambiance theme should be used whenever appropriate. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress ** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1356779 Title: MainView.backgroundColor is not usable any more Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: Since the latest SDK updates, MainView.backgroundColor is not usable any more. It completely messes up the whole theming: For example setting a dark background causes: * Text in Dialogs to be unreadable * Header Popovers (the new ones) to turn purple(!) * Active ListItem's text color to be unreadable And the situation seems to get worse with each uitk update... Maybe the *color properties of the MainView should just be removed? If you think that should be kept but all the places that break should be fixed instead to make it work again, please let me know and I'll do my best to collect all the places it broke. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1356779/+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 1389792] Re: theme not found when using a user-defined theme
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1389792 Title: theme not found when using a user-defined theme Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Status in “ubuntu-ui-toolkit” package in Ubuntu RTM: In Progress Bug description: This bugs makes it so that developers cannot update the theming, which can be pretty important for some people and also important for working around color scheme issues in the theming (I've filed other bugs on this). Attached is a very simple application that tries to define the Foo theme which is derived from the SuruDark theme. $ tar -zxvf ./theme-test.tar.gz ./theme-test/ ./theme-test/themes/ ./theme-test/themes/Foo/ ./theme-test/themes/Foo/parent_theme ./theme-test/themes/Foo/Palette.qml ./theme-test/themes/Foo/MainViewStyle.qml ./theme-test/main.qml $ cd theme-test/ $ qmlscene ./main.qml "Theme not found: " "themes.Foo" QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:330:9: QML AppHeader: Warning: Style PageHeadStyle.qml not found in theme themes.Foo file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:202:5: QML StyledItem: Warning: Style MainViewStyle.qml not found in theme themes.Foo QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:70:5: QML Binding: Binding loop detected for property "target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1389792/+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 1309785] Re: blurry font as document is longer than one page and scroll bars appear
Thank you so much for the workaround! This was driving me nuts! Of course its going to take FOREVER for this to get fixed in the reps... #1 problem with linux. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1309785 Title: blurry font as document is longer than one page and scroll bars appear Status in GTK+ GUI Toolkit: Fix Released Status in “gtk+3.0” package in Ubuntu: Triaged Bug description: I have recently installed GNOME Ubuntu 14.04 and gEdit application seems to have a strange behavior whenever the document is longer than a page and vertical scroll bars appear on the screen (I just checked the same problem with long lines that enable horizontal scroll bars). To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1309785/+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 1213043] Re: Binding loop detected when changing backgroundColor of MainView dynamically
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1213043 Title: Binding loop detected when changing backgroundColor of MainView dynamically Status in Sudoku game for Ubuntu Touch: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: When changing the backgroundColor of MainView programmatically, a binding loop occurs: file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" To manage notifications about this bug go to: https://bugs.launchpad.net/sudoku-app/+bug/1213043/+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 1330510] Re: Valgrind warning when theme is changed from MainViewStyle.qml
Not checked with Valgrind, however the binding loops on properties were still there with the fix. The auto-theming got moved into MainView and is only applied for system themes. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1330510 Title: Valgrind warning when theme is changed from MainViewStyle.qml Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: We are getting this warning in valgrind (with Qt 5.3) ==20334== Invalid read of size 8 ==20334==at 0x581568A: QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (qrecursionwatcher_p.h:94) ==20334==by 0x57A5A82: QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) (qqmlincubator.cpp:357) ==20334==by 0x57A6215: QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) (qqmlincubator.cpp:95) ==20334==by 0x57A169C: QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) (qqmlcomponent.cpp:1072) ==20334==by 0x5DCE449: QQuickLoaderPrivate::_q_sourceLoaded() (qquickloader.cpp:721) ==20334==by 0x5DCE5E7: QQuickLoaderPrivate::load() (qquickloader.cpp:604) ==20334==by 0x581564D: QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (qqmlobjectcreator.cpp:1202) ==20334==by 0x57A1076: QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) (qqmlcomponent.cpp:932) ==20334==by 0x57A1108: QQmlComponentPrivate::completeCreate() (qqmlcomponent.cpp:968) ==20334==by 0x57A0FCF: QQmlComponent::create(QQmlContext*) (qqmlcomponent.cpp:795) ==20334==by 0x5DD538E: QQuickView::continueExecute() (qquickview.cpp:489) ==20334==by 0x5DD5AB3: QQuickViewPrivate::execute() (qquickview.cpp:133) ==20334==by 0x407045: startShell(int, char const**, void*) (main.cpp:162) ==20334==by 0x407A74: main (main.cpp:227) ==20334== Address 0x20df8968 is 104 bytes inside a block of size 112 free'd ==20334==at 0x4C2C2BC: operator delete(void*) (vg_replace_malloc.c:503) ==20334==by 0x5815FB0: QQmlObjectCreator::~QQmlObjectCreator() (qqmlobjectcreator.cpp:156) ==20334==by 0x57A52AA: QQmlIncubatorPrivate::clear() (qscopedpointer.h:62) ==20334==by 0x57A53C6: QQmlIncubator::clear() (qqmlincubator.cpp:577) ==20334==by 0x5DCD7CF: QQuickLoaderPrivate::clear() (qquickloader.cpp:95) ==20334==by 0x5DCEB02: QQuickLoader::setSourceComponent(QQmlComponent*) (qquickloader.cpp:472) Because MainViewStyle.qml is replacing the theme once it gets loaded (if it needs to go Dark) and we're basically changing the component in MainView.qml while the component is being loaded and it seems Qt doesn't like that. Not sure if it could be argued this is a Qt 5.3 bug, haven't tried if the warning is there in Qt 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1330510/+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 1330510] Re: Valgrind warning when theme is changed from MainViewStyle.qml
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1330510 Title: Valgrind warning when theme is changed from MainViewStyle.qml Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: We are getting this warning in valgrind (with Qt 5.3) ==20334== Invalid read of size 8 ==20334==at 0x581568A: QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (qrecursionwatcher_p.h:94) ==20334==by 0x57A5A82: QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) (qqmlincubator.cpp:357) ==20334==by 0x57A6215: QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) (qqmlincubator.cpp:95) ==20334==by 0x57A169C: QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) (qqmlcomponent.cpp:1072) ==20334==by 0x5DCE449: QQuickLoaderPrivate::_q_sourceLoaded() (qquickloader.cpp:721) ==20334==by 0x5DCE5E7: QQuickLoaderPrivate::load() (qquickloader.cpp:604) ==20334==by 0x581564D: QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (qqmlobjectcreator.cpp:1202) ==20334==by 0x57A1076: QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) (qqmlcomponent.cpp:932) ==20334==by 0x57A1108: QQmlComponentPrivate::completeCreate() (qqmlcomponent.cpp:968) ==20334==by 0x57A0FCF: QQmlComponent::create(QQmlContext*) (qqmlcomponent.cpp:795) ==20334==by 0x5DD538E: QQuickView::continueExecute() (qquickview.cpp:489) ==20334==by 0x5DD5AB3: QQuickViewPrivate::execute() (qquickview.cpp:133) ==20334==by 0x407045: startShell(int, char const**, void*) (main.cpp:162) ==20334==by 0x407A74: main (main.cpp:227) ==20334== Address 0x20df8968 is 104 bytes inside a block of size 112 free'd ==20334==at 0x4C2C2BC: operator delete(void*) (vg_replace_malloc.c:503) ==20334==by 0x5815FB0: QQmlObjectCreator::~QQmlObjectCreator() (qqmlobjectcreator.cpp:156) ==20334==by 0x57A52AA: QQmlIncubatorPrivate::clear() (qscopedpointer.h:62) ==20334==by 0x57A53C6: QQmlIncubator::clear() (qqmlincubator.cpp:577) ==20334==by 0x5DCD7CF: QQuickLoaderPrivate::clear() (qquickloader.cpp:95) ==20334==by 0x5DCEB02: QQuickLoader::setSourceComponent(QQmlComponent*) (qquickloader.cpp:472) Because MainViewStyle.qml is replacing the theme once it gets loaded (if it needs to go Dark) and we're basically changing the component in MainView.qml while the component is being loaded and it seems Qt doesn't like that. Not sure if it could be argued this is a Qt 5.3 bug, haven't tried if the warning is there in Qt 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1330510/+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 1213043] Re: Binding loop detected when changing backgroundColor of MainView dynamically
** No longer affects: ubuntu-ui-toolkit ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1213043 Title: Binding loop detected when changing backgroundColor of MainView dynamically Status in Sudoku game for Ubuntu Touch: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: When changing the backgroundColor of MainView programmatically, a binding loop occurs: file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property "style" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property "target" To manage notifications about this bug go to: https://bugs.launchpad.net/sudoku-app/+bug/1213043/+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 1380914] Re: OnlineAccountsClient::Setup::exec() should execute a signon auth session
** Also affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings-online-accounts (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Assignee: (unassigned) => Alberto Mardegan (mardy) -- 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/1380914 Title: OnlineAccountsClient::Setup::exec() should execute a signon auth session Status in the base for Ubuntu mobile products: Confirmed Status in Online Accounts setup for Ubuntu Touch: In Progress Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: In Progress Status in “ubuntu-system-settings-online-accounts” package in Ubuntu RTM: New Bug description: There is a fix to unity8 coming up that will soon be hiding the OA splash screen. Hiding the splash screen is great for 50% of the situations that it pops up, but there is a point where its actually nice to see that something is happening. With scopes, after the OnlineAccountsClient::Setup class returns from exec(), the shell then calls signon_auth_session_process_async() to request an access token. Thats when seeing the splash screen is useful as the user can see that something is still happening. With that slash screen hidden, the focus will be returned to the scope without any indication that the sign on process is still busy. Could we have the OnlineAccountsClient::Setup::exec() method execute the auth session itself before returning / sending the “finished” signal? That way you'll stay on the setup screen until the oauth token has been granted, hence returning to the scope when all is ready to go. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380914/+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 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
** Also affects: ubuntu-system-settings-online-accounts (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM)
Assignee: (unassigned) => Alberto Mardegan (mardy)
--
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/1376445
Title:
Addition of signon-apparmor-extension causes token lookup problems
Status in go-onlineaccounts:
Incomplete
Status in The Savilerow project:
Invalid
Status in ACL for signond, AppArmor backend:
Fix Released
Status in Online Accounts setup for Ubuntu Touch:
In Progress
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
In Progress
Status in “ubuntuone-credentials” package in Ubuntu:
Confirmed
Status in “signon-apparmor-extension” package in Ubuntu RTM:
Triaged
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu RTM:
New
Status in “ubuntuone-credentials” package in Ubuntu RTM:
Confirmed
Bug description:
As of image ~264 of ubuntu-touch, the signon-apparmor-extension
package is included. As a result, apps like pay-ui cannot find the
token any longer, and are not being notified that they are not allowed
to access the token. The following error appears in the payui log
file:
2014-10-01 19:15:51,550 - DEBUG -
../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
"Client has insuficient permissions to access the
service.Method:getAuthSessionObjectPath")
To manage notifications about this bug go to:
https://bugs.launchpad.net/go-onlineaccounts/+bug/1376445/+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 1389792] Re: theme not found when using a user-defined theme
** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Status: Confirmed => In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1389792 Title: theme not found when using a user-defined theme Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Status in “ubuntu-ui-toolkit” package in Ubuntu RTM: In Progress Bug description: This bugs makes it so that developers cannot update the theming, which can be pretty important for some people and also important for working around color scheme issues in the theming (I've filed other bugs on this). Attached is a very simple application that tries to define the Foo theme which is derived from the SuruDark theme. $ tar -zxvf ./theme-test.tar.gz ./theme-test/ ./theme-test/themes/ ./theme-test/themes/Foo/ ./theme-test/themes/Foo/parent_theme ./theme-test/themes/Foo/Palette.qml ./theme-test/themes/Foo/MainViewStyle.qml ./theme-test/main.qml $ cd theme-test/ $ qmlscene ./main.qml "Theme not found: " "themes.Foo" QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:330:9: QML AppHeader: Warning: Style PageHeadStyle.qml not found in theme themes.Foo file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:202:5: QML StyledItem: Warning: Style MainViewStyle.qml not found in theme themes.Foo QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:70:5: QML Binding: Binding loop detected for property "target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1389792/+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 1394935] Re: "All" can not be translated correctly
** Branch linked: lp:~aacid/dialer-app/AllIsNotAll
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1394935
Title:
"All" can not be translated correctly
Status in “dialer-app” package in Ubuntu:
New
Bug description:
At the moment we use the "All" string in two situations
./src/qml/ContactsPage/ContactsPage.qml:72:sections.model:
[i18n.tr("All"), i18n.tr("Favorites")]
./src/qml/HistoryPage/HistoryPage.qml:49:head.sections.model: [
i18n.tr("All"), i18n.tr("Missed") ]
Unfortunately for the first instance in spanish it would be "Todos"
(since it refers to Contacts which is a masculine word) while the
second has to be "Todas" (since it refers to Calls which is a femenine
word)
This needs the ubuntu-ui-toolkit to gain support to specify context
for strings, see https://bugs.launchpad.net/ubuntu-ui-
toolkit/+bug/1394904
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1394935/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
I patch the bug description: - 2. sudo add-apt-repository ppa:phablet-team/tools + 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa I can't access the pc I produce it for now (in the office), but I believe I add the correct ppa, or I won't have the rtm-14.09 instance available. ** Description changed: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. - 2. sudo add-apt-repository ppa:phablet-team/tools + 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". - But this work around failed as I stop the instance and run again. I even create the same instance with the other name -and try this work around, still can't see anything on the screen. + But this work around failed as I stop the instance and run again. I even create the same instance with the other name + and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
yes I did , typo.. -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1394614] Re: Cached results stay in scopes even with no internet
No, I can't, this is all handled by scopes api and scopes themselves, we're only asking them for results, not caring whether network is there or not. -- 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/1394614 Title: Cached results stay in scopes even with no internet Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in “unity8” package in Ubuntu: Incomplete Bug description: I am testing the latest image and as per the test plan, if internet is disabled there are cached results in a scope they should vanish as we refresh the scope but right now that's not the case. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 15:06:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+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 1394614] Re: Cached results stay in scopes even with no internet
I can reproduce it in image 169 (RTM proposed, 119 ES): cached content is displayed and test case says it must be blank. But I think some changes landed for scopes to display cached content. Saviq, can you confirm? -- 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/1394614 Title: Cached results stay in scopes even with no internet Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in “unity8” package in Ubuntu: Incomplete Bug description: I am testing the latest image and as per the test plan, if internet is disabled there are cached results in a scope they should vanish as we refresh the scope but right now that's not the case. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 15:06:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Why do you use ppa:phablet-team/tools and not the official SDK ppa? http://developer.ubuntu.com/start/ubuntu-sdk/installing-the-sdk/ -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1330410] Re: All keyboard types in "Keyboard layout" are not localized during installation
I use pbuilder to build in a utopic chroot, find that DEBIAN/config *is* translated, this is different from the package in our utopic archive. I also tested to build console-setup 1.70ubuntu9 in a PPA with the recipe [1] for Trusty, Utopic and Vivid, and the DEBIAN/config files of these packages are *NOT* translated. [1] https://code.launchpad.net/~anthonywong/+recipe/console-setup-utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1330410 Title: All keyboard types in "Keyboard layout" are not localized during installation Status in Ubuntu Kylin: Triaged Status in “console-setup” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: Invalid Bug description: 系统：UK 14.10 dailybuild 32 位 6-15 机器型号：vritualbox 现象： 安装过程中键盘布局页面所有的键盘布局类型没有汉化 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Yes, I mean vivid on the desktop/as the host, rtm/14.09 as the guest. I suspect you meant RTM/14.09 for desktop 14.10? -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1385882] Re: Unable to mount iPad with IOS 8
** Changed in: libimobiledevice (Ubuntu) Importance: Undecided => High -- 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/1385882 Title: Unable to mount iPad with IOS 8 Status in “libimobiledevice” package in Ubuntu: Confirmed Bug description: I can't mount my iPad after I upgraded to IOS 8. After plugging in I get a series of error messages, also my iPad keep asking wether I trust my computer. I get messages like: Unable to mount ...'s iPad: Location is already mounted - (it's not) Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20) If I remember correctly this happened last year after I upgraded to iOS 7. The problem exists in Utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 14:36:14 2014 InstallationDate: Installed on 2014-01-10 (288 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: libimobiledevice UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1385882/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Marking this as critical as we are due to start a developer program that will require this functionality for a stable desktop release. Also marking as confirmed since this is being verified by 3 people in the PES team ** Tags added: devtrain rtm14 ** Tags removed: devtrain ** Tags added: univ-train -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1339792] Re: Panel network icon - too much latency when network type changes
As requested by Antti, here's the i-n-sniffer log. This starts with wifi killswitch enabled and the indicator showing the 3G icon. Wlan killswitch changed to: 0 NetworkManager properties changed: WirelessEnabled false NetworkManager properties changed: WirelessEnabled true NetworkManager properties changed: ActiveConnections (now have 1) NetworkManager properties changed: ActiveConnections (now have 1) NetworkManager properties changed: ActivatingConnection ActiveConnections (now have 2) NetworkManager properties changed: ActiveConnections (now have 2) NetworkManager properties changed: ActivatingConnection PrimaryConnection NetworkManager primary connection type changed to 802-11-wireless. Ofono network registration 1 property Strength changed to 48. Ofono network registration 1 property LocationAreaCode changed to 1018. Ofono network registration 1 property CellId changed to 32087. The icon changes at the exact moment the third lowest line (Strength changed to 48.) gets printed to the console. -- 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/1339792 Title: Panel network icon - too much latency when network type changes Status in Network Menu: Confirmed Status in “indicator-network” package in Ubuntu: Confirmed Status in “indicator-network” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Confirmed Status in “indicator-network” package in Ubuntu RTM: Confirmed Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi -> 3G -> WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click "Previous Networks" - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to "3G". To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1339792/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
When you say vivid you mean for the desktop or the emulator image. Either way the version that we are going to support for developers is : Desktop 14.04 + RTM/14.09 for the emulator and, Desktop 14.10 + RTM/14.10 for the emulator. ** Changed in: unity8 (Ubuntu) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu) Status: Incomplete => Confirmed -- 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1236588] Re: signon-ui crashed with SIGABRT in QMessageLogger::fatal()
I reproduce the bug every time after booting the machine, as soon as I log on, with ubuntu 14.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1236588 Title: signon-ui crashed with SIGABRT in QMessageLogger::fatal() Status in “signon-ui” package in Ubuntu: Confirmed Bug description: Crash after update. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: signon-ui 0.15+13.10.20131003.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Mon Oct 7 18:53:33 2013 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2013-06-19 (110 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True ProcCmdline: /usr/bin/signon-ui Signal: 6 SourcePackage: signon-ui StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so ?? () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 Title: signon-ui crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev robots sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1236588/+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 1376344] Re: MTP can access locked device data after rebooting
** Changed in: mtp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1376344 Title: MTP can access locked device data after rebooting Status in “mtp” package in Ubuntu: Incomplete Bug description: ENVIRONMENT: Device: ubuntu-rtm/14.09 build 3 Desktop: Ubuntu 14.10 SUMMARY: MTP can access locked device data after rebooting STEPS: 1) Ensure device is locked with PIN/passphrase and showing locked greeter 2) Insert USB cable and try to access device content over MTP - No content is displayed as expected 3) Reboot device, leaving USB cable connected 4) When device is rebooted and still locked, try and access device content over MTP again EXPECTED RESULT: It should not be possible to view device content using MTP whilst the device is locked ACTUAL RESULT: You can copy and view all content on device using MTP whilst device is still locked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1376344/+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 1394614] Re: Cached results stay in scopes even with no internet
In the regression test, this bug is linked to this test case: 1) Swipe from apps scope to view News scope => News content is displayed 2) Return to apps scope => Apps scope is displayed 3) Put device in flight mode to disable data connection => Data is disabled 4) Return to News scope => Cached news content is displayed 5) Refresh scope by dragging down => Scope displays blank page 6) Disable flight mode => Data connection is established 7) Refresh scope again => Scope reloads showing news content -- 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/1394614 Title: Cached results stay in scopes even with no internet Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in “unity8” package in Ubuntu: Incomplete Bug description: I am testing the latest image and as per the test plan, if internet is disabled there are cached results in a scope they should vanish as we refresh the scope but right now that's not the case. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01.1+15.04.2014~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Thu Nov 20 15:06:59 2014 InstallationDate: Installed on 2014-11-19 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141119-181707) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394614/+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 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- 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/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in “bluez” package in Ubuntu: Incomplete Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387949/+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 1396968] Re: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1396968 Title: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück Status in “systemd” package in Ubuntu: New Bug description: Package structure messed up? I always get errors on postinstall for four packages: libpam-systemd:amd64 libpam-gnome-keyring:amd64 apparmor flashplugin-installer Please fix this. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Thu Nov 27 09:43:12 2014 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.8:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück InstallationDate: Installed on 2013-10-02 (420 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: systemd Title: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück UpgradeStatus: Upgraded to trusty on 2014-03-29 (243 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1396968/+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 1396628] Re: qtsysteminfo fails to build against Qt 5.4.0 beta
** Changed in: qtsystems-opensource-src (Ubuntu) Status: In Progress => Fix Committed ** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtsystems- opensource-src -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1396628 Title: qtsysteminfo fails to build against Qt 5.4.0 beta Status in “qtsystems-opensource-src” package in Ubuntu: Fix Committed Bug description: The qtsysteminfo fails to build against Qt 5.4.0 beta: https://launchpadlibrarian.net/191256134/buildlog_ubuntu-vivid-amd64 .qtsystems-opensource- src_5.0~git20130712-0ubuntu8~vivid1~test1_FAILEDTOBUILD.txt.gz The only user of the package is ubuntu-system-settings. There would seem to be something related in the upstream git. More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1396628/+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 1396968] [NEW] package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück
Public bug reported: Package structure messed up? I always get errors on postinstall for four packages: libpam-systemd:amd64 libpam-gnome-keyring:amd64 apparmor flashplugin-installer Please fix this. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Thu Nov 27 09:43:12 2014 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.8:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück InstallationDate: Installed on 2013-10-02 (420 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: systemd Title: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück UpgradeStatus: Upgraded to trusty on 2014-03-29 (243 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1396968 Title: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück Status in “systemd” package in Ubuntu: New Bug description: Package structure messed up? I always get errors on postinstall for four packages: libpam-systemd:amd64 libpam-gnome-keyring:amd64 apparmor flashplugin-installer Please fix this. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Thu Nov 27 09:43:12 2014 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.8:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück InstallationDate: Installed on 2013-10-02 (420 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: systemd Title: package libpam-systemd:amd64 204-5ubuntu20.8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 255 zurück UpgradeStatus: Upgraded to trusty on 2014-03-29 (243 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1396968/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Hey, I just tried this on vivid, and seems to work fine. On first boot it does take a while to complete, but it does start. There is a bug where the dash starts a little too early and unity8 misses it, that you can fix by SSHing into the emulator and going "restart unity8-dash". ** 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/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in “unity8” package in Ubuntu: Incomplete Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:phablet-team/tools 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash". But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1396951] Re: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied
Interestingly, I’m seeing the same error when running webbrowser-app’s unit tests inside a vivid chroot. The permissions for /dev/shm there are "drwxr-xr-x". ** Also affects: otto Importance: Undecided Status: New -- 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/1396951 Title: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied Status in Automated UI testing on Hardware: New Status in “webbrowser-app” package in Ubuntu: New Bug description: The CI job that runs autopilot tests for webbrowser-app on otto (desktop) has been consistently failing since the switch to vivid. The error seen in the log is the following: /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.org.chromium.Chromium.UAVbQt failed: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(234)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:FATAL:shared_memory_posix.cc(236)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. At a first glance it looks to me like the problem is in the otto setup itself. To manage notifications about this bug go to: https://bugs.launchpad.net/otto/+bug/1396951/+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 1396951] Re: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied
Oxide, which is based on chromium, needs write-access to /dev/shm to function properly. So we need to ensure /dev/shm is writeable in our test environment. -- 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/1396951 Title: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied Status in Automated UI testing on Hardware: New Status in “webbrowser-app” package in Ubuntu: New Bug description: The CI job that runs autopilot tests for webbrowser-app on otto (desktop) has been consistently failing since the switch to vivid. The error seen in the log is the following: /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.org.chromium.Chromium.UAVbQt failed: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(234)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:FATAL:shared_memory_posix.cc(236)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. At a first glance it looks to me like the problem is in the otto setup itself. To manage notifications about this bug go to: https://bugs.launchpad.net/otto/+bug/1396951/+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 1396951] [NEW] webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied
Public bug reported: The CI job that runs autopilot tests for webbrowser-app on otto (desktop) has been consistently failing since the switch to vivid. The error seen in the log is the following: /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.org.chromium.Chromium.UAVbQt failed: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(234)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:FATAL:shared_memory_posix.cc(236)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. At a first glance it looks to me like the problem is in the otto setup itself. ** Affects: otto Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - autopilot tests fail on otto: access to /dev/shm is denied + webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied -- 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/1396951 Title: webbrowser-app’s autopilot tests fail on otto: access to /dev/shm is denied Status in Automated UI testing on Hardware: New Status in “webbrowser-app” package in Ubuntu: New Bug description: The CI job that runs autopilot tests for webbrowser-app on otto (desktop) has been consistently failing since the switch to vivid. The error seen in the log is the following: /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(231)] Creating shared memory in /dev/shm/.org.chromium.Chromium.UAVbQt failed: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:ERROR:shared_memory_posix.cc(234)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied /var/local/autopilot/autopilot.log: [1127/102329:FATAL:shared_memory_posix.cc(236)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. At a first glance it looks to me like the problem is in the otto setup itself. To manage notifications about this bug go to: https://bugs.launchpad.net/otto/+bug/1396951/+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 221844] Re: no session is set active by consolekit
The problem of my last comments apparently is the new cinnamon session name that is unsupported by lightdm. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/221844 Title: no session is set active by consolekit Status in “consolekit” package in Ubuntu: Confirmed Bug description: I installed hardy from the release candidate installer, and after a default install installed kubuntu-desktop. logging in either in a gnome or kde session, and running 'ck-list- sessions' shows 'active = FALSE' for all sessions, even the one currently active (the one shown on the screen). As a large part of default authorizations are set to 'No' for everyone except the active session, this breaks all sorts of things. (For example, mounting usb thumbdrives, or changing authorizations, etc.) If there is any way to debug this problem I would love to help, but I have no idea what I should be looking for (what logfile / etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/221844/+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 1360359] Re: [Performance] Alarm Model is reloaded after creating/deleting an alarm instead of just appending to it causing unnecessary listview repaint
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1360359 Title: [Performance] Alarm Model is reloaded after creating/deleting an alarm instead of just appending to it causing unnecessary listview repaint Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: Once https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/30-alarm- update-fix has landed, when you create/delete an alarm, you will notice that the entire list view is repainted due to the alarm model being refreshed. It would better performance and user experience wise to just append to alarm model since it can be a bit jarring for the user to see all the alarm switched being reinitialized after creating/deleting an alarm. It is not critical, but could perhaps be considered as Medium Priority bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1360359/+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 1380559] Re: [API Request] Alarms API should expose a slot Update() to allow app devs to manually refresh the model
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1380559 Title: [API Request] Alarms API should expose a slot Update() to allow app devs to manually refresh the model Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: Use Case: When a repeating alarm is triggered, the alarm date still shows the old date instead of the next new alarm date. There is nothing the Ubuntu SDK can do since it doesn't get the signal when an alarm is triggered. But the clock app can check that and update the alarm model accordingly which in turn would update the alarm date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1380559/+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 1322558] Re: Investigate flaky test_updateAlarm_Repeating
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1322558 Title: Investigate flaky test_updateAlarm_Repeating Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: FAIL! : tst_UCAlarms::test_updateAlarm_Repeating() 'containsAlarm(&alarm)' returned FALSE. () Loc: [tst_alarms.cpp(356)] The test is flaky and fails repeatedly during CI builds. It will need thorough investigation and re-enabling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1322558/+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 1380553] Re: Alarm Model is refreshed after creating/deleting an alarm
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1380553 Title: Alarm Model is refreshed after creating/deleting an alarm Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When creating a new alarm or deleting an existing alarm, the entire alarm model is refreshed which causes the listview showing the alarms to be repainted as well. This causes a glaring ui refresh since doing either of the tasks mentioned will result in the alarm switches to reset and then be set to the correct position which is a bad experience for the user. I was requested by design to check if this can be avoided. This is strongly correlated to bug 1359112 where one use case has been fixed which is editing and saving an alarm avoids refreshing the entire alarm model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1380553/+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 1394904] Re: Need context variants of i18n.tr and i18n.dtr
This bug was fixed in the package ubuntu-ui-toolkit -
1.1.1347+15.04.20141126-0ubuntu1
---
ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium
[ Zsombor Egri ]
* Expose refresh() function in revision 1 (Ubuntu.Components 1.1).
Fixes LP: #1380559
* Alarm adaptation refactored to support change granular model
updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649,
LP: #1380553
* Fix Header thin divider margins, restored to original no-margins.
Fixes LP: #1380766.
[ Tim Peeters ]
* Add ensure_visible() function to header AP helper.
Fixes LP: #1363591
[ Albert Astals Cid ]
* Add context support for i18n.tr calls. This allows to have strings
like "All" translated to two different strings in the translated
language if different contexts are given. Fixes LP: #1394904
-- Ubuntu daily releaseWed, 26 Nov 2014
08:33:25 +
** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1394904
Title:
Need context variants of i18n.tr and i18n.dtr
Status in “ubuntu-ui-toolkit” package in Ubuntu:
Fix Released
Bug description:
Sometimes you need to show a small string like "All" but you need to
give it a context so translations can translate it differently than
other "All" occurrences in the same domain.
Example, in the phone-app we have two occurrences of "All", one is
about Contacts, the other about Calls, so in Spanish you need the
first "All" translated as "Todos" and the second one as "Todas"
So you would write i18n.ctr("All Calls", "All") and i18n.ctr("All
Contacts", "All") in the code so there would be the possibility of
having different translations.
So we basically need
https://www.gnu.org/software/gettext/manual/html_node/Contexts.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1394904/+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 1385010] Re: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink Status in “resolvconf” package in Ubuntu: Confirmed Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines the make_resolv_conf function (previously defined by dhclient-script) to send nameserver information to resolvconf instead of writing it directly to /etc/resolv.conf. However, the hook also checks if /etc/resolv.conf is a symlink. This is problematic because if /etc/resolv.conf is not a symlink then the script does not redefine make_resolv_conf() and so dhclient will overwrite /etc/resolv.conf when it configures an interface, even though the resolvconf package is installed. The behavior I would expect would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. Debian implements the behavior I would expect. At the very least, I think that the different behavior in Ubuntu should be documented in the man pages for resolvconf. As far as I can tell, there's no reason to check for /etc/resolv.conf being a symlink when resolvconf itself already does that. The patch was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+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 1363591] Re: It's not safe to override the show header autopilot helper
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1363591 Title: It's not safe to override the show header autopilot helper Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: We need a method called ensure_visible on the header autopilot helper. This method will be public, so it will be safe for apps to override it if they change the header behaviour. For example, on the gallery, clicking on the center of the app will show the header. Swiping won't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1363591/+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 1394081] Re: Add manual options for administrators
*** This bug is a duplicate of bug 1385010 *** https://bugs.launchpad.net/bugs/1385010 > did not know I am stepping on your toe here No toes being stepped on here. > had to take care of this, so I generate the resolv.conf from a package - no link anymore OK. Leave the resolvconf package installed; remove the symlink. > once you ifdown/ifup one of the dhcp interfaces, the resolv.conf got overwritten It's not resolvconf doing that. > It was bug #1385010 ... that caused this. Ah, glad you figured it out. I'll merge this report with that one. ** This bug has been marked a duplicate of bug 1385010 Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1394081 Title: Add manual options for administrators Status in “resolvconf” package in Ubuntu: Incomplete Bug description: Currently - trusty LTS - there is no way to turn off the regeneration of /etc/resolv.conf that would survive a package upgrade. - you cannot remove resolvconf as it is needed by minimal - you cannot disable-upgrades as this flag is removed by reboots - if you disable the resolvconf job in upstart package upgrade will reset the disable-upgrade flags - if you hack the scripts - it will only last until the next upgrade There are two ways to ensure that admins willing to turn it off can do so: First solution: add a run=no to /etc/default/resolvconf and bail out if it is set. The second solution is more subtile. In /etc/network/if- up.d/000resolvconf you will find this line: [ -x /sbin/resolvconf ] || exit 0 While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then Way more clever! So if you do not want to implement the default option, why not check if its a link all the way? So at least a conf gets not overwritten once the admin wrote his own. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1394081/+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 1370649] Re: Reset an alarm doesn't return the properties to their default values
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1370649 Title: Reset an alarm doesn't return the properties to their default values Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When I reset a repeating alarm with multiple daysOfWeek set, daysOfWeek is not reset to Alarm.AutoDetect. To reproduce: Apply the patch in http://paste.ubuntu.com/8366602/ and run the tests. FAIL! : qmltestrunner::AlarmAPI::test_resetAlarmMustSetDefaultPropertiesValues() property daysOfWeek Actual (): 4 Expected (): 128 Loc: [/home/elopio/workspace/canonical/ubuntu-ui-toolkit/trunk/tests/unit_x11/tst_components/tst_alarms.qml(266)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1370649/+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 1380766] Re: revert listitem dividers to previous (no margins)
This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1 --- ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium [ Zsombor Egri ] * Expose refresh() function in revision 1 (Ubuntu.Components 1.1). Fixes LP: #1380559 * Alarm adaptation refactored to support change granular model updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649, LP: #1380553 * Fix Header thin divider margins, restored to original no-margins. Fixes LP: #1380766. [ Tim Peeters ] * Add ensure_visible() function to header AP helper. Fixes LP: #1363591 [ Albert Astals Cid ] * Add context support for i18n.tr calls. This allows to have strings like "All" translated to two different strings in the translated language if different contexts are given. Fixes LP: #1394904 -- Ubuntu daily releaseWed, 26 Nov 2014 08:33:25 + ** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1380766 Title: revert listitem dividers to previous (no margins) Status in the base for Ubuntu mobile products: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: 2gu margin was added to the left and right of listitem dividers. However this is causing issues with a large number of apps. For RTM let's revert back to previous (no left/right margins on listitem dividers) and after that we can explore the issues again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380766/+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 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
> I see that your change has made it to vivid
\o/
> undesirable behavior: all DNS queries go to the VPN nameservers
That is in most cases the *desired* behavior, since only the VPN
nameservers have name information about both the VPN and the Internet.
Also, under what circumstances do you not trust the VPN with your DNS
traffic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
Status in “resolvconf” package in Ubuntu:
Confirmed
Bug description:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part
of Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
< nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
> nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP
one as well so that it can work out of the box on Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+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
