[Touch-packages] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so
** Changed in: debian 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/1371834 Title: Chrome causes segfault in i965_dri.so Status in Chromium Browser: Unknown Status in mesa package in Ubuntu: Confirmed Status in Debian GNU/Linux: Confirmed Bug description: Running chrome 38.0.2125.66-1 on Ubuntu 14.10, on Lenovo X230 When I start a new instance of chrome, it cannot enable WebGL. I have reported that bug separately to chrome at https://code.google.com/p/chromium/issues/detail?id=416207 I suspect the cause of the bug is in mesa, as dmesg contains evidence of a segfault: [31979.398090] chrome[24013]: segfault at 20 ip 7fbbd5ca5d83 sp 7fffd7669ab0 error 4 in i965_dri.so[7fbbd59c4000+50a000] [31979.585606] chrome[24104]: segfault at 20 ip 7f7550c26d83 sp 7fff970b4630 error 4 in i965_dri.so[7f7550945000+50a000] [31979.737378] chrome[24117]: segfault at 20 ip 7ffd06e45d83 sp 7fffc989f440 error 4 in i965_dri.so[7ffd06b64000+50a000] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.2.6-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Sep 20 11:17:41 2014 DistUpgraded: 2014-09-02 14:59:08,481 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO 23301B9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-16-generic root=/dev/mapper/hostname--vg-root ro splash quiet crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to utopic on 2014-09-02 (17 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 23301B9 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn23301B9:pvrThinkPadX230:rvnLENOVO:rn23301B9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23301B9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Sep 19 15:45:16 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4204 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398971] Re: [SATELLITE P50t-B-112, Realtek ALC284, Speaker, Internal] No sound at all
Suddenly now it works. An Alsa package update? I have not tested well before? I have no idea. But now it works. After getting the sound work in configuration test, I also needed to install sound plugins: sudo apt-get install libasound2-plugins:i386 To make the sound work also in firefox and Chrome. -- 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/1398971 Title: [SATELLITE P50t-B-112, Realtek ALC284, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: My sound card is not working under Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2473 F pulseaudio /dev/snd/controlC1: maria 2473 F pulseaudio maria 12484 F alsamixer CurrentDesktop: Unity Date: Wed Dec 3 21:26:29 2014 InstallationDate: Installed on 2014-11-29 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2473 F pulseaudio /dev/snd/controlC1: maria 2473 F pulseaudio maria 12484 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [SATELLITE P50t-B-112, Realtek ALC284, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.10 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.10:bd04/03/2014:svnTOSHIBA:pnSATELLITEP50t-B-112:pvrPSPNVE-01G00FCE:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE P50t-B-112 dmi.product.version: PSPNVE-01G00FCE dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1398971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361825] Re: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
[Expired for pygobject (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pygobject (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1361825 Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in pygobject package in Ubuntu: Expired Bug description: Got this when I started an xubuntu session on utopic. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click-apparmor 0.2.9 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Mon Aug 25 11:20:50 2014 DuplicateSignature: package:click-apparmor:0.2.9:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-31 (452 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: click-apparmor SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1361825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376849] Re: em28xx audio device no sound (Pinnacle Dazzle DVC100, Terratec Grabby)
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1376849 Title: em28xx audio device no sound (Pinnacle Dazzle DVC100, Terratec Grabby) Status in alsa-driver package in Ubuntu: Expired Bug description: I'm getting no input signal at all with these devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-lowlatency 3.13.11.6 Uname: Linux 3.13.0-36-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zequence 1679 F pulseaudio /dev/snd/controlC0: zequence 1679 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 2 19:02:28 2014 InstallationDate: Installed on 2014-10-02 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2111Q0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2111Q0:bd09/08/2008:svnSonyCorporation:pnVGN-CR31Z_R:pvr01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CR31Z_R dmi.product.version: 01 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1376849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374750] Re: Cannot create chroot in 14.04
[Expired for click (Ubuntu) because there has been no activity for 60 days.] ** Changed in: click (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1374750 Title: Cannot create chroot in 14.04 Status in click package in Ubuntu: Expired Bug description: In Trusty, on an amd64 system, running "sudo click chroot -a amd64 -f ubuntu-sdk-14.04 create" terminates with: Reading state information... Done Note, selecting 'libc6-dev' instead of 'libc-dev' E: Unable to locate package g++-x86_64-linux-gnu E: Couldn't find any package by regex 'g++-x86_64-linux-gnu' E: Unable to locate package pkg-config-x86_64-linux-gnu Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 -- /finish.sh I'm adding the full logs as an attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1374750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377239] Re: cups-pdf 2.6.1-9 not able to lookup domain user because apparmor profile
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1377239 Title: cups-pdf 2.6.1-9 not able to lookup domain user because apparmor profile Status in cups package in Ubuntu: Expired Bug description: I use cups-pdf for years now. But now it's no longer able to lookup users from domain. lookup user by getent passwd works fine. lookup user by wbinfo works fine. Login with domain user works fine. kinit username works, too. But cups-pdf with log level 7 tells: unknown user (admin) It's regardless of wether I use UserPrefix MYDOMAIN\ or leave it blank. Just the output of the log file differs to: unknown user (MYDOMAIN\admin) After long time of searching around in all log files I tried to set apparmor profile use.sbin.cupsd to complain mode. That fixes my problem. But what I have to change in apparmor profile to switch back to enforce mode? I don't get any logging by complain, enforce or audit mode in /var/log/syslog. It looks like getpwnam or another method used in cups-pdf.c is restricted by apparmor in Ubuntu 14.04.1 LTS. I use the default cups-pdf.conf and default usr.sbin.cupsd apparmor profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1377239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
The stacktrace looks very similar to the one in this bug: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395455 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385770] Re: [CMI8786 - Xonar DG, playback] No sound at all
I can confirm that using QasMixer to adjust the configuration settings fixes the incorrect default configuration. It looks like Ubuntu configuration ships by default to send audio on this sound card to the front ports (if they exist), rather than the rear ports (that always exist), and then does not provide a clear path to the relevant configuration setting. Installing QasMixer allows easy GUI access to the necessary configuration settings. This is just my intuition, but it appears to be a bug within the default "Sound" panel under "Settings": the Input tab correctly lists both the back and front panel microphones, but the Output tab only lists the back panel speakers (which actually aren't the back panel speaker jacks, but instead sends the audio to the front panel jack, as revealed by QasMixer). I may be entirely incorrect, perhaps it's a driver issue! Hope that helps someone? If I knew anything about programming, I'd take things apart and look myself. Since I don't, I figure I'd add as much detail as I could imagine would be useful in order to help someone else get up to speed on the issue. If anyone has any questions or problems, I've subscribed to this bug report and will (eventually) respond to requests for more information. ** Attachment added: "QasMixer displaying the relevant settings" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385770/+attachment/4275520/+files/Screenshot%20from%202014-12-06%2019%3A54%3A42.png -- 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/1385770 Title: [CMI8786 - Xonar DG, playback] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Since I upgraded to UBUNTU 14.10, I finally had to reinstall ubuntu for half actualiazción error, the computer has been moved. Appear either audio controls on the system configuration, but no sound. Found that: is using the sound card (Asus Xonar) and not the motherboard, so it appears in Sound settings. the speakers are on and in correct volumes. In windows (another partition) still works And the fact is that they do not try to touch or configuration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rafa 1683 F...m pulseaudio /dev/snd/controlC0: rafa 1683 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 26 00:38:26 2014 InstallationDate: Installed on 2014-10-24 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DG failed Symptom_Card: CMI8788 [Oxygen HD Audio] (CMI8786 (Xonar DG)) - Xonar DG Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rafa 1683 F...m pulseaudio /dev/snd/controlC0: rafa 1683 F pulseaudio Symptom_Type: No sound at all Title: [CMI8786 - Xonar DG, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: G41M-S3 dmi.board.vendor: ASRock 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.:bvrP1.50:bd05/16/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400010] [NEW] mv fails to preserve COW on btrfs
Public bug reported:
the /bin/mv command fails to preserve extended attributes, specifically
the COW (lsattr; chattr +C) on btrfs, for both files and directories.
Affects virtual machine images in VirtualBox which perform POORLY if
hosted on btrfs without COW set.
Workaround:
1. Set the folder to have the COW flag (chattr +C .)
2. Back up all of the files (for c in *; do mv $c $c.old; done)
3. Copy the files to the same folder, assuming that there is space, and delete
the backup upon success (for c in $.old; do cp $c ${c/.old/} && rm $c)
User has to copy the file to a COW flagged directory before VirtualBox
will talk correctly to the block device images.
coreutils, 8.21-1ubuntu5, amd64
btrfs-tools, 3.12-1, amd64
kernel 3.13.0-32-generic
Filesystem was created under Trusty (14.04.1 LTS).
$ apt-cache policy coreutils
coreutils:
Installed: 8.21-1ubuntu5
Candidate: 8.21-1ubuntu5
Version table:
*** 8.21-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: coreutils 8.21-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec 6 15:33:07 2014
InstallationDate: Installed on 2014-11-06 (30 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: coreutils (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 coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1400010
Title:
mv fails to preserve COW on btrfs
Status in coreutils package in Ubuntu:
New
Bug description:
the /bin/mv command fails to preserve extended attributes,
specifically the COW (lsattr; chattr +C) on btrfs, for both files and
directories. Affects virtual machine images in VirtualBox which
perform POORLY if hosted on btrfs without COW set.
Workaround:
1. Set the folder to have the COW flag (chattr +C .)
2. Back up all of the files (for c in *; do mv $c $c.old; done)
3. Copy the files to the same folder, assuming that there is space, and
delete the backup upon success (for c in $.old; do cp $c ${c/.old/} && rm $c)
User has to copy the file to a COW flagged directory before VirtualBox
will talk correctly to the block device images.
coreutils, 8.21-1ubuntu5, amd64
btrfs-tools, 3.12-1, amd64
kernel 3.13.0-32-generic
Filesystem was created under Trusty (14.04.1 LTS).
$ apt-cache policy coreutils
coreutils:
Installed: 8.21-1ubuntu5
Candidate: 8.21-1ubuntu5
Version table:
*** 8.21-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: coreutils 8.21-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec 6 15:33:07 2014
InstallationDate: Installed on 2014-11-06 (30 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1400010/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316156] Re: speakers audio won't work - pavucontrol is switching continually between speakers and headphones
Do you mean a physically connected microphone? I never used one with this Notebook... I did not find a command/script 'hda-jack-sense-test'... When I connect ear phones the connection is noticed by the desktop environment, so it seems there is some jack detection at least for the phones. -- 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/1316156 Title: speakers audio won't work - pavucontrol is switching continually between speakers and headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: The port is continually switching between Speakers and Heaphones and no audio is outputting from the speakers. I have tried various distributions and have found that this problems is NOT present in Ubuntu 11.04, 12.04, 13.04. I have not tried 11.10, or 12.10. But have found 13.10 and 14.04 to show this identical problem. My main concern is for the 14.04 LTS version I am currently using. - I tried regulating the audio from alsamixer -by disabling auto-mute in alsamixer i managed to stop it switching from one port to the other. Still, no audio from speakers (only a regular and low-volume BUMP comes out) - I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i could not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration list, i have tried using only the audio boards main info as referral (Intel HDA AD1986A NM10/ICH7). Thus i have added to the alsa-base.conf the following and rebooted after trying each and every new line (added only once per try, not all of them together). -options snd-hda-intel model=laptop -options snd-hda-intel model=laptop-eapd -options snd-hda-intel model=3stack -options snd-hda-intel model=generic - Also tried the position_fix quirking suggested on the ubuntu documentation pages -options snd-hda-intel position_fix= 1 -options snd-hda-intel position_fix= 2 The audio outputted from the speakers kept being a regular BUMP and nothing more, regardless of the input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3690 F pulseaudio CasperVersion: 1.340 Date: Mon May 5 13:48:40 2014 LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12FvNC.203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX45 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00206:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX45 dmi.product.version: PB64H00206 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 571356] Re: gdbtui shows "dl-debug.c:77: No such file or directory."
This problem still exits.
Linux 3.13.0-32-generic
Ubuntu
Ubuntu 14.04.1 LTS
14.04
trusty
x86_64
** Changed in: gdb (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/571356
Title:
gdbtui shows "dl-debug.c:77: No such file or directory."
Status in gdb package in Ubuntu:
Confirmed
Bug description:
Binary package hint: gdb
Using gdbtui to run a simple program shows "dl-debug.c:77: No such
file or directory." repeatedly. It seems that debugging can continue
normally.
Observed on
Ubuntu 10.04 LTS
g++ 4:4.4.3-1ubuntu1
gdb version 7.1-1ubuntu2
To reproduce:
1) Create a dumb program, e.g. foo.cpp:
int main(int argc, char *argv[]) {return 0; }
2) Compile using g++ foo.cpp -o foo
3) Fire up gdb tui using gdbtui ./foo
4) Enter 'r' to run the program
5) Observe the error message
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/571356/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Branch linked: lp:nux/trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: Fix Committed Status in Nux trusty series: Fix Committed Status in nux package in Ubuntu: Fix Released Status in nux source package in Trusty: Fix Released Bug description: [Impact] Dash content flickers when two-finger scrolling on the touchpad [Test case] 1. Enable two fingers scroll from Unity Control Center -> Mouse and Touchpad 2. Open the unity dash, expand the search results and start scrolling vertically 3. Content should not flicker and should ignore horizontal scroll events [Regression potential] Scrolling on dash content does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398984] Re: Bootloop with system language Turkish on the Nexus 4
I just wanted to pop in and say thank you for looking into it and fixing it. It's really appreciated. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398984 Title: Bootloop with system language Turkish on the Nexus 4 Status in Mir: Fix Committed Status in Mir 0.8 series: Triaged Status in mir package in Ubuntu: Triaged Status in mir package in Ubuntu RTM: Triaged Bug description: Lately, a member (Ümit) of the XDA Developers forum reported that his Nexus 4 always goes into a bootloop when he sets the system language to Turkish. It doesn't matter whether he sets it in the system settings wizard which is shown on first boot or in the system settings application. If he sets it in the system settings wizard, he won't get to see the OS after finishing the setup process, and if he changes the language in the system settings application, the phone will hang after a reboot. In any case, he will see the spinning "circle of friends" logo but the Unity8 dash will never appear. Here's the link to his first forum post regarding it issue. The discussion continues on the next few pages: http://forum.xda-developers.com/nexus-4/general/rom-ubuntu-touch-14-10-utopic-unico-t2324683/post57093935#post57093935 He's running build #10 in the stable Ubuntu RTM channel. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286552] Re: No wifi after suspend
Lenovo Thinkpad 520 with the same issue here T -- 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/1286552 Title: No wifi after suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: After suspending ubuntu the wifi doesn't work. The solution given here (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re- connecting-after-suspend) worked for me but when I have updated my Ubuntu now it won't work. I have tried to test mainline kernel but it won't to boot with it. To reproduce the bug : just suspend the computer and then power it. There's no wifi network until you restart the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashDB: ubuntu Date: Sat Mar 1 15:20:39 2014 InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1503 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 Tags: saucy Uname: Linux 3.11.0-15-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] perf samples too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399984] Re: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand'
** Tags removed: need-duplicate-check ** Changed in: gdebi (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1399984 Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' Status in gdebi package in Ubuntu: New Bug description: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashCounter: 1 Date: Sat Dec 6 21:15:46 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1399984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399983] [NEW] gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand'
Public bug reported: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 6 21:13:20 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: ** Affects: gdebi (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1399983 Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' Status in gdebi package in Ubuntu: New Bug description: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 6 21:13:20 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1399983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399984] [NEW] gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand'
Public bug reported: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashCounter: 1 Date: Sat Dec 6 21:15:46 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: ** Affects: gdebi (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1399984 Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' Status in gdebi package in Ubuntu: New Bug description: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CrashCounter: 1 Date: Sat Dec 6 21:15:46 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1399984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399983] Re: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand'
** Tags removed: need-duplicate-check ** Changed in: gdebi (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1399983 Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' Status in gdebi package in Ubuntu: New Bug description: updating teamviewer ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gdebi 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 6 21:13:20 2014 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2014-02-17 (292 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /home/master/Downloads/teamviewer_10.0.36281_i386.deb PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/master/Downloads/teamviewer_10.0.36281_i386.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with AttributeError in _maybe_append_multiarch_suffix(): 'NoneType' object has no attribute '_cand' UpgradeStatus: Upgraded to trusty on 2014-05-23 (197 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1399983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
** Changed in: unity Status: Incomplete => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid -- 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings->Keyboard->Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the "Key to show the HUD" setting. However, we still have a pain-inducing regression here ;). That setting is "Disabled" on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1331555] Re: Trusty's libsepol1 causes issues with Precise's Upstart during dist-upgrade
Confirmed in an lxc container, job status from initctl list and processes preserved across upgrade from precise to (trusty + trusty- updates + trusty-proposed) which pulled the new libsepol ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsepol in Ubuntu. https://bugs.launchpad.net/bugs/1331555 Title: Trusty's libsepol1 causes issues with Precise's Upstart during dist- upgrade Status in libsepol package in Ubuntu: Fix Released Status in libsepol source package in Trusty: Fix Committed Status in libsepol source package in Utopic: Fix Released Status in libsepol package in Debian: Fix Released Bug description: Trusty's libsepol1 (2.2-1) has no Upstart version check for the 'telinit u' call. During the dist-upgrade from Precise to Trusty this causes Upstart to loose its state. Because of this Upstart no longer knows which PIDs running services have and thus all service reloads fail. This bug is similarly to bug http://pad.lv/1313712 and the same fix applies. Faulty code: if [ "$1" = "configure" ]; then # Restart init. If it fails, there is nothing we can do, so # just ignore the error (NOTE: Borrowed from libc6.postinst) telinit u 2>/dev/null || true ; sleep 1 fi Correct code: if [ "$1" = "configure" ]; then # Restart init. If it fails, there is nothing we can do, so # just ignore the error (NOTE: Borrowed from libc6.postinst) if dpkg --compare-versions "$UPSTART_VERSION_RUNNING" ge 1.6.1; then telinit u 2>/dev/null || true ; sleep 1 fi fi accepted fix in debian packaging is to drop the postinst all together, since none of the libsepol symbols are used by neither upstart or systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsepol/+bug/1331555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399972] [NEW] [12985QG, Conexant CX20590, Black Headphone Out, Left] No sound at all
Public bug reported: - ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 3838 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 6 20:03:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-31 (249 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta i386 (20140326.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 3838 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [12985QG, Conexant CX20590, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to utopic on 2014-10-30 (37 days ago) dmi.bios.date: 07/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8NET27WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 12985QG 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:bvr8NET27WW(1.11):bd07/27/2011:svnLENOVO:pn12985QG:pvrThinkPadEdgeE320:rvnLENOVO:rn12985QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 12985QG dmi.product.version: ThinkPad Edge E320 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1399972 Title: [12985QG, Conexant CX20590, Black Headphone Out, Left] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: - ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 3838 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 6 20:03:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-31 (249 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta i386 (20140326.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 3838 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [12985QG, Conexant CX20590, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to utopic on 2014-10-30 (37 days ago) dmi.bios.date: 07/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8NET27WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 12985QG 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:bvr8NET27WW(1.11):bd07/27/2011:svnLENOVO:pn12985QG:pvrThinkPadEdgeE320:rvnLENOVO:rn12985QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 12985QG dmi.product.version: ThinkPad Edge E320 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1399972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
On Dec 06, 2014, at 02:29 PM, Andrea Azzarone wrote: >Is this still a problem? No. It's not entirely discoverable, but it is possible to fix. -- 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings->Keyboard->Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the "Key to show the HUD" setting. However, we still have a pain-inducing regression here ;). That setting is "Disabled" on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
In a nuthsell: the bug is not fixed. You using ldap? Probably it's a configuration issue. Gnome screensaver used to be buggy using ldap authentication too, but most of time it's just a configuration issue. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
So, I screwed up and thought this was an indicator-sound bug, and found an issue. But I can't find anything to do with dbus closing in indicator-power :-( ** Changed in: indicator-power (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-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-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed : mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source "(%rdi)" (0x0021) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New => In Progress ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-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-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed : mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source "(%rdi)" (0x0021) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399958] [NEW] package libpcrecpp0:amd64 1:8.35-3ubuntu1 failed to install/upgrade: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert
Public bug reported: Installation ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpcrecpp0:amd64 1:8.35-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 18:31:17 2014 ErrorMessage: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert InstallationDate: Installed on 2014-12-06 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: pcre3 Title: package libpcrecpp0:amd64 1:8.35-3ubuntu1 failed to install/upgrade: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcre3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1399958 Title: package libpcrecpp0:amd64 1:8.35-3ubuntu1 failed to install/upgrade: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert Status in pcre3 package in Ubuntu: New Bug description: Installation ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpcrecpp0:amd64 1:8.35-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 18:31:17 2014 ErrorMessage: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert InstallationDate: Installed on 2014-12-06 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: pcre3 Title: package libpcrecpp0:amd64 1:8.35-3ubuntu1 failed to install/upgrade: Paket libpcrecpp0:amd64 ist schon installiert und konfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1399958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391164] Re: Silent mode setting is not read on startup
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1391164 Title: Silent mode setting is not read on startup Status in the base for Ubuntu mobile products: New Status in indicator-sound package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu RTM: Confirmed Bug description: 1) Enable silent mode in system-settings 2) Restart the device 3) Notice that the sound indicator shows silent mode as disabled but the system-settings shows it as enabled It appears like the sound indicator is not reading the silent mode state on start up? $ system-image-cli -i current build number: 125 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-11-08 05:08:10 version version: 125 version ubuntu: 20141108 version device: 20141106 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397576] Re: USB printer no longer works (apparmor?)
Looks like the same problem as reported in Bug #1296085. Worked once last week, no longer works. Tried the power-on printer, run hp-setup, but no luck. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1397576 Title: USB printer no longer works (apparmor?) Status in cups package in Ubuntu: Incomplete Bug description: # cat /etc/os-release NAME="Ubuntu" VERSION="14.04.1 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.1 LTS" VERSION_ID="14.04" HW is: Manufacturer: LENOVO Product Name: 4061-AC4 Version: ThinkPad W500 4 GB RAM, 250 GB disk (7% used) usb printing to an HP1020 stopped working after applying all updates with apt-get upgrade. Jobs get queued, but status indicates device never comes online. Testpage won't even print now. I suspect: 184 -rw-r--r-- 1 root root 184556 Sep 8 10:24 cups_1.7.2-0ubuntu1.2_amd64.deb 312 -rw-r--r-- 1 root root 318794 Nov 20 15:43 apparmor_2.8.95~2430-0ubuntu5.1_amd64.deb I see several reports of problems with apparmor, from my syslog: Nov 29 12:35:01 eW500 python: io/hpmud/musb.c 2085: invalid serial id string ret=-7 Nov 29 12:35:05 eW500 kernel: [ 2521.005901] type=1400 audit(1417282505.501:112): apparmor="DENIED" operation="signal" profile="/usr/sbin/cupsd" pid=3884 comm="cups-deviced" requested_mask="send" denied_mask="send" signal=term peer="unconfined" Nov 29 12:35:05 eW500 kernel: [ 2521.005923] type=1400 audit(1417282505.501:113): apparmor="DENIED" operation="signal" profile="/usr/sbin/cupsd" pid=3884 comm="cups-deviced" requested_mask="send" denied_mask="send" signal=term peer="unconfined" Nov 29 12:35:05 eW500 kernel: [ 2521.008337] type=1400 audit(1417282505.501:114): apparmor="DENIED" operation="signal" profile="/usr/sbin/cupsd" pid=2037 comm="cupsd" requested_mask="send" denied_mask="send" signal=term peer="unconfined" Nov 29 12:35:05 eW500 kernel: [ 2521.008354] type=1400 audit(1417282505.501:115): apparmor="DENIED" operation="signal" profile="/usr/sbin/cupsd" pid=2037 comm="cupsd" requested_mask="send" denied_mask="send" signal=term peer="unconfined" Nov 29 12:35:05 eW500 hp[3887]: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Nov 29 12:35:05 eW500 hp[3887]: io/hpmud/musb.c 2090: invalid manufacturer string ret=-7 Nov 29 12:35:06 eW500 python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Nov 29 12:35:06 eW500 python: io/hpmud/musb.c 2090: invalid manufacturer string ret=-7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1397576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
** Branch linked: lp:~ted/indicator-sound/lp1399862-active-port-null -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399862] Re: SIGSEGV with module-remap-sink mixing to mono
** Changed in: indicator-sound (Ubuntu) Status: New => In Progress ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1399862 Title: SIGSEGV with module-remap-sink mixing to mono Status in indicator-sound package in Ubuntu: In Progress Bug description: indicator-sound-service crashes with a SIGSEGV immediately when it's executed if I have a mono sink made with module-remap-sink in /etc/pulse/default.pa. This is the line that makes it crash: load-module module-remap-sink sink_name=mono master=alsa_output.pci-_00_1b.0.analog-stereo channels=2 channel_map=mono,mono I have never tried variations of that line, but I know that the sink works normally and does what it's supposed to do (mix the audio to mono), so I don't think it's a problem with it. If I comment it and restart pulseaudio, then I can start indicator-sound-service and it will work normally. I'm using Ubuntu 15.04. indicator-sound 12.10.2+15.04.20141105-0ubuntu1 (the most recent version as of now). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
** Changed in: mesa (Debian) Status: Unknown => 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/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Confirmed Status in mesa package in Fedora: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=, renderer=0x7fffdc1cc670, fboId=) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: Kamal Wanas (kamalwanas) => (unassigned) ** Changed in: initramfs-tools Status: Fix Committed => Confirmed ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399953] Re: Google contacts authentication problem with U-O-A (Trusty, Unity7)
** Description changed:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution & click on the
address-book list, it shows following error:
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required".
I tried to revoke access for UOA from google accounts, & re-authorize
it. But it did not help. However google-calendar integration is working
fine. And if log into gnome-shell & add my Google account in Gnome-
Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
- Here is some other information:
+ Here is some more information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 ()
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
https://bugs.launchpad.net/bugs/1399953
Title:
Google contacts authentication problem with U-O-A (Trusty, Unity7)
Status in account-plugins package in Ubuntu:
New
Bug description:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution & click on the
address-book list, it shows following error:
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required".
I tried to revoke access for UOA from google accounts, & re-authorize
it. But it did not help. However google-calendar integration is
working fine. And if log into gnome-shell & add my Google account in
Gnome-Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some more information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 ()
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1399953/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399924] Re: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1399924 Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: Confirmed Bug description: nothing happens just a window at every startup appears about fixing the problem ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sudo 1.8.9p5-1ubuntu2 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 5 01:47:59 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-06-23 (165 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1399924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399953] [NEW] Google contacts authentication problem with U-O-A (Trusty, Unity7)
Public bug reported:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution & click on the
address-book list, it shows following error:
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required".
I tried to revoke access for UOA from google accounts, & re-authorize
it. But it did not help. However google-calendar integration is working
fine. And if log into gnome-shell & add my Google account in Gnome-
Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some other information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 ()
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
)
-
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
https://bugs.launchpad.net/bugs/1399953
Title:
Google contacts authentication problem with U-O-A (Trusty, Unity7)
Status in account-plugins package in Ubuntu:
New
Bug description:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution & click on the
address-book list, it shows following error:
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required".
I tried to revoke access for UOA from google accounts, & re-authorize
it. But it did not help. However google-calendar integration is
working fine. And if log into gnome-shell & add my Google account in
Gnome-Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some other information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 ()
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1399953/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316156] Re: speakers audio won't work - pavucontrol is switching continually between speakers and headphones
do pulseaudio log complain about the mic jack ?
the model which you select set bit 8 of pin default of node 0x1f
0x1f 0x01a19020
0x1f 0x02a191f0
Sysfs Files
!!---
/sys/class/sound/hwC0D0/init_pin_configs:
0x1a 0x0121401f
0x1b 0x9117f110
0x1c 0x410110f0
0x1d 0x410110f0
0x1e 0x411711f0
0x1f 0x01a19020
0x20 0x418130f0
0x21 0x5993e1f0
0x22 0x5933112e
0x23 0x59b371f0
0x24 0x53f711f0
0x25 0x410110f0
/sys/class/sound/hwC0D0/driver_pin_configs:
0x1a 0x02214021
0x1b 0x90170110
0x1c 0x41f0
0x1d 0x90a7013e
0x1e 0x41f0
0x1f 0x02a191f0
0x20 0x41f0
control.14 {
iface CARD
name 'Mic Phantom Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
control.15 {
iface CARD
name 'Internal Mic Phantom Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
--
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/1316156
Title:
speakers audio won't work - pavucontrol is switching continually
between speakers and headphones
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
The port is continually switching between Speakers and Heaphones and no audio
is outputting from the speakers. I have tried various distributions and have
found that this problems is NOT present in Ubuntu 11.04, 12.04, 13.04. I have
not tried 11.10, or 12.10. But have found 13.10 and 14.04 to show this
identical problem.
My main concern is for the 14.04 LTS version I am currently using.
- I tried regulating the audio from alsamixer -by disabling auto-mute in
alsamixer i managed to stop it switching from one port to the other. Still, no
audio from speakers (only a regular and low-volume BUMP comes out)
- I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i could
not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration list, i
have tried using only the audio boards main info as referral (Intel HDA AD1986A
NM10/ICH7). Thus i have added to the alsa-base.conf the following and rebooted
after trying each and every new line (added only once per try, not all of them
together).
-options snd-hda-intel model=laptop
-options snd-hda-intel model=laptop-eapd
-options snd-hda-intel model=3stack
-options snd-hda-intel model=generic
- Also tried the position_fix quirking suggested on the ubuntu documentation
pages
-options snd-hda-intel position_fix= 1
-options snd-hda-intel position_fix= 2
The audio outputted from the speakers kept being a regular BUMP and
nothing more, regardless of the input.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: xubuntu3690 F pulseaudio
CasperVersion: 1.340
Date: Mon May 5 13:48:40 2014
LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T12FvNC.203
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: EasyNote_MX45
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell BV
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00206:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
dmi.product.name: EasyNote_MX45
dmi.product.version: PB64H00206
dmi.sys.vendor: Packard Bell BV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316156/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316156] Re: speakers audio won't work - pavucontrol is switching continually between speakers and headphones
try hda-jack-sense-test -a when you plugged and unplugged mic jack to find whether your mic jack support jack detection -- 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/1316156 Title: speakers audio won't work - pavucontrol is switching continually between speakers and headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: The port is continually switching between Speakers and Heaphones and no audio is outputting from the speakers. I have tried various distributions and have found that this problems is NOT present in Ubuntu 11.04, 12.04, 13.04. I have not tried 11.10, or 12.10. But have found 13.10 and 14.04 to show this identical problem. My main concern is for the 14.04 LTS version I am currently using. - I tried regulating the audio from alsamixer -by disabling auto-mute in alsamixer i managed to stop it switching from one port to the other. Still, no audio from speakers (only a regular and low-volume BUMP comes out) - I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i could not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration list, i have tried using only the audio boards main info as referral (Intel HDA AD1986A NM10/ICH7). Thus i have added to the alsa-base.conf the following and rebooted after trying each and every new line (added only once per try, not all of them together). -options snd-hda-intel model=laptop -options snd-hda-intel model=laptop-eapd -options snd-hda-intel model=3stack -options snd-hda-intel model=generic - Also tried the position_fix quirking suggested on the ubuntu documentation pages -options snd-hda-intel position_fix= 1 -options snd-hda-intel position_fix= 2 The audio outputted from the speakers kept being a regular BUMP and nothing more, regardless of the input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3690 F pulseaudio CasperVersion: 1.340 Date: Mon May 5 13:48:40 2014 LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12FvNC.203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX45 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00206:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX45 dmi.product.version: PB64H00206 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
Launchpad has imported 6 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=77402. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-04-13T15:48:44+00:00 Alexander E. Patrakov wrote: Created attachment 97312 valgrind log This is a clone of https://bugs.kde.org/show_bug.cgi?id=328496 KWin sometimes gets into a mode when it always crashes on start if desktop effects are enabled. This happens on Haswell hardware. 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) The crash looks as follows: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f525dcc3800 (LWP 22941))] Thread 6 (Thread 0x7f523c0b4700 (LWP 22992)): #0 0x7f5257ef67de in pthread_cond_timedwait () from /lib64/libpthread.so.0 #1 0x7f5258188624 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f525817bda5 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f525818816f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f5257ef2201 in start_thread () from /lib64/libpthread.so.0 #5 0x7f525d50158d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f523ae18700 (LWP 23018)): #0 0x7f5257ef67de in pthread_cond_timedwait () from /lib64/libpthread.so.0 #1 0x7f5258188624 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f525817bda5 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f525818816f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f5257ef2201 in start_thread () from /lib64/libpthread.so.0 #5 0x7f525d50158d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f523a617700 (LWP 23019)): #0 0x7f525d4fa403 in select () from /lib64/libc.so.6 #1 0x7f5258264b21 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f525818816f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f5257ef2201 in start_thread () from /lib64/libpthread.so.0 #4 0x7f525d50158d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5239c87700 (LWP 23024)): #0 0x7f5257ef640c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f525c6fb86b in ?? () from /usr/lib64/qt4/libQtScript.so.4 #2 0x7f525c6fb8a9 in ?? () from /usr/lib64/qt4/libQtScript.so.4 #3 0x7f5257ef2201 in start_thread () from /lib64/libpthread.so.0 #4 0x7f525d50158d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5238eff700 (LWP 23025)): #0 0x7f5257ef67de in pthread_cond_timedwait () from /lib64/libpthread.so.0 #1 0x7f5258188624 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f525817bda5 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f525818816f in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f5257ef2201 in start_thread () from /lib64/libpthread.so.0 #5 0x7f525d50158d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f525dcc3800 (LWP 22941)): [KCrash Handler] #5 0x7f51abbbe758 in get_stencil_miptree (irb=0x27cf660) at brw_misc_state.c:257 #6 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7f5238126038, clear_mask=clear_mask@entry=0) at brw_misc_state.c:273 #7 0x7f51abb7b72d in brw_try_draw_prims (indirect=0x0, max_index=23, min_index=0, ib=0x0, nr_prims=1, prims=0x7fff99c1b300, arrays=0x28a4730, ctx=0x7f5238126038) at brw_draw.c:415 #8 brw_draw_prims (ctx=0x7f5238126038, prims=0x7fff99c1b300, nr_prims=1, ib=0x0, index_bounds_valid=, min_index=0, max_index=23, unused_tfb_object=0x0, indirect=0x0) at brw_draw.c:569 #9 0x7f51ab9da23d in vbo_draw_arrays (ctx=0x7f5238126038, mode=4, start=0, count=24, numInstances=1, baseInstance=0) at vbo/vbo_exec_array.c:661 #10 0x7f5258fb337e in KWin::GLVertexBuffer::draw (this=this@entry=0x2e6b470, region=..., primitiveMode=primitiveMode@entry=4, first=first@entry=0, count=24, hardwareClipping=hardwareClipping@entry=false) at /usr/portage/packages/portage/kde- base/kwin-4.11.8/work/kwin-4.11.8/kwin/libkwineffects/kwinglutils.cpp:1949 #11 0x7f5258fb6359 in KWin::GLVertexBuffer::render (this=0x2e6b470, region=..., primitiveMode=4, hardwareClipping=) at /usr/portage/packages/portage/kde- base/kwin-4.11.8/work/kwin-4.11.8/kwin/libkwineffects/kwinglutils.cpp:1902 #12 0x7f5258fb63bd in KWin::GLVertexBuffer::render (this=0x2e6b470, primitiveMode=4) at /usr/portage/packages/portage/kde- base/kwin-4.11.8/work/kwin-4.11.8/kwin/libkwineffects/kwinglutils.cpp:1896 #13 0x7f525d893115 in KWin::SceneOpenGL::paintBackground (this=this@entry=0x2e70060, region=...) at /usr/portage/packages/portage /kde-base/kwin-4.11.8/work/kwin-4.11.8/kwin/scene_openg
[Touch-packages] [Bug 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Changed in: indicator-power (Ubuntu) Status: Confirmed => In Progress ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-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-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed : mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source "(%rdi)" (0x0021) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
** Branch linked: lp:~ted/indicator-sound/lp1307021-closed-disconnect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: In Progress Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-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-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed : mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source "(%rdi)" (0x0021) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399710] Re: no audible warning of high volume level
Marked to be looked at by design. Let them adjust it then we can add it to the indicator-sound backlog. Thanks! ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: New => Incomplete ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level Status in Ubuntu UX bugs: New Status in indicator-sound package in Ubuntu: Incomplete Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click "ok"). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399948] [NEW] Commands on found if both ./bin and ~/bin in PATH
Public bug reported: I use (and have been using for 20 years or so) a path variable that looks like PATH=".;./bin;~/bin;$PATH"; export PATH This PATH should execute in priority: project specific commands (in the working directory, or the bin subdirectory of the working directory), my personal commands (in my $HOME/bin folder) and then system commands. The problem seems to be that when I start a shell in my home directory, it will cache the location of commands in ~/bin as if they were in ./bin and then will be unable to find them if I cd out of my home directory. For example, I have a personal command called SlideShow: Here is a short example: ralmond@Limu:~$ file ~/bin/SlideShow /home/ralmond/bin/SlideShow: POSIX shell script, ASCII text executable ralmond@Limu:~$ # Works fine if I execute it from home directory ralmond@Limu:~$ SlideShow Pictures/ ^C [Working as expected] ralmond@Limu:~$ cd Pictures/ ralmond@Limu:~/Pictures$ #But if I change directory it does not work. ralmond@Limu:~/Pictures$ SlideShow Pics bash: ./bin/SlideShow: No such file or directory ralmond@Limu:~/Pictures$ #If I start the shell in a directory other than home it works ralmond@Limu:~/Pictures$ bash ralmond@Limu:~/Pictures$ SlideShow Pics ^C [Working as expected] I suspect that it is some cache which is not properly getting reset. Here are my system details: ralmond@Limu:~/Pictures$ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 ralmond@Limu:~/Pictures$ apt-cache policy bash bash: Installed: 4.3-7ubuntu1.5 Candidate: 4.3-7ubuntu1.5 Version table: *** 4.3-7ubuntu1.5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 4.3-6ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ralmond@Limu:~/Pictures$ ^C ralmond@Limu:~/Pictures$ ** Affects: bash (Ubuntu) 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/1399948 Title: Commands on found if both ./bin and ~/bin in PATH Status in bash package in Ubuntu: New Bug description: I use (and have been using for 20 years or so) a path variable that looks like PATH=".;./bin;~/bin;$PATH"; export PATH This PATH should execute in priority: project specific commands (in the working directory, or the bin subdirectory of the working directory), my personal commands (in my $HOME/bin folder) and then system commands. The problem seems to be that when I start a shell in my home directory, it will cache the location of commands in ~/bin as if they were in ./bin and then will be unable to find them if I cd out of my home directory. For example, I have a personal command called SlideShow: Here is a short example: ralmond@Limu:~$ file ~/bin/SlideShow /home/ralmond/bin/SlideShow: POSIX shell script, ASCII text executable ralmond@Limu:~$ # Works fine if I execute it from home directory ralmond@Limu:~$ SlideShow Pictures/ ^C [Working as expected] ralmond@Limu:~$ cd Pictures/ ralmond@Limu:~/Pictures$ #But if I change directory it does not work. ralmond@Limu:~/Pictures$ SlideShow Pics bash: ./bin/SlideShow: No such file or directory ralmond@Limu:~/Pictures$ #If I start the shell in a directory other than home it works ralmond@Limu:~/Pictures$ bash ralmond@Limu:~/Pictures$ SlideShow Pics ^C [Working as expected] I suspect that it is some cache which is not properly getting reset. Here are my system details: ralmond@Limu:~/Pictures$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ralmond@Limu:~/Pictures$ apt-cache policy bash bash: Installed: 4.3-7ubuntu1.5 Candidate: 4.3-7ubuntu1.5 Version table: *** 4.3-7ubuntu1.5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 4.3-6ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ralmond@Limu:~/Pictures$ ^C ralmond@Limu:~/Pictures$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1399948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Thanks for your answer and also for your work Andrea ! Thanks to Marco Trevisan too. Sorry for my english but I don't understand if the fix works or not when you say "We released a fix but it does not work" then "The one we released was text entry not showing randomly on multimonitor and seems to be fixed", for me it's contradictory. What I can say : - My PC using Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) works perfectly since 2014-09-11, - Another PC using Ubuntu's unity package, randomly, I have no input field to type password for unlock (normally this PC is up to date but I have to check). Both use multimonitor and LDAP authentication. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
** Bug watch added: Red Hat Bugzilla #1123691 https://bugzilla.redhat.com/show_bug.cgi?id=1123691 ** Also affects: mesa (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1123691 Importance: Unknown Status: Unknown -- 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/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Unknown Status in mesa package in Fedora: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=, renderer=0x7fffdc1cc670, fboId=) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
I did some experiments on an Ubuntu GNOME 14.04 LTS desktop standard installation. There are 4 (!) components involved in this annoying traffic: whoopsie network manager dnsmasq (started by network manager) IPv6 The repeated DNS-requests for daisy.ubuntu.com stop when de-activating anyone of these! You (as root) may use these recipes as workarounds: Workaround #1: De-activate whoopsie: #initctl stop whoopsie #echo 'manual' > /etc/init/whoopsie.override Or workaround #2: De-activate Network Manager: #initctl stop network-manager #echo 'manual' > /etc/init/network-manager.override - Bring up network interface through config lines in file /etc/network/interfaces, e.g. iface eth0 inet dhcp auto eth0 #ifup eth0 Or workaround #3: Disable dnsmasq - Edit file /etc/NetworkManager/NetworkManager.conf and change line with dns=dnsmasq to #dns=dnsmasq - Restart Network Manager: # initctl restart network-manager Or workaround #4: Disable IPv6: #sysctl -w net/ipv6/conf/all/disable_ipv6=1 #echo 'net/ipv6/conf/all/disable_ipv6=1' >/etc/sysctl.d/10-ipv6-off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com Status in Ubuntu error tracker client (whoopsie): Confirmed Status in glib2.0 package in Ubuntu: Invalid Status in network-manager package in Ubuntu: In Progress Status in whoopsie package in Ubuntu: Triaged Bug description: Watching GNetworkMonitor's network-changed signal causes constant DNS traffic. Andy Whitcroft points out that the NETLINK_ROUTE socket set up by GNetworkMonitor will fire events every time an ARP entry appears or disappears. Unfortunately, we currently need an additional layer of connectivity checking because checking NetworkManager's state for CONNECTED_GLOBAL is not enough to know whether we're really online. Ubuntu does not yet use the NetworkManager connectivity check [1]. The likely solution to this bug is a replacement for GNetworkMonitor in whoopsie. 1: http://bazaar.launchpad.net/~daisy- pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326 Original report follows: Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1368146] Re: keyboard not set to English
Colin You could well be right. The point I was making was that the published workaround for a known bug did not help me at all. I changed the setup manually. Regards Carol -- Carol Painting +44 (0)23 9235 2855 http://www.carol762.org.uk On Sat, 2014-12-06 at 13:58 +, Colin Law wrote: > I think this is a duplicate of bug #1240198 > -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1368146 Title: keyboard not set to English Status in ibus package in Ubuntu: New Bug description: I upgraded to 14.04 and have the international keyboard layout instead of English. This is reported as a known bug with a workaround that says I should disable IBus. I can't even find IBus! I use Xubuntu on an AMD64 system and had no problems with the previous LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1368146/+subscriptions -- 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/1368146 Title: keyboard not set to English Status in ibus package in Ubuntu: New Bug description: I upgraded to 14.04 and have the international keyboard layout instead of English. This is reported as a known bug with a workaround that says I should disable IBus. I can't even find IBus! I use Xubuntu on an AMD64 system and had no problems with the previous LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1368146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
** Bug watch added: freedesktop.org Bugzilla #77402 https://bugs.freedesktop.org/show_bug.cgi?id=77402 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=77402 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Also affects: mesa (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 Importance: Unknown Status: Unknown -- 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/1289243 Title: Regression in trusty, i965_dri.so crashes Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Unknown Bug description: I am now getting crashes like (gdb) bt #0 0x7fffe6d74958 in get_stencil_miptree (irb=0x7fffdd870080) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:257 #1 brw_workaround_depthstencil_alignment (brw=brw@entry=0x7fffdc027018, clear_mask=clear_mask@entry=0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_misc_state.c:273 #2 0x7fffe6d3197d in brw_try_draw_prims (indirect=0x0, max_index=11, min_index=0, ib=0x7fffe621da80, nr_prims=1, prims=0x7fffe621daa0, arrays=0x7fffdc211030, ctx=0x7fffdc027018) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:415 #3 brw_draw_prims (ctx=0x7fffdc027018, prims=0x7fffe621daa0, nr_prims=1, ib=0x7fffe621da80, index_bounds_valid=, min_index=0, max_index=11, unused_tfb_object=0x0, indirect=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:569 #4 0x7fffe6b8ec03 in vbo_handle_primitive_restart (ctx=ctx@entry=0x7fffdc027018, prim=prim@entry=0x7fffe621daa0, nr_prims=nr_prims@entry=1, ib=ib@entry=0x7fffe621da80, index_bounds_valid=index_bounds_valid@entry=0 '\000', min_index=min_index@entry=4294967295, max_index=max_index@entry=4294967295) at ../../../../src/mesa/vbo/vbo_exec_array.c:585 #5 0x7fffe6b8ff20 in vbo_validated_drawrangeelements (ctx=ctx@entry=0x7fffdc027018, mode=mode@entry=5, index_bounds_valid=index_bounds_valid@entry=0 '\000', start=start@entry=4294967295, end=end@entry=4294967295, count=count@entry=14, type=type@entry=5123, indices=indices@entry=0x7fffdc0c6bc0, basevertex=basevertex@entry=0, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1006 #6 0x7fffe6b90443 in vbo_exec_DrawElements (mode=5, count=14, type=5123, indices=0x7fffdc0c6bc0) at ../../../../src/mesa/vbo/vbo_exec_array.c:1156 #7 0x76744e0c in QSGDefaultRenderer::renderNodes (this=this@entry=0x7fffdc1cc670, nodes=, count=count@entry=40) at scenegraph/coreapi/qsgdefaultrenderer.cpp:536 #8 0x7674554c in QSGDefaultRenderer::render (this=0x7fffdc1cc670) at scenegraph/coreapi/qsgdefaultrenderer.cpp:281 #9 0x7674acc8 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:271 #10 0x7674adf7 in QSGRenderer::renderScene (this=this@entry=0x7fffdc1cc670) at scenegraph/coreapi/qsgrenderer.cpp:229 #11 0x76754365 in QSGContext::renderNextFrame (this=, renderer=0x7fffdc1cc670, fboId=) at scenegraph/qsgcontext.cpp:270 #12 0x7678139a in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x662c10, size=...) at items/qquickwindow.cpp:349 #13 0x76863483 in QQuickRenderThreadSingleContextWindowManager::run (this=0x6634f0) at items/qquickthreadedwindowmanager.cpp:456 #14 0x77629186 in QThreadPrivate::start (arg=0x6634f0) at thread/qthread_unix.cpp:333 #15 0x75842182 in start_thread (arg=0x7fffe621e700) at pthread_create.c:312 #16 0x75b5312d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 When running some of the tests of unity8 where a few days ago it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole
Vivid feedback (booted with systemd):
both /dev/console & /dev/xconsole exist but with different settings:
- dev/console owned by root/root
- dev/xconsole owned by root/admin
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Triaged
Status in rsyslog package in Ubuntu:
Triaged
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358823] Re: count emblem in launcher and tabbox doesn't regard high dpi scale settings
*** This bug is a duplicate of bug 1353070 *** https://bugs.launchpad.net/bugs/1353070 ** This bug has been marked a duplicate of bug 1353070 Launcher icon emblems (count) do not scale to match DPI settings -- 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/1358823 Title: count emblem in launcher and tabbox doesn't regard high dpi scale settings Status in Unity: New Status in unity package in Ubuntu: New Bug description: The count emblem on icons in launcher and tabbox stay really tiny even though the rest of the interface is scaled up. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1358823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361311] Re: Dash fade-in/fade-out animation should be configurable
** Changed in: unity Status: New => Opinion ** Changed in: unity (Ubuntu) Status: New => Opinion ** Changed in: unity Importance: Undecided => Wishlist -- 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/1361311 Title: Dash fade-in/fade-out animation should be configurable Status in Unity: Opinion Status in unity package in Ubuntu: Opinion Bug description: When I hit "super" key, or click on Ubuntu logo, there's a fade-in/fade-out transition for the dash window. I personally don't like any type of animation or transition effects, as they seem to me a waste of time. Especialy this fade-in/fade-out transition, it's highly erratic depending on the hardware been executed, the system load, the number of lenses running, etc. I think when using UNITY_LOW_GFX_MODE=1 all animations and transitions should be disabled, or better, this animation times should be configurable by dconf keys. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode
** Changed in: unity 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/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: On a high DPI screen (220 DPI) the mouse cursor is really tiny when hovering unity elements. There are various keys in dconf to change the cursor's scale factor or size. I've managed to change it in a way that it looks normal when inside application windows, but its still tiny when on unity elements. I think this should be set automatically by the scale factor setting in system settings. (Using unity 7.3.1+14.10.20140811-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1359211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
** Changed in: unity Status: New => Confirmed ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Milestone: None => 7.3.2 -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289204] Re: Local Menus don't work when running as root or invoking as root with "gksu" [video demo]
** Changed in: unity 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/1289204 Title: Local Menus don't work when running as root or invoking as root with "gksu" [video demo] Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Video Demo: http://youtu.be/jFrSjHgpMEI This is a small usability bug for the Local Menus in Ubuntu 14.04. This will probably not be experienced by most people and I pretty much just stumbled across this bug myself so it probably wouldn't be a high priority but I wanted to submit it anyway. The bug occurs when running as root or invoking root with gksu. Another bug is found when invoking with gksu using the "-k" option to stay in the user environment. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1289204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
Is this still a problem? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings->Keyboard->Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the "Key to show the HUD" setting. However, we still have a pain-inducing regression here ;). That setting is "Disabled" on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263392] Re: I no longer have a "shut down" on that menu
Your shutdown menu is back? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1263392 Title: I no longer have a "shut down" on that menu Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A few months - sometime after getting Time Warner Cable - I lost the shut down option. I have to manually hold the power button in for 5 seconds. Where did it go? I know that I did not delete it even if I could. Is it something that Time Warner does with the cable modem? Very annoying. How can I fix this? Can you fix this? 12.04 LTS has been very problematic for me. I have to pray that Unity will pop out. It may take many tries of slamming the mouse against the edge. I've tried low and high sensitivity and in the middle; it doesn't seem to matter!! I can't tell you how many times I've had to wait for my mouse click to do anything!! 30 seconds or more and very often!! What happened to Ubuntu??? Very frustrated with this version of Ubuntu!! I can't seem to find where to stop scripts until one hangs the system for minutes!!! Even when I click "stop script" It laughs at me!! Not really, just hangs some more. There is no option in the system that I can locate that lets me choose " don't run scripts" or something equivalent. Help! Please, I really hate Windows. I've been using Linux systems for many years, I'd like to stay a user of a real operating system rather than Bill's. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic-pae 3.2.53 Uname: Linux 3.2.0-58-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 21 12:20:48 2013 MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263392/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263137] Re: unity-panel-service eats cpu and ram
@Alan, it's already fixed right? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1263137 Title: unity-panel-service eats cpu and ram Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I am getting high cpu and ram usage from unity-panel-service on 13.10. Maybe bug 1199877 isn't fixed? My laptop was crawling and swapping like mad, ran top and found unity- panel-service at the top. Killed it and all is happy again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 Uname: Linux 3.12.0-031200-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] Date: Fri Dec 20 15:29:42 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (538 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-07-12 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243369] Re: Mouse cursor movement became jerky, then system stopped responding
Can you still reproduce that? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1243369 Title: Mouse cursor movement became jerky, then system stopped responding Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Just after the failure described in https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1243365 and after removing the usb pendrive, mouse cursor movements became jerky, meaning that from time to time the mouse cursor would freeze even though I was moving the mouse. Then, the system stopped responding to clicks and I couldn't do anything useful. Apparently there wasn't high CPU or disk activity. Only thing I could do was a hard power off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 21:22:15 2013 InstallationDate: Installed on 2013-10-11 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1232351] Re: the screen blackens out completely for few seconds and it's highly difficult to perform multiple operations at the same time.
Can you still reproduce that? How? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1232351 Title: the screen blackens out completely for few seconds and it's highly difficult to perform multiple operations at the same time. Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Multiple operations are difficult and the screen blackens for few seconds and also the system generates lot of heat. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20 Uname: Linux 3.5.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Sat Sep 28 10:50:05 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1232351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1205876] Re: whole system became unresponsive to clicks and keystrokes for a couple of minutes
Can you still reproduce that? How often does it happen? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1205876 Title: whole system became unresponsive to clicks and keystrokes for a couple of minutes Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I went to close a couple of windows (Gedit and a Nautilus window), both became grey and both showed up the not-responding pupup (to both of which I replied "cancel") and the system stayed unresponsive to both clicks and keystrokes for a full two minutes or so. Mouse cursor was moving fluidly without the smallest jerkyness, but neither clicks nor keystrokes would do nothing. Even Ctrl+Alt+F1 wouldn't work (which would have allowed me to open a virtual terminal and have a look at the processes) By chance, I had a visible open terminal window with top running just prior to the incident, and it wasn't showing high CPU consumption; also, the cooler fan speed didn't seem to indicate that was the case. After a few minutes everything got back to normal. NO MATTER WHAT, keystrokes and clicks must always have the highest priority, in shuch a way that it must NEVER, EVER happen that you can't even open a virtual terminal with Ctrl+Alt+F1. Something is very wrong at a very low level if the whole system can become unresponsive due to some process being very busy or even if this was due to swapping. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu12 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Jul 28 18:27:47 2013 InstallationDate: Installed on 2010-06-23 (1131 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-13 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1205876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1180548] Re: High load when running VirtualBox
** Changed in: unity (Ubuntu) Status: New => Invalid ** Changed in: unity Status: New => Invalid ** Also affects: virtualbox Importance: Undecided Status: New -- 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/1180548 Title: High load when running VirtualBox Status in Unity: Invalid Status in Virtualbox: New Status in unity package in Ubuntu: Invalid Bug description: When running VirtualBox, the system load suddenly raises without stopping. When I kill compiz (which includes Unity), the load goes down again. If I don't kill it quick enough, the system locks up completely and I need to power off the machine. I was searching very long for a solution because I thought it's a VirtualBox problem. I'm using the Oracle 4.2.12 package provided on http://www.virtualbox.org/, but I also tried using the stock Ubuntu package and even with an older VirtualBox version (4.1), but the problem still occured. Before I had this problem, I was using Ubuntu 12.10 without any issues. When 13.04 came out, I decided to make a fresh installation and have this problem since then. Description of the problem: - I'm running Ubuntu 13.04 on an Asus Zenbook UX31A with 4 GB memory and 128 GB SSD. - Before I start VirtualBox, I have already opened several programs: Chromium, Firefox, Skype are the biggest in terms of memory usage (I think the problem occured less often when VirtualBox was running alone, so maybe it's related to memory usage) - When I start VirtualBox, the problem occurs sometimes during boot, but sometimes only after a a few minutes of uptime. Most of the time, it happened when the machine was idle and I was working in a different window. Workarounds: 1) I can use Unity only when I run a background job which checks for the load and kills / replaces compiz & unity if the system load is too high. 2) I decided to install ubuntu-gnome-desktop and switch to GNOME for the time being. It uses compiz as well but without Unity, and the problem is completely gone! (That's why I'm pretty sure it must be a Unity issue...) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1180548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1190898] Re: segfault in unity_support_test
Can you still reproduce that? ** Changed in: unity Status: Confirmed => Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1190898 Title: segfault in unity_support_test Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After update to Ubuntu 13.04 I was unable to use unity as shell. lxde and gnome appear to work fine. When I choose unity the screen gives just the background and never arrives at the the point where the quicklist is visible or the dash. I made a copy of the /var/log/syslog and then a "cat /dev/null > / var/log/syslog" This is what I got in /var/log/syslog after a login attempt to unity: root@legolas:/var/log# cat syslog Jun 14 09:52:57 legolas colord: device removed: xrandr-LVDS1 Jun 14 09:52:57 legolas colord: Profile removed: icc-0aad3f9acbd994c5976bc9cd10292033 Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/HFPAG Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/HFPHS Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/A2DPSource Jun 14 09:52:57 legolas bluetoothd[771]: Endpoint unregistered: sender=:1.362 path=/MediaEndpoint/A2DPSink Jun 14 09:52:57 legolas bluetoothd[771]: hci0: Remove UUID (0x0011) failed: Busy (0x0a) Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7285 of process 7285 (n/a) owned by '1000' high priority at nice level -11. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 1 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas pulseaudio[7285]: [pulseaudio] pid.c: Stale PID file, overwriting. Jun 14 09:52:57 legolas dbus[733]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Jun 14 09:52:57 legolas dbus[733]: [system] Successfully activated service 'org.freedesktop.systemd1' Jun 14 09:52:57 legolas colord: Device added: xrandr-LVDS1 Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7312 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 2 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7313 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 3 threads of 1 processes of 1 users. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Successfully made thread 7314 of process 7285 (n/a) owned by '1000' RT at priority 5. Jun 14 09:52:57 legolas rtkit-daemon[1840]: Supervising 4 threads of 1 processes of 1 users. Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/HFPAG Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/HFPHS Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/A2DPSource Jun 14 09:52:58 legolas bluetoothd[771]: Endpoint registered: sender=:1.375 path=/MediaEndpoint/A2DPSink Jun 14 09:52:58 legolas rtkit-daemon[1840]: Successfully made thread 7319 of process 7319 (n/a) owned by '1000' high priority at nice level -11. Jun 14 09:52:58 legolas rtkit-daemon[1840]: Supervising 5 threads of 2 processes of 1 users. Jun 14 09:52:58 legolas pulseaudio[7319]: [pulseaudio] pid.c: Daemon already running. Jun 14 09:52:58 legolas colord: Profile added: icc-9b80530f957bc21605981b113eb57c5c Jun 14 09:52:58 legolas kernel: [ 2376.756271] unity_support_t[7352]: segfault at c2 ip 0040173f sp 7fff55e49250 error 4 in unity_support_test[40+4000] Jun 14 09:53:28 legolas goa[7539]: goa-daemon version 3.6.2 starting [main.c:112, main()] root@legolas:/var/log# Thanks ahead, any suggestions welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1190898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 932834] Re: Enable equalizer
As I've noted before, Trusty already has the equaliser module available in the standard pulseaudio package: $ dpkg -L pulseaudio | grep eq /usr/lib/pulse-4.0/modules/module-equalizer-sink.so So at least in Trusty this is actually fixed. All the critical "hard to fix" blumping is now in position. Having a GUI frontend for it, is a completely different matter, which has nothing to do with this bug, and has nothing to do with pulseaudio (to which this bug applies). If one were to have a proper equalizer GUI frontend in Ubuntu, it would have to be integrated into unity-control-center's sound panel: $ dpkg -L unity-control-center | grep -i panels | grep -i sound /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libsound.so So for that a feature request would have to be filed against the unity- control-center package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/932834 Title: Enable equalizer Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Precise: Won't Fix Status in pulseaudio source package in Quantal: Won't Fix Status in pulseaudio source package in Raring: Won't Fix Bug description: pulseaudio has support for built in equalizer, but ubuntu does not have enabled it. pulseudio provides module module-equalizer-sink which needs to be enabled at compile time. In src/Makefile.am is this code: if HAVE_DBUS if HAVE_FFTW modlibexec_LTLIBRARIES += \ module-equalizer-sink.la bin_SCRIPTS += utils/qpaeq endif endif So for equalizer module is needed package fftw-dev. Please add needed fftw packages to pulseaudio build depends for equalizer support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/932834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1180260] Re: frozen applications keep the mouse click focus
Can you still reproduce that? ** Changed in: unity Status: New => Incomplete ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1180260 Title: frozen applications keep the mouse click focus Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: happened to me at least twice. An application window is not responding (but not greyed so not considered not responding ), CPU load is low(no high computing) as well as i/o. This time the application was eclipse Kepler Last time I think it was firefox Well, then the mouse can't click. I move the pointer, I can use super key to show unity board, but I can't click anywhere just as there was a glass panel between the mouse and the applications. I press ctrl alt F1, killall -9 "application" (firefox or java) and on ctrl alt F7 I got my mouse click again. I think this is a bug in the renderer library, maybe a race condition. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11 Uname: Linux 3.8.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Wed May 15 09:24:26 2013 InstallationDate: Installed on 2011-07-05 (679 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-26 (18 days ago) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2011-07-05 (679 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True NonfreeKernelModules: nvidia wl Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11 Tags: gnome3-ppa raring third-party-packages Uname: Linux 3.8.0-20-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-26 (18 days ago) UserGroups: adm admin cdrom davfs2 dialout fuse libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1180260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed. Probably what you can reproduce now is a problem with permissions. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368146] Re: keyboard not set to English
I think this is a duplicate of bug #1240198 -- 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/1368146 Title: keyboard not set to English Status in ibus package in Ubuntu: New Bug description: I upgraded to 14.04 and have the international keyboard layout instead of English. This is reported as a known bug with a workaround that says I should disable IBus. I can't even find IBus! I use Xubuntu on an AMD64 system and had no problems with the previous LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1368146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399924] Re: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1399924 Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: nothing happens just a window at every startup appears about fixing the problem ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sudo 1.8.9p5-1ubuntu2 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 5 01:47:59 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-06-23 (165 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1399924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399924] [NEW] package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: nothing happens just a window at every startup appears about fixing the problem ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sudo 1.8.9p5-1ubuntu2 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 5 01:47:59 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-06-23 (165 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1399924 Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: nothing happens just a window at every startup appears about fixing the problem ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sudo 1.8.9p5-1ubuntu2 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 5 01:47:59 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-06-23 (165 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1399924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315369] Re: Log in not available after lock screen with multi-monitor
** Changed in: xserver-xorg-video-intel Status: Incomplete => Invalid -- 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in X.org xf86-video-intel: Invalid Status in linux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in unity source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select "lock screen" from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315369]
I guess this one is either fixed or dead. -- 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in X.org xf86-video-intel: Invalid Status in linux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in unity source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select "lock screen" from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399906] [NEW] guest session does not start with Xorg
Public bug reported: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- 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/1399906 Title: guest session does not start with Xorg Status in unity package in Ubuntu: New Bug description: When choosing the guest session from the login screen, the screen freezes. `pidof Xorg` gives no running process of the x server. When being logged into a user account and switching to a guest session, it returns after some time to the lock screen of the logged in user. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Dec 6 12:51:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1399906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice
> I can't find the option to tag this report "Tags:" right below the description, above the first comment. ** Tags added: 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/1399595 Title: systemd is activating swap twice Status in systemd package in Ubuntu: New Bug description: systemd is activating swap twice, via its sda name and its uuid. It looks like it's because two swap units are being generated. # journalctl | grep swap | grep -v unit_create_cgroups Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition... Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb... Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device or resource busy Dec 05 04:30:40 yoga.lenovo systemd[1]: dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap process exited, code=exited status=255 Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb. Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap entered failed state. Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition. Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3. Priority:-1 extents:1 across:8298492k SSFS # systemctl status dev-sda3.swap ● dev-sda3.swap - Swap Partition Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap) Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago What: /dev/sda3 Docs: man:systemd-gpt-auto-generator(8) Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, status=0/SUCCESS) Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition... Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition. # systemctl status dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb Loaded: loaded Active: inactive (dead) What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb # swapon -s Filename TypeSizeUsedPriority /dev/sda3 partition 8298492 0 -1 # blkid /dev/sda3 /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0" # find /run -name "*73d341f1*" /run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap /run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb # find /run -name "*sda3*" /run/systemd/generator.late/swap.target.wants/dev-sda3.swap /run/systemd/generator.late/dev-sda3.swap ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 217-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory Date: Fri Dec 5 04:51:30 2014 MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd ipv6.disable_ipv6=1 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1399595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
For me, the bug status is not clear ? Someone know if the fix for Ubuntu 14.04 has been released or not ? Below what I understand : - The fix has not been yet released for Ubuntu 14.04 - The fix will be released on Ubuntu 14.04 with Unity 7.2.4 (The current release of Unity is 7.2.3) => https://launchpad.net/unity => https://launchpad.net/unity/+milestones => https://launchpad.net/unity/+milestone/7.2.4 Anyone can tell me if I'm right or not ? Thanks and have a good day ;) -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399900] [NEW] screen brightness cannot be changed anymore
Public bug reported: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 6 12:20:50 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-24-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (306 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (31 days ago) XorgConf: dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 6 12:19:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- 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/1399900 Title: screen brightness cannot be changed anymore Status in unity package in Ubuntu: New Bug description: The screen brightness does not reliably respond to adjustments anymore since 14.10 release. Previously in 14.04 it was adjustable via a slider in Ubuntu Control Center and via the keyboard buttons (so there is driver and keyboard support for this laptop). Now the keyboard buttons as well as the slider have no effect and the brightness defaults to 100% which is on this device about five times brighter than the comfortable level, and strains the battery. However about 1 in 20 bootups/logins, the brightness is adjustable, but when I logout/login again in the user session, it might again become locked to 100%. I have the suspicion that it depends on the loading of desktop configs or the time I wait before typing my password to login. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSi
[Touch-packages] [Bug 1307021] Re: indicator-power-service crashed with SIGSEGV in g_type_check_instance()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1307021 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() Status in indicator-power package in Ubuntu: Confirmed Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd; apt-cache policy indicator-power Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 indicator-power: Zainstalowana: 12.10.6+14.04.20140328-0ubuntu1 Kandydująca: 12.10.6+14.04.20140328-0ubuntu1 Tabela wersji: *** 12.10.6+14.04.20140328-0ubuntu1 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ shows problem on startup ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140328-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-0ubuntu1 Architecture: amd64 Date: Sat Apr 12 23:06:23 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service InstallationDate: Installed on 2014-03-01 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service SegvAnalysis: Segfault happened at: 0x7f7ffe6237ed : mov (%rdi),%rax PC (0x7f7ffe6237ed) ok source "(%rdi)" (0x0021) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-power StacktraceTop: g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: indicator-power-service crashed with SIGSEGV in g_type_check_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1307021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 889145] Re: focus follows mouse breaks desktop interaction
*** This bug is a duplicate of bug 674138 *** https://bugs.launchpad.net/bugs/674138 In 14.04 - in many cases using Super+D focuses correctly on the desktop. -- 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/889145 Title: focus follows mouse breaks desktop interaction Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Environment: 11.10 x86_64, unity; focus follows mouse enabled with 'gconftool-2 --get /apps/metacity/general/focus_mode' The problem: When there is at least one window open, the desktop doesn't get focus. Key presses go to the window and not the desktop. To reproduce: 1) start with empty desktop 2) create an empty test folder (mouse 3>new folder) 3) open nautilus window. Move so that it doesn't obscure the test folder 4) select test folder on desktop. Leave mouse outside nautilus window. 5) type delete to delete the folder. The keypress is delivered to the nautilus window. (If anything was selected in the nautilus window, it was deleted instead of the test folder.) Since Unity doesn't come with a configuration interface I'm unsure which user preferences are supported/intended by developers and which ones aren't. I'm assuming that Canonical intends users to be able to set prevalent preferences (such as focus follows mouse) since doing otherwise would create a profound user experience regression. Is that assumption correct? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/889145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399401] Re: SmartScopesProxy should allow send the User Agent also when doing the remote-scopes request
Yes, partner-id would be enough for all the situations that we need now (in the future this may change, of course, but let's keep it simple: if "partner-id" only will be fast, let's do that soon and we'll handle the future when it arrives). thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1399401 Title: SmartScopesProxy should allow send the User Agent also when doing the remote-scopes request Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: In the following call: SmartScopesClient.get_remote_scopes(): GET https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en ...the SmartScopesProxy is not sending the normal User Agent (with "partner", etc). The server receives 'Mozilla/5.0', which is not very useful. The SmartScopesProxy should send the User Agent like when doing the search and preview requests, specially because in the "remote-scopes" request is needed to decide which scopes to enable for different partners. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1399401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
Hello. The device is ZTE MF820D. After chaning the old modem to a 4G one I've got: "GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Sending USSD command failed" How do I apply a patch? Regards & respect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager (with NetworkManager support): New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole
the bug is still in Ubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Triaged
Status in rsyslog package in Ubuntu:
Triaged
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager (with NetworkManager support): New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399888] [NEW] Wireless network connection terminates and won't reconnect
Public bug reported: On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Wireless connections terminate without obvious reason. A reconnect is not possible. Every now and then (every second day) the network connection drops. The network indicator shows no signal strenght (empty icon) The correct connection is selected, a wealth of other SSIDs are in the list. A reconnect opens up the password dialog (which is an indication that the old error was reintroduced into the code). I reported this bug several times. The reason at the time was that reconnection would try to fetch the encrypted password and reencrypt it leading to a wrong password. There is a workaround: Disabling and Enabling the network connection reconnects correctly. In the code (as I analyzed then), this is due to the fact that the password from searing is taken as is and forwarded to the authentication code (not reencrypted). The connection gets established again. This issue did not occur in 12.04 and 12.10 (due to less connection problems or due to a fix is beyond me, I simple confirmed there were no connection aborts). It reappeared in 13.x and now is back as an annoyance. The error numbers then were around 460.000 - 490.000 as far is I remember (I have deleted bug reports I considered solved). I observed this issue on any Ubuntu machine. I also observed that the list of SSIDs is extremely long when this incident arises (approx. 15 - 20). Maybe a storm of SSID broadcasts is the basic cause but I have not done any research beyond what I described here. Hope this gets fixed for good now. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:27:42 2014 InstallationDate: Installed on 2013-05-17 (567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1399888 Title: Wireless network connection terminates and won't reconnect Status in wpa package in Ubuntu: New Bug description: On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Wireless connections terminate without obvious reason. A reconnect is not possible. Every now and then (every second day) the network connection drops. The network indicator shows no signal strenght (empty icon) The correct connection is selected, a wealth of other SSIDs are in the list. A reconnect opens up the password dialog (which is an indication that the old error was reintroduced into the code). I reported this bug several times. The reason at the time was that reconnection would try to fetch the encrypted password and reencrypt it leading to a wrong password. There is a workaround: Disabling and Enabling the network connection reconnects correctly. In the code (as I analyzed then), this is due to the fact that the password from searing is taken as is and forwarded to the authentication code (not reencrypted). The connection gets established again. This issue did not occur in 12.04 and 12.10 (due to less connection problems or due to a fix is beyond me, I simple confirmed there were no connection aborts). It reappeared in 13.x and now is back as an annoyance. The error numbers then were around 460.000 - 490.000 as far is I remember (I have deleted bug reports I considered solved). I observed this issue on any Ubuntu machine. I also observed that the list of SSIDs is extremely long when this incident arises (approx. 15 - 20). Maybe a storm of SSID broadcasts is the basic cause but I have not done any research beyond what I described here. Hope this gets fixed for good now. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:27:42 2014 InstallationDate: Installed on 2013-05-17 (567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1399888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice
(I can't find the option to tag this report with "systemd-boot". Is this a question of Launchpad permissions or am I too stupid to find the right thing to click?) I saw that "/lib/systemd/system-generators/" has systemd-fstab-generator and systemd-gpt-auto-generator so I disabled swap in my fstab: # grep swap /etc/fstab #UUID=73d341f1-eedc-43fc-9e53-ba4194dae3fb noneswap sw0 0 And swap's now activated once: # journalctl | grep swap | grep -v unit_create_cgroups Dec 06 04:21:00 yoga.lenovo systemd[1]: Activating swap Swap Partition... Dec 06 04:21:00 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3. Priority:-1 extents:1 across:8298492k SSFS Dec 06 04:21:00 yoga.lenovo systemd[1]: Activated swap Swap Partition. # swapon -s FilenameTypeSizeUsedPriority /dev/sda3 partition 8298492 0 -1 # find /run -name "*73d341f1*" /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb # find /run -name "*sda3*" /run/systemd/generator.late/swap.target.wants/dev-sda3.swap /run/systemd/generator.late/dev-sda3.swap -- 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/1399595 Title: systemd is activating swap twice Status in systemd package in Ubuntu: New Bug description: systemd is activating swap twice, via its sda name and its uuid. It looks like it's because two swap units are being generated. # journalctl | grep swap | grep -v unit_create_cgroups Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition... Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb... Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device or resource busy Dec 05 04:30:40 yoga.lenovo systemd[1]: dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap process exited, code=exited status=255 Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap /dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb. Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap entered failed state. Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition. Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3. Priority:-1 extents:1 across:8298492k SSFS # systemctl status dev-sda3.swap ● dev-sda3.swap - Swap Partition Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap) Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago What: /dev/sda3 Docs: man:systemd-gpt-auto-generator(8) Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, status=0/SUCCESS) Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition... Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition. # systemctl status dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb Loaded: loaded Active: inactive (dead) What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb # swapon -s Filename TypeSizeUsedPriority /dev/sda3 partition 8298492 0 -1 # blkid /dev/sda3 /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0" # find /run -name "*73d341f1*" /run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap /run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb # find /run -name "*sda3*" /run/systemd/generator.late/swap.target.wants/dev-sda3.swap /run/systemd/generator.late/dev-sda3.swap ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 217-3ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory Date: Fri Dec 5 04:51:30 2014 MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd ipv6.disable_ipv6=1 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directo
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
MegaBrutal, you may want to ping an lvm2 maintainer about this. As per https://launchpad.net/ubuntu/+source/lvm2/+changelog the most recent person to commit to this is Dave Chiluk . ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: New Bug description: Hi all, I open this report based on the linked conversation I had on the linux-lvm mailing list, and the Ask Ubuntu question I posted regarding this case. https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot I have 2 VGs on my system, and for some reason, only one of them gets activated during the initrd boot sequence, which doesn't have my root LV, so my boot sequence halts with an initrd prompt. When I get to the initrd BusyBox prompt, I can see my LVs are inactive with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The boot sequence continues as I exit the BusyBox prompt. The expected behaviour would be that both VGs should activate automatically. On LVM mailing list, I've been advised it may be a problem with Ubuntu initrd scripts, hence I report this problem here. (I'm not sure if I'm reporting it to the correct place by assigning it to "linux", but I didn't find a package directly related to the initrd only, so I assumed initrd scripts are maintained by the kernel team. If you think it's an error, and know the correct package, please reassign!) Our suspicion is, initrd prematurely issues "vgchange -ay" before all the PVs come online. This makes sense. I already tried to set the "rootdelay" kernel parameter to make initrd wait longer for the boot LV to come up, but it didn't work. Note however, it worked with previous kernel versions. The problem came up when I upgraded to Utopic, and got kernel vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty (vmlinuz-3.13.0-37-generic), it works fine. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Card1.Amixer.info: Error: [Errno 2] No such file or directory Card1.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0 InstallationDate: Installed on 2013-12-06 (354 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: WinFast 6150M2MA Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ rootdelay=300 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-23-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 01/19/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 686W1D28 dmi.board.name: 6150M2MA dmi.board.vendor: WinFast dmi.board.version: FAB2.0 dmi.chassis.type: 3 dmi.chassis.vendor: WinFast dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr: dmi.product.name: 6150M2MA dmi.product.version: FAB2.0 dmi.sys.vendor: WinFast --- ApportVe
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
I can confirm. It might be that this occurs only from time to time but the first report is about two months old. Why is this bug not permanently fixed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. "apt-get update" failed, and later "apt-get dist upgrade" It started with this when doing a normal "apt-get update" W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
