[Touch-packages] [Bug 1851154] Re: libindicator ftbfs: G_ADD_PRIVATE
I note this is the same problem indicator-messages had in bug 1843740. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: New Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851154] [NEW] libindicator ftbfs: G_ADD_PRIVATE
Public bug reported: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. ** Affects: libindicator (Ubuntu) Importance: Undecided Status: New ** Attachment added: "build log from makechrootpkg" https://bugs.launchpad.net/bugs/1851154/+attachment/5302542/+files/libindicator-buildlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: New Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 641479] Re: Surround Sound hisstles (hiss + whistle) when the volume is changed
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/445849/comments/258 >This issue is fixed since long ago. I'm inclined to believe that, though to be honest I simply got into the habit of avoiding changing pulseaudio's main volume. Does it matter if the fix is done in pulseaudio or the alsa-driver package? We're not even talking about the same pulseaudio now. >pulseaudio 10.0 ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/641479 Title: Surround Sound hisstles (hiss + whistle) when the volume is changed Status in alsa-driver package in Ubuntu: Fix Released Bug description: This bug has been troublesome since Karmic and also affects Lucid. It's more likely a bug in pulseaudio than in alsa-driver. Whenever pulseaudio changes the sound level, audio begins to hisstle. It only clears up at max volume. I've heard that using a 7.1 surround configuration resolves the issue, but my card only supports up to 5.1 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.34-5.14-generic 2.6.34 Uname: Linux 2.6.34-5-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.22.1. Architecture: amd64 Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 16' Mixer name : 'Nvidia GT220 HDMI' Components : 'HDA:10de000a,10de0101,00100100' Controls : 16 Simple ctrls : 4 Card1.Amixer.info: Card hw:1 'Live'/'SB Live! 5.1 Dell OEM [SB0228] (rev.10, serial:0x80661102) at 0xcc00, irq 19' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 224 Simple ctrls : 45 Date: Sat Sep 18 01:37:22 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SelectedCard: 1 Live EMU10K1 - SB Live! 5.1 Dell OEM [SB0228] SourcePackage: alsa-driver Symptom: audio Title: [EMU10K1 - SB Live! 5.1 Dell OEM [SB0228]] Surround problem dmi.bios.date: 12/12/2007 dmi.bios.vendor: HP dmi.bios.version: O11 dmi.board.name: ProLiant ML115 G1 dmi.board.vendor: HP dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnHP:bvrO11:bd12/12/2007:svnHP:pnProLiantML115G1:pvr1.0:rvnHP:rnProLiantML115G1:rvr:cvnHP:ct7:cvr1.0: dmi.product.name: ProLiant ML115 G1 dmi.product.version: 1.0 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/641479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315659] Re: Some widget have black background
*** This bug is a duplicate of bug 1167079 *** https://bugs.launchpad.net/bugs/1167079 ** This bug is no longer a duplicate of bug 1367764 Themes using overlay scrollbars have to set explicitly set backgrounds on all scrollable widgets ** This bug has been marked a duplicate of bug 1167079 GtkScrolledWindow widgets (GTK3) have black or transparent backgrounds with Ayatana overlay-scrollbar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1315659 Title: Some widget have black background Status in ubuntu-themes package in Ubuntu: New Bug description: You can see the problem in Glade when opening the Menu Editor > Hierarchy tab. I am using the default Ambiance theme and the Faenza icon set. Overlay scrollbars are on on my system. When starting an app from MonoDevelop which disables overlay scrollbars there is no issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-themes 14.04+14.04.20140410-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 14:11:03 2014 InstallationDate: Installed on 2014-04-18 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1315659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
** Description changed: Plug in iOS device, and it doesn't show the documents on it. - Please package the recent fix in libimobiledevice: + Please package the recent fix in libimobiledevice*: + Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 + + *This discussion is quite vague. One comment points out "iOS 10 devices + don't allow SSLv3 anymore but require at least TLSv1", but not how or if + that has been fixed in libimobiledevice git HEAD. + + This ppa packages the git version and may resolve the issue: + https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages + + There are several other upstream reports related to this problem. + + Partial success patch (idevicepair only) trying to keep GnuTLS: + https://github.com/libimobiledevice/libimobiledevice/issues/413 + + Failure with GnuTLS, Success with OpenSSL: + https://gitlab.com/gnutls/gnutls/issues/145 + + Ubuntu packages libimobiledevice with "--disable-openssl": + https://github.com/libimobiledevice/ifuse/issues/32 + + Duplicate bug 1638177 suggests to repackage libimobiledevice using + OpenSSL to avoid this problem, as per comment 27 below. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
Is there any aspect of deb package management that isn't broken? -- 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/972077 Title: apt repository disk format has race conditions Status in apt package in Ubuntu: Confirmed Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/972077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails
I am very, very painfully going through this process right now. I REALLY need dpkg to stop trying to remove colord and network-manager (dependent on policykit-1). It would also help if Ubuntu Web Browser were a little more responsive.. Took 10 minutes to type this far probably unrelated... Is the reboot absolutely necessary? I don't think my system will come back. -- 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/1423811 Title: 219-1ubuntu1 regression: boot hangs, logind fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Status in systemd package in Fedora: Unknown Bug description: Since yesterday, systemd does not boot properly any more. It takes very long, ends up in an X failsafe session, and eventually you just get a getty on VT1. Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the boot again. This happens both with the standard "quiet splash $vt_handoff" as well as without these tree options, i. e. text mode boot. $ sudo systemctl list-jobs JOB UNITTYPESTATE 1634 sound.targetstopwaiting 1176 NetworkManager.service start running 1598 cgproxy.service start waiting 1632 failsafe-graphical.target stopwaiting 1563 alsa-restore.servicestart waiting 1594 plymouth-quit-wait.service start waiting 1588 getty-static.servicestart waiting 1562 alsa-state.service start waiting 121 systemd-update-utmp-runlevel.servicestart waiting 1640 ifup@wlan0.service stopwaiting 1544 systemd-ask-password-plymouth.path start waiting 1507 friendly-recovery.service start waiting 1607 anacron.service start waiting 1489 systemd-binfmt.service start waiting 1637 system-systemd\x2drfkill.slice stopwaiting 1636 systemd-rfkill@rfkill1.service stopwaiting 1631 failsafe-x.service stopwaiting 1638 systemd-backlight@backlight:intel_backlight.service stopwaiting 1610 pppd-dns.servicestart waiting 1483 systemd-machine-id-commit.service start waiting 1635 system-systemd\x2dbacklight.slice stopwaiting 1557 systemd-hwdb-update.service start waiting 1630 systemd-backlight@backlight:acpi_video0.service stopwaiting 1500 sys-kernel-config.mount start waiting 92 multi-user.target start waiting 1509 debian-fixup.servicestart waiting 1641 systemd-rfkill@rfkill0.service stopwaiting 1613 plymouth-quit.service start waiting 1639 system-ifup.slice stopwaiting 1642 ifup@lxcbr0.service stopwaiting 1633 acpid.service stopwaiting 1643 systemd-logind.service restart waiting 1543 plymouth-start.service start waiting 1499 plymouth-read-write.service start waiting Attaching debug journal. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 20 07:39:03 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (91 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119) MachineType: LENOVO 2324CTO ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet splash vt.handoff=7 init=/sbin/upstart SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Touch-packages] [Bug 578928] Re: package libc-bin 2.11.1-0ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135
Five years later, no one--anywhere--has any idea what causes "Bus error" or why it ruins everything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/578928 Title: package libc-bin 2.11.1-0ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 Status in eglibc: New Status in eglibc package in Ubuntu: Expired Bug description: Trying to install mp3 support for Ubuntu. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libc-bin 2.11.1-0ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Tue May 11 21:45:38 2010 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 135 SourcePackage: eglibc Title: package libc-bin 2.11.1-0ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 135 To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/578928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
defaria I think you may have encountered what I was getting at in #32 GNOME has tied hotkey support into gnome-shell, such that hotkeys no longer work without gnome-shell in any gnome-derivative desktops (like Unity). The GNOME team has provided a utility to restore hotkey support without gnome-shell: gnome-fallback-media-keys-helper At the moment, the only Ubuntu package available is in the Zorion OS PPA: https://launchpad.net/~zorin-os/+archive/ubuntu/packages Rather than add the whole PPA, it's probably a better idea to download the one package and install it with dpkg. -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423351] [NEW] Cease development and distribution of notify-osd
Public bug reported: Citing this tragedy: bug 390508 And this travesty: bug 533631 I fail to see a point in notify-osd's continued existence other than intentionally alienating developers and users. ** Affects: libnotify (Ubuntu) Importance: Undecided Status: New ** Description changed: Citing this tragedy: bug 390508 - And this travesty: bugs 533631 + And this travesty: bug 533631 I fail to see a point in notify-osd's continued existence other than intentionally alienating developers and users. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1423351 Title: Cease development and distribution of notify-osd Status in libnotify package in Ubuntu: New Bug description: Citing this tragedy: bug 390508 And this travesty: bug 533631 I fail to see a point in notify-osd's continued existence other than intentionally alienating developers and users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1423351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
How does unity work around gnome-settings-daemon dropping support for media keys? Does unity handle these keys itself now? -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working
or has that change not hit Ubuntu yet? -- 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/1302885 Title: Media keyboard shortcuts not working Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume up/down to Volume up/down, but when I press the Volume keys on the keyboard nothing happens. I have noticed the same problem with other keys on my Logitech Internet 350 keyboard with Tools, Mail, and HomePage. They can all be mapped with Keyboard Shortcuts, but nothing happens afterwards when the keyboard key is pressed. All these keyboard settings worked fine in older versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 23:49:58 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-02 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 931929] Re: Installation on RAID or LVM fails to boot
** Summary changed: - root on RAID:0 fails to boot + Installation on RAID or LVM fails to boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/931929 Title: Installation on RAID or LVM fails to boot Status in dmraid: New Status in tools for generating an initramfs: Confirmed Status in udev - /dev/ management daemon: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Booting from RAID is often broken after upgrades or fresh installations of Ubuntu. initramfs is not activating RAID devices. Steps to reproduce: 1. Upgrade or Install Ubuntu on a RAID 2. Reboot 3. Observe failure to find root drive and drop to busybox To work around this, when given the busybox prompt enter: dmraid -ay Verify that all of your raid devices are initialized, then enter: exit Booting should then continue. See comment #2 for a persistent (rebootable) workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/dmraid/+bug/931929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
** Changed in: ayatana-design Status: Fix Committed = Opinion ** Changed in: ayatana-design Status: Opinion = In Progress -- 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/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: In Progress Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in unity source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
Have I mentioned before that I think this is a layering problem? I was reading the old xscreensaver (one of many things unity appears on top of) faq and came a across this: __ Every few minutes, xscreensaver will raise itself above any other windows that have popped up, but it can't prevent other programs from popping up their windows in the first place. So they will appear for a little while, and then be hidden. If this is happening and it bothers you, switching to a different window manager may fix it. You might consider this a bug in your window manager (though some consider it a feature.) If you think it's a bug, then the magic incantation to repeat to the author of your window manager is as follows: you should be mapping windows with XRestackWindows instead of XRaiseWindow, to ensure that managed windows always appear below override-redirect windows. It is also possible that the application that is popping up the window is doing so using an override-redirect window of its own. (This is currently the case with GTK_WINDOW_POPUP style dialogs.) In that case, it is impossible for either xscreensaver or the window manager to prevent those windows from popping up, since override-redirect windows, by definition, bypass the window manager. __ Is Unity drawn using override-redirect? Is it mapped with XRaiseWindow? -- 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/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Confirmed Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
