[Touch-packages] [Bug 1375067] Re: Can't open pdf file from webdav share, apparmor denies access to dbus
This was fixed in utopic in apparmor 2.8.98-0ubuntu2; marking closed. (Sorry, I missed the reference to this bug when updating the changelog for that release.) ** Changed in: apparmor (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1375067 Title: Can't open pdf file from webdav share, apparmor denies access to dbus Status in “apparmor” package in Ubuntu: Fix Released Bug description: I've recently upgraded to Ubuntu utopic. When trying to access a pdf file on a dav:// share, I get a permission denied error. While getting peer-to-peer dbus connection: Verbindung ist gescheitert: Keine Berechtigung In dmesg, I see this [ 1394.331262] audit: type=1400 audit(1411945678.080:57): apparmor=DENIED operation=connect profile=/usr/bin/evince pid=18278 comm=EvJobScheduler family=unix sock_type=stream protocol=0 requested_mask=send receive connect denied_mask=send connect addr=none peer_addr=@/dbus-vfs-daemon/socket-8Ij86BjH peer=unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1375067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352975] Re: GUI symbol for Wi-fi in 14.10 shows not connected even when connected
The question mark has disappeared; don't know what changed... -- 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/1352975 Title: GUI symbol for Wi-fi in 14.10 shows not connected even when connected Status in “network-manager” package in Ubuntu: Confirmed Status in “wifi-radar” package in Ubuntu: Invalid Bug description: Using Ubuntu 14.10 alpha 2 with all updates. Clean install. Network manager 0.9.8.8-0ubuntu23 Wifi-card: Intel Wireless 7260 (Rev 73) The Wi-fi symbol in the top right corner does not indicate that it is connected to Wi-fi even when it is connected. (It shows a question mark instead) Expected behavior is that it would show signal strength, or at the very least make it grey and remove the question mark. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 5 17:42:57 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140730) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.110 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 18b6987c1-3f15-4b41-be88-ea9f5ae9eff6 802-3-ethernet1407252000 ti. 05. aug. 2014 kl. 17.20 +0200 yes no /org/freedesktop/NetworkManager/Settings/1 Diskokatt 5Ghz6a2433b7-9e20-4c4a-9c9d-455fee3505ef 802-11-wireless 1407253201 ti. 05. aug. 2014 kl. 17.40 +0200 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1352975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
Forgot to mention, all these patches will go into upstream 5.4, but will also cleanly apply to 5.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
I now have a mako to test on. As far as I can tell, those patches did not fix this. At leastnow the bearer backend is mostly working. Tested with the soundcloud scope tutorial app :) and one I made testing QNAM/QNetworkConfiguration and friends. I think the problem is the bearer backend does not find any usable configurations when connected to mobile data. Will do more work on the bearer backend... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382267] Re: edges intro fails on rtm krillin 112
** Branch linked: lp:~unity-team/unity8/edgedemo-update-indicators -- 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/1382267 Title: edges intro fails on rtm krillin 112 Status in “unity8” package in Ubuntu: Confirmed Bug description: On rtm krillin image 112, the edges intro doesn't work. After swiping down from the top to reveal an indicator menu, the bottom-edge tutorial overlay doesn't appear. However, if I swipe it up anyway, the final edge overlay appears and I can proceed to use the device. Only one of the five overlays fails (right, top, bottom, left, tap... bottom fails). This worked in image 109. Update: Saviq reports it's also failing on 109. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368492] Re: crash opening image file
This bug was fixed in the package gallery-app - 0.0.67+14.10.20141010-0ubuntu1 --- gallery-app (0.0.67+14.10.20141010-0ubuntu1) 14.09; urgency=low [ Bill Filler ] * Scale the album title proportionally to the album itself, so it works on all devices. (LP: #1377767) [ Ubuntu daily release ] * New rebuild forced [ Florian Boucault ] * Respect EXIF orientation when showing a photo by starting to use the GalleryStandardImageProvider again. (LP: #1377298) [ Jussi Pakkanen ] * Fix thumbnailer import. (LP: #1368492) [ Ugo Riboni ] * Scale the album title proportionally to the album itself, so it works on all devices. (LP: #1377767) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 10 Oct 2014 01:30:08 + ** Branch linked: lp:ubuntu/utopic-proposed/gallery-app ** Changed in: gallery-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1368492 Title: crash opening image file Status in Ubuntu UI Toolkit: In Progress Status in “gallery-app” package in Ubuntu: Fix Released Status in “thumbnailer” package in Ubuntu: Invalid Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: Fix Released Bug description: krillin image 25 libthumbailer version 1.2+14.10.20140814-0ubuntu1 - take a picture with the camera - open the gallery app - click on the thumbnail of the photo just taken - boom, crash happens Here is the stack trace. Core file and picture used are attached [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1. Core was generated by `./gallery-app'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb5b2201c in std::string::assign(std::string const) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (gdb) bt #0 0xb5b2201c in std::string::assign(std::string const) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 #1 0xacebe712 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0 #2 0xacebec62 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0 #3 0xacebff34 in Thumbnailer::get_thumbnail(std::string const, ThumbnailSize, ThumbnailPolicy) () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0 #4 0xacec00ae in Thumbnailer::get_thumbnail(std::string const, ThumbnailSize) () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0 #5 0xacf7b70e in ThumbnailGenerator::requestImage(QString const, QSize*, QSize const) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so #6 0xb640acfa in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1368492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382278] Re: Image #94 on mako / #88 on flo fails to start - mir crash
Same on #95, and also after --bootstrap. My crashes on #95 after the --bootstrap wipe are as follows. I tried a local backtracing but for some reason it's failing to find ExecutablePath for all of them, so I sent them now to Launchpad: ubuntu-system-settings: LP: #1382373 media-hub LP: #1382375 mtp-server LP: #1382376 -- 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/1382278 Title: Image #94 on mako / #88 on flo fails to start - mir crash Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Update from #93 to #94 and I get the constant ubuntu spinning logo. adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs. Reverting to #93 'fixes' it, and going forward to #94 breaks it again. FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382376] Re: mtp-server crashed with SIGSEGV
** Tags removed: need-armhf-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1382376 Title: mtp-server crashed with SIGSEGV Status in “mtp” package in Ubuntu: New Bug description: One of the crashes on mako rtm #95 which stays at Ubuntu boot logo after flashing (bug #1382278). ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: mtp-server 0.0.4+14.10.20140909~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf CurrentDesktop: Unity Date: Fri Oct 17 06:34:03 2014 ExecutablePath: /usr/bin/mtp-server ExecutableTimestamp: 1410282505 InstallationDate: Installed on 2014-10-17 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141017-030205) ProcCmdline: /usr/bin/mtp-server ProcCwd: /home/phablet SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mtp Stacktrace: #0 0xb6df4520 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 No symbol table info available. #1 0x in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 ?? () UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1382376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
Exactly the same issue here. Fresh installation and opensource (no catalyst) ati drivers (Radeon HD 4670). This is frustrating, especially as it is already half a year after the 14.04 release. When 12.04 came out, I changed the graphics card (removed NVidia 8800 and replaced it by Radeon 4670) on my workstation because I couldn't get the system work correctly. Do we have to change graphics cards possibly everytime after a major release?? Pardon me for this small rant, but this is utterly frustrating. That said, I'd like to mention that the broken suspend function hasn't been fixed now in years. We run more than 5 different computers and laptops here in the office. Not one is able to suspend and to resume correctly. I know that doesn't belong into this thread, but I just needed to rant and unload some frustration that I picked up over months and years. Other than that, I love Ubuntu :-)(despite some new window/menu related focusing issues in Unity lately...) -- 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/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic
[Touch-packages] [Bug 805303] Re: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui
** Changed in: qt4-x11 (Ubuntu) Assignee: (unassigned) = aruna (sudhaparimala) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/805303 Title: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui Status in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Invalid Status in The Oneiric Ocelot: Fix Released Status in “qt4-x11” source package in Oneiric: Fix Released Status in “xorg-server” source package in Oneiric: Invalid Bug description: vlc will hang when trying to open anything additional - it also appears to crash unity-window-decorator among other things (have crash report on that) Ex.'s - the playlist, tools preferences and so forth Switching the qt4 gui to anything but 'default' (gtk+) in qtconfig-qt4 and it works without incidence (tooltips are empty bit otherwise good). Will attach xsession.errors, reflects a login, opening vlc, opening xsession.errors, then attempting to open playlist window in vlc. (using nvidia-current) Note to Vlc users - I've found clearlooks to be best choice, should be good for other apps as well. Also do as mentioned in comment 13 Note to Anki users - please review comments 20, 22 for current workaround This happens with many Qt4 and PyQt4 applications. Some errors displayed (from comments 16 and 18): (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed QWidget::setMinimumSize: (/MainWindow) The largest allowed size is (16777215,16777215) X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 (X_CreatePixmap) Resource id: 0x15a X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension:152 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x42004f6 X Error: RenderBadPicture (invalid Picture parameter) 174 Extension:152 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x42004f6 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x42004f6 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vlc 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7 Uname: Linux 2.6.38-9-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Jul 3 23:23:42 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to oneiric on 2011-07-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/805303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382252] Re: Unity8 needs to support fullscreen surfaces.
We do support fullcreen, not sure how it works, but both Camera and Gallery go full screen. ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- 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/1382252 Title: Unity8 needs to support fullscreen surfaces. Status in “unity8” package in Ubuntu: Invalid Bug description: Right now in unity8 the top panel eats up an some of the pixels for the surface height. So say i request a surface for 540x960, then mir resizes the surface to 540x921. This means any application that depends on a WxH will lose an X amount of H. This hurts games, as they usually depend on a set WxH. If unity8 supported a fullscreen mode where the top panel wouldn't be visable and wouldn't eat pixels from the WxH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382027] Re: Tracks without embedded art do not download the art
The file has been ripped and tagged by a CD ripper on Ubuntu. I don't exactly remember which. Note that in VLC I get an album art (right artist but wrong album though) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1382027 Title: Tracks without embedded art do not download the art Status in “unity-scope-mediascanner” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Download http://people.canonical.com/~j-lallement/supertramp_1979_paris_cd1_School.mp3 2. Plug the device in and transfer the file above over MTP to the internal storage 3. Open the Music scope and locate the track (by searching or browsing) 4. Confirm that eventually the album art for the track is downloaded Expected result: After a period of time the album art is downloaded and appears as the cover art Actual result: The album art is never downloaded ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:09:07 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1382027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382267] Re: edges intro fails on rtm krillin 112
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical -- 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/1382267 Title: edges intro fails on rtm krillin 112 Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: On rtm krillin image 112, the edges intro doesn't work. After swiping down from the top to reveal an indicator menu, the bottom-edge tutorial overlay doesn't appear. However, if I swipe it up anyway, the final edge overlay appears and I can proceed to use the device. Only one of the five overlays fails (right, top, bottom, left, tap... bottom fails). This worked in image 109. Update: Saviq reports it's also failing on 109. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351423] Re: [Dash] icon significantly different to that on other platforms
If you want design to comment, don't reopen the unity8 task, reopen the design one :) -- 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/1351423 Title: [Dash] icon significantly different to that on other platforms Status in Ubuntu UX bugs: Won't Fix Status in “unity8” package in Ubuntu: New Bug description: The dash icon is shown as an orange square (with very hard straight edges btw) with the Ubuntu logo within. This seems odd since it is so markedly different to the dash icon on desktop systems (the swirl). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310746] Re: NetworkManager wired ethernet times out waiting for dhcp on 14.04 trusty tahr
Affects even running 14.04 from live CD. On fresh install network manager does not work also, even setting static IPs. Ping says destination host unreachable 99% queries and very long timeout 1%. This means network does not work at all. -- 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/1310746 Title: NetworkManager wired ethernet times out waiting for dhcp on 14.04 trusty tahr Status in “network-manager” package in Ubuntu: Confirmed Bug description: I'm experiencing dhcp timeouts on 14.04 that I didn't experience in earlier releases (13.10 and 12.04 are in use in the office). Others in my office have similar complaints that wired ethernet stops working in 14.04 which all equate to a dhcp timeout. When switching back to 13.10 dhcp works flawlessly. network-manager 0.9.8.8-0ubuntu7 (the current version on trusty) contains the following changelog: * debian/tests/nm: Bump DHCP timeouts from 15 to 20 seconds, something in the stack got even slower as it used to be. * debian/tests/nm: With the patch in 0.9.8.8-0ubuntu5, interfaces with PE disabled still get a temporary IP. Disable that check for now. -- Martin Pitt _...@ubuntu.com Wed, 09 Apr 2014 15:41:11 +0200 I don't think increasing the timeout in the test in order to get it to pass is the correct approach. It's likely masking the underlying issue that we're experiencing. -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status isc-dhcp-client: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status isc-dhcp-common: Installed: 4.2.4-7ubuntu12 Candidate: 4.2.4-7ubuntu12 Version table: *** 4.2.4-7ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Ethernet to just work 4) What happened instead Wired ethernet times out waiting for a dhcp connection. This does not occur on the same hardware using past releases of Ubuntu. It also doesn't happen when connecting via wireless. debug logs attached: sudo python debug-helper.py --nm debug ; tail -n0 -f /var/log/syslog | sed -e '/get_active_ap/d' -e '/dump_route/d' /tmp/syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1310746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351423] Re: [Dash] icon significantly different to that on other platforms
Ah, you can't reopen the design one. I'll assign John Lea to the unity8 task then. ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = John Lea (johnlea) -- 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/1351423 Title: [Dash] icon significantly different to that on other platforms Status in Ubuntu UX bugs: Won't Fix Status in “unity8” package in Ubuntu: New Bug description: The dash icon is shown as an orange square (with very hard straight edges btw) with the Ubuntu logo within. This seems odd since it is so markedly different to the dash icon on desktop systems (the swirl). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322764] Re: apache2 does not work with shipped profiles
** Changed in: apparmor Status: In Progress = Fix Committed -- 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/1322764 Title: apache2 does not work with shipped profiles Status in AppArmor Linux application security framework: Fix Committed Status in “apparmor” package in Ubuntu: Fix Released Bug description: Apache2 fails dramatically with apparmor module enabled. $ apt-get install apache2 libapache2-mod-php5 libapache2-mod-apparmor #bug? #Processing triggers for ufw (0.34~rc-0ubuntu2) ... #WARN: Skipping 'ufw-directoryserver': couldn't process $ service apache2 stop $ service apache2 start # All is well # By default, apache2 is disabled: $ aa-status | grep apache | wc -l 0 $ ls /etc/apparmor.d/disable | grep apache2 | wc -l 1 $ grep complain /etc/apparmor.d/usr.sbin.apache2 /usr/sbin/apache2 flags=(complain) { ^DEFAULT_URI flags=(complain) { ^HANDLING_UNTRUSTED_INPUT flags=(complain) { $ aa-enforce /etc/apparmor.d/usr.sbin.apache2 $ ls /etc/apparmor.d/disable | grep apache2 | wc -l 0 $ grep complain /etc/apparmor.d/usr.sbin.apache2 ^DEFAULT_URI flags=(complain) { ^HANDLING_UNTRUSTED_INPUT flags=(complain) { #bug: complain not removed on hats when aa-enforce runs $ aa-status ... 31 profiles are in enforce mode. ... /usr/sbin/apache2 ... 2 profiles are in complain mode. /usr/sbin/apache2//DEFAULT_URI /usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT 6 processes are unconfined but have a profile defined. /usr/sbin/apache2 (811) /usr/sbin/apache2 (814) ... $ service apache2 stop * Stopping web server apache2 $ ps -ef | grep apache2 | wc -l 8 #bug: stop fails, via seemingly impossible signal blocking # dmesg shows: # [17967.520600] type=1400 audit(1399577975.916:104): apparmor=DENIED operation=signal profile=/usr/sbin/apache2 pid=29013 comm=apache2 requested_mask=send denied_mask=send signal=term peer=unconfined # How did this happen? The /usr/sbin/apache2 profile has base, which includes the signal # rules for allowing an unconfined process send to it. # Get back to sanity: $ apparmor_parser -R /etc/apparmor.d/usr.sbin.apache2 $ service apache2 stop $ vi /etc/apparmor.d/usr.sbin.apache2 #remove complain flags on HATs $ apparmor_parser -r /etc/apparmor.d/usr.sbin.apache2 $ aa-status ... 33 profiles are in enforce mode. ... /usr/sbin/apache2 /usr/sbin/apache2//DEFAULT_URI /usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT ... $ service apache2 start $ aa-status ... 13 processes are in enforce mode. ... /usr/sbin/apache2 (1152) /usr/sbin/apache2 (1153) ... $ wget http://localhost/ # All is well $ a2enmod apparmor $ service apache2 restart $ aa-status ... 13 processes are in enforce mode. ... /usr/sbin/apache2 (1162) /usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT (1165) /usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT (1166) ... $ wget http://localhost/ # All is well $ service apache2 stop # Apache2 can't shut down # logs: [Fri May 09 22:34:42.280997 2014] [core:warn] [pid 1162] AH00045: child process 1165 still did not exit, sending a SIGTERM # dmesg: [140073.881409] type=1400 audit(1399700082.276:328): apparmor=DENIED operation=signal profile=/usr/sbin/apache2//HANDLING_UNTRUSTED_INPUT pid=1162 comm=apache2 requested_mask=receive denied_mask=receive signal=term peer=/usr/sbin/apache2 #bug: signals from apache to hats fail $ pkill apache2 pkill: killing pid 1382 failed: Permission denied pkill: killing pid 1383 failed: Permission denied ... #bug: signals from unconfined to hats fail # Fix things up... $ apparmor_parser -R /etc/apparmor.d/usr.sbin.apache2 $ service apache2 stop $ pkill apache2 $ vi /etc/apparmor.d/usr.sbin.apache2 # add to ^HANDLING_UNTRUSTED_INPUT (instead of adding all of base): ## Allow unconfined processes to send us signals by default #signal (receive) peer=unconfined, ## Allow apache to send us signals by default #signal (receive) peer=/usr/sbin/apache2, ## Allow us to signal ourselves #signal peer=@{profile_name}, # add to ^DEFAULT_URI (not in base): ## Allow apache to send us signals by default #signal (receive) peer=/usr/sbin/apache2, # add to /usr/sbin/apache2: ## Send signals to all hats. #signal (send) peer=/usr/sbin/apache2//*, # add to /etc/apparmor.d/abstractions/apache2-common (instead of all of base): ## Allow unconfined processes to send us signals by default #signal (receive) peer=unconfined, ## Allow apache to send us signals by default #signal (receive) peer=/usr/sbin/apache2, ## Allow us to signal ourselves #signal peer=@{profile_name}, $ apparmor_parser -r
[Touch-packages] [Bug 1379296] Re: unity8-dash should be excluded from app lifecycle management
if the dash would not be in lifecycle management at all and you would have gotten your system in such a state, the kernel would just have randomly killed bits of your session instead of the dash. it is wanted that in such cases the dash gets killed before i.e. ofono gets killed so that your session still stays functional. imho the behavior is just fine, in case the sysem functions normal it should be the last of your UI apps that gets killed. in case where not even that would free up enough memory you have a whole lot of bigger probs ... the bug here lies within the apps that consume all your ram where they should not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379296 Title: unity8-dash should be excluded from app lifecycle management Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Status in “qtmir” package in Ubuntu RTM: New Bug description: STEPS: 1. Install the BBC NEWS app from the store 2. Go back to the apps scope 3. Open the bbc app browse about a bit 4. Click on a video link 5. let it play for a while 6. Cycle back to the scopes Scopes then restarts having a lot of apps open my unity8-dash gets contantly killed along the apps if a certain OOM threshold is reached ... this appears like a system crash of the UI (even though it is desired killing) from a user perspective ... checking the oom_score_adj values of all running apps i see that the dash has the same high value as all other open foreground apps: ... 117960oxide-renderer 117963oxide-renderer 117988oxide-renderer 300 6170oxide-renderer 802 12514 unity8-dash 802 6088webbrowser-app 802 6873webapp-containe 802 7425webapp-containe 802 7910webapp-containe (the full log can be found at http://paste.ubuntu.com/8526308/ ) given that the dash is one part of our core UI it should be excluded from app lifecycle management (keeping the same oom_score of 10 as unity8 does) so that only actual apps get killed on high memory pressure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1379296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350308] Re: Blank entries in transfer indicator
** Changed in: unity8 (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1350308 Title: Blank entries in transfer indicator Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: Updating an app, and installing another i see no icon in transfer indicator and no text. See screenshot. Compare bug 1350771, the equivalent for in-progress updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-transfer/+bug/1350308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382278] Re: Image #94 on mako / #88 on flo fails to start - mir crash
qtmir was changed in image #93 (which translates to rtm krillin image 111) image #94 maps to krillin rtm 112 for which the change set is at http://people.canonical.com/~ogra/touch-image-stats/rtm/112.changes ... note that the libhybris change in there required a change on the android side, i assume this bit was forgotten for mako. ** Also affects: libhybris (Ubuntu) Importance: Undecided Status: New ** Package changed: libhybris (Ubuntu) = libhybris (Ubuntu RTM) -- 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/1382278 Title: Image #94 on mako / #88 on flo fails to start - mir crash Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu RTM: New Bug description: Update from #93 to #94 and I get the constant ubuntu spinning logo. adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs. Reverting to #93 'fixes' it, and going forward to #94 breaks it again. FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382278] Re: Image #94 on mako / #88 on flo fails to start - mir crash
I've tried reverting libhybris, media-hub and qmenumodel landings, but reverting those to the #93 versions doesn't seem to help. -- 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/1382278 Title: Image #94 on mako / #88 on flo fails to start - mir crash Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu RTM: New Bug description: Update from #93 to #94 and I get the constant ubuntu spinning logo. adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs. Reverting to #93 'fixes' it, and going forward to #94 breaks it again. FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381546] Re: Please backport patches to add '.csd' class to CSDed windows
Ok, as discussed on IRC they are not that important for utopic but we are going to get that in next cycle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1381546 Title: Please backport patches to add '.csd' class to CSDed windows Status in “gtk+3.0” package in Ubuntu: Confirmed Bug description: Please backport these two patches: * https://github.com/GNOME/gtk/commit/bde4e863579f05368661347bfaf55e0480e4555c * https://github.com/GNOME/gtk/commit/60cd7076cf885cbc421babfba44c9081ded3ad78 They are useful to have a '.csd' class on the CSDed windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1381546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382401] [NEW] Easy to trigger 404/416 errors after recent security update
Public bug reported: The recent security update make it easy to trigger debian bug #710924 - i.e. apt does not deal well with 416 requests from the remote server. TEST CASE: 1 install latest apt from security 2 run sudo apt-get update 3 run sudo apt-get update again and ctrl somewhere in the middle 4 run sudo apt-get update again 5 verify that you get either 404 or 416 errors 6 install the updated version from prospoed 7 verify that sudo apt-get update works now 8 verify that steps 2-4 do not lead to a failure ** Affects: apt (Ubuntu) Importance: High Status: Fix Released ** Affects: apt (Ubuntu Lucid) Importance: High Status: In Progress ** Affects: apt (Ubuntu Precise) Importance: High Status: In Progress ** Also affects: apt (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Lucid) Status: New = In Progress ** Changed in: apt (Ubuntu Lucid) Importance: Undecided = High ** Changed in: apt (Ubuntu) Importance: Undecided = High ** Changed in: apt (Ubuntu) Status: New = Fix Released ** Changed in: apt (Ubuntu Precise) Status: New = In Progress ** Changed in: apt (Ubuntu Precise) Importance: Undecided = High -- 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/1382401 Title: Easy to trigger 404/416 errors after recent security update Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Lucid: In Progress Status in “apt” source package in Precise: In Progress Bug description: The recent security update make it easy to trigger debian bug #710924 - i.e. apt does not deal well with 416 requests from the remote server. TEST CASE: 1 install latest apt from security 2 run sudo apt-get update 3 run sudo apt-get update again and ctrl somewhere in the middle 4 run sudo apt-get update again 5 verify that you get either 404 or 416 errors 6 install the updated version from prospoed 7 verify that sudo apt-get update works now 8 verify that steps 2-4 do not lead to a failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1382401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 805303] Re: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui
** Changed in: qt4-x11 (Ubuntu) Assignee: aruna (sudhaparimala) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/805303 Title: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui Status in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Invalid Status in The Oneiric Ocelot: Fix Released Status in “qt4-x11” source package in Oneiric: Fix Released Status in “xorg-server” source package in Oneiric: Invalid Bug description: vlc will hang when trying to open anything additional - it also appears to crash unity-window-decorator among other things (have crash report on that) Ex.'s - the playlist, tools preferences and so forth Switching the qt4 gui to anything but 'default' (gtk+) in qtconfig-qt4 and it works without incidence (tooltips are empty bit otherwise good). Will attach xsession.errors, reflects a login, opening vlc, opening xsession.errors, then attempting to open playlist window in vlc. (using nvidia-current) Note to Vlc users - I've found clearlooks to be best choice, should be good for other apps as well. Also do as mentioned in comment 13 Note to Anki users - please review comments 20, 22 for current workaround This happens with many Qt4 and PyQt4 applications. Some errors displayed (from comments 16 and 18): (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed QWidget::setMinimumSize: (/MainWindow) The largest allowed size is (16777215,16777215) X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 (X_CreatePixmap) Resource id: 0x15a X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension:152 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x42004f6 X Error: RenderBadPicture (invalid Picture parameter) 174 Extension:152 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x42004f6 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x42004f6 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vlc 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7 Uname: Linux 2.6.38-9-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Jul 3 23:23:42 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to oneiric on 2011-07-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/805303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382278] Re: Image #94 on mako / #88 on flo fails to start - mir crash
Reverting to the following media-hub packages seems to help: libmedia-hub-client2_2.0.0+14.10.20141015-0ubuntu1_armhf.deb libmedia-hub-common2_2.0.0+14.10.20141015-0ubuntu1_armhf.deb media-hub_2.0.0+14.10.20141015-0ubuntu1_armhf.deb Upgrading those back breaks the boot. libhybris revert was actually not needed, even though I did that first. -- 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/1382278 Title: Image #94 on mako / #88 on flo fails to start - mir crash Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “libhybris” package in Ubuntu RTM: New Bug description: Update from #93 to #94 and I get the constant ubuntu spinning logo. adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs. Reverting to #93 'fixes' it, and going forward to #94 breaks it again. FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382115] Re: package dictionaries-common 1.12.1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1382115 Title: package dictionaries-common 1.12.1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in “dictionaries-common” package in Ubuntu: New Bug description: the pc did not want to shut down ProblemType: Package DistroRelease: Ubuntu 12.04 Package: dictionaries-common 1.12.1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39 Uname: Linux 3.2.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Oct 12 08:00:28 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.12.1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1382115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382139] Re: scope appearance key not being used in agg scope
** 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/1382139 Title: scope appearance key not being used in agg scope Status in The Savilerow project: New Status in “unity8” package in Ubuntu: New Status in “unity8” package in Ubuntu RTM: New Bug description: Facebook Photos scope ini has this Appearance setting: PreviewButtonColor=#45619d A fb photos button uses this color. It's the button that displays when the user has not logged into Facebook. It displays in a Result, not in a preview. The button allows the user to log in to FB through Online Accounts. (see fb.png) Photos aggregator scope includes Facbook Photos scope as a child scope. When the user has not yet logged into facebook the facebook photos category in the Photos scope HAS the button. But, the button has no color (neither the button background nor the text), thus making it invisible (see invisible.png and invisiblePressed.png). I would expect the child scope's settings to be honored so that Photos scope displays the button with the Facebook Blue color as defined in the child scope. Note that different child scopes may need different colored buttons in the aggregator scope context. At the very least, the button should display in the agg scope's default Appearance (and not be invisible). Note: even when setting PreviewButtonColor=#45619d in the Photos agg scope ini, still, the button is invisible. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1382139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363405] Re: Setting a PIN can result in a passphrase instead
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1363405 Title: Setting a PIN can result in a passphrase instead Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu RTM: Incomplete Bug description: It's happened to me a few times that even though I selected passcode (4 digit) as my lock (e.g. in the wizard), I was still presented with a full keyboard in the lockscreen. I'm worried that for someone it might result in the opposite, rendering the phone inaccessible because you can't type your passphrase with a pin-pad. We either need to improve robustness of the setting (ideally storing the lick type next to the password itself in PAM somehow?) or allow switching to a full keyboard entry in the passcode lockscreen. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings 0.3+14.10.20140828.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 30 11:23:04 2014 InstallationDate: Installed on 2014-08-30 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1363405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368489] Re: trusty tahr upgrade system error, cups based.
** Package changed: cups (Ubuntu) = cups-pk-helper (Ubuntu) -- 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/1368489 Title: trusty tahr upgrade system error, cups based. Status in “cups-pk-helper” package in Ubuntu: New Bug description: DIST-UPGRADED to trusty tahr, what a mess. Previously fine-working auto-loaded canon printer, now toast. Annoying sys error, like others complain but diff. details as follow, hand typed best I can. Is it possible, linux is having viruses now? Keep asking me to sign into keyring; fix online did not solve. Afraid to sign in, as its similar to a windows virus popup, etc. Signs of browser virus, transposer of type, only in browser window typing/addy bar, all spelling jumbled in pairs. Even after purging/reinstalling chrome. Notice the below, says no log of upgrade, i did dist-upgrade, so should be there. 13.04 worked fine with printer. thinking apps, as keep failing weird errors, purged openshot, gimp, chromium-browser; reinstalled, all 3 bizarre problems. No effect. still have the typo backwards spelling-affecting thing similar to virus, tho browser now fully replaced. sys: dell latitude d620 amd64, running upgraded to trusty tahr; no google info, others similar, but not identical cups origin: Sorry, Ubuntu 14.04 has experienced an error: executable (hand typing) path: /usr/lib/x86)64-linux-gnu/cups-pk-helper-mechanism package cups-pk-helper 0.2.5-Oubuntu1 problem type - crash title cups-pk-helper-mechanism crashed wtih signal 5 in g_variant_new_va() apportversion: 2.14.1-Oubuntu3.4 Architecture: amd64 Core Dump (binary data) Date Sept. 9 ... Dependencies: adduser3.113+nmu3ubuntu3 apt-utils 1.0.1ubuntu2.1 base-passwd 3.5.33 busybox-initramfs 1:1.21.0-1ubuntu1 coreutils 8.21-1ubuntu5 cpio 2.11+dfsg-1ubuntu1 dbus 1.6.18-0ubuntu4.1 debconf 1.5.51ubuntu2 debianutils 4.4 dpkg 1.17.5ubuntu5.3 e2fslibs 1.42.9-3ubuntu1 e2fsprogs 1.42.9-3ubuntu1 findutils4.4.2-7 gcc-4.8-base 4.8.2-19ubuntu1 gcc-4.9-base 4.9-20140406-0ubuntu1 ifupdown 0.7.47.2ubuntu4.1 initramfs-tools 0.103ubuntu4.2 initramfs-tools-bin 0.103ubuntu4.2 initscripts 2.88dsf-41ubuntu6 insserv 1.14.0-5ubuntu2 iproute2 3.12.0-2 isc-dhcp-client 4.2.4-7ubuntu12 isc-dhcp-common 4.2.4-7ubuntu12 klibc-utils .20.3-0ubuntu1 kmod 14-0ubuntu6 krb5-locales 1.12+dfsg-2ubuntu4.2 libacl1 2.2.52-1 libapparmor1 2.8.95~2430-0ubuntu5 libapt-inst1.5 1.0.1ubuntu2.1 libapt-pkg4.12 1.0.1ubuntu2.1 libattr1 1:2.4.47-1ubuntu1 AN DA WHOLE SHOOTLOAD MORE THAT I CANNOT POSSIBLY TYPE. ITS MAKING SYS SO SLOW, CURSOR ON BROWSRE TAKES FOREVER TO UNFREEZE, FRUCKING UP MY SPELLING CONSTANTLY. LIST continues: disassembly: ubnhc of niternla addsy DsitorRleesae Uubnut 41.04 SEE THAT? I TYPED IT ACCURATELY, TOOK FOREVER TO SHOW, ALL JUMBLED: disassembly (bunch of IRQ looking addys) Distro Release: Ubuntu 14.04 Installation Date: 2014 7 30 Install media: trusty tahr amd64 arch: amd64 procCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism ProcEnviron (blank) ProcMaps: (ton of stuff) ProcStatus: name: cups-pk-helper- (ver batim) state S (sleeping) tgid: 13288 Ngid 0 Pid 13288 PPid 1 tracer Pid 0 Uid 0 0 0 0 Gid 0 0 0 0 FDSize 64 Groups 0 VMPeak: 307264 kb VMSize 241864 kb VmLck: 0 kb vmPin 0 kb VmHWM: 5016 kB vmRSS 5016 kB vmData: 148244 kB VmStk 136 kB vmExe 112 KB VmLib 10980 kB VmPTE: 208 kb vmSwap: 0 kb threads 3 sigQ 0/23835 sigPnd 00 shdPnd: SigBlk ditto SigIgn ditto SigCgt 00018000 CapInh all zeros CapPrm 001f Cap Eff 001 f CapBnd 001 f Seccomp 0 Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed ,1 Mems_allowed_list: 0 voluntary_ctxt_switches: 21 nonvoluntary_ctxt_switches: 2 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Registers: ton of stuff: Signal: 5 Source Package: cups-pk-helper Stacktrace: too much to type Tags: trusty Threadstacktrace (not typing) Uname: Linux 3.13.0-35-generic x86x64 UpgradeStatus: no upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1368489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
I just noticed that on a fresh boot, with only 'Videos' application open, expected behaviour occurs (menu items appear with cursor hard to top of screen). BUT - when I open another application (Thunderbird) both it and 'Videos' go back to the buggy behaviour - menu items only appear with cursor slightly away from absolute top of screen. So behaviour is somewhat inconsistent. -- 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/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence snatching defeat from the jaws of victory - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382027] Re: Tracks without embedded art do not download the art
Perhaps it was low quality metadata from FreeDB then? As far as providing more fuzzy matching goes, the online album art provided by the thumbnailer is hitting an in-house service. Perhaps it is the best place to do this sort of thing (so it can cache the result, and avoid extra round trips, etc)? It will depend on what capabilities 7digital exposes exactly though (what our service uses). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1382027 Title: Tracks without embedded art do not download the art Status in “unity-scope-mediascanner” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Download http://people.canonical.com/~j-lallement/supertramp_1979_paris_cd1_School.mp3 2. Plug the device in and transfer the file above over MTP to the internal storage 3. Open the Music scope and locate the track (by searching or browsing) 4. Confirm that eventually the album art for the track is downloaded Expected result: After a period of time the album art is downloaded and appears as the cover art Actual result: The album art is never downloaded ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:09:07 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1382027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Changed in: unity-scope-mediascanner (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in Ubuntu Rest Scopes: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
Same thing here - although I'm not sure whether this should be fixed in PulseAudio, or if the underlying layers (alsa-lib and kernel) should provide information the way PA wants to instead. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = Triaged -- 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/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Triaged Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374426] Re: [ap] Dash sometimes fails to appear during Autopilot tests - causes fails
** Branch linked: lp:~aacid/qtmir/sessionAuthorizerWaitSignalListener ** Changed in: unity8 (Ubuntu) Assignee: Gerry Boland (gerboland) = Albert Astals Cid (aacid) ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity8 (Ubuntu) Assignee: Albert Astals Cid (aacid) = (unassigned) ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) = Albert Astals Cid (aacid) ** Changed in: unity8 (Ubuntu) Status: Fix Released = Invalid ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Invalid ** Changed in: qtmir (Ubuntu) Status: New = Fix Released ** Changed in: qtmir (Ubuntu) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1374426 Title: [ap] Dash sometimes fails to appear during Autopilot tests - causes fails Status in “qtmir” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: Dash sometimes fails to appear during Autopilot tests - causes failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1374426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1191934] Re: orientation wrong in playback for recorded videos
Videoflip does not work because the pipeline is not emitting the orientation tag. I wrote a test app to dump all tags and ran it with GST_DEBUG=3. In the output we find this: 0:00:00.034587209 32036 0x7f047c0522d0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type pasp 0:00:00.034666428 32036 0x7f047c0522d0 FIXMEqtdemux qtdemux.c:7212:qtdemux_inspect_transformation_matrix:qtdemux0 Unhandled transformation matrix values -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1191934 Title: orientation wrong in playback for recorded videos Status in Media Hub: Fix Committed Status in QT Ubuntu Media: New Status in Thumbnail generator for all kinds of files: New Status in “qtubuntu-camera” package in Ubuntu: Fix Released Status in “media-hub” package in Ubuntu RTM: Fix Committed Status in “qtvideo-node” package in Ubuntu RTM: Fix Committed Bug description: saucy-15 + updates Galaxy Nexus camera-app 2.9.1daily13.06.17-0ubuntu1 gallery-app 0.0.67daily13.06.17-0ubuntu1 If you record a video in portrait orientation in the camera, it should be played back in same orientation in gallery but it is not. It's incorrectly displayed in landscape mode rotated 90 degrees to the left. See attached images. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1191934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255180] Re: Reading scope models sometimes produces lots of criticals
Unity8 doesn't use dee anymore. ** Changed in: unity8 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1255180 Title: Reading scope models sometimes produces lots of criticals Status in Dee: New Status in Unity: New Status in “unity” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: In some cases shell gets into a situation where the results in the dee model are not properly synchronized with the qt model, which can cause the qt wrapper to try reading (now) invalid rows. This was identified to be caused because of the way the scope results model works and how its qt wrapper deals with changesets. Basically we have a single DeeSharedModel that contains all the results for a particular search, that model gets split up by category id into multiple DeeFilterModels, which contain results for a specific category. Now the problem is that when there's a transaction (ie multiple row additions/removals) on the master shared model, the transaction is mirrored in the per-category filter models, but it introduces a problem cause we don't serialize the changes, which means that multiple filter models can have an active transaction at the same time, and when one the filter models synchronizes with the qt wrapper, a visibility change can cause a different model to be shown, and since that model is still processing the transaction, the qt wrapper won't be properly synchronized, and can ask for rows that are about to be removed. A solution to this problem is making sure that there's always just one active transaction on the filter models. To manage notifications about this bug go to: https://bugs.launchpad.net/dee/+bug/1255180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Invalid Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349921] Re: Empty! message needs to be marked for translation
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1349921 Title: Empty! message needs to be marked for translation Status in Ubuntu Translations: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: When an indicator has no content, there is an Empty! message shown that appears always in English. It seems to come from: http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Panel/Indicators/DefaultIndicatorPage.qml#L200 So to make it translatable it should simply be enclosed in i18n.tr() and the .pot template updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1349921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362017] Re: Focusing already-focused apps does not close indicators
** Changed in: unity8 (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: qtmir Status: Fix Committed = Fix Released ** Changed in: qtmir (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1362017 Title: Focusing already-focused apps does not close indicators Status in Qt integration with the Mir display server: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: Ubuntu 14.10 r203 1. Select Bluetooth Settings... from the Bluetooth indicator menu, or Cellular Settings... or Wi-Fi Settings... from the Network indicator menu, or Battery Settings... from the Battery indicator menu, or Sound Settings... from the sound indicator menu, etc. What should happen: The indicator menu closes and the relevant System Settings screen appears. What happens: Apparently nothing. The relevant settings screen actually does open, but you can't see it because the indicator menu stays open in front of it. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1362017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Albert Astals Cid (aacid) -- 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/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Confirmed Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371047] Re: Apps start but their splash screen is shown constantly in the right edge switcher
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1371047 Title: Apps start but their splash screen is shown constantly in the right edge switcher Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: image 245 1. Make sure none of the apps are running 2. start a new app from the launcher What happens: The app starts but its splash screen stays in the right edge switcher constantly. So basically we are getting two entries of each app in the switcher. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140910.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Thu Sep 18 15:25:34 2014 InstallationDate: Installed on 2014-09-18 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140918-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1371047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375491] Re: Store scope change the layout after opening the app preview
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Albert Astals Cid (aacid) -- 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/1375491 Title: Store scope change the layout after opening the app preview Status in “unity8” package in Ubuntu: Triaged Bug description: - Open the apps scope - Long tape on any app to get the preview - Hit the back button What to expect : The layout should stay the same What do i get : The layout change to the old way once you hit the back button ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140926-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Mon Sep 29 23:22:09 2014 InstallationDate: Installed on 2014-09-29 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1375491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365733] Re: unity8-dash keeps trying to start but never does
** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1365733 Title: unity8-dash keeps trying to start but never does Status in “unity8” package in Ubuntu: Incomplete Bug description: mako image 22 rtm. unity8 8.00+14.10.20140827.2-0ubuntu1 Sometimes when I reboot my phone, unity8-dash does not start. It just shows the starting animation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1365733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378384] Re: The pick mode title/options show untranslated
** Branch linked: lp:ubuntu/utopic-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1378384 Title: The pick mode title/options show untranslated Status in “gallery-app” package in Ubuntu: In Progress Bug description: Using rtm 87 in french locale - open settings-background - click on add an image - select gallery - the events/photos top-left menu and header titles show as untranslated, the same titles are displayed correctly translated in the non picker mode (confirming that the translations are available on disk) The same thing happens if gallery is already open before so it doesn't seem to be due to the content-picker invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1378384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234128] Re: Album still created when cancelling
** Branch linked: lp:ubuntu/utopic-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1234128 Title: Album still created when cancelling Status in “gallery-app” package in Ubuntu: In Progress Bug description: 1. Visit the albums page 2. Toolbar - Add 3. Cancel (by clicking outside of the album cover) 4. The album is visible on the albums page you are returned to Expected behaviour At 4, the album should not have been created. This also happens when creating an album directly from an image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1234128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378367] Re: The add to album screen should have an header by default
** Branch linked: lp:ubuntu/utopic-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1378367 Title: The add to album screen should have an header by default Status in “gallery-app” package in Ubuntu: In Progress Bug description: Using rtm 87 image - start gallery - go to the albums view - tap on one of the albums - you get a screen with a + in the middle, that screen has no indication of the album you are editing not a wait to come back if you selected the wrong album, if you click the + and then in the header add to album, you get back to the + screen but with an header this time bit more annoying... - if then you click the + symbol again, it brings you to the photos lists but with an empty header and no way to get out of the screen, you are stucked and needs to force close gallery and restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1378367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382462] [NEW] Desktop/windows painted incorrectly in dual monitor configuration
Public bug reported: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 17 11:02:50 2014 DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a3] NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:14a3] InstallationDate: Installed on 2012-03-21 (939 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Precision M4600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic root=UUID=37dce0bb-1e68-402b-8cba-78a6e04193de ro quiet splash reboot=pci acpi_backlight=vendor resume=UUID=4b9dc764-1ab9-4d9f-b661-1561bfe83648 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-17 (0 days ago) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.56+git20140920.77dce9a0-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20140925.23247e80-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1375491] Re: Store scope change the layout after opening the app preview
** Changed in: unity8 (Ubuntu) Assignee: Albert Astals Cid (aacid) = (unassigned) -- 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/1375491 Title: Store scope change the layout after opening the app preview Status in “unity8” package in Ubuntu: Triaged Bug description: - Open the apps scope - Long tape on any app to get the preview - Hit the back button What to expect : The layout should stay the same What do i get : The layout change to the old way once you hit the back button ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140926-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Mon Sep 29 23:22:09 2014 InstallationDate: Installed on 2014-09-29 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140929-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1375491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Changed in: unity8 (Ubuntu) Assignee: Albert Astals Cid (aacid) = (unassigned) -- 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/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Confirmed Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382027] Re: Tracks without embedded art do not download the art
Dropping importance, since this is not a general problem with online album art display, but only affects files with incorrect metadata. We've also got the option to improve matching on the server side, which is independent of what we ship on the client (although I don't agree that returning random incorrect art is better than no art). ** Changed in: unity-scope-mediascanner (Ubuntu) Importance: Critical = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1382027 Title: Tracks without embedded art do not download the art Status in “unity-scope-mediascanner” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Download http://people.canonical.com/~j-lallement/supertramp_1979_paris_cd1_School.mp3 2. Plug the device in and transfer the file above over MTP to the internal storage 3. Open the Music scope and locate the track (by searching or browsing) 4. Confirm that eventually the album art for the track is downloaded Expected result: After a period of time the album art is downloaded and appears as the cover art Actual result: The album art is never downloaded ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 12:09:07 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1382027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382466] [NEW] Greeter lock timeout can be reset by rebooting device
Public bug reported: 14.09-proposed image #113 STEPS: 1. Ensure passphrase is set. 2. Lock device. 3. At locked greeter, attempt to unlock using incorrect passphrase 7 times until 'Device Locked' notice is displayed. This displays a 5 minute timeout before device can be unlocked again. 4. Reboot device straight away. 5. At locked greeter attempt to unlock device again. EXPECTED: The lock period should persist after reboot so it is not possible to unlock the device until the timeout period has expired. ACTUAL: The lock period is removed, so it is possible to unlock (or attempt to unlock) device immediately after reboot. ** Affects: unity8 (Ubuntu) Importance: High Status: New ** Tags: rtm14 -- 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/1382466 Title: Greeter lock timeout can be reset by rebooting device Status in “unity8” package in Ubuntu: New Bug description: 14.09-proposed image #113 STEPS: 1. Ensure passphrase is set. 2. Lock device. 3. At locked greeter, attempt to unlock using incorrect passphrase 7 times until 'Device Locked' notice is displayed. This displays a 5 minute timeout before device can be unlocked again. 4. Reboot device straight away. 5. At locked greeter attempt to unlock device again. EXPECTED: The lock period should persist after reboot so it is not possible to unlock the device until the timeout period has expired. ACTUAL: The lock period is removed, so it is possible to unlock (or attempt to unlock) device immediately after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374016] Re: Wrong position of pop-us on gallery-app
This bug was fixed in the package gallery-app - 0.0.67+14.10.20141017-0ubuntu1 --- gallery-app (0.0.67+14.10.20141017-0ubuntu1) utopic; urgency=low [ Arthur Mello ] * Show header by default on an empty album (LP: #1378367) [ Ugo Riboni ] * Delete the new empty album if the album editor is closed by clicking outside of the album cover (LP: #1234128) * Adjust the popover position for the cover pattern editor. (LP: #1374016) [ Sebastien Bacher ] * Use a Binding to set the gettext domain, fixes the import mode translations (LP: #1378384) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 17 Oct 2014 07:41:18 + ** Changed in: gallery-app (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1374016 Title: Wrong position of pop-us on gallery-app Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: Fix Released Bug description: When we try to edit a photo or the cover of an album the pop-us with options are misplaced. They are not centralized on the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1374016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378384] Re: The pick mode title/options show untranslated
This bug was fixed in the package gallery-app - 0.0.67+14.10.20141017-0ubuntu1 --- gallery-app (0.0.67+14.10.20141017-0ubuntu1) utopic; urgency=low [ Arthur Mello ] * Show header by default on an empty album (LP: #1378367) [ Ugo Riboni ] * Delete the new empty album if the album editor is closed by clicking outside of the album cover (LP: #1234128) * Adjust the popover position for the cover pattern editor. (LP: #1374016) [ Sebastien Bacher ] * Use a Binding to set the gettext domain, fixes the import mode translations (LP: #1378384) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 17 Oct 2014 07:41:18 + ** Changed in: gallery-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1378384 Title: The pick mode title/options show untranslated Status in “gallery-app” package in Ubuntu: Fix Released Bug description: Using rtm 87 in french locale - open settings-background - click on add an image - select gallery - the events/photos top-left menu and header titles show as untranslated, the same titles are displayed correctly translated in the non picker mode (confirming that the translations are available on disk) The same thing happens if gallery is already open before so it doesn't seem to be due to the content-picker invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1378384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378367] Re: The add to album screen should have an header by default
This bug was fixed in the package gallery-app - 0.0.67+14.10.20141017-0ubuntu1 --- gallery-app (0.0.67+14.10.20141017-0ubuntu1) utopic; urgency=low [ Arthur Mello ] * Show header by default on an empty album (LP: #1378367) [ Ugo Riboni ] * Delete the new empty album if the album editor is closed by clicking outside of the album cover (LP: #1234128) * Adjust the popover position for the cover pattern editor. (LP: #1374016) [ Sebastien Bacher ] * Use a Binding to set the gettext domain, fixes the import mode translations (LP: #1378384) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 17 Oct 2014 07:41:18 + ** Changed in: gallery-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1378367 Title: The add to album screen should have an header by default Status in “gallery-app” package in Ubuntu: Fix Released Bug description: Using rtm 87 image - start gallery - go to the albums view - tap on one of the albums - you get a screen with a + in the middle, that screen has no indication of the album you are editing not a wait to come back if you selected the wrong album, if you click the + and then in the header add to album, you get back to the + screen but with an header this time bit more annoying... - if then you click the + symbol again, it brings you to the photos lists but with an empty header and no way to get out of the screen, you are stucked and needs to force close gallery and restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1378367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234128] Re: Album still created when cancelling
This bug was fixed in the package gallery-app - 0.0.67+14.10.20141017-0ubuntu1 --- gallery-app (0.0.67+14.10.20141017-0ubuntu1) utopic; urgency=low [ Arthur Mello ] * Show header by default on an empty album (LP: #1378367) [ Ugo Riboni ] * Delete the new empty album if the album editor is closed by clicking outside of the album cover (LP: #1234128) * Adjust the popover position for the cover pattern editor. (LP: #1374016) [ Sebastien Bacher ] * Use a Binding to set the gettext domain, fixes the import mode translations (LP: #1378384) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 17 Oct 2014 07:41:18 + ** Changed in: gallery-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1234128 Title: Album still created when cancelling Status in “gallery-app” package in Ubuntu: Fix Released Bug description: 1. Visit the albums page 2. Toolbar - Add 3. Cancel (by clicking outside of the album cover) 4. The album is visible on the albums page you are returned to Expected behaviour At 4, the album should not have been created. This also happens when creating an album directly from an image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1234128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
Eric Lambart, did you close the app by right clicking on the launcher icon and choosing Exit from the menu, before trying to launch it? To find the app, you have two options: 1. or write software update (without the final r) in the dash (Super key OR Super+A, not Super-R). 2. choose System details (I dont know the exact translation, but should be the first menu item) from the gear menu in the top right corner. Then click the button in bottom right corner, if updates are available. About the crashes, it's off topic for this bug, so please report it as a separate bug report. However, since I had similar problems, I can say you that it's probably a problem with the video drivers. Here's a couple of references that helped me to solve them: http://askubuntu.com/a/507299/11223 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329689 -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “update-manager” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Fix Released Status in “update-manager” source package in Precise: Confirmed Status in “unity” source package in Quantal: Fix Released Status in “update-manager” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
** Attachment added: After starting a session and opening a few windows https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238845/+files/DSC_0029.JPG -- 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/1382462 Title: Desktop/windows painted incorrectly in dual monitor configuration Status in “xorg” package in Ubuntu: New Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, loggin in and then connecting. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 17 11:02:50 2014 DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a3] NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:14a3] InstallationDate: Installed on 2012-03-21
[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
** Attachment added: Windows, which normally were placed in one of the screens, now are placed partially on both https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238846/+files/DSC_0030.JPG -- 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/1382462 Title: Desktop/windows painted incorrectly in dual monitor configuration Status in “xorg” package in Ubuntu: New Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, loggin in and then connecting. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 17 11:02:50 2014 DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a3] NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:14a3]
[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
** Attachment added: The same windows immediately after undocking the laptop, see how aspect ratio on the builtin screen changed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4238849/+files/DSC_0031.JPG -- 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/1382462 Title: Desktop/windows painted incorrectly in dual monitor configuration Status in “xorg” package in Ubuntu: New Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, loggin in and then connecting. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 17 11:02:50 2014 DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04a3] NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device
[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
** Description changed: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. - I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. - I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. + If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. + The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, loggin in and then connecting. + + BTW: I'm using a docking station - not sure if it is related - if you + think it might be, I can try with connecting the monitor directly. + + + I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. + I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 - GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 + GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu7 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 17 11:02:50 2014 DistUpgraded: 2014-10-17 10:20:38,145 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:04a3] - NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:14a3] + Intel Corporation 2nd Generation Core
[Touch-packages] [Bug 1382033] Re: [SIM PIN] 'Incorrect PIN' warning is not cleared from display for SIM2 PIN entry
** Changed in: indicator-network (Ubuntu) Importance: Undecided = High ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- 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/1382033 Title: [SIM PIN] 'Incorrect PIN' warning is not cleared from display for SIM2 PIN entry Status in “indicator-network” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: 14.09-proposed image #109 STEPS: 1. Ensure 2 SIMs inserted into device with PIN lock enabled 2. Boot up 3. At SIM1 PIN entry insert incorrect PIN once 4. Insert correct SIM1 PIN on second attempt (do this reasonably quickly before the warning disappears) EXPECTED RESULT: SIM2 PIN entry should display with no warning message ACTUAL RESULT: The incorrect PIN warning is still displayed for SIM2 PIN entry, when no PIN has been entered for SIM2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382129] Re: [SIM PIN] Retry count is not displayed following a reboot
** Changed in: indicator-network (Ubuntu) Importance: Undecided = High ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- 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/1382129 Title: [SIM PIN] Retry count is not displayed following a reboot Status in “indicator-network” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: 14.09-proposed image #109 STEPS: 1. Ensure at least 1 SIM inserted with PIN lock 2. Boot up 3. At SIM PIN entry, enter incorrect PIN for fist attempt. The number of retries left is displayed to user. 4. Reboot phone and wait for SIM PIN entry dialog EXPECTED RESULT: After the phone has rebooted the SIM PIN entry dialog should still display how many retries the user has left before the SIM is blocked. ACTUAL RESULT: After a reboot the SIM PIN entry dialog does not show how many retry attempts the user has left before the SIM is blocked. If the user inputs 2 incorrect PINs there is a dialog warning the user that the 3rd will be the last attempt before the SIM is blocked. However if the user reboots at this point, there is no warning to the user to indicate that this is the 3rd and final attempt when they come to enter their PIN. Comparing to Android, this will display the number of retries left after a reboot has occured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle
Righto, uploaded to the queue. It'll be held for review, stand by. ** Description changed: + [ Description ] + + Cannot connect to servers with SSLv3 disabled, with a message Cannot + communicate securely with peer: no common encryption algorithm(s). + + [ QA ] + + Try to connect to a server with SSLv3 disabled and see if you can + retrieve mail (and that it errors before the update). + + [ Regression potential ] + + Might enable a different set of SSL/TLS versions, check with different + servers. + + [ Original report ] + Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382133 Title: Issue with servers with SSLv3 disabled due to Poodle Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Precise: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: [ Description ] Cannot connect to servers with SSLv3 disabled, with a message Cannot communicate securely with peer: no common encryption algorithm(s). [ QA ] Try to connect to a server with SSLv3 disabled and see if you can retrieve mail (and that it errors before the update). [ Regression potential ] Might enable a different set of SSL/TLS versions, check with different servers. [ Original report ] Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle
** Branch linked: lp:~ubuntu-desktop/evolution-data-server/ubuntu-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382133 Title: Issue with servers with SSLv3 disabled due to Poodle Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Precise: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: [ Description ] Cannot connect to servers with SSLv3 disabled, with a message Cannot communicate securely with peer: no common encryption algorithm(s). [ QA ] Try to connect to a server with SSLv3 disabled and see if you can retrieve mail (and that it errors before the update). [ Regression potential ] Might enable a different set of SSL/TLS versions, check with different servers. [ Original report ] Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382470] Re: [Dash] Aligment of typography is wrong
Just to make clear, this is only for the text or for the image too? -- 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/1382470 Title: [Dash] Aligment of typography is wrong Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: New Bug description: There should be 2 grid units space (margin) between the typography and the border. See attached screenshots for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382475] Re: [Dash] Margins typography
You are aware these are different elements right? One is a category label and the other is the department chooser. -- 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/1382475 Title: [Dash] Margins typography Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: New Bug description: Typography should be aligned, all at the same distance from the edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382501] [NEW] Android GPS HAL should only be started/stopped at most once
Public bug reported: Some Android GPS HAL implementations seem to have an issue with multiple start/stop attempts if they are already running/stopped. The subsequent behavior is undefined and results in bugs that are difficult to track/identify/trace back to the misbehaving HAL. With that, the gps provider implementation should ensure correct behavior. ** Affects: location-service (Ubuntu) Importance: Critical Assignee: Thomas Voß (thomas-voss) Status: In Progress ** Tags: rtm14 ** Branch linked: lp:~thomas-voss/location-service/fix-gps-integration- and-allow-for-decorating-provider-names -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1382501 Title: Android GPS HAL should only be started/stopped at most once Status in “location-service” package in Ubuntu: In Progress Bug description: Some Android GPS HAL implementations seem to have an issue with multiple start/stop attempts if they are already running/stopped. The subsequent behavior is undefined and results in bugs that are difficult to track/identify/trace back to the misbehaving HAL. With that, the gps provider implementation should ensure correct behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1382501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382510] [NEW] systemd-logind upstart script is flawed
Public bug reported: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1382510 Title: systemd-logind upstart script is flawed Status in “systemd” package in Ubuntu: New Bug description: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372187] Re: Desktop console-kit permissions (e.g shutdown, network, users) broken for all accounts after upgrade to 14.10
Please check if you are affected by bug 1295521, i. e. whether the root cause is that you have both the i386 and amd64 version of libpam-systemd installed. If so, this is a likely duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1372187 Title: Desktop console-kit permissions (e.g shutdown, network, users) broken for all accounts after upgrade to 14.10 Status in “consolekit” package in Ubuntu: Incomplete Bug description: 1. System worked without any problems under 14.04 2. Upgrade to 14.10 3. Upgrade went without any problems 4. Notice that standby has disappeared from the gears menu 5. notice that I cannot disconnect or change the network connection (exact error is: (32) Not authorized to control networking.) 6. I can't see, change or unlock setting under Settings User accounts 7. Running dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop from the terminal results in the error: Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized 8. Running sudo pam-auth-update --force doesn't solve any errors 9. Creating a new user account (sudo adduser) and switching to the account results in the same permission problems. Sudo works as expected so I can help to further debug this problem and provide relevant information. Unfortunately I have very limited experience with ConsoleKit and PAM so I hope I have reported this to the right package. If someone could point me in the right direction (wiki, man page, tutorial) I would be more than happy to see if I can see what went wrong and if I can debug this myself. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: consolekit 0.4.6-5 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 21 23:55:41 2014 InstallationDate: Installed on 2013-04-21 (518 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130421) SourcePackage: consolekit UpgradeStatus: Upgraded to utopic on 2014-09-14 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1372187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382039] Re: Apps scope empty on boot
The other one is more about location data being missing - leads to nearby scope returning no results. -- 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/1382039 Title: Apps scope empty on boot Status in “unity-scopes-shell” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1382039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382039] Re: Apps scope empty on boot
I don't think this is the same underlying bug. ** This bug is no longer a duplicate of bug 1374481 Nearby and News scope do not load on reboot -- 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/1382039 Title: Apps scope empty on boot Status in “unity-scopes-shell” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1382039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382510] Re: systemd-logind upstart script is flawed
Argh, many thanks for pointing this out! What an obvious and silly error. This does not affect 14.10 as the upstart job for logind is gone entirely in favor of D-BUS activation. But this must be fixed for 14.04. ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New = Fix Released ** Changed in: systemd (Ubuntu Trusty) Status: New = Triaged ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided = High ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: systemd (Ubuntu Trusty) Milestone: None = ubuntu-14.04.2 ** Summary changed: - systemd-logind upstart script is flawed + systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch -- 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/1382510 Title: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Triaged Bug description: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Julien et al, please have a look at bug 1382510. This is currently the most obvious case of logind breakage with libpam-systemd for both i386 and amd64 installed. (I. e. this bug is very likely a duplicate of 1382510) -- 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/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break Status in Light Display Manager: Invalid Status in “systemd” package in Ubuntu: Incomplete Bug description: Hi, After I upgraded to Ubuntu Trusty, I've seen that it is no longer possible to suspend/shutdown/restart my system from the GUI. In other words within lightdm buttons to do so are grayed out, and within KDE it is the same. I had the same bug in Saucy beta and the culprit was the login component, and after its upgrade the issue was fixed. My system : Kubuntu 14.04 LTS AMD64 AMD Phenom 9850 8 GB RAM NVidia GeForce 660 Ti w/ NVidia 331 driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: login 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 21 07:21:52 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382517] [NEW] SSL subject to POODLE vulnerability
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: It seems that Evolution 2.3.2 uses SSLv3 and is therefore subject to the recently announced POODLE vulnerability. (As a result I can no longer access my IMAP server at fastmail.fm, because they have turned off the SSLv3 fallback). Evolution 2.3.2 is the latest version from the Ubuntu 12.04 repositories. I use Ubuntu 12.04 on 4 computers, so all are affected by this. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- SSL subject to POODLE vulnerability https://bugs.launchpad.net/bugs/1382517 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia
** Changed in: tzdata (Ubuntu) Assignee: (unassigned) = Adam Conrad (adconrad) ** Changed in: tzdata (Ubuntu Trusty) Assignee: (unassigned) = Adam Conrad (adconrad) ** Changed in: tzdata (Ubuntu Precise) Assignee: (unassigned) = Adam Conrad (adconrad) ** Also affects: tzdata (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu Lucid) Status: New = Confirmed ** Changed in: tzdata (Ubuntu Lucid) Importance: Undecided = Critical ** Changed in: tzdata (Ubuntu Lucid) Assignee: (unassigned) = Adam Conrad (adconrad) ** Changed in: tzdata (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: Fix Released Status in “tzdata” source package in Lucid: Confirmed Status in “tzdata” source package in Precise: Confirmed Status in “tzdata” source package in Trusty: Confirmed Status in “tzdata” package in Debian: Fix Released Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382517] Re: SSL subject to POODLE vulnerability
*** This bug is a duplicate of bug 1382133 *** https://bugs.launchpad.net/bugs/1382133 ** Package changed: evolution (Ubuntu) = evolution-data-server (Ubuntu) ** This bug has been marked a duplicate of bug 1382133 Issue with servers with SSLv3 disabled due to Poodle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382517 Title: SSL subject to POODLE vulnerability Status in “evolution-data-server” package in Ubuntu: New Bug description: It seems that Evolution 2.3.2 uses SSLv3 and is therefore subject to the recently announced POODLE vulnerability. (As a result I can no longer access my IMAP server at fastmail.fm, because they have turned off the SSLv3 fallback). Evolution 2.3.2 is the latest version from the Ubuntu 12.04 repositories. I use Ubuntu 12.04 on 4 computers, so all are affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336953] Re: [qtcomp] main stage blank when only sidestage app is launched
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1336953 Title: [qtcomp] main stage blank when only sidestage app is launched Status in “unity8” package in Ubuntu: Fix Released Bug description: using the Qtcomp ppa on the latest tablet images results in the main stage area being blank/black instead of seeing the Dash upon launching a side stage application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1336953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341770] Re: [QtComp] swipe away app while loading, missing in running apps section of apps scope
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1341770 Title: [QtComp] swipe away app while loading, missing in running apps section of apps scope Status in “unity8” package in Ubuntu: Fix Released Bug description: image #126 w/ silo 6(qtcomp) if i launch an application, but swipe back to the dash before its loaded, it will not have a placeholder in the running application section of the application scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1341770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344205] Re: French translation for Please enter SIM PIN is too long
** Changed in: unity8 (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1344205 Title: French translation for Please enter SIM PIN is too long Status in “unity8” package in Ubuntu: Fix Released Bug description: Please see the attached screenshot (taken on a Nexus 4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1344205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1181332] Re: Sidestage brought in when focusing mainstage app (even when there's no sidestage apps)
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1181332 Title: Sidestage brought in when focusing mainstage app (even when there's no sidestage apps) Status in Touch Preview Images: Confirmed Status in “unity8” package in Ubuntu: Fix Released Bug description: HARDWARE=manta JENKINS_BUILD=125 Steps to reproduce: - Open facebook webapp - Close facebook webapp - Playback a video Expected result: - Video seen without artifacts Actual result: - Artifacts from sidestage frames (as seen in the attached screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1181332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382133 Title: Issue with servers with SSLv3 disabled due to Poodle Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Precise: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: [ Description ] Cannot connect to servers with SSLv3 disabled, with a message Cannot communicate securely with peer: no common encryption algorithm(s). [ QA ] Try to connect to a server with SSLv3 disabled and see if you can retrieve mail (and that it errors before the update). [ Regression potential ] Might enable a different set of SSL/TLS versions, check with different servers. [ Original report ] Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name
** Changed in: openstack-manuals Status: Invalid = Confirmed ** Changed in: openstack-manuals Importance: Undecided = Critical ** Changed in: openstack-manuals Milestone: None = juno ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1362521 Title: juno: not a valid cloud-archive name Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Manuals: Confirmed Status in “software-properties” package in Ubuntu: Confirmed Bug description: While installing Openstack on Ubuntu 14.04 (LTS) getting the below error. I am following the instructions as per the document @ http://docs.openstack.org/trunk/install-guide/install/apt/openstack- install-guide-apt-trunk.pdf # add-apt-repository cloud-archive:juno 'juno': not a valid cloud-archive name. Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 'tools-proposed'] Is the document still in development? let me know what does this error mean and how to proceed further. Page 22 : URL : http://docs.openstack.org/trunk/install- guide/install/apt/openstack-install-guide-apt-trunk.pdf Regards, Satish To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1362521 Title: juno: not a valid cloud-archive name Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Manuals: Confirmed Status in “software-properties” package in Ubuntu: Confirmed Bug description: While installing Openstack on Ubuntu 14.04 (LTS) getting the below error. I am following the instructions as per the document @ http://docs.openstack.org/trunk/install-guide/install/apt/openstack- install-guide-apt-trunk.pdf # add-apt-repository cloud-archive:juno 'juno': not a valid cloud-archive name. Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 'tools-proposed'] Is the document still in development? let me know what does this error mean and how to proceed further. Page 22 : URL : http://docs.openstack.org/trunk/install- guide/install/apt/openstack-install-guide-apt-trunk.pdf Regards, Satish To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373319] Re: Indicator sound menu always showing media player in running state
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1373319 Title: Indicator sound menu always showing media player in running state Status in Media Hub: New Status in “unity8” package in Ubuntu: Fix Released Bug description: Even if nothing is playing or loaded into a music player, the player still shows in running state. Unity8 should be using the state in conjunction with the running flag to determine if it should display track info. Partial output of actions shows running=true dbus-send --print-reply --session --dest=com.canonical.indicator.sound /com/canonical/indicator/sound org.gtk.Actions.DescribeAll dict entry( string mediaplayer-app.desktop struct { boolean false signature array [ variant array [ dict entry( string running variantboolean true ) dict entry( string state variantstring Stopped ) ] ] } ) To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1373319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name
It looks like Ubuntu is not ready for Juno. You could try their staging repository: apt-add-repository ppa:ubuntu-cloud-archive/juno-staging Note: this is not an OpenStack documentation bug - it's related to Ubuntu packaging. ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1362521 Title: juno: not a valid cloud-archive name Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Manuals: Confirmed Status in “software-properties” package in Ubuntu: Confirmed Bug description: While installing Openstack on Ubuntu 14.04 (LTS) getting the below error. I am following the instructions as per the document @ http://docs.openstack.org/trunk/install-guide/install/apt/openstack- install-guide-apt-trunk.pdf # add-apt-repository cloud-archive:juno 'juno': not a valid cloud-archive name. Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 'tools-proposed'] Is the document still in development? let me know what does this error mean and how to proceed further. Page 22 : URL : http://docs.openstack.org/trunk/install- guide/install/apt/openstack-install-guide-apt-trunk.pdf Regards, Satish To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365530] Re: Time in indicator out of sync on resume from suspend
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1365530 Title: Time in indicator out of sync on resume from suspend Status in “unity8” package in Ubuntu: Fix Released Bug description: mako: 221 krillin: 16 last known good build: ? Similar defect: bug 1328646 When the device is resumed by pressing the power button and the device is not connected over USB to any power source the clock on the greeter and the date/time indicator is out of sync. TEST CASE 1. Unplug the device from its USB cable 2. Press the power button to switch to suspend mode 3. Wait a moment (several minutes) 4. Press the power button again to resume the device 5. Compare the time on the greeter and indicator with the time on another system or with the clock app. EXPECTED RESULT Clocks are in sync ACTUAL RESULT Time on the device is behind by several minutes. The time on the clock app is always correct. The screenshot attached shows that time in the indicator is 13:48 and 13:49 in the clock app (correct time) after waiting less than 10 minutes. The time difference can be several minutes. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-datetime 13.10.0+14.10.20140819-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Thu Sep 4 13:57:35 2014 InstallationDate: Installed on 2014-09-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140904-020205) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1365530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378648] Re: ISST-KVM:R2-0:No login prompt displayed on FB console after Ubuntu 14.10 installation
This bug was fixed in the package linux - 3.16.0-23.30 --- linux (3.16.0-23.30) utopic; urgency=low [ Andy Whitcroft ] * Release Tracking Bug - LP: #1381927 * [Config] CONFIG_DRM_BOCHS=n - LP: #1378648 [ Paolo Pisati ] * [Config] armhf: disable JUMP_LABEL - LP: #1378856 -- Andy Whitcroft a...@canonical.com Thu, 16 Oct 2014 10:09:49 +0200 ** Changed in: linux (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1378648 Title: ISST-KVM:R2-0:No login prompt displayed on FB console after Ubuntu 14.10 installation Status in “kmod” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: == Comment: #0 - Richard M. Scheller rsche...@us.ibm.com - 2014-10-06 13:42:47 == ---Problem Description--- After installing Ubuntu 14.10 (3.16.0-20-generic kernel) using a qemu virtual VGA framebuffer console and rebooting the installed system, there is no login prompt displayed on the fb console. This is a regression from 14.04.1, where the login prompt is displayed on the console. (Note that this is *not* related to IBM bug#113591/LauchPad bug#1346851, which has been fixed in the latest daily builds.) The OS installation completes without any errors, then the guest reboots from the installed virtual disk. The guest comes up without any problems (it is possible to ssh into the guest) but no login prompt is displayed on the fb console. Machine Type = 8247-22L (PowerKVM guest) ---Steps to Reproduce--- Configure guest with framebuffer console and USB keyboard/mouse and install through that interface. ---uname output--- Linux netg7 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Debugger--- A debugger is not configured Install ISO Information: 2014-10-06 daily build (network install) Install disk info: n/a Install method: TFTP boot of kernel/initrd from local server, then direct download from ports.ubuntu.com == Comment: #4 - Richard M. Scheller rsche...@us.ibm.com - 2014-10-06 14:34:43 == I should also point out that there is no login prompt displayed on the virtual serial console (/dev/hvc0) either. Here is a list of the getty processes which are started on reboot: root@netg7:~# ps -ef|grep getty|grep -v grep root 869 1 0 12:23 tty4 00:00:00 /sbin/getty -8 38400 tty4 root 871 1 0 12:23 tty5 00:00:00 /sbin/getty -8 38400 tty5 root 874 1 0 12:23 tty2 00:00:00 /sbin/getty -8 38400 tty2 root 875 1 0 12:23 tty3 00:00:00 /sbin/getty -8 38400 tty3 root 881 1 0 12:23 tty6 00:00:00 /sbin/getty -8 38400 tty6 root 1026 1 0 12:23 tty1 00:00:00 /sbin/getty -8 38400 tty1 root@netg7:~# == Comment: #10 - Richard M. Scheller rsche...@us.ibm.com - 2014-10-06 17:31:23 == OK, I think I'm getting closer to the root cause. I'm pretty sure it's the framebuffer device. These are the related kernel messages from Ubuntu 14.04.1 (netg9): root@netg9:~# dmesg|egrep -i 'buffer|offb|vga' [0.099978] vgaarb: device added: PCI::00:05.0,decodes=io+mem,owns=io+mem,locks=none [0.099979] vgaarb: loaded [0.099980] vgaarb: bridge control possible :00:05.0 [0.581438] Using unsupported 800x600 vga at 100a000, depth=32, pitch=3200 [0.583419] Console: switching to colour frame buffer device 100x37 [0.584748] fb0: Open Firmware frame buffer device on /pci@8002000/vga@5 root@netg9:~# And here are the related messages from 14.10 (netg7): root@netg7:~# dmesg|egrep -i 'buffer|offb|vga' [0.136665] vgaarb: device added: PCI::00:05.0,decodes=io+mem,owns=io+mem,locks=none [0.136701] vgaarb: loaded [0.136733] vgaarb: bridge control possible :00:05.0 [0.580147] Using unsupported 800x600 vga at 100a000, depth=32, pitch=3200 [0.583407] Console: switching to colour frame buffer device 100x37 [0.585721] fb0: Open Firmware frame buffer device on /pci@8002000/vga@5 [4.264808] fb: switching to bochsdrmfb from OFfb vga [4.266985] [drm:bochs_hw_init] *ERROR* Cannot request framebuffer root@netg7:~# Everything looks pretty much the same on both guests until 14.10 tries to switch to the bochsdrmfb device. I'm going to assume that device only works on x86. On 14.10, the kernel has a new driver that doesn't exist on 14.04: 14.10: root@netg7:~# grep -i bochs /boot/config-3.16.0-20-generic CONFIG_DRM_BOCHS=m root@netg7:~# 14.04.1: root@netg9:~# grep -i bochs /boot/config-3.13.0-36-generic root@netg9:~# == Comment: #11 - Richard M. Scheller rsche...@us.ibm.com - 2014-10-06 18:28:25 == I disabled the bochs
[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia
Uploads on the way and being pushed through with critical urgency, sorry for the delay. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: Fix Released Status in “tzdata” source package in Lucid: Confirmed Status in “tzdata” source package in Precise: Confirmed Status in “tzdata” source package in Trusty: Confirmed Status in “tzdata” package in Debian: Fix Released Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1191934] Re: orientation wrong in playback for recorded videos
The core issue is in gstreamer, so I filed an upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=738681 ** Bug watch added: GNOME Bug Tracker #738681 https://bugzilla.gnome.org/show_bug.cgi?id=738681 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1191934 Title: orientation wrong in playback for recorded videos Status in Media Hub: Fix Committed Status in QT Ubuntu Media: New Status in Thumbnail generator for all kinds of files: New Status in “qtubuntu-camera” package in Ubuntu: Fix Released Status in “media-hub” package in Ubuntu RTM: Fix Committed Status in “qtvideo-node” package in Ubuntu RTM: Fix Committed Bug description: saucy-15 + updates Galaxy Nexus camera-app 2.9.1daily13.06.17-0ubuntu1 gallery-app 0.0.67daily13.06.17-0ubuntu1 If you record a video in portrait orientation in the camera, it should be played back in same orientation in gallery but it is not. It's incorrectly displayed in landscape mode rotated 90 degrees to the left. See attached images. To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1191934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 940924] Re: Keyboard Layout German (qwerty) missing since 12.04
** Tags added: kubuntu -- 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/940924 Title: Keyboard Layout German (qwerty) missing since 12.04 Status in “xkeyboard-config” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Debian: New Bug description: I have updated to 12.04 today. Now I am missing the possibility to choose German (qwerty) within the Keyboard Layout dialog. This has been my preferred keyboard layout for a lot of years now. I couldn't find any traces of that layout within /usr/share/X11/xkb/symbols/de. In 11.10 this file contains the relevant section. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 [modified: usr/share/X11/xkb/symbols/de] ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Sat Feb 25 14:03:27 2012 Dependencies: DistUpgraded: Log time: 2012-02-25 11:24:09.168227 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. UX31E PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=1506efae-1012-4450-b164-b1d238bd74e2 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to precise on 2012-02-25 (0 days ago) dmi.bios.date: 10/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.207:bd10/25/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/940924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 940924] Re: Keyboard Layout German (qwerty) missing since 12.04
Seriously, guys, no German keyboard anymore? I can confirm this issue in Trusty, I only see German, Swiss in the list. This bug should be raised in importance, as it leaves out a complete country! -- 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/940924 Title: Keyboard Layout German (qwerty) missing since 12.04 Status in “xkeyboard-config” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Debian: New Bug description: I have updated to 12.04 today. Now I am missing the possibility to choose German (qwerty) within the Keyboard Layout dialog. This has been my preferred keyboard layout for a lot of years now. I couldn't find any traces of that layout within /usr/share/X11/xkb/symbols/de. In 11.10 this file contains the relevant section. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 [modified: usr/share/X11/xkb/symbols/de] ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Sat Feb 25 14:03:27 2012 Dependencies: DistUpgraded: Log time: 2012-02-25 11:24:09.168227 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. UX31E PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=1506efae-1012-4450-b164-b1d238bd74e2 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to precise on 2012-02-25 (0 days ago) dmi.bios.date: 10/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.207:bd10/25/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/940924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name
.. but the updated software-properties package is not available in Trusty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1362521 Title: juno: not a valid cloud-archive name Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Manuals: Confirmed Status in “software-properties” package in Ubuntu: Confirmed Bug description: While installing Openstack on Ubuntu 14.04 (LTS) getting the below error. I am following the instructions as per the document @ http://docs.openstack.org/trunk/install-guide/install/apt/openstack- install-guide-apt-trunk.pdf # add-apt-repository cloud-archive:juno 'juno': not a valid cloud-archive name. Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 'tools-proposed'] Is the document still in development? let me know what does this error mean and how to proceed further. Page 22 : URL : http://docs.openstack.org/trunk/install- guide/install/apt/openstack-install-guide-apt-trunk.pdf Regards, Satish To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 940924] Re: Keyboard Layout German (qwerty) missing since 12.04
Setting bug importance to High, as it makes Ubuntu literally unusable by all people using a German keyboard. This is a very serious regression in xkb-data, and needs to be fixed ASAP ** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided = High -- 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/940924 Title: Keyboard Layout German (qwerty) missing since 12.04 Status in “xkeyboard-config” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Debian: New Bug description: I have updated to 12.04 today. Now I am missing the possibility to choose German (qwerty) within the Keyboard Layout dialog. This has been my preferred keyboard layout for a lot of years now. I couldn't find any traces of that layout within /usr/share/X11/xkb/symbols/de. In 11.10 this file contains the relevant section. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 [modified: usr/share/X11/xkb/symbols/de] ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Sat Feb 25 14:03:27 2012 Dependencies: DistUpgraded: Log time: 2012-02-25 11:24:09.168227 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. UX31E PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=1506efae-1012-4450-b164-b1d238bd74e2 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to precise on 2012-02-25 (0 days ago) dmi.bios.date: 10/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.207:bd10/25/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/940924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
This is not a bug in indicator-network. The same issue can be triggered from the command line with this: dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill org.freedesktop.URfkill.FlightMode boolean:true -- 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/1382283 Title: wifi toggle interrupts sound playback Status in “indicator-network” package in Ubuntu: Confirmed Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia
** Branch linked: lp:ubuntu/lucid-proposed/tzdata ** Branch linked: lp:ubuntu/precise-proposed/tzdata ** Branch linked: lp:ubuntu/trusty-proposed/tzdata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: Fix Released Status in “tzdata” source package in Lucid: Confirmed Status in “tzdata” source package in Precise: Confirmed Status in “tzdata” source package in Trusty: Confirmed Status in “tzdata” package in Debian: Fix Released Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 940924] Re: Keyboard Layout German (qwerty) missing since 12.04
** Changed in: xkeyboard-config (Ubuntu) Milestone: None = ubuntu-14.10 -- 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/940924 Title: Keyboard Layout German (qwerty) missing since 12.04 Status in “xkeyboard-config” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Debian: New Bug description: I have updated to 12.04 today. Now I am missing the possibility to choose German (qwerty) within the Keyboard Layout dialog. This has been my preferred keyboard layout for a lot of years now. I couldn't find any traces of that layout within /usr/share/X11/xkb/symbols/de. In 11.10 this file contains the relevant section. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xkb-data 2.5-1ubuntu1 [modified: usr/share/X11/xkb/symbols/de] ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Sat Feb 25 14:03:27 2012 Dependencies: DistUpgraded: Log time: 2012-02-25 11:24:09.168227 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. UX31E PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=1506efae-1012-4450-b164-b1d238bd74e2 ro quiet splash vt.handoff=7 SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to precise on 2012-02-25 (0 days ago) dmi.bios.date: 10/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.207:bd10/25/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/940924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
Yes, this clearly is a lower level issue, and I will reassign this bug to a more appropriate component once I figure out what that component should be. ** Changed in: indicator-network (Ubuntu) Status: Confirmed = Incomplete -- 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/1382283 Title: wifi toggle interrupts sound playback Status in “indicator-network” package in Ubuntu: Incomplete Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352876] Re: apt-get update crashes
*** This bug is a duplicate of bug 1352504 *** https://bugs.launchpad.net/bugs/1352504 I confirm the bug, and the nscd temp workaround. Same version. Wow, how'd you figure out that stopping nscd would help? For me, apt-get update/upgrade after stopping nscd fixes it permanently. There must have been a libc patch between when this was filed and now. -- 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/1352876 Title: apt-get update crashes Status in “apt” package in Ubuntu: Confirmed Bug description: This is on Ubuntu 10.04 After the last uprade, apt-get crashes with: root@zoo:~# apt-get update 0% [Working]*** glibc detected *** /usr/lib/apt/methods/http: munmap_chunk(): invalid pointer: 0x7f2ee7e963f0 *** === Backtrace: = /lib/libc.so.6(+0x78cc6)[0x7f2ee6f6] /lib/libc.so.6(+0x125ec9)[0x7f2ee7079ec9] /lib/libc.so.6(+0x12628b)[0x7f2ee707a28b] /lib/libc.so.6(getservbyname_r+0x183)[0x7f2ee705cde3] /lib/libc.so.6(+0xb9ff2)[0x7f2ee700dff2] /lib/libc.so.6(+0xbad50)[0x7f2ee700ed50] /lib/libc.so.6(getaddrinfo+0x162)[0x7f2ee70118f2] /usr/lib/apt/methods/http[0x40b337] /usr/lib/apt/methods/http[0x406748] /usr/lib/apt/methods/http[0x407d39] /usr/lib/apt/methods/http[0x40a0cb] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f2ee6f72cad] /usr/lib/apt/methods/http[0x4041c9] === Memory map: 0040-0040e000 r-xp 08:01 656796 /usr/lib/apt/methods/http 0060d000-0060e000 r--p d000 08:01 656796 /usr/lib/apt/methods/http 0060e000-0060f000 rw-p e000 08:01 656796 /usr/lib/apt/methods/http 0060f000-0063 rw-p 00:00 0 [heap] 7f2ee6b4d000-7f2ee6b4f000 r-xp 08:01 396191 /lib/libdl-2.11.1.so 7f2ee6b4f000-7f2ee6d4f000 ---p 2000 08:01 396191 /lib/libdl-2.11.1.so 7f2ee6d4f000-7f2ee6d5 r--p 2000 08:01 396191 /lib/libdl-2.11.1.so 7f2ee6d5-7f2ee6d51000 rw-p 3000 08:01 396191 /lib/libdl-2.11.1.so 7f2ee6d51000-7f2ee6d53000 r-xp 08:01 396199 /lib/libutil-2.11.1.so 7f2ee6d53000-7f2ee6f52000 ---p 2000 08:01 396199 /lib/libutil-2.11.1.so 7f2ee6f52000-7f2ee6f53000 r--p 1000 08:01 396199 /lib/libutil-2.11.1.so 7f2ee6f53000-7f2ee6f54000 rw-p 2000 08:01 396199 /lib/libutil-2.11.1.so 7f2ee6f54000-7f2ee70d3000 r-xp 08:01 396200 /lib/libc-2.11.1.so 7f2ee70d3000-7f2ee72d3000 ---p 0017f000 08:01 396200 /lib/libc-2.11.1.so 7f2ee72d3000-7f2ee72d7000 r--p 0017f000 08:01 396200 /lib/libc-2.11.1.so 7f2ee72d7000-7f2ee72d8000 rw-p 00183000 08:01 396200 /lib/libc-2.11.1.so 7f2ee72d8000-7f2ee72dd000 rw-p 00:00 0 7f2ee72dd000-7f2ee72f3000 r-xp 08:01 392455 /lib/libgcc_s.so.1 7f2ee72f3000-7f2ee74f2000 ---p 00016000 08:01 392455 /lib/libgcc_s.so.1 7f2ee74f2000-7f2ee74f3000 r--p 00015000 08:01 392455 /lib/libgcc_s.so.1 7f2ee74f3000-7f2ee74f4000 rw-p 00016000 08:01 392455 /lib/libgcc_s.so.1 7f2ee74f4000-7f2ee7576000 r-xp 08:01 396194 /lib/libm-2.11.1.so 7f2ee7576000-7f2ee7775000 ---p 00082000 08:01 396194 /lib/libm-2.11.1.so 7f2ee7775000-7f2ee7776000 r--p 00081000 08:01 396194 /lib/libm-2.11.1.so 7f2ee7776000-7f2ee000 rw-p 00082000 08:01 396194 /lib/libm-2.11.1.so 7f2ee000-7f2ee786d000 r-xp 08:01 655632 /usr/lib/libstdc++.so.6.0.13 7f2ee786d000-7f2ee7a6d000 ---p 000f6000 08:01 655632 /usr/lib/libstdc++.so.6.0.13 7f2ee7a6d000-7f2ee7a74000 r--p 000f6000 08:01 655632 /usr/lib/libstdc++.so.6.0.13 7f2ee7a74000-7f2ee7a76000 rw-p 000fd000 08:01 655632 /usr/lib/libstdc++.so.6.0.13 7f2ee7a76000-7f2ee7a8b000 rw-p 00:00 0 7f2ee7a8b000-7f2ee7b5 r-xp 08:01 656789 /usr/lib/libapt-pkg-libc6.10-6.so.4.8.0 7f2ee7b5-7f2ee7d5 ---p 000c5000 08:01 656789 /usr/lib/libapt-pkg-libc6.10-6.so.4.8.0 7f2ee7d5-7f2ee7d53000 r--p 000c5000 08:01 656789 /usr/lib/libapt-pkg-libc6.10-6.so.4.8.0 7f2ee7d53000-7f2ee7d54000 rw-p 000c8000 08:01 656789 /usr/lib/libapt-pkg-libc6.10-6.so.4.8.0 7f2ee7d54000-7f2ee7d74000 r-xp 08:01 394878 /lib/ld-2.11.1.so 7f2ee7e96000-7f2ee7f1e000 r--s 08:01 915774 /var/cache/nscd/services
[Touch-packages] [Bug 1382548] [NEW] no warning upon headset plugin
Public bug reported: #114 krillin The warning works fine for changing the volume when the headset is plugged in. But, if you set the volume to max without the headset plug it in afterward there is no warning. I would have expected just a brief display of the warning reflecting the current volume setting. ** Affects: indicator-sound (Ubuntu) Importance: High Status: New ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1382548 Title: no warning upon headset plugin Status in “indicator-sound” package in Ubuntu: New Bug description: #114 krillin The warning works fine for changing the volume when the headset is plugged in. But, if you set the volume to max without the headset plug it in afterward there is no warning. I would have expected just a brief display of the warning reflecting the current volume setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1382548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382212] Re: [wizard] selecting terms and conditions link for HERE continues to next screen
The intended behaviour is that users are redirected to the full page of TCs. A BACK button allows them to navigate to the previous page with the check boxes. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Assignee: (unassigned) = Olga Kemmet (olga-kemmet) -- 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/1382212 Title: [wizard] selecting terms and conditions link for HERE continues to next screen Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: On the Location screen in the setup wizard, there's a checkbox for Accept the HERE terms and conditions to enable these services. The sting terms and conditions is underlined and appears to be a link, but when you tap it, it takes you to the next screen rather than to something to let you read the terms and conditions. Tapping anywhere else on the line appears to select or deselect the checkbox, so I think the underlined text is intended to have some different behavior, but appears to have the wrong behavior right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp