[Touch-packages] [Bug 1432247] [NEW] [SATELLITE P50-B-118, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported:
I guess all the info is in the bug description. I get no sound from my
laptop.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-26-generic.
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC284 Analog [ALC284 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lazy 2161 F pulseaudio
/dev/snd/controlC0: lazy 2161 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xf7c14000 irq 50'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7c1 irq 51'
Mixer name : 'Realtek ALC284'
Components : 'HDA:10ec0284,1179f943,0011'
Controls : 20
Simple ctrls : 9
Date: Sat Mar 14 22:30:25 2015
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
2161 2161 lazy F pulseaudio
/dev/snd/controlC0: lazy F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [SATELLITE P50-B-118, Intel Haswell HDMI, Digital Out, HDMI] No sound at
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.30
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG20SQ
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnTOSHIBA:bvr1.30:bd08/14/2014:svnTOSHIBA:pnSATELLITEP50-B-118:pvrPSPNUE-01F044CE:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: SATELLITE P50-B-118
dmi.product.version: PSPNUE-01F044CE
dmi.sys.vendor: TOSHIBA
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise running-unity
--
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/1432247
Title:
[SATELLITE P50-B-118, Intel Haswell HDMI, Digital Out, HDMI] No sound
at all
Status in alsa-driver package in Ubuntu:
New
Bug description:
I guess all the info is in the bug description. I get no sound from my
laptop.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-26-generic.
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC284 Analog [ALC284 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lazy 2161 F pulseaudio
/dev/snd/controlC0: lazy 2161 F pulseaudio
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xf7c14000 irq 50'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 21
Simple ctrls : 3
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xf7c1 irq 51'
Mixer name : 'Realtek ALC284'
Components : 'HDA:10ec0284,1179f943,0011'
Controls : 20
Simple ctrls : 9
Date: Sat Mar 14 22:30:25 2015
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
2161 2161 lazy F pulseaudio
/dev/snd/controlC0: lazy F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [SATELLITE P50-B-118, Intel Haswell HDMI, Digital Out, HDMI] No sound
at all
UpgradeStatus: No upgrade log
[Touch-packages] [Bug 1307102] Re: Unable to set autologin
This bug occure only on 64 bit ubuntu 14.04 version -- 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/1307102 Title: Unable to set autologin Status in lightdm package in Ubuntu: Invalid Bug description: In 14.04 Xubuntu I am unable to set autologin The /usr/lib/lightdm/lightdm-set-defaults --autologin command is now gone it seems ( https://launchpad.net/ubuntu/+source/lightdm/1.9.4-0ubuntu1 ) I've tried editing the various .conf files with no success. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 13 11:09:31 2014 InstallationDate: Installed on 2014-04-06 (6 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1307102/+subscriptions -- Mailing list: https://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 1250875] Re: Lightdm sometimes fails to auto login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- Mailing list: https://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 1159405] Re: Canceling a bug report / backtrace causes Apport to freeze
It took some seconds then closed. I don't have this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1159405 Title: Canceling a bug report / backtrace causes Apport to freeze Status in Ubuntu GNOME: Triaged Status in apport package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Press Alt+F2 keys and write ubuntu-bug apport. 2. In the opened window, quickly press the cancel button. *** BEHAVIOUR *** - EXPECTED: The Apport backtrace to be cancelled. - REAL: Apport freezes. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport 2.9.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Sun Mar 24 13:34:24 2013 InstallationDate: Installed on 2013-03-23 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130323) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1159405/+subscriptions -- Mailing list: https://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 1421093] [NEW] package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned
You have been subscribed to a public bug: upon upgrading my vivid test installation I received this error. It seems this might be a dupe of bug 1394849 and/or bug 1416739 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-15ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 Date: Thu Feb 12 12:31:32 2015 Dependencies: gcc-5-base 5-20150202-0ubuntu1 libc6 2.19-15ubuntu1 libcap2 1:2.24-6 libgcc1 1:5-20150202-0ubuntu1 multiarch-support 2.19-15ubuntu1 DuplicateSignature: package:libc-bin:2.19-15ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-07-23 (203 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140522) SourcePackage: glibc Title: package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-icon-theme (Ubuntu) Importance: High Status: Confirmed ** Tags: apport-package i386 vivid -- package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned https://bugs.launchpad.net/bugs/1421093 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. -- Mailing list: https://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 1416739] [NEW] package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned
You have been subscribed to a public bug: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-13ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sat Jan 31 21:05:56 2015 Dependencies: gcc-5-base 5-20150128-0ubuntu1 libc6 2.19-13ubuntu3 libcap2 1:2.24-6 libgcc1 1:5-20150128-0ubuntu1 multiarch-support 2.19-13ubuntu3 DuplicateSignature: package:libc-bin:2.19-13ubuntu3:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-12-27 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141224) SourcePackage: glibc Title: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-icon-theme (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-package vivid -- package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned https://bugs.launchpad.net/bugs/1416739 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. -- Mailing list: https://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 1394849] [NEW] package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned
You have been subscribed to a public bug: error happened during dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-13ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Thu Nov 20 18:06:54 2014 Dependencies: gcc-4.9-base 4.9.2-1ubuntu1 libc6 2.19-13ubuntu2 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.2-1ubuntu1 multiarch-support 2.19-13ubuntu2 DuplicateSignature: package:libc-bin:2.19-13ubuntu2:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-30 (21 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141028) SourcePackage: glibc Title: package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ureadahead (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-package vivid -- package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned https://bugs.launchpad.net/bugs/1394849 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. -- Mailing list: https://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 1432216] Re: PCI/internal sound card not detected
[ 13.424298] snd_hda_intel :00:1b.0: CORB reset timeout#2, CORBRP = 65535 [ 13.424404] snd_hda_intel :00:1b.0: no AFG or MFG node found [ 13.424414] snd_hda_intel :00:1b.0: no AFG or MFG node found [ 13.424421] snd_hda_intel :00:1b.0: no AFG or MFG node found [ 13.424427] snd_hda_intel :00:1b.0: no AFG or MFG node found [ 13.424430] snd_hda_intel :00:1b.0: no codecs initialized -- 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/1432216 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I freshly installed ubuntu 14.10 on a toshiba tecra a8 pta83 the sound is not working although it's still functional on the windows partition. Maybe the soundcard isn't recognised. thank you for your help ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Mar 14 19:17:44 2015 InstallationDate: Installed on 2014-11-11 (123 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.40 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.40:bd03/12/2007:svnTOSHIBA:pnTECRAA8:pvrPTA83E-04L023AR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA A8 dmi.product.version: PTA83E-04L023AR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1432216/+subscriptions -- Mailing list: https://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 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdbusmenu (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/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in The Messaging Menu: Fix Released Status in Messaging Menu 13.04 series: Fix Released Status in Sound Menu: Fix Released Status in The Sound Menu 13.04 series: Fix Released Status in DBus Menu: Triaged Status in MPRIS D-Bus Interface Specification: Confirmed Status in Ubuntu One Client: Fix Committed Status in Unity: Invalid Status in compiz package in Ubuntu: Invalid Status in empathy package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in libdbusmenu package in Ubuntu: Confirmed Status in tomboy package in Ubuntu: Confirmed Status in ubuntuone-client package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 11.10 beta compiz 1:0.9.5.94+bzr2803-0ubuntu5 unity 4.16.0-0ubuntu1 1. open banshee, start a song in it and minimize 2. open another application lets say gnome-terminal 3. click on the sound menu and select banshee What happens banshee icon in the launcher wiggles and banshee main window is not shown What should happen banshee main window should come to focus This is a long standing bug which Ted Gould thinks should be fixed at window manager's level. Some other observations= The problem wont happen 1. if every other app is minimized or 2. Banshee is the only opened app or 3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again =Comment from Ted Gould= om26er tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible tedg om26er, My thought is that window managers should $%#$ get fixed... though I haven't convinced smspillaz of it yet. =The good rule= 3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event. Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification. See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations. For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two hackish ways: 1. Use the server time to present a window: https://bugzilla.gnome.org/show_bug.cgi?id=688830 2. Get the event timestamp from the dbus-menu linked to the gtk-menus: http://paste.ubuntu.com/5701235/ 3. Qt applications workaround: http://is.gd/WnW9eN Window managers will obey to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- Mailing list: https://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 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
Running 14.04.2 here with some of the same issues. I was seeing it with ownCloud client, network manager, and a weather applet known as my- weather-indicator. The issue came up at random, but it was easy to replicate within a matter of 15-20 seconds while continuously navigating around open windows followed by opening applications with system tray icons. I brought up conversation with some other users who gave me a suggestion that has, so far, worked. Figured I'd post it here in case it can benefit anybody else until the bug can be properly fixed. I ran this in terminal, followed by a log out/log in. dconf write /org/compiz/profiles/unity/plugins/core/focus-prevention- level 0 This is a similar idea that Rael posted in response 43 above. I seem to recall Ubuntu switching to dconf over gconf at some point. I tested it in my 14.04.2 virtual machine (brand new, but fully updated install) however the gconf key didn't appear to fix the issue, as I was still able to replicate it. In the same VM, that dconf write command above seemed to fix the issue, as I have been unable to replicate it in my VM, nor my main laptop. The default focus-prevention-level is 1, which is considered low, but appears to be the cause of this random behavior. Setting it to 0 seems to make it consistent. I haven't ran with this change for days/weeks/months, but in my tinkering so far today, the issue hasn't resurfaced a single time. -- 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/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in The Messaging Menu: Fix Released Status in Messaging Menu 13.04 series: Fix Released Status in Sound Menu: Fix Released Status in The Sound Menu 13.04 series: Fix Released Status in DBus Menu: Triaged Status in MPRIS D-Bus Interface Specification: Confirmed Status in Ubuntu One Client: Fix Committed Status in Unity: Invalid Status in compiz package in Ubuntu: Invalid Status in empathy package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in libdbusmenu package in Ubuntu: Confirmed Status in tomboy package in Ubuntu: Confirmed Status in ubuntuone-client package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 11.10 beta compiz 1:0.9.5.94+bzr2803-0ubuntu5 unity 4.16.0-0ubuntu1 1. open banshee, start a song in it and minimize 2. open another application lets say gnome-terminal 3. click on the sound menu and select banshee What happens banshee icon in the launcher wiggles and banshee main window is not shown What should happen banshee main window should come to focus This is a long standing bug which Ted Gould thinks should be fixed at window manager's level. Some other observations= The problem wont happen 1. if every other app is minimized or 2. Banshee is the only opened app or 3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again =Comment from Ted Gould= om26er tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible tedg om26er, My thought is that window managers should $%#$ get fixed... though I haven't convinced smspillaz of it yet. =The good rule= 3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event. Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification. See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations. For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two hackish ways: 1. Use the server time to present a window: https://bugzilla.gnome.org/show_bug.cgi?id=688830 2. Get the event timestamp from the dbus-menu linked to the gtk-menus: http://paste.ubuntu.com/5701235/ 3. Qt applications workaround: http://is.gd/WnW9eN Window managers will obey to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- Mailing list: https://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 438638] Re: add-apt-repository should call apt-get update after adding the repository
** Changed in: software-properties (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/438638 Title: add-apt-repository should call apt-get update after adding the repository Status in software-properties package in Ubuntu: Confirmed Bug description: After adding a PPA with add-apt-repository I have tried sudo apt-get upgrade, there were no updates available, I had to manually call apt-get update. If I am adding a repository I want the cache to be updated, that should be automatically done by add-apt-repostiory . Using this strategy would allow to update only the just added repository: http://askubuntu.com/a/197532/7788 ProblemType: Bug Architecture: i386 Date: Tue Sep 29 11:12:45 2009DistroRelease: Ubuntu 9.10 Package: python-software-properties 0.75.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_PT.utf8 PATH=(custom, user) LANG=pt_PT.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-genericSourcePackage: software-properties Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/438638/+subscriptions -- Mailing list: https://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 438638] Re: add-apt-repository should call apt-get update after adding the repository
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/438638 Title: add-apt-repository should call apt-get update after adding the repository Status in software-properties package in Ubuntu: Confirmed Bug description: After adding a PPA with add-apt-repository I have tried sudo apt-get upgrade, there were no updates available, I had to manually call apt-get update. If I am adding a repository I want the cache to be updated, that should be automatically done by add-apt-repostiory . Using this strategy would allow to update only the just added repository: http://askubuntu.com/a/197532/7788 ProblemType: Bug Architecture: i386 Date: Tue Sep 29 11:12:45 2009DistroRelease: Ubuntu 9.10 Package: python-software-properties 0.75.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_PT.utf8 PATH=(custom, user) LANG=pt_PT.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-genericSourcePackage: software-properties Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/438638/+subscriptions -- Mailing list: https://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 1432287] [NEW] I don't know
Public bug reported: I don't know ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 14 23:24:45 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d3] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d3] InstallationDate: Installed on 2015-03-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: LENOVO 4173RL1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=da80fb25-4bda-4ea4-8b2e-5230cf228d48 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET44WW (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173RL1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET44WW(1.24):bd05/23/2011:svnLENOVO:pn4173RL1:pvrThinkPadT420s:rvnLENOVO:rn4173RL1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173RL1 dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 14 16:08:50 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 870 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432287 Title: I don't know Status in xorg package in Ubuntu: New Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 14 23:24:45 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d3] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d3] InstallationDate: Installed on 2015-03-14 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: LENOVO 4173RL1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=da80fb25-4bda-4ea4-8b2e-5230cf228d48 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2011 dmi.bios.vendor: LENOVO
[Touch-packages] [Bug 288762] Re: totem: can't skip chapters in matroska files
This issue is still present in Ubuntu 14.04 LTS, fully updated. An .mkv file with OR without chapters is treated the same by Totem. Most of my files played on VLC (or other player) have chpater information and you can navigate to next/previous chapter. What is the root cause? Why did this fix (xine-lib v1.1.17, per comment #11) never reach/affect Trusty (14.04)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/288762 Title: totem: can't skip chapters in matroska files Status in gstreamer0.10 package in Ubuntu: Confirmed Status in xine-lib package in Ubuntu: Fix Released Bug description: Binary package hint: totem-xine Totem is unable to access the chapters of Matroska files. The Next/Previous chapter menu options are disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/288762/+subscriptions -- Mailing list: https://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 1432256] Re: compiz crashed on enabling the opacity, brightness and saturation plugin with SIGSEGV in unity::glib::Source::IsRunning()
*** This bug is a duplicate of bug 1425085 *** https://bugs.launchpad.net/bugs/1425085 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1425085, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1432256/+attachment/4345737/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345739/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345741/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345742/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345743/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345744/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1432256/+attachment/4345745/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1425085 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1432256 Title: compiz crashed on enabling the opacity, brightness and saturation plugin with SIGSEGV in unity::glib::Source::IsRunning() Status in unity package in Ubuntu: New Bug description: Hello, Just enabled the opacity, brightness and saturation plugin in CCSM and got the crash. Ubuntu 15.04, all updates, xorg from edgers though. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 23:47:29 2015 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-10-10 (520 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f5516e403d3 _ZNK5unity4glib6Source9IsRunningEv+3: mov0x18(%rdi),%rdi PC (0x7f5516e403d3) ok source 0x18(%rdi) (0x0038) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::glib::Source::IsRunning() const () from /usr/lib/libunity-core-6.0.so.9 unity::XdndStartStopNotifierImp::DndTimeoutSetup() () from /usr/lib/compiz/libunityshell.so sigc::internal::signal_emit1void, unsigned long, sigc::nil::emit(sigc::internal::signal_impl*, unsigned long const) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::Notify(CompWindow*, CompWindowNotify) () from /usr/lib/compiz/libunityshell.so unity::UnityWindow::windowNotify(CompWindowNotify) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::glib::Source::IsRunning() UpgradeStatus: Upgraded to vivid on 2015-03-01 (13 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432256/+subscriptions -- Mailing list: https://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 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed
#66: With this rate of things, somewhere around 2055. -- 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/124440 Title: [enhancement] Ubuntu needs a way to set mouse scrolling speed Status in GNOME Control Center: Confirmed Status in GTK+ GUI Toolkit: Confirmed Status in One Hundred Papercuts: Triaged Status in Mir: Triaged Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- Mailing list: https://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 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
I couldn't see an obvious way to edit my above post, so apologies for sending out a second comment, but I do have to ask... why would the default parameter for focus-prevention-level not be 0 anyways? It doesn't seem, do I dare say, all that logical to have it set to 1 since it only ends up providing inconsistent behavior with the way things from system tray open. It being set to 0 provides that consistency. It would surely remove the look on your launcher, see? it's there after all comments I have to make quite often so users know that the application they tried to open from system tray isn't broken, it indeed launched, it's just... minimized and in your left launcher. Thanks for all of your work! -- 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/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus Status in Ayatana Design: Fix Committed Status in Compiz: Invalid Status in The Messaging Menu: Fix Released Status in Messaging Menu 13.04 series: Fix Released Status in Sound Menu: Fix Released Status in The Sound Menu 13.04 series: Fix Released Status in DBus Menu: Triaged Status in MPRIS D-Bus Interface Specification: Confirmed Status in Ubuntu One Client: Fix Committed Status in Unity: Invalid Status in compiz package in Ubuntu: Invalid Status in empathy package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in libdbusmenu package in Ubuntu: Confirmed Status in tomboy package in Ubuntu: Confirmed Status in ubuntuone-client package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 11.10 beta compiz 1:0.9.5.94+bzr2803-0ubuntu5 unity 4.16.0-0ubuntu1 1. open banshee, start a song in it and minimize 2. open another application lets say gnome-terminal 3. click on the sound menu and select banshee What happens banshee icon in the launcher wiggles and banshee main window is not shown What should happen banshee main window should come to focus This is a long standing bug which Ted Gould thinks should be fixed at window manager's level. Some other observations= The problem wont happen 1. if every other app is minimized or 2. Banshee is the only opened app or 3. after opening gnome-terminal, banshee window is closed so that it hides to the SoundMenu and opened again =Comment from Ted Gould= om26er tedg, Hi! any thoughts on the long standing bug 627195 ? Its been there before unity so I guess we can conclude unity not to be responsible tedg om26er, My thought is that window managers should $%#$ get fixed... though I haven't convinced smspillaz of it yet. =The good rule= 3v1n0: Indicators should present the application windows by passing to them the timestamp of the menu item activation event. Unfortunately for indicator-sound, this is not trival as it sounds, since it needs a change to the MPRIS dbus specification. See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 for more informations. For what concerns libappindicator based indicators (such as the one used by tomboy), since it's not currently possible in libdbusmenu to pass the event during activation (so that clients will be able to get the proper timestamp using gtk_get_current_event_time), there are two hackish ways: 1. Use the server time to present a window: https://bugzilla.gnome.org/show_bug.cgi?id=688830 2. Get the event timestamp from the dbus-menu linked to the gtk-menus: http://paste.ubuntu.com/5701235/ 3. Qt applications workaround: http://is.gd/WnW9eN Window managers will obey to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- Mailing list: https://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 1421093] Re: package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Package changed: glibc (Ubuntu) = gnome-icon-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1421093 Title: package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-icon-theme package in Ubuntu: Confirmed Bug description: upon upgrading my vivid test installation I received this error. It seems this might be a dupe of bug 1394849 and/or bug 1416739 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-15ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 Date: Thu Feb 12 12:31:32 2015 Dependencies: gcc-5-base 5-20150202-0ubuntu1 libc6 2.19-15ubuntu1 libcap2 1:2.24-6 libgcc1 1:5-20150202-0ubuntu1 multiarch-support 2.19-15ubuntu1 DuplicateSignature: package:libc-bin:2.19-15ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-07-23 (203 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140522) SourcePackage: glibc Title: package libc-bin 2.19-15ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1421093/+subscriptions -- Mailing list: https://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 1416739] Re: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned
** Package changed: glibc (Ubuntu) = gnome-icon-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1416739 Title: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned Status in gnome-icon-theme package in Ubuntu: Confirmed Bug description: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-13ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sat Jan 31 21:05:56 2015 Dependencies: gcc-5-base 5-20150128-0ubuntu1 libc6 2.19-13ubuntu3 libcap2 1:2.24-6 libgcc1 1:5-20150128-0ubuntu1 multiarch-support 2.19-13ubuntu3 DuplicateSignature: package:libc-bin:2.19-13ubuntu3:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-12-27 (35 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141224) SourcePackage: glibc Title: package libc-bin 2.19-13ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1416739/+subscriptions -- Mailing list: https://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 1308037] Re: No results from application scope
Looks like I solved the problem on my machine thanks to a recent post in Ubuntu subreddit. The post was titled: How I sped up my Ubuntu Dash. The user had problems with Dash being very slow to show him search results and he found out that the culprit was Zeitgeist. This thing tracks the files, applications you used and your other activities. It turned out that his Zeitgeist history was over two years long! When I checked on my system I had it dating back to February 2012 so it was even longer than his. I deleted the folder /home/your_user_name/.local/share/zeitgeist (almost 700 MB of data) containing the Zeitgeist history just like he did and I confirm that it sped up Dash. But it also resolved the problem described in this bug report. http://www.reddit.com/r/Ubuntu/comments/2ysuqu/how_i_sped_up_my_ubuntu_dash/ -- 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in Unity: Confirmed Status in Unity Applications Lens: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for spotify, which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+subscriptions -- Mailing list: https://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 1432171] Re: Starting version 219 systemd-boot
We shouldn't scare our users. I have not chosen quiet splash, I've chosen the standard bootsplash. There is no reason for 40 seconds of black screen rather than the chosen splash image. There should be plymouth and direct transition to sddm. This certainly IS a bug which should be fixed before launch. Valorie -- 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/1432171 Title: Starting version 219 systemd-boot Status in systemd package in Ubuntu: Incomplete Bug description: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://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 1432254] [NEW] stale openvpn dns servers left in /etc/resolv.conf
Public bug reported: I use an openvpn vpn through network manager to connect to the canonical vpn; when I suspend and resume my laptop the openvpn vpn does not come up again. However the DNS server that it inserted into my /etc/resolv.conf is left there, causing all dns lookups to take six seconds longer, until I either bring up the vpn again or hand-edit my resolv.conf. I want the DNS server to be removed when the VPN is no longer functional. (The indicator knows the VPN is down, so presumably this is knowable.) Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 15:27:30 2015 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-18 (877 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-04-12 (336 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetdisconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1432254 Title: stale openvpn dns servers left in /etc/resolv.conf Status in network-manager package in Ubuntu: New Bug description: I use an openvpn vpn through network manager to connect to the canonical vpn; when I suspend and resume my laptop the openvpn vpn does not come up again. However the DNS server that it inserted into my /etc/resolv.conf is left there, causing all dns lookups to take six seconds longer, until I either bring up the vpn again or hand-edit my resolv.conf. I want the DNS server to be removed when the VPN is no longer functional. (The indicator knows the VPN is down, so presumably this is knowable.) Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 15:27:30 2015 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-18 (877 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-04-12 (336 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetdisconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432254/+subscriptions -- Mailing list: https://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 1432265] [NEW] after the upstart replacement with systemd, the system fails to boot with 2 LUKS encrypted devices.
Public bug reported: after the recent upstart - systemd migration my system is left unable to complete it's boot process. It asks for the first passphrase, but not for the second. When booting with upstart (via the advanced boot options), the system behaves correctly and asks for both passphrases. /etc/crypttab sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt /ext4 discard,noatime,nodiratime,commit=300,errors=remount-ro 0 1 /dev/sda1 /boot ext3 discard,relatime,nodiratime,commit=300,defaults 0 2 /dev/mapper/sdb1_crypt /opt btrfs nofail,autodefrag,discard,enospc_debug 0 1 # tmpfs /tmp tmpfs relatime,nosuid 0 0 #/dev/mapper/swap none swapsw,discard 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 15 00:10:02 2015 InstallationDate: Installed on 2014-05-30 (288 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=UUID=c72e0d8e-4822-45c8-b95f-6e13971940d3 ro nomodeset allow-discards root_trim=yes nomdmonddf nomdmonisw crashkernel=384M-:128M nogpumanager init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PMFT3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1432265 Title: after the upstart replacement with systemd, the system fails to boot with 2 LUKS encrypted devices. Status in systemd package in Ubuntu: New Bug description: after the recent upstart - systemd migration my system is left unable to complete it's boot process. It asks for the first passphrase, but not for the second. When booting with upstart (via the advanced boot options), the system behaves correctly and asks for both passphrases. /etc/crypttab sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt /ext4 discard,noatime,nodiratime,commit=300,errors=remount-ro 0 1 /dev/sda1 /boot ext3 discard,relatime,nodiratime,commit=300,defaults 0 2 /dev/mapper/sdb1_crypt /opt btrfs nofail,autodefrag,discard,enospc_debug 0 1 # tmpfs/tmp tmpfs relatime,nosuid 0 0 #/dev/mapper/swap none swapsw,discard 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 15 00:10:02 2015 InstallationDate: Installed on 2014-05-30 (288 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine:
[Touch-packages] [Bug 836616] Re: 100% cpu usage in lightdm
And I , from yesterday, after the weekly updates, by opening today my system (Ubuntu 12.04.5 LTS) i faced than same problem. One of my eight cores of my system worked at 100% . As I watched from the application ''top'' the process charged my system was the ightdm. Than he shown from the application synaptic package manager, i have installed the ''ightdm (1.2.3-0ubuntu2.6)'' version, description : http://pastebin.com/M6DKpJrV Following this guide : http://www.g-lts.info/index.php/forum/odigoi-odigies-xrisis/247-ypovathmisi-paketon-se-proigoymeni-ekdosi reverted to version ightdm (1.2.3-0ubuntu2.5) and longer everything move smoothly (as before). If there is anything new please let as know. Thank you very very mych. :) (Sorry for the perhaps bad english) -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+subscriptions -- Mailing list: https://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 1407907] Re: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely
Juts saw this again, the issue seems to be that when leaving Wifi coverage and before the phone suspends the connect dialog is created while the screen is off, so when the user resumes the phone it is displayed. But the AP prompted for connection should no longer have been visible in the first place. ** Changed in: canonical-devices-system-image Status: Incomplete = Confirmed ** Changed in: canonical-devices-system-image Milestone: ww11-2015 = ww13-2015 -- 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/1407907 Title: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: Steps: * connect to a password-protected WiFi network * suspend the phone * turn the WiFi off or leave the network's covered area * resume the phone Expected: * phone is connected via a GSM data connection Current: * phone is connected via a GSM data connection * there is a WiFi password dialog displayed for a network that isn't in range any more (and for which the password is known) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407907/+subscriptions -- Mailing list: https://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 1415029] Re: Not yet available but configured providers should be added as soon as they become available
** Changed in: canonical-devices-system-image Milestone: ww11-2015 = ww13-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1415029 Title: Not yet available but configured providers should be added as soon as they become available Status in the base for Ubuntu mobile products: In Progress Status in location-service package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu RTM: Confirmed Bug description: Right now, the location service tries to instantiate configured providers at startup. In specific corner cases, some of the configured sensors might not be available and the service should be able to be notified when those providers become available. In particular, this affects the wizard running on first boot, and subsequent login to the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415029/+subscriptions -- Mailing list: https://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 405294] Re: a2dp skips terribly
Same problem here, with ThinkPad x220 Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 61300 us (= 10812 bytes) in audio stream Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 43008 us (= 7584 bytes) in audio stream Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 279302 us (= 49268 bytes) in audio stream Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 96393 us (= 17000 bytes) in audio stream Mar 15 00:46:01 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 201482 us (= 35540 bytes) in audio stream Mar 15 00:46:01 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 7530 us (= 1328 bytes) in audio stream Mar 15 00:46:01 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 107377 us (= 18940 bytes) in audio stream Mar 15 00:46:02 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c: Skipping 152131 us (= 26832 bytes) in audio stream I just got my Bluetooth headphones and I can't believe that a basic thing like that is missing in 2015. This makes the headphones unusable. -- 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/405294 Title: a2dp skips terribly Status in PulseAudio sound server: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
FYI, in case there are some lesser experienced users that have this issue and are looking for a temporary solution for the time being, below are the instructions to revert to the previous release of lightdm until this gets resolved. You can do this with the following command in a terminal (CTRL + ALT + T): sudo apt-get install lightdm=1.2.3-0ubuntu2.5 Then to kill the current lightdm session and start a new one using the previous released version, log out, then press CTRL + ALT + F1. Log into the fullscreen terminal session. Then type the following: sudo service lightdm stop sudo service lightdm start Then to close the terminal session, press CTRL + ALT + F1 once again, type exit, then CTRL + ALT + F7 to return to your lightdm session. After that, you can log in and you're back to normal. I also locked the lightdm package after reverting back for the time being so that I don't accidentally reinstall the broken version by doing the following in a terminal: sudo echo lightdm hold | dpkg --set-selections Once this gets fixed or a new version is released later on, you can release the lock/hold with the following command in a terminal: sudo echo lightdm install | dpkg --set-selections Hope that helps! -- 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/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage Status in lightdm package in Ubuntu: Confirmed Bug description: Since updating lightdm today, one core of my CPU is always maxed out at 100%. I rolled back to version 1.2.3-0ubuntu2.5 and the issue stopped. I tried this with 2 different kernels: 3.2.0-77-generic and 3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still caused 100% cpu usage. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Thu Mar 12 20:20:12 2015 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+subscriptions -- Mailing list: https://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 1432236] [NEW] lid hinge 360 degree, touch pad is not disabled automatically
Public bug reported: dell 3147(dell 11 3000) , lid hinged and the keyboard auto disabled, however, the touch pad still enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 Uname: Linux 3.18.0-031800-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Sun Mar 15 04:37:14 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:064d] InstallationDate: Installed on 2015-02-06 (36 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 11 - 3147 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-031800-generic root=UUID=5a93f377-0fc2-41fa-80da-8f3375cd5306 ro quiet splash atkbd.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TWP67 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd01/23/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0TWP67:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Mar 15 04:30:39 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432236 Title: lid hinge 360 degree, touch pad is not disabled automatically Status in xorg package in Ubuntu: New Bug description: dell 3147(dell 11 3000) , lid hinged and the keyboard auto disabled, however, the touch pad still enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 Uname: Linux 3.18.0-031800-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Sun Mar 15 04:37:14 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:064d] InstallationDate: Installed on 2015-02-06 (36 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 11 - 3147 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-031800-generic root=UUID=5a93f377-0fc2-41fa-80da-8f3375cd5306 ro quiet splash atkbd.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TWP67 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A04 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd01/23/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0TWP67:rvrA00:cvnDellInc.:ct8:cvrA04: dmi.product.name: Inspiron 11 - 3147 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
[Touch-packages] [Bug 1432171] Re: Starting version 219 systemd-boot
** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: Starting version 219 systemd-boot Status in systemd package in Ubuntu: Confirmed Bug description: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://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 1429388] Re: Can't select sunday 29.03.2015
** Branch linked: lp:~charlesk/indicator-datetime/lp-1429388-fix-start- of-day-calculation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1429388 Title: Can't select sunday 29.03.2015 Status in indicator-datetime package in Ubuntu: Triaged Bug description: Can't select sunday 29.03.2015 in calendar. Date is changing to 28.03.2015 immediately. See the video. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 15:12:01 2015 InstallationDate: Installed on 2014-11-04 (122 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1429388/+subscriptions -- Mailing list: https://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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
Also, an addendum to the previous instructions, the Ubuntu repo that has version 1.2.3-0ubuntu2.5 of lightdm is the precise-updates repo. To add that repository, do the following: From terminal: sudo gedit /etc/apt/sources.list Add the following lines to the end of your file: ## Ubuntu Update Repos deb http://us.archive.ubuntu.com/ubuntu/ precise-updates main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ precise-updates main restricted universe multiverse Save changes, close the file, then run the following from Terminal: sudo apt-get update sudo apt-get install lightdm=1.2.3-0ubuntu2.5 -- 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/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage Status in lightdm package in Ubuntu: Confirmed Bug description: Since updating lightdm today, one core of my CPU is always maxed out at 100%. I rolled back to version 1.2.3-0ubuntu2.5 and the issue stopped. I tried this with 2 different kernels: 3.2.0-77-generic and 3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still caused 100% cpu usage. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Thu Mar 12 20:20:12 2015 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+subscriptions -- Mailing list: https://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 1429388] Re: Can't select calendar days where DST springs forward
** Summary changed: - Can't select sunday 29.03.2015 + Can't select calendar days where DST springs forward ** Changed in: indicator-datetime (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1429388 Title: Can't select calendar days where DST springs forward Status in indicator-datetime package in Ubuntu: In Progress Bug description: Can't select sunday 29.03.2015 in calendar. Date is changing to 28.03.2015 immediately. See the video. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 7 15:12:01 2015 InstallationDate: Installed on 2014-11-04 (122 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1429388/+subscriptions -- Mailing list: https://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 1394849] Re: package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned
** Package changed: glibc (Ubuntu) = ureadahead (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394849 Title: package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in ureadahead package in Ubuntu: Confirmed Bug description: error happened during dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc-bin 2.19-13ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Thu Nov 20 18:06:54 2014 Dependencies: gcc-4.9-base 4.9.2-1ubuntu1 libc6 2.19-13ubuntu2 libcap2 1:2.24-0ubuntu2 libgcc1 1:4.9.2-1ubuntu1 multiarch-support 2.19-13ubuntu2 DuplicateSignature: package:libc-bin:2.19-13ubuntu2:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-30 (21 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141028) SourcePackage: glibc Title: package libc-bin 2.19-13ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1394849/+subscriptions -- Mailing list: https://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 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Changed in: gnutls26 (Debian) Status: Confirmed = Fix Released ** Changed in: sudo (Debian) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in gnutls26 source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in gnutls26 source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in gnutls26 source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in gnutls26 source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in gnutls26 source package in Precise: Invalid Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: Invalid Status in sudo source package in Precise: Invalid Status in gnutls26 source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Fix Released Status in libgcrypt11 package in Debian: Fix Released Status in libnss-ldap package in Debian: Fix Released Status in sudo package in Debian: Fix Released Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://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 1432234] [NEW] Reboot after quick and dirty openFrameworks workaround
Public bug reported:
code
$ uname -a
Linux nil-NV57H 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14
UTC 2015 x86 64 x86_64 GNU/Linux
/code
The laptop trackpad has ceased its functioning after the steps outlined below.
I have attempted reloading the psmouse module via
code
modprobe -r !$ modprobe !$ ;
/code
to no avail. Ubuntu still responds to the left/0 button, however.
code
egrep Name|Handlers /proc/bus/input/devices ;
/code
Defines
code
Name=ETPS/2 Elantech Touchpad
Handlers=mouse0 event6
/code
as the mouse handler.
//
FOOT NOTE ON INSTALLING OPENFRAMEWORKS
openFrame works shell script at
${ofRoot}/scripts/linux/ubuntu/install_dependancies.sh WILL NOT RUN in the
manner defined by the openFrameworks documentation:
code
sudo ./install_dependancies.sh ;
/code
The error message suggested that my internet connection may be failing;
however, this was not true, so I installed the gstreamer plug-ins in the final
if block (of the referenced script, snippet to follow) via codeapt-get
install; /code
code
apt-get update
GSTREAMER_VERSION=0.10
GSTREAMER_FFMPEG=gstreamer${GSTREAMER_VERSION}-ffmpeg
echo detecting latest gstreamer version
apt-cache show libgstreamer1.0-dev
exit_code=$?
if [ $exit_code = 0 ]; then
echo selecting gstreamer 1.0
GSTREAMER_VERSION=1.0
GSTREAMER_FFMPEG=gstreamer${GSTREAMER_VERSION}-libav
fi
# {...}
echo installing gstreamer
apt-get install libgstreamer${GSTREAMER_VERSION}-dev
libgstreamer-plugins-base${GSTREAMER_VERSION}-dev ${GSTREAMER_FFMPEG}
gstreamer${GSTREAMER_VERSION}-pulseaudio gstreamer${GSTREAMER_VERSION}-x
gstreamer${GSTREAMER_VERSION}-plugins-bad gstreamer${GSTREAMER_VERSION}-alsa
gstreamer${GSTREAMER_VERSION}-plugins-base
gstreamer${GSTREAMER_VERSION}-plugins-good
exit_code=$?
if [ $exit_code != 0 ]; then
echo error installing gstreamer, there could be an error with your
internet connection
echo if the error persists, please report an issue in github:
http://github.com/openframeworks/openFrameworks/issues;
exit $exit_code
fi
/code
I installed gstreamer 1.0, and (of course, to my chagrin) that did not
solve the dependancy issue. I attempted to install each of the
dependancies with apt-get individually (the ones in this if block, where
i thought the problem was), and found that gstreamer0.10-ffmpeg package
is not available in the standard repositories. I did install the
gstreamer0.10-ffmpeg package from a third party. However, the script
still did not recognize that all of the dependancies were installed!
A clever person on the openFrameworks community forum announced that if
you (fix broken and install the packages freeglut3 freeglut3-dev
freeglut3-dbg) via synaptic install_dependancies.sh runs without errors.
By some freak twist of package manangement abstraction the script only
worked properly after that operation. I did just go ahead and install
synaptic to replicate the experiment accurately: I do not know if I
could have just installed those packages through apt-get without broken
dependancies. If so, openFrameworks should know that freeglut3 et al
should be in their linux/ubuntu/install_dependancies.sh script.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.7
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 Mar 14 15:34:04 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0511]
InstallationDate: Installed on 2015-03-13 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
Lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b2dc Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway NV57H
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/17/2012
dmi.bios.vendor: Gateway
dmi.bios.version: V1.19
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV50_HR
dmi.board.vendor: Gateway
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor:
[Touch-packages] [Bug 1432245] [NEW] network-manager no longer recognizes my wifi-device
Public bug reported: Since the update on Thursday, 12 Mar network-manager no longer recognizes my wifi-device. In /var/log/upstart/network-manager.log i find: (NetworkManager:781): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:795): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:792): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:788): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:777): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:764): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:697): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:767): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:776): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:753): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:795): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« (NetworkManager:790): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Die Schlüsselwertedatei enthält nicht die Gruppe »connectivity« ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 14 21:53:52 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-11-25 (473 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 192.168.178.1 dev eth0 proto static 192.168.178.0/23 dev eth0 proto kernel scope link src 192.168.178.5 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-05-03 (315 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL
[Touch-packages] [Bug 1373607] Re: Switching the camera from rear to front to rear facing causing the controls to disappear
** Changed in: canonical-devices-system-image Milestone: ww11-2015 = ww13-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1373607 Title: Switching the camera from rear to front to rear facing causing the controls to disappear Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in camera-app package in Ubuntu: In Progress Status in qtvideo-node package in Ubuntu: In Progress Status in camera-app package in Ubuntu RTM: In Progress Bug description: $ system-image-cli -i current build number: 254 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-09-24 16:38:15 version version: 254 version ubuntu: 20140924 version device: 20140923.1 version custom: mako-0.6 What happened: 1) Start the camera app, note the contols at the bottom (video mode, capture photo, switch camera) 2) Select switch camera to change to the front facing, note the controls are still there 3) Select switch camera again to switch back to rear facing 4) Notice that the controls have disappeared and that the user has to touch the screen for the controls to appear again. What was expected: At step 4 for the controls to be visible To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1373607/+subscriptions -- Mailing list: https://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 992194] Re: BOM symbols in ru_RU.aff affect some package installation
I Confirm this bug. Same problem in 14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+subscriptions -- Mailing list: https://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 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Changed in: libnss-ldap (Debian) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in gnutls26 source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in gnutls26 source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in gnutls26 source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in gnutls26 source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in gnutls26 source package in Precise: Invalid Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: Invalid Status in sudo source package in Precise: Invalid Status in gnutls26 source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Confirmed Status in libgcrypt11 package in Debian: Fix Released Status in libnss-ldap package in Debian: Fix Released Status in sudo package in Debian: Confirmed Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373463] Re: [indicators] Impossible to disable cellular data from indicator
what is the status of this ? I'm using ubuntu touch daily on my phone and this is one of the things I really miss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Network Menu: Triaged Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to help designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1373463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311403] Re: Can't type password after resume.
*** This bug is a duplicate of bug 1311316 *** https://bugs.launchpad.net/bugs/1311316 another workaround without the risk of losing your work: http://askubuntu.com/questions/463372/lightdm-cannot-type-password-on- login-screen Does anyone know if there is a fix for this issue perhaps available in 15.04 when it arrives? I have encountered this bug since 12.04 LTS on very random occasions. Was a major letdown that it was present even in 14.04 LTS . Have not tested with 14.10. -- 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/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
Let me chime in here as maintainer of NM in Debian: The reason why we ship the patch, which removes Wants/Before=network.target is, that this lead to dependency cycles if services/sysv init scripts in rcS (sysinit.target) had Should-Start/Required-Start: $network, like for example /etc/init.d/rpcbind in Debian. If there is no such sysv init script Ubuntu, this patch can be dropped indeed. As for Colin's remark in #25, sounds sensible, to add After=network.target to wpa_supplicant.service as well. Have you tried adding that and see if that fixes the problem on shutdown with WiFi? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Confirmed Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
Sorry, meant Before=network.target, of course... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Confirmed Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1400473] Re: Apache 2.2 on Ubuntu 12.04 LTS only supports TLS1.0 which is vulnerable to BEAST attack
[Expired for openssl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssl (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1400473 Title: Apache 2.2 on Ubuntu 12.04 LTS only supports TLS1.0 which is vulnerable to BEAST attack Status in openssl package in Ubuntu: Expired Bug description: For PCI compliance, one must not be vulnerable to the POODLE or BEAST or CRIME attacks. POODLE suggests removing SSLv2 and SSLv3, and BEAST suggests removing TLSv1. However, since TLSv1.1 and TLSv1.2 do not seem to be supported by apache 2.2 on 12.04 LTS, and since apache 2.4 on 12.04 LTS does not support PHP 5.3.X, the last branch to allow PHP register_globals, which is required for lots of legacy production code often used by sites with payment systems, and since Ubuntu 14.04 LTS does not support apache 2.2, and since Ubuntu 10.04 LTS does not support SHA256 signed SSL certificates, there may be no feasible way for someone to run a credit card processing system with any Ubuntu LTS system if they require both PCI compliance and PHP register_globals support. It looks like manually compiling PHP may be the only plausible way to surmount this issue in this particular circumstance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1400473/+subscriptions -- Mailing list: https://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 1432294] [NEW] ibus max cpu and freeze when typing in firefox location bar
Public bug reported: When using Ibus for text entry into the firefox location bar I regularly get freezes of 5 - 20 seconds. Looking at 'top' both ibus and firefox are maxing out CPU. On return from the freeze I can type freely but if I leave and return to location or I go to a new tab location bar the problem will often but not always occur again. I don't see this in the search box (Ctrl K) and I don't see this in other software using IBus - eg. Gedit, chrome location bar, terminals.. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 15 13:01:56 2015 InstallationDate: Installed on 2015-03-07 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1432294 Title: ibus max cpu and freeze when typing in firefox location bar Status in ibus package in Ubuntu: New Bug description: When using Ibus for text entry into the firefox location bar I regularly get freezes of 5 - 20 seconds. Looking at 'top' both ibus and firefox are maxing out CPU. On return from the freeze I can type freely but if I leave and return to location or I go to a new tab location bar the problem will often but not always occur again. I don't see this in the search box (Ctrl K) and I don't see this in other software using IBus - eg. Gedit, chrome location bar, terminals.. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 15 13:01:56 2015 InstallationDate: Installed on 2015-03-07 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1432294/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network{, -online}.target
Indeed, this morning it just occurred to me that this is missing. Indeed
our unit doesn't have that, this was fixed later upstream. This is
indeed fixed in upstream's unit, but not in our's.
** Changed in: network-manager (Ubuntu)
Status: Triaged = In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Summary changed:
- cifs mount hangs on shutdown - NetworkManager needs to stop after
network{,-online}.target
+ cifs mount hangs on shutdown - NetworkManager needs to stop after
network.target
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
cifs mount hangs on shutdown - NetworkManager needs to stop after
network.target
Status in network-manager package in Ubuntu:
In Progress
Bug description:
To replicate, perform a manual cifs mount, for example:
sudo mount -t cifs -o credentials=,user,rw,uid=1000
//192.168.1.nnn/docs /media/test_mount
Then shutdown. When booted with systemd there is a 1 to 2 minute
delay before shutdown. In syslog the last shutdown (09:47:11 13th
March) showed the effect, though I fear that syslog shuts down too
early to see anything.
If booted with upstart there is no noticeable delay on shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 09:50:08 2015
InstallationDate: Installed on 2014-10-21 (142 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
MachineType: FUJITSU LIFEBOOK A544
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.18
dmi.board.name: FJNBB35
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK A544
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions
--
Mailing list: https://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 1428337] Re: MATE power statistics crashed
** Branch linked: lp:ubuntu/upower -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1428337 Title: MATE power statistics crashed Status in Upower: Fix Released Status in mate-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower package in Debian: Confirmed Bug description: MATE Power Statistics will crash. Just click between a few tabs and power sources and it will soon die :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: mate-power-manager 1.8.1+dfsg1-3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 4 21:26:28 2015 ExecutablePath: /usr/bin/mate-power-statistics InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150304) ProcCmdline: /usr/bin/mate-power-statistics --device /org/freedesktop/UPower/devices/battery_BAT0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-power-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1428337/+subscriptions -- Mailing list: https://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 1069218] Re: users.conf doesn't match users.c
changing to verfication-failed, the update is at least creating a 100% cpu use for quite some users in trusty, see bug #1431654, the tag is to avoid having the SRU validated and copied over to updates before that's resolved ** Tags removed: verification-done ** Tags added: verification-failed -- 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/1069218 Title: users.conf doesn't match users.c Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in Light Display Manager 1.8 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Committed Status in lightdm source package in Trusty: Fix Released Bug description: [Impact] The default users.conf provided by LightDM mentions a section [UserAccounts]. It should be [UserList]. [Test Case] 1. Check default installed users.conf Expected result: Should have a [UserList] section with all items available but disabled. Observed result: Have a [UserAccounts] section with all items available but disabled. [Regression Potential] Very low - just changing the default configuration file which has no active configuration items. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1069218/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu11 --- network-manager (0.9.10.0-4ubuntu11) vivid; urgency=medium * Disable 0001-Debian-specific-tweaks-for-NetworkManager-systemd-se.patch. We actually do want NetworkManager stop after network.target. Fixes long shutdown hangs with remote mounts, and other network services which need connectivity on shutdown. (LP: #1431774) -- Martin Pitt martin.p...@ubuntu.com Sat, 14 Mar 2015 07:42:18 +0100 ** Changed in: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Fix Released Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1432070] Re: package initramfs-tools 0.103ubuntu13 failed to install/upgrade: triggers looping, abandoned
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/1432070 Title: package initramfs-tools 0.103ubuntu13 failed to install/upgrade: triggers looping, abandoned Status in initramfs-tools package in Ubuntu: Confirmed Bug description: sudo apt-get upgrade -y ProblemType: Package DistroRelease: Ubuntu 15.04 Package: initramfs-tools 0.103ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Fri Mar 13 23:46:26 2015 DuplicateSignature: package:initramfs-tools:0.103ubuntu13:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-02-18 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu13 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2015-03-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1432070/+subscriptions -- Mailing list: https://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 1367870] Re: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome
Unfortunately the motherboard was trashed by the incorrect BIOS update. After 2 weeks and quite a bit of money I now have a new system - but using a different motherboard and a different graphics card (Nvidia this time). The guy who fixed the system thought the previous AMD card was broken, although I had seen no sign of that myself. Since my system has changed so much I can no longer provide you with debug info on this issue. So feel free to close it unless you think someone else will have a similar setup and be able to provide you with the relevant info. I'll be much more careful upgrading my BIOS in the future; i.e., I won't unless I absolutely have to! -- 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/1367870 Title: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome Status in xorg package in Ubuntu: Incomplete Bug description: I'm reporting this bug at the request of k...@chromium.org at https://code.google.com/p/chromium/issues/detail?id=404357#c34 . Please see https://code.google.com/p/chromium/issues/detail?id=404357 for details. The appropriate package for this bug might be xserver- xorg-video-ati but that's a guess. Summary: Using Google Chrome 36+ on an ubuntu 14.04 system with an AMD Radeon HD 6330M graphics card has been regularly causing system hangs. These appear to be particularly likely when playing Flash-based games such as those on Facebook. Scroll up and down using the vertical scrollbar or the mousewheel and chrome will segfault. WORKAROUND: Use fglrx. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 10 19:29:10 2014 DistUpgraded: 2014-07-06 18:19:11,036 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Robson LE [Radeon HD 6330M] [1002:68e5] (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Cedar [Radeon HD 5450] [148c:5450] InstallationDate: Installed on 2013-10-19 (326 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MachineType: MEDIONPC MS-7366 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=57c8f83f-22f9-4998-9943-259a1df235a0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-07-06 (66 days ago) XorgConf: Section Module Loadglx EndSection dmi.bios.date: 01/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7366NM7.20E dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7366 dmi.board.vendor: MEDIONPC dmi.board.version: 2.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7366NM7.20E:bd01/08/2008:svnMEDIONPC:pnMS-7366:pvr2.2:rvnMEDIONPC:rnMS-7366:rvr2.2:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7366 dmi.product.version: 2.2 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 10 19:00:35 2014 xserver.configfile: /etc/X11/xorg.conf 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/1367870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1367870] Re: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome
Lucas Partridge, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1367870/comments/13 regarding you no longer have the original hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xorg (Ubuntu) Status: Incomplete = Invalid -- 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/1367870 Title: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome Status in xorg package in Ubuntu: Invalid Bug description: I'm reporting this bug at the request of k...@chromium.org at https://code.google.com/p/chromium/issues/detail?id=404357#c34 . Please see https://code.google.com/p/chromium/issues/detail?id=404357 for details. The appropriate package for this bug might be xserver- xorg-video-ati but that's a guess. Summary: Using Google Chrome 36+ on an ubuntu 14.04 system with an AMD Radeon HD 6330M graphics card has been regularly causing system hangs. These appear to be particularly likely when playing Flash-based games such as those on Facebook. Scroll up and down using the vertical scrollbar or the mousewheel and chrome will segfault. WORKAROUND: Use fglrx. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 10 19:29:10 2014 DistUpgraded: 2014-07-06 18:19:11,036 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Robson LE [Radeon HD 6330M] [1002:68e5] (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Cedar [Radeon HD 5450] [148c:5450] InstallationDate: Installed on 2013-10-19 (326 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MachineType: MEDIONPC MS-7366 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=57c8f83f-22f9-4998-9943-259a1df235a0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-07-06 (66 days ago) XorgConf: Section Module Loadglx EndSection dmi.bios.date: 01/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7366NM7.20E dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7366 dmi.board.vendor: MEDIONPC dmi.board.version: 2.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7366NM7.20E:bd01/08/2008:svnMEDIONPC:pnMS-7366:pvr2.2:rvnMEDIONPC:rnMS-7366:rvr2.2:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7366 dmi.product.version: 2.2 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 10 19:00:35 2014 xserver.configfile: /etc/X11/xorg.conf 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/1367870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
Re: [Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users
On Sat, Mar 14, 2015 at 1:41 AM, Gunnar Hjalmarsson 1430...@bugs.launchpad.net wrote: On 2015-03-12 18:59, Aron Xu wrote: On 2015-03-12 17:00, Ikuya Awashiro wrote: Japanese users prefer to use Fcitx, too. @Ikuya, you might want to talk to people on #ubuntu-desktop (alternatively discuss on ubuntu-desktop@l.u.c) about the preference of Japanese users, and we can work this out if there's an agreement. @Aron: Please note that there is a Japanese remix with fcitx as default. https://bugs.launchpad.net/indicator-keyboard/+bug/1363150/comments/8 So considering that debian/rules in im-config is about to be changed in 15.04, Ikuya's request has to be dealt with instantly. (Not much time for discussion.) The above speaks for adding a ja_JP fcitx entry to locale_prefs. @Nobuto: Do you have any input on this? I don't have any objections on making fcitx default for Japanese users, it should be up to their choice. Motivation behind this FFe is giving fcitx a try in a wider range of audience before we can decide whether Ubuntu shall switch to use it as default, and desktop team agreed on doing that for Chinese users first. So if @nobuto can tell that using fcitx as default is desired for Japanese users, let's talk with other people on desktop team next week (preferably on IRC). Even this makes me think about whether it's desirable for Korean users, but if no one speak up let's leave it as is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+subscriptions -- Mailing list: https://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 1428337] Re: MATE power statistics crashed
This bug was fixed in the package upower - 0.99.2-2 --- upower (0.99.2-2) experimental; urgency=medium * libupower: Fix crash due to uninitialized GVariant. (Closes: #774546, LP: #1428337) -- Martin Pitt mp...@debian.org Fri, 13 Mar 2015 15:59:59 +0100 ** Changed in: upower (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 upower in Ubuntu. https://bugs.launchpad.net/bugs/1428337 Title: MATE power statistics crashed Status in Upower: Fix Released Status in mate-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower package in Debian: Confirmed Bug description: MATE Power Statistics will crash. Just click between a few tabs and power sources and it will soon die :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: mate-power-manager 1.8.1+dfsg1-3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 4 21:26:28 2015 ExecutablePath: /usr/bin/mate-power-statistics InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150304) ProcCmdline: /usr/bin/mate-power-statistics --device /org/freedesktop/UPower/devices/battery_BAT0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-power-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1428337/+subscriptions -- Mailing list: https://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 1432126] [NEW] Evince denied from opening
Public bug reported: Apparmor is denying evince from running. It initially started when I tried opening a PDF attachment in Thunderbird. Saving the file to disk and opening via nautilus renders the same result. Trying to just open evince without a file doesn't work as well. Mar 14 11:10:00 host evince[27787]: audit-1400 apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 Mar 14 11:10:00 host kernel: audit: type=1400 audit(1426324200.744:33): apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 Mar 14 11:10:00 host evince.desktop[27787]: No protocol specified Mar 14 11:10:00 host evince.desktop[27787]: ** (evince:27787): WARNING **: Could not open X display Mar 14 11:10:00 host evince[27787]: audit-1400 apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apparmor 2.9.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 14 11:07:03 2015 InstallationDate: Installed on 2015-02-08 (33 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=80974ebe-fd7c-446d-89c5-23bf40b9b915 ro quiet splash SourcePackage: apparmor Syslog: Mar 14 00:31:22 tanagra dbus[775]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-gnome Importance: Undecided Status: New ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: ubuntu-gnome Importance: Undecided Status: New -- 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/1432126 Title: Evince denied from opening Status in Ubuntu GNOME: New Status in apparmor package in Ubuntu: New Bug description: Apparmor is denying evince from running. It initially started when I tried opening a PDF attachment in Thunderbird. Saving the file to disk and opening via nautilus renders the same result. Trying to just open evince without a file doesn't work as well. Mar 14 11:10:00 host evince[27787]: audit-1400 apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 Mar 14 11:10:00 host kernel: audit: type=1400 audit(1426324200.744:33): apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 Mar 14 11:10:00 host evince.desktop[27787]: No protocol specified Mar 14 11:10:00 host evince.desktop[27787]: ** (evince:27787): WARNING **: Could not open X display Mar 14 11:10:00 host evince[27787]: audit-1400 apparmor=DENIED operation=open profile=/usr/bin/evince name=/run/user/1000/gdm/Xauthority pid=27787 comm=evince requested_mask=r denied_mask=r fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apparmor 2.9.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 14 11:07:03 2015 InstallationDate: Installed on 2015-02-08 (33 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=80974ebe-fd7c-446d-89c5-23bf40b9b915 ro quiet splash SourcePackage: apparmor Syslog: Mar 14 00:31:22 tanagra dbus[775]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1432126/+subscriptions -- Mailing list: https://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 1007423] Re: ibus won't turn 'on' when in certain programs
Look like this problem exist for long time. But as far as I remember last LTS 12.04 ibus does not behavior like this. It change when I use the shortcut key. I can confirm the Ibus-daemon is working. When I use my shortcut key CTRL + space, I can see the input change from English to Chinese in the daemon at panel (in my case). But when I type, it still show english. I can only type Chinese if I switch it using mouse. I also observe 1 problem. The ibus will stick to the input of previous shutdown. If I used Chinese in my previous shutdown, the next time, it will keep showing Chinese. Even I switch it, it still show Chinese in the next program. The only solution is restart the ibus-daemon. So bad, don't have other better input method. I still like the old version of SCIM input at 8.04. So bad the -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1007423 Title: ibus won't turn 'on' when in certain programs Status in ibus package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Won't Fix Status in libreoffice package in Fedora: Unknown Bug description: What I expect to happen: I can turn on and change and use input methods in ibus in any program. What really happens: When in gedit, ibus turns on fine and I can input in Japanese (anthy) and other languages e.g. Chinese pinyin. However, when using firefox, I can't get the input method to change to anthy or any other from Input method Off using my shortcut keys (Ctrl+Space). If I manually right click ibus icon in the tray and left click the input method (e.g. anthy), the first time, the bullet point changes to anthy AND Input method Off, the second time it will change completely to anthy but sometimes it stays at Input method Off. Even if the bullet point changes to anthy, I am not able to input in anthy at all. The first time I turned ibus 'on' to anthy in EiskaltDC++ it worked, however the following times it didn't work at all. When I restart ibus, and try to switch to anthy or another input using right-click on the ibus icon, I only see No input window where there should be input methods. However, when I switch to kate/gedit, I am able to use any other input method, and can switch input methods using keyboard shortcut or GUI click menu. After switching to another input method (e.g. anthy), I am able to switch to other input methods in apps that I can't use other input methods in (e.g. firefox) via the GUI click menu (but not keyboard shortcut). If I check Share the same input method among all applications: -- and switch to anthy (or any other input method besides Input method Off) in gedit, I am able to type using anthy in gedit, but when I switch programs to firefox for example, it won't work. I can see the anthy logo in the tray icon, and also in the anthy menu, but all the switch input mode typing mode conversion mode dictionary buttons will have disappeared, and only the anthy logo button (change ibus input) and About the input method button remain. -- I can't change the input method (using keyboard shortcut orc GUI click menu) in any application I can't type using other input methods. -- I can also no longer change input methods using the GUI click menu, but must use my shortcut (Alt-Shift_L), even in applications that I can input non-english in (i.e. gedit/kate). Sometimes the GUI click menu displaying input methods with current input method bullet pointed doesn't display correctly, even in apps that I can input non-english in (gedit/kate). I must right-click the tray icon again for it to refresh and display properly. For example, if I switch using the keyboard shortcut, the input method will have changed but the bullet point will still be on the previous input method, unless I right click the tray icon again. To 'input' other languages into firefox (or any other program), I must first type in gedit or kate and then copy the text over to firefox. I can't even type non-english languages in LibreOffice Writer! I'm running Kubuntu 12.04 amd64 with KDE 4.8.3 and IBus 1.4.1-3ubuntu1 (On i5-520M, 4GB, GT330M) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ibus 1.4.1-3ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 1 23:33:41 2012 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) ProcEnviron: LANGUAGE=en_AU TERM=xterm LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1007423/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1426328] Re: Undocking laptop moves windows to different workspaces they were originally
Another undesired behaviour: 1. Undock laptop 2. Suspend laptop by closing lid 3. Resume, open screen lock 4. Click on window (maximised, under another smaller window) 5. Window vanishes 6. Window found on another (one to right) workspace. Similar click on window (or pick one with Alt-Tab) often causes window to get lost and only way to find it is to use Super-Shift-w search for window title. Very annoying feature as work spaces are used just for optimise each task and now I use more time to hunt where the window did go than is saved by those. -- 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/1426328 Title: Undocking laptop moves windows to different workspaces they were originally Status in unity package in Ubuntu: New Bug description: I use desktop with 2x2 workspaces. As hardware, I use dual-head display, i.e. using laptop internal monitor and external monitor connected to docking station. When I undock laptop, in many cases windows move to another workspace they were before undocking. This is a bit annoying as I have windows related to each task in their own workspace and I has to move windows around each time I undock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-desktop 1.325 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 27 13:15:40 2015 InstallationDate: Installed on 2014-09-20 (160 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1426328/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
** Changed in: network-manager (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Fix Committed Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
** Branch linked: lp:~network-manager/network-manager/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Fix Committed Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1432125] [NEW] Program switcher freeze when using three touch program switching in touchpad
Public bug reported: open some random apps. now using touchpad attempt to perform task similar to alt+tab.(three touch twice and drag) now instead of moving the fingers on second touch hold them until alt+tab window appears and release it. the alt+tab window switcher persists even after releasing and is impossibe to remove it dissappears after several seconds but is annoying nontheless. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 14 14:20:55 2015 InstallationDate: Installed on 2015-03-05 (8 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: video of problem https://bugs.launchpad.net/bugs/1432125/+attachment/4345051/+files/bug.mp4 -- 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/1432125 Title: Program switcher freeze when using three touch program switching in touchpad Status in unity package in Ubuntu: New Bug description: open some random apps. now using touchpad attempt to perform task similar to alt+tab.(three touch twice and drag) now instead of moving the fingers on second touch hold them until alt+tab window appears and release it. the alt+tab window switcher persists even after releasing and is impossibe to remove it dissappears after several seconds but is annoying nontheless. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 14 14:20:55 2015 InstallationDate: Installed on 2015-03-05 (8 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432125/+subscriptions -- Mailing list: https://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 1428337] Re: MATE power statistics crashed
** Branch linked: lp:ubuntu/vivid-proposed/upower -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1428337 Title: MATE power statistics crashed Status in Upower: Fix Released Status in mate-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Status in upower package in Debian: Confirmed Bug description: MATE Power Statistics will crash. Just click between a few tabs and power sources and it will soon die :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: mate-power-manager 1.8.1+dfsg1-3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 4 21:26:28 2015 ExecutablePath: /usr/bin/mate-power-statistics InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150304) ProcCmdline: /usr/bin/mate-power-statistics --device /org/freedesktop/UPower/devices/battery_BAT0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-power-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1428337/+subscriptions -- Mailing list: https://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 1431743] Re: fails to boot due to read-ony file system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431743 Title: fails to boot due to read-ony file system Status in systemd package in Ubuntu: Confirmed Bug description: I have just recently done a sudo apt-get upgrade, noting something about an included 219 update -- after consequent reboot, the system now hangs at starting 219. No light on Caps Lock. I have since been using upstart. Kernel using - I am on: Linux kubuntu 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Same error when I try the 3.19.0.7-generic kernel. I have updated Grub, no change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions -- Mailing list: https://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 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver
** Tags removed: 14.04.2 hwe ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1314653 Title: sysvinit: default cpufreq governor to powersave for intel-pstate driver Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Trusty: Fix Committed Status in sysvinit source package in Utopic: Fix Released Bug description: When defaulting to the intel-pstate driver, there are only a couple of cpufreq governors available, none of which are handled in the /etc/init.d/ondemand script. Since this driver is meant to be used for power saving, it seems wrong to leave the system in the kernel default configured performance governor after boot, so I think it is pertinent to set this to powersave if it is the only suitable non-power hungry governor available. How to reproduce: 1. enable the intel_pstate driver on a recent Intel machine (Sandybridge or above) edit /etc/default/grub, modify the following: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash intel_pstate=enable and run: sudo update-grub and reboot. 2. login 3. wait at least 60 seconds for /etc/init.d/ondemand to complete check out the default cpufreq governor, you will see it is still set to the boot default of performance: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor With the attached fix the system will boot into a less aggressive cpufreq governor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1314653/+subscriptions -- Mailing list: https://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 1432122] [NEW] mountall service unavailable on systemd, preventing full zfs integration
Public bug reported: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 mountall bug report: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: mountall systemd zfs ** Tags added: mountall systemd zfs ** Description changed: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall - mountall.service -Loaded: masked (/dev/null) -Active: inactive (dead) + mountall.service + Loaded: masked (/dev/null) + Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null - - Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. + Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is + what is keeping all of my zfs filesystems from being automounted at + boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 + mountall bug report: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123 -- 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/1432122 Title: mountall service unavailable on systemd, preventing full zfs integration Status in systemd package in Ubuntu: New Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 mountall bug report: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122/+subscriptions -- Mailing list: https://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 1432123] [NEW] mountall service unavailable on systemd, preventing full zfs integration
Public bug reported: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122 ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: mountall systemd zfs ** Tags added: mountall systemd zfs ** Description changed: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall - mountall.service -Loaded: masked (/dev/null) -Active: inactive (dead) + mountall.service + Loaded: masked (/dev/null) + Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null - - Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. + Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is + what is keeping all of my zfs filesystems from being automounted at + boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 - systemd bug report: + systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1432123 Title: mountall service unavailable on systemd, preventing full zfs integration Status in mountall package in Ubuntu: New Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123/+subscriptions -- Mailing list: https://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 836616] Re: 100% cpu usage in lightdm
Hi, I also confirm this bug on Ubuntu 12.04.5 LTS, after the latest update : lightdm constantly uses 100% CPU just after login. Forcing the downgrade to lightdm 1.2.3-0ubuntu2.5 fixed this. -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+subscriptions -- Mailing list: https://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 836616] Re: 100% cpu usage in lightdm
Same issue here too, Ubuntu 12.04.5 LTS and 1.2.3-0ubuntu2.6 lightdm Thank you -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+subscriptions -- Mailing list: https://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 1432122] Re: mountall service unavailable on systemd, preventing full zfs integration
*** This bug is a duplicate of bug 1431523 *** https://bugs.launchpad.net/bugs/1431523 mountall is upstart specific and not intended to be used under systemd. Duplicating to bug 1431523. Thanks! ** This bug has been marked a duplicate of bug 1431523 zfs not automounting after upgrading from upstart to systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432122 Title: mountall service unavailable on systemd, preventing full zfs integration Status in systemd package in Ubuntu: New Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 mountall bug report: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122/+subscriptions -- Mailing list: https://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 1432139] [NEW] The font on screen ar distorted and i am not able to read them
Public bug reported: The font on screen ar distorted and i am not able to read them. I have taken the screenshots. This bug can be seen in the menu and the taskbar ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 Mar 14 16:13:28 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationDate: Installed on 2014-10-31 (134 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=fdabc773-5d60-4e7e-bc18-c3f5f885b7d7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. 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.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Mar 14 14:30:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.16.0-1ubuntu1.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu utopic ** Attachment added: Font distorted https://bugs.launchpad.net/bugs/1432139/+attachment/4345084/+files/Screenshot%20from%202015-03-14%2016%3A13%3A58.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432139 Title: The font on screen ar distorted and i am not able to read them Status in xorg package in Ubuntu: New Bug description: The font on screen ar distorted and i am not able to read them. I have taken the screenshots. This bug can be seen in the menu and the taskbar ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 Mar 14 16:13:28 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationDate: Installed on 2014-10-31 (134 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=fdabc773-5d60-4e7e-bc18-c3f5f885b7d7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1432139] Re: The font on screen ar distorted and i am not able to read them
** Attachment added: Screenshot from 2015-03-02 12:25:15.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432139/+attachment/4345123/+files/Screenshot%20from%202015-03-02%2012%3A25%3A15.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432139 Title: The font on screen ar distorted and i am not able to read them Status in xorg package in Ubuntu: New Bug description: The font on screen ar distorted and i am not able to read them. I have taken the screenshots. This bug can be seen in the menu and the taskbar ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 Mar 14 16:13:28 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationDate: Installed on 2014-10-31 (134 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=fdabc773-5d60-4e7e-bc18-c3f5f885b7d7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. 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.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Mar 14 14:30:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432139/+subscriptions -- Mailing list: https://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 1432139] Re: The font on screen ar distorted and i am not able to read them
** Attachment added: Screenshot from 2015-03-02 12:25:15.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432139/+attachment/4345124/+files/Screenshot%20from%202015-03-02%2012%3A25%3A15.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432139 Title: The font on screen ar distorted and i am not able to read them Status in xorg package in Ubuntu: New Bug description: The font on screen ar distorted and i am not able to read them. I have taken the screenshots. This bug can be seen in the menu and the taskbar ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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 Mar 14 16:13:28 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationDate: Installed on 2014-10-31 (134 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 1440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=fdabc773-5d60-4e7e-bc18-c3f5f885b7d7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0K138P dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/20/2009:svnDellInc.:pnInspiron1440:pvr:rvnDellInc.:rn0K138P:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1440 dmi.sys.vendor: Dell Inc. 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.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Mar 14 14:30:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432139/+subscriptions -- Mailing list: https://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 1430893] Re: [FFe] Install Fcitx for Chinese users
As regards Korean, and considering bug #1412036, I suspect that Korean users wish some change: Either the bug fixed or switch to fcitx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
Hello Martin, I still have a 120sec delay at shutdown. Mär 14 12:17:58 holze-desktop kernel: CIFS VFS: Server 192.168.178.1 has not responded in 120 seconds. Reconnecting... Regards, Norbert ** Attachment added: journal.txt https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+attachment/4345154/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Fix Released Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1431743] Re: fails to boot due to read-ony file system
Hi, sry for being late. I have been using upstart all along. I am happy to say I tried the workaround Ricard suggested and it worked for me: Did you do CTRL + ALT + F1? and log in? Then, sudo systemctl enable sddm.service -f sudo reboot Not sure what this means for things going forward, at least it gets me in. Is there anything I need to do further? -- 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/1431743 Title: fails to boot due to read-ony file system Status in systemd package in Ubuntu: Confirmed Bug description: I have just recently done a sudo apt-get upgrade, noting something about an included 219 update -- after consequent reboot, the system now hangs at starting 219. No light on Caps Lock. I have since been using upstart. Kernel using - I am on: Linux kubuntu 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Same error when I try the 3.19.0.7-generic kernel. I have updated Grub, no change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions -- Mailing list: https://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 1431582] Re: there is no wi-fi after suspend mode
The same bug- Asus U38N, Vivid ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Anton (anton-postbox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431582 Title: there is no wi-fi after suspend mode Status in network-manager package in Ubuntu: Confirmed Bug description: During last three days: after suspend mode there is no wi-fi. I have to turn off Network-manager and turn it on again- only after that wi- fi works again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 00:56:10 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (510 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1426197268 Пт. 13 марта 2015 00:54:28 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431582/+subscriptions -- Mailing list: https://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 1088768] Re: Toolbar Won't Appear Upon Hover-Top-Of-Screen After RDP Launches to Monitor2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1088768 Title: Toolbar Won't Appear Upon Hover-Top-Of-Screen After RDP Launches to Monitor2 Status in Unity: New Status in remmina package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When a session is full-screen and scaled onto Monitor 2, Remmina won't display the auto-hide-tool-bar (like it previously did) when I would hover my mouse-cursor at the top of the screen. Therefore, I'm unable to minimize, scale-toggle, full-screen-toggle, etc. When I double-click on a RDP Server Entry (from my list of servers in Remmina), Unity always Launches that session to Monitor 2. I prefer the sessions to launch full-screen and scaled, and Remmina does indeed remember that preference from the last time I connected to that server. However, when the session is full screen (and scaled) on Monitor 2, the hide-away tool bar doesn't appear when I hover my mouse at the top of Monitor2's screen. Because of this, I cannot minimize the session to view other application that are opened behind it (or use any other feature provided on the toolbar: scale-toggle, full-screen-toggle, etc). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: remmina 1.0.0-1ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Dec 10 22:24:30 2012 InstallationDate: Installed on 2012-11-28 (12 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1088768/+subscriptions -- Mailing list: https://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 1432152] [NEW] Can't print
Public bug reported: The cups program crashes. This happens using the Wifi connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 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.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 14 12:51:29 2015 DistUpgraded: 2014-09-27 13:42:13,227 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca] NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2871] InstallationDate: Installed on 2014-02-24 (383 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=nl_NL PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=28478695-9e82-4e38-abd8-57343c56b0a2 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-09-27 (168 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 04/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LE PLUS 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.:bvr0401:bd04/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS: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.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 14 10:11:01 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432152 Title: Can't print Status in xorg package in Ubuntu: New Bug description: The cups program crashes. This happens using the Wifi connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 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
[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
Having tried with wifi connection (was previously wired) I also still see the problem if connected via wifi. ** Changed in: network-manager (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Confirmed Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1432158] [NEW] network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as long to boot to the login screen
Public bug reported: The enablement of NetworkManager-wait-online.service in network-manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly twice as long to boot to the login screen. I did some investigating and determined that this is because sddm.service depends on systemd-user- sessions.service which depends on remote-fs.target which depends on network-online.target which depends on NetworkManager-wait- online.service. For that reason, systemd is apparently waiting to start sddm until both the wired and wireless adapters are connected, which makes the system take much longer to boot. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1432158 Title: network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as long to boot to the login screen Status in network-manager package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: The enablement of NetworkManager-wait-online.service in network- manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly twice as long to boot to the login screen. I did some investigating and determined that this is because sddm.service depends on systemd-user-sessions.service which depends on remote-fs.target which depends on network-online.target which depends on NetworkManager-wait-online.service. For that reason, systemd is apparently waiting to start sddm until both the wired and wireless adapters are connected, which makes the system take much longer to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432158/+subscriptions -- Mailing list: https://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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
I have the latest version of network-manager installed: holze@holze-desktop:~$ dpkg --list | grep network-manager ii network-manager 0.9.10.0-4ubuntu11 amd64network management framework (daemon and userspace tools) ii network-manager-gnome 0.9.10.1-0ubuntu1 amd64network management framework (GNOME frontend) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Fix Released Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- Mailing list: https://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 1432197] [NEW] systemd-analyze plot not plotting appropriately
Public bug reported: After updating to ubuntu-core version 3, systemd-analyze stopped working as expected. A systemctl prints https://gist.github.com/vmayoral/a1b1120f44b8c784c7da. A call to systemd-analyze plot erle-brain.svg is expected to create a plot with all these services however it only contains a few (see the attached file) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd-analyze -- 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/1432197 Title: systemd-analyze plot not plotting appropriately Status in systemd package in Ubuntu: New Bug description: After updating to ubuntu-core version 3, systemd-analyze stopped working as expected. A systemctl prints https://gist.github.com/vmayoral/a1b1120f44b8c784c7da. A call to systemd-analyze plot erle-brain.svg is expected to create a plot with all these services however it only contains a few (see the attached file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432197/+subscriptions -- Mailing list: https://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 1432197] Re: systemd-analyze plot not plotting appropriately
Something else troubling me is the fact that systemd-analyze blame shows only a subset of the services https://gist.github.com/vmayoral/2f28b9e3ed0f83a6d02d -- 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/1432197 Title: systemd-analyze plot not plotting appropriately Status in systemd package in Ubuntu: New Bug description: After updating to ubuntu-core version 3, systemd-analyze stopped working as expected. A systemctl prints https://gist.github.com/vmayoral/a1b1120f44b8c784c7da. A call to systemd-analyze plot erle-brain.svg is expected to create a plot with all these services however it only contains a few (see the attached file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432197/+subscriptions -- Mailing list: https://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 1432197] Re: systemd-analyze plot not plotting appropriately
** Attachment added: erle-brain.svg https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432197/+attachment/4345382/+files/erle-brain.svg -- 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/1432197 Title: systemd-analyze plot not plotting appropriately Status in systemd package in Ubuntu: New Bug description: After updating to ubuntu-core version 3, systemd-analyze stopped working as expected. A systemctl prints https://gist.github.com/vmayoral/a1b1120f44b8c784c7da. A call to systemd-analyze plot erle-brain.svg is expected to create a plot with all these services however it only contains a few (see the attached file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432197/+subscriptions -- Mailing list: https://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 1429137] Re: Chrome crash on startup, after Kubuntu 14.04.2 fresh install, may be related to bug 1424263, which also affects me
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1429137 Title: Chrome crash on startup, after Kubuntu 14.04.2 fresh install, may be related to bug 1424263, which also affects me Status in mesa package in Ubuntu: Confirmed Bug description: I downloaded and installed Google Chrome 64 bit official deb, and when I get this blowout in the command line: $ google-chrome-stable [1:1:0306/095859:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif. [7748:7748:0306/095859:ERROR:browser_main_loop.cc(198)] GTK theme error: Unable to locate theme engine in module_path: oxygen-gtk, [7748:7748:0306/095859:ERROR:browser_main_loop.cc(198)] GTK theme error: Unable to locate theme engine in module_path: oxygen-gtk, Aborted (core dumped) Since I have not found the problem reported somewhere else in Google Chrome's product forum, I posted a bug report: https://productforums.google.com/forum/#!category- topic/chrome/report-a-problem-and-get-troubleshooting- help/linux/Stable/LniyR9bsfus, but then I also tried to install Steam and ended up on the page with the bug number 1424263: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263. I guess the two bugs may be related in the sense that the update of the Kubuntu install disk may have triggered them both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1429137/+subscriptions -- Mailing list: https://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 1432177] Re: #1432171
*** This bug is a duplicate of bug 1432171 *** https://bugs.launchpad.net/bugs/1432171 ** This bug has been marked a duplicate of bug 1432171 Starting version 219 systemd-boot -- 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/1432177 Title: #1432171 Status in systemd package in Ubuntu: New Bug description: I can confirm the bug with Starting version 219 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432177/+subscriptions -- Mailing list: https://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 1417429] Re: back port signon-plugin-oauth2 Sina weibo fix to rtm
** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = In Progress ** Changed in: canonical-devices-system-image Milestone: None = ww13-ota ** Changed in: canonical-devices-system-image Assignee: (unassigned) = David Barth (dbarth) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-plugin-oauth2 in Ubuntu. https://bugs.launchpad.net/bugs/1417429 Title: back port signon-plugin-oauth2 Sina weibo fix to rtm Status in the base for Ubuntu mobile products: In Progress Status in signon-plugin-oauth2 package in Ubuntu: In Progress Bug description: We have already createtd a RTM (14.10) image for the developers contest in China. Due to some limitation of the Sina weibo API, it wrongly returns the message type (text/plain) which is incorrect for json content. Mardy has fixed the issue, and it is finally landed to vivid. The developers in China is recommended using rtm since it is more stable. The contest started Dec 18th last year, and it will be ended June this year. Sina weibo is an important social network service in China. Some developers may use it for their development for the competition. It is strongly recommended backporting the fix to rtm. This problem happens on RTM image of the phone. it seems that it is duplicated bug report as https://bugs.launchpad.net/ubuntu/+source/signon-plugin- oauth2/+bug/1415376 Thanks best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417429/+subscriptions -- Mailing list: https://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 1431798] Re: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes
** Attachment added: _usr_bin_unity8-dash.32011.crash https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431798/+attachment/4345301/+files/_usr_bin_unity8-dash.32011.crash -- 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/1431798 Title: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes Status in unity8 package in Ubuntu: Incomplete Bug description: Original is bug #1431440: I was simply paging through the scopes ad got this crash. I swiped in in the open dialer app and then I see the scopes restarting Reproduced three times in a row,and after a reboot. mako running 213 rtm ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150226~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Thu Mar 12 12:05:54 2015 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1424989859 InstallationDate: Installed on 2015-03-12 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) LocalLibraries: /android/system/lib/libadreno_utils.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libcorkscrew.so /android/system/lib/libGLESv1_CM.so /android/system/lib/libGLES_trace.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libmemalloc.so /android/system/lib/libui.so /android/system/lib/libGLESv2.so /android/system/lib/libhardware.so /android/system/lib/libc.so /android/system/lib/libstdc++.so /android/system/lib/libstlport.so /android/system/lib/libdsyscalls.so /android/system/lib/libm.so /android/system/lib/libsync.so /android/system/lib/libsc-a3xx.so /android/system/lib/libz.so /android/system/lib/libcutils.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libqdutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libgsl.so /android/system/lib/libutils.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/liblog.so /android/system/lib/libEGL.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 7 SourcePackage: unity8 StacktraceTop: QMutex::lock() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Title: unity8-dash crashed with signal 7 in QMutex::lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431798/+subscriptions -- Mailing list: https://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 1090293] Re: Crash on using exec
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1090293 Title: Crash on using exec Status in bash package in Ubuntu: Confirmed Status in bash package in Debian: New Bug description: I'm using Ubuntu 13.04 dev with bash 4.2-5ubuntu2. Using exec with any command (for example exec echo 0) will cause the terminal to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- Mailing list: https://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 1432171] [NEW] Starting version 219 systemd-boot
Public bug reported: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: systemd-boot ** Tags added: systemd-boot ** Description changed: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. + Ubuntu version: Kubuntu 15.04 Beta 1 + systemd package: systemd219-4ubuntu5 + + systemd-boot -- 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/1432171 Title: Starting version 219 systemd-boot Status in systemd package in Ubuntu: Confirmed Bug description: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://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 1090293] Re: Crash on using exec
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' - DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-l$ uname output: Linux josua 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 4.3 Patch Level: 11 Release Status: release Description: exec hangs up when using exec 2SOMETHING. Just tested on Ubuntu 14.04, Ubuntu 12.04, Debian7 working when just using exec 1SOMETHING Repeat-By: using in a script for logging or just try it in bash or dash Fix: Dont't know how to fix it Just using the workaround with PATH/SCRIPT 2SOMETHING which does not use exec ** Also affects: bash (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1090293 Title: Crash on using exec Status in bash package in Ubuntu: Confirmed Status in bash package in Debian: New Bug description: I'm using Ubuntu 13.04 dev with bash 4.2-5ubuntu2. Using exec with any command (for example exec echo 0) will cause the terminal to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- Mailing list: https://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 1432171] Re: Starting version 219 systemd-boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: Starting version 219 systemd-boot Status in systemd package in Ubuntu: Confirmed Bug description: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://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 1432173] [NEW] fails to bring up network bridge
Public bug reported: Probably a dup of #1430675 After upgrading to vivid with systemd my network bridge isn't configured on boot: $ systemctl --all |grep ifup ● ifup-wait-all-auto.service loadedfailed failed Wait for all auto /etc/network/interfaces to be up for network-online.target ● ifup@eth0.service loadedfailed failed ifup for eth0 ifup@eth1.service loadedactive exited ifup for eth1 ifup@lxcbr0.service loadedactive exited ifup for lxcbr0 ifup@virbr0-nic.service loadedactive exited ifup for virbr0/nic ifup@virbr0.service loadedactive exited ifup for virbr0 ifup@wlan0.service loadedactive exited ifup for wlan0 system-ifup.slice loadedactive active system-ifup.slice $ journalctl -u ifup-wait-all-auto.service -- Logs begin at Sat 2015-03-14 15:17:08 CET, end at Sat 2015-03-14 15:21:30 CET. -- Mar 14 15:17:56 yofel-desktop systemd[1]: Starting Wait for all auto /etc/network/interfaces to be up for network-online.target... Mar 14 15:17:56 yofel-desktop sh[1114]: Segmentation fault Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service start operation timed out. Terminating. Mar 14 15:19:56 yofel-desktop systemd[1]: Failed to start Wait for all auto /etc/network/interfaces to be up for network-online.target. Mar 14 15:19:56 yofel-desktop systemd[1]: Unit ifup-wait-all-auto.service entered failed state. Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service failed. $ sudo ifconfig br0 up br0: ERROR while getting interface flags: No such device $ sudo ifup br0 /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Waiting for DAD... Done resolv.conf is intentionally a regular file. But after running ifup the bridge works fine. interfaces: auto lo br0 iface lo inet loopback iface eth0 inet manual iface br0 inet static address 192.168.1.5 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth1 bridge_stp off bridge_maxwait 0 bridge_fd 0 iface br0 inet6 static address fec0::218:f3ff:fe2c:eb60/64 netmask 64 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Sat Mar 14 15:29:24 2015 InstallationDate: Installed on 2011-01-03 (1530 days ago) InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=9c833d6f-4685-4a19-ad27-fa60a77a4054 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug systemd-boot vivid ** Tags added: systemd-boot ** Description changed: Probably a dup of #1430675 After upgrading to vivid with systemd my network bridge isn't configured on boot: - $ systemctl --all |grep ifup + $ systemctl --all |grep ifup ● ifup-wait-all-auto.service loadedfailed failed Wait for all auto
[Touch-packages] [Bug 1431836] Re: Boot process takes too long when Ethernet is not connected
@Martin, Everything i shared was done in the BeagleBone Black latest image. Cheers, -- 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/1431836 Title: Boot process takes too long when Ethernet is not connected Status in Snappy Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The boot process takes a minute with Internet access (e.g.: Ethernet) and several minutes when no Ethernet is connected. The kernel dump for the later is shown at https://gist.github.com/vmayoral/135aef30218b8d00d4f1. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1431836/+subscriptions -- Mailing list: https://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 1432177] [NEW] #1432171
*** This bug is a duplicate of bug 1432171 *** https://bugs.launchpad.net/bugs/1432171 Public bug reported: I can confirm the bug with Starting version 219 systemd-boot ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432177 Title: #1432171 Status in systemd package in Ubuntu: New Bug description: I can confirm the bug with Starting version 219 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432177/+subscriptions -- Mailing list: https://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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
** Changed in: intel Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions -- Mailing list: https://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 1432171] Re: Starting version 219 systemd-boot
This is not a bug; it's simply the plymooth comment due to the 'quiet splash' boot options When these options are removed from grub, and then grub updated, that comment is replaced by the full booting process. That is, some user says 'hey what is this ?' while some osthers are scared when nothing is displayed. That's life !!! ** Changed in: systemd (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: Starting version 219 systemd-boot Status in systemd package in Ubuntu: Incomplete Bug description: Everytime the system is booted up I get a Starting version 219 which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://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 1428337] Re: MATE power statistics crashed
** Changed in: upower (Debian) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1428337 Title: MATE power statistics crashed Status in Upower: Fix Released Status in mate-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower package in Debian: Fix Released Bug description: MATE Power Statistics will crash. Just click between a few tabs and power sources and it will soon die :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: mate-power-manager 1.8.1+dfsg1-3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 4 21:26:28 2015 ExecutablePath: /usr/bin/mate-power-statistics InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150304) ProcCmdline: /usr/bin/mate-power-statistics --device /org/freedesktop/UPower/devices/battery_BAT0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-power-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1428337/+subscriptions -- Mailing list: https://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 1090293] Re: Crash on using exec
This is not a bug (see comment 3). ** Changed in: bash (Debian) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1090293 Title: Crash on using exec Status in bash package in Ubuntu: Incomplete Status in bash package in Debian: Invalid Bug description: I'm using Ubuntu 13.04 dev with bash 4.2-5ubuntu2. Using exec with any command (for example exec echo 0) will cause the terminal to crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- Mailing list: https://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 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed
When will this finally get implemented? -- 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/124440 Title: [enhancement] Ubuntu needs a way to set mouse scrolling speed Status in GNOME Control Center: Confirmed Status in GTK+ GUI Toolkit: Confirmed Status in One Hundred Papercuts: Triaged Status in Mir: Triaged Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
