[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
Hmm, actually this has only been reported on i945 systems so far (me and another person in: https://bugs.launchpad.net/mir/+bug/1275398/comments/20 My Haswell desktop works fine with the same image. Maybe we're missing something in our relatively recent mesa patches to support i945?... -- 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/1408910 Title: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context) Status in Mir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run: unity8.log: std::exception::what: Failed to create shared EGL context I've also verified mir_proving_server with mir_demo_client_* runs fine in another VT. I think this might be a new issue introduced by the upgrade to Mir 0.10 last night? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics
filip: I've reproduced the bug you describe. Please see -> bug 1408910 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics Status in Mir: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
** Description changed: - Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. + Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run: unity8.log: std::exception::what: Failed to create shared EGL context + + I've also verified mir_proving_server with mir_demo_client_* runs fine + in another VT. I think this might be a new issue introduced by the upgrade to Mir 0.10 last night? -- 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/1408910 Title: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context) Status in Mir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run: unity8.log: std::exception::what: Failed to create shared EGL context I've also verified mir_proving_server with mir_demo_client_* runs fine in another VT. I think this might be a new issue introduced by the upgrade to Mir 0.10 last night? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408910] [NEW] Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)
Public bug reported: Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run: unity8.log: std::exception::what: Failed to create shared EGL context I've also verified mir_proving_server with mir_demo_client_* runs fine in another VT. I think this might be a new issue introduced by the upgrade to Mir 0.10 last night? ** Affects: mir Importance: Critical Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Affects: unity8 (Ubuntu) Importance: Critical Status: Triaged ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir Milestone: None => 0.11.0 -- 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/1408910 Title: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context) Status in Mir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: Ubuntu Desktop Next fails to start. I just get a black screen and mouse pointer. So unity-system-compositor is working fine. Only the nested unity8 can't run: unity8.log: std::exception::what: Failed to create shared EGL context I've also verified mir_proving_server with mir_demo_client_* runs fine in another VT. I think this might be a new issue introduced by the upgrade to Mir 0.10 last night? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1408910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408747] Re: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1376612 *** https://bugs.launchpad.net/bugs/1376612 ** Tags added: bot-stop-nagging -- 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/1408747 Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Installed with gui updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu8.2 Uname: Linux 3.16.6-031606-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Jan 8 13:12:51 2015 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu8.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-09-18 (476 days ago) InstallationMedia: This SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1408747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408605] Re: last -t does not work as what man page said
Any chance this bug to be assigned? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1408605 Title: last -t does not work as what man page said Status in sysvinit package in Ubuntu: New Bug description: The man page of the last command says as follows: -t MMDDHHMMSS Display the state of logins as of the specified time. This is useful, e.g., to determine easily who was logged in at a particular time -- specify that time with -t and look for "still logged in”. However, Wen I ran the command with -t, I got the following output: # last -F -t 2015010700 | grep pts root pts/2jp001.solidtunne Tue Jan 6 18:39:05 2015 - Tue Jan 6 18:40:34 2015 (00:01) root pts/2jp001.solidtunne Tue Jan 6 18:37:24 2015 - Tue Jan 6 18:37:41 2015 (00:00) root pts/2jp001.solidtunne Tue Jan 6 16:42:33 2015 - Tue Jan 6 16:43:49 2015 (00:01) root pts/2jp001.solidtunne Tue Jan 6 13:03:26 2015 - Tue Jan 6 13:07:02 2015 (00:03) root pts/2jp001.solidtunne Tue Jan 6 09:03:24 2015 - Tue Jan 6 09:03:54 2015 (00:00) root pts/2jp001.solidtunne Tue Jan 6 04:53:54 2015 - Tue Jan 6 04:54:07 2015 (00:00) root pts/042.243.9.2 Mon Jan 5 03:06:48 2015 - Mon Jan 5 03:07:10 2015 (00:00) root pts/242.243.9.2 Sun Jan 4 14:08:02 2015 - Sun Jan 4 14:09:02 2015 (00:01) root pts/142.243.9.2 Sun Jan 4 12:09:56 2015 - Sun Jan 4 12:10:05 2015 (00:00) root pts/042.243.9.2 Sun Jan 4 03:24:57 2015 - Sun Jan 4 03:25:10 2015 (00:00) root pts/242.243.96.183Sat Jan 3 14:47:38 2015 - Sat Jan 3 14:47:54 2015 (00:00) root pts/4sf003.solidtunne Fri Jan 2 15:23:12 2015 - Fri Jan 2 15:23:51 2015 (00:00) root pts/0hk000.solidtunne Thu Jan 1 16:40:55 2015 - Thu Jan 1 16:41:21 2015 (00:00) root pts/2hk000.solidtunne Thu Jan 1 15:41:52 2015 - Thu Jan 1 15:42:02 2015 (00:00) root pts/4hk000.solidtunne Thu Jan 1 11:24:56 2015 - Thu Jan 1 13:40:40 2015 (02:15) root pts/4hk000.solidtunne Thu Jan 1 11:24:34 2015 - Thu Jan 1 11:24:48 2015 (00:00) root pts/0hk000.solidtunne Thu Jan 1 08:31:13 2015 - Thu Jan 1 08:31:25 2015 (00:00) The current date is as follows: # date Thu Jan 8 08:12:32 UTC 2015 And Ubuntu version: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty Kernel: # uname -a Linux install 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux So, it seems the -t actually returns the state of logins "up till" the specified time, as opposed to "as of" the specified time as written in the man page, or am I missing something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1408605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1051935] Re: Fails with SystemError when too many files are open
** Changed in: oneconf (Ubuntu Precise) Status: Confirmed => Fix Released ** Changed in: gdebi (Ubuntu Precise) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1051935 Title: Fails with SystemError when too many files are open Status in Python-APT: New Status in gdebi package in Ubuntu: Fix Released Status in oneconf package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in gdebi source package in Precise: Fix Released Status in oneconf source package in Precise: Fix Released Status in python-apt source package in Precise: Fix Released Status in ubiquity source package in Precise: Fix Released Status in gdebi source package in Saucy: Fix Released Status in oneconf source package in Saucy: Fix Released Status in python-apt source package in Saucy: Fix Released Status in ubiquity source package in Saucy: Won't Fix Bug description: [Impact] * Failure to complete installation. [Test Case] * At times, apt cache can run out of file descriptors as seen in this bug and its duplicates. * There is no clear-cut way to reproduce it in ubiquity, but there is a significant amount of crash reports submit, which dropped off after the proposed fix has been applied. [Regression Potential] * The proposed fix has been well tested in trusty both automated & manual testing and does not regress on any configuration. [Other Info] This error occurs each time I try to install a .deb file with Gdebi in Ubuntu 12.10, after the deb installation finishes. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gdebi 0.8.5build1 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 17 15:33:34 2012 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120914) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb'] SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/python-apt/+bug/1051935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319698] Re: Gallery app shows pictures abnormally if target directory or file name contained Chinese text .
@Arthur, From Ara says we need it for our pre-installed Ubuntu Desktop, and we use the trusty, do we prepare to fix it for trusty? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1319698 Title: Gallery app shows pictures abnormally if target directory or file name contained Chinese text . Status in Gallery App: Fix Released Status in OEM Priority Project: Fix Released Status in Thumbnail generator for all kinds of files: Fix Released Status in thumbnailer package in Ubuntu: Fix Released Bug description: Steps: 1. Copy some pictures to ~/Pictures 2. Launch Gallery app by entering "gallery" in Dash 3. Observe what the Gallery shows. Actual results: There are some transparent frames in Gallery. Expected results: Gallery app should show pictures included in ~/Pictures directory in step 2. Platform: Lenovo S440s Note: Once Gallery's target directory or file name of the target directory contains Chinese text, the issue will be reproduced. Adverse, if Gallery's target directory or file name of the target directory in English, Gallery displays normally. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1319698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390474] Re: "Volume element PCM has 6 channels. That's too much!" - PA doesn't support elements with more than two channels
+if (e->n_channels > 2) {
+/* FIXME: In some places code like this is used:
+ *
+ * e->masks[alsa_channel_ids[p]][e->n_channels-1]
+ *
+ * The definition of e->masks is
+ *
+ * pa_channel_position_mask_t
masks[SND_MIXER_SCHN_LAST][2];
+ *
+ * Since the array size is fixed at 2, we obviously
+ * don't support elements with more than two
+ * channels... */
+pa_log_warn("Volume element %s has %u channels. That's
too much! I can't handle that!", e->alsa_name, e->n_channels);
+return -1;
+}
+
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa
/alsa-mixer.c?id=527078523815587bfd021bc1d10782403e9b3e84
the answer was aleady stated in the patch
you need to change alsa-mixer.h
-pa_channel_position_mask_t masks[SND_MIXER_SCHN_LAST][2];
+pa_channel_position_mask_t masks[SND_MIXER_SCHN_LAST][8];
and
- if (e->n_channels > 2) {
+ if (e->n_channels > 8) {
--
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/1390474
Title:
"Volume element PCM has 6 channels. That's too much!" - PA doesn't
support elements with more than two channels
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the
error "Volume element PCM has 6 channels. That's too much! I can't handle
that!" and the card fails to show up in Sound Settings.
Everything is fine with 24/48 mode (2 channels).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408856] Re: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all
control.19 {
iface CARD
name 'Headphone Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
Node 0x14 [Pin Complex] wcaps 0x40018d: Stereo Amp-Out
Control: name="Speaker Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Control: name="Speaker Phantom Jack", index=0, device=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x0001003c: IN OUT HP EAPD Detect
EAPD 0x2: EAPD
Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
Unsolicited: tag=00, enabled=0
Connection: 1
0x0f
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
speaker is muted (pin ctls is zero) by driver when headphone is plugged
try
hda-jack-sense-test
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1408856
Title:
[HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No
sound at all
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
Sound won´t work on default install on internal speakers or
headphones.
Downloaded Realtek driver, compiled and installed and still no sound.
Compile command
./configure --with-cards=hda-intel
Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18
Clearly some thing is happeing as the volume controls work, and in
pulse volume control it shows varying volume on the meters.
Analogue Stero shows ´Speakers not connected´
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: john 1791 F pulseaudio
john 2138 F gnome-alsamixer
/dev/snd/pcmC0D0p: john 1791 F...m pulseaudio
CurrentDesktop: XFCE
Date: Fri Jan 9 03:43:09 2015
InstallationDate: Installed on 2014-12-08 (31 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140723)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: john 1791 F pulseaudio
john 2138 F gnome-alsamixer
/dev/snd/pcmC0D0p: john 1791 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.58
dmi.board.name: 30D2
dmi.board.vendor: Quanta
dmi.board.version: 79.2E
dmi.chassis.asset.tag: dv6758es
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-09T03:36:52.607919
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1408856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407723] Re: Text cursor/selection handles too small and confusing
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1407723 Title: Text cursor/selection handles too small and confusing Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: It is still very difficult to reliably select text in text fields and areas, the handles are tiny and even if you manage to target them, you'll cover the text you operate on with your finger. It is also very difficult to distinguish between moving the cursor and selecting text. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1364+15.04.20141209-0ubuntu2 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Mon Jan 5 16:25:22 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1407723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390668] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1390668 Title: [ICH - Intel 82801AA-ICH, playback] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: No sound ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lpuente1760 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 7 20:58:54 2014 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH successful Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lpuente1760 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [ICH - Intel 82801AA-ICH, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-19 (19 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407865] Re: "Super+Alt+S" did not function at the login screen
Tired on both stock Ubuntu 14.04 and Vidid Stock Ubuntu 14.04 the hotkey "Super+Alt+S" did not function. Vidid Ubuntu the hotkey "Super+Alt+S" function. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1407865 Title: "Super+Alt+S" did not function at the login screen Status in OEM Priority Project: Incomplete Status in OEM Priority Project trusty series: New Status in lightdm package in Ubuntu: New Status in orca package in Ubuntu: New Bug description: Summary:Some accessibility features of the Ubuntu operating system did not function. The command to toggle the Orca screen reader on and off (super+alt+S) did not function at the Login screen. Steps to reproduce: 1. Boot into the system. 2. Press "super+alt+s" to enable the orca screen reader. Expected result:The screen reader should be enabled. Actual result:It doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1407865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404094] Re: Sound stops working
client(s) logged in. index: 0 driver: owner module: 15 properties: application.name = "Login Session c3" systemd-login.session = "c3" index: 1 driver: owner module: 15 properties: application.name = "Login Session c2" systemd-login.session = "c2" index: 2 -- 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/1404094 Title: Sound stops working Status in pulseaudio package in Ubuntu: New Bug description: My fully working sound configuration occasionally stops working. Symptoms are: - System Settings -> Sound only shows "dummy output" and no input devices - restarting pulseaudio has no effect - aplay -l as root shows sound cards - fuser -v /dev/snd/* shows nothing; /dev/dsp and /dev/seq do not exist - Rebooting solves the problem This did not occur on trusty but has occurred twice on utopic in the last month or two. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Dec 19 12:40:29 2014 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Title: [CTO, Intel PantherPoint HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: Upgraded to utopic on 2014-11-10 (38 days ago) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1404094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404094] Re: Sound stops working
did this happen when there are two or more user login since first user 's pulseaudio accquire the sound card and second user ' pulseaudio cannot open the sound card any more ? sudo fuser /dev/snd/* -- 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/1404094 Title: Sound stops working Status in pulseaudio package in Ubuntu: New Bug description: My fully working sound configuration occasionally stops working. Symptoms are: - System Settings -> Sound only shows "dummy output" and no input devices - restarting pulseaudio has no effect - aplay -l as root shows sound cards - fuser -v /dev/snd/* shows nothing; /dev/dsp and /dev/seq do not exist - Rebooting solves the problem This did not occur on trusty but has occurred twice on utopic in the last month or two. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Dec 19 12:40:29 2014 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Title: [CTO, Intel PantherPoint HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: Upgraded to utopic on 2014-11-10 (38 days ago) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1404094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes
I can confirm this bug. I installed Ubuntu on 2 laptops, Dell and Asus, both have Nvidia graphics cards and both got same issue. -- 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/1387134 Title: when enabled nvidia graphics card, desktop freezes Status in xorg package in Ubuntu: Confirmed Bug description: Screen freezes occasionally while simply browsing the web, can be recovered by ctrl+alt+f1 and ctrl+alt+f7 This has been the case in 14.04, and it's still the case in 14.10 (64 bit) Asus UX32V 331.89-0ubuntu5 *** 331.89-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: '/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: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 29 12:40:01 2014 DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] InstallationDate: Installed on 2014-05-31 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash processor.ignore_ppc=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 29 12:00:13 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4931 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1387134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404094] Re: Sound stops working
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1404094 Title: Sound stops working Status in pulseaudio package in Ubuntu: New Bug description: My fully working sound configuration occasionally stops working. Symptoms are: - System Settings -> Sound only shows "dummy output" and no input devices - restarting pulseaudio has no effect - aplay -l as root shows sound cards - fuser -v /dev/snd/* shows nothing; /dev/dsp and /dev/seq do not exist - Rebooting solves the problem This did not occur on trusty but has occurred twice on utopic in the last month or two. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Dec 19 12:40:29 2014 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Title: [CTO, Intel PantherPoint HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: Upgraded to utopic on 2014-11-10 (38 days ago) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1404094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
** Changed in: mir/0.9 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in The "G" Library - GLib: New Status in Mir: Fix Released Status in Mir 0.9 series: Won't Fix Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408856] Re: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all
Note I also tried varying different lines in alsa.base.conf -- 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/1408856 Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Sound won´t work on default install on internal speakers or headphones. Downloaded Realtek driver, compiled and installed and still no sound. Compile command ./configure --with-cards=hda-intel Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18 Clearly some thing is happeing as the volume controls work, and in pulse volume control it shows varying volume on the meters. Analogue Stero shows ´Speakers not connected´ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Jan 9 03:43:09 2015 InstallationDate: Installed on 2014-12-08 (31 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.asset.tag: dv6758es dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-09T03:36:52.607919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1408856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1355173 Title: Switching windows with a Trusted Prompt Session active loses the trusted prompt session Status in the base for Ubuntu mobile products: In Progress Status in Mir: Fix Released Status in Qt integration with the Mir display server: In Progress Status in Online Accounts setup for Ubuntu Touch: Invalid Status in mir package in Ubuntu: Fix Released Status in pay-service package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: In Progress Status in trust-store package in Ubuntu: Confirmed Status in ubuntu-system-settings-online-accounts package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Status in qtmir package in Ubuntu RTM: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: When we create a trusted prompt session over an application, let's say a small dialog, and then switch applications, when we switch back to the original application the dialog is not overlayed on top of the original application. The program providing the dialog seems happy, and is still running, but visually it is not there. We notice this when using the payments UI which overlays ontop of the dash. In some cases we need to show Online Accounts which runs as an independent application and causes a switching behavior. When returning back to the dash the Payment UI is not visible. It also happens if the Payment UI is visible and you switch applications using the right swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1355173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408856] [NEW] [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all
Public bug reported: Sound won´t work on default install on internal speakers or headphones. Downloaded Realtek driver, compiled and installed and still no sound. Compile command ./configure --with-cards=hda-intel Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18 Clearly some thing is happeing as the volume controls work, and in pulse volume control it shows varying volume on the meters. Analogue Stero shows ´Speakers not connected´ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Jan 9 03:43:09 2015 InstallationDate: Installed on 2014-12-08 (31 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.asset.tag: dv6758es dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-09T03:36:52.607919 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1408856 Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Sound won´t work on default install on internal speakers or headphones. Downloaded Realtek driver, compiled and installed and still no sound. Compile command ./configure --with-cards=hda-intel Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18 Clearly some thing is happeing as the volume controls work, and in pulse volume control it shows varying volume on the meters. Analogue Stero shows ´Speakers not connected´ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Jan 9 03:43:09 2015 InstallationDate: Installed on 2014-12-08 (31 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 1791 F pulseaudio john 2138 F gnome-alsamixer /dev/snd/pcmC0D0p: john 1791 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion dv6700 Notebook PC, Realtek ALC268, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.asset.tag: dv6758es dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:
[Touch-packages] [Bug 1394221] Re: acceptance_tests are too chatty
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1394221 Title: acceptance_tests are too chatty Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: acceptance tests have started becoming obfuscated with messages that are not related to what is being tested: eg: [--] 3 tests from ServerSignal [ RUN ] ServerSignal.terminate_handler_is_called_for_SIGTERM [1416406602.185984] (II) UnknownComponent: Starting Mir server [1416406602.200318] (II) UnknownComponent: Stopping Mir Server [1416406602.204740] (II) UnknownComponent: Stopping Mir Server [ OK ] ServerSignal.terminate_handler_is_called_for_SIGTERM (22 ms) [ RUN ] ServerSignal.terminate_handler_is_called_for_SIGINT [1416406602.207911] (II) UnknownComponent: Starting Mir server [1416406602.221617] (II) UnknownComponent: Stopping Mir Server [1416406602.226197] (II) UnknownComponent: Stopping Mir Server [ OK ] ServerSignal.terminate_handler_is_called_for_SIGINT (22 ms) [ RUN ] ServerSignal.multiple_cleanup_handlers_are_called [1416406602.229390] (II) UnknownComponent: Starting Mir server [ OK ] ServerSignal.multiple_cleanup_handlers_are_called (198 ms) [--] 3 tests from ServerSignal (242 ms total) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1394221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382209] Re: [Enhancement] Add an API to lock surface orientation
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1382209 Title: [Enhancement] Add an API to lock surface orientation Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Sometimes, applications are written to take advantage of the entire surface of screen. So they need a way to tell MIR, the orientation they want for drawing themselves. This can be portrait for some, landscape for others, or even combinations. Without this feature, portrait application get distorted when running in a landscape oriented device. So, it would be nice to have an API, in MIR client, to precisely lock the orientation of the MirSurface used for drawing. My use case is a full-screen game, that require always Portrait Orientation. Another is a full-screen game that requires always Landscape. Better (future): - allow this even for non full-screen applications - allow combination like Portait+PortraitUpsideDown, or LandscapeLeft+LandscapeRight - allow to change the orientation when the application run (so not only when creating/requesting the surface). Remarks : - touch event may need to be translated into the correct coordinates system! To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1382209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391488] Re: [testfail] BasicThreadPool.recycles_threads in CI
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1391488 Title: [testfail] BasicThreadPool.recycles_threads in CI Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid- armhf/37/console [ RUN ] BasicThreadPool.recycles_threads /tmp/buildd/mir-0.8.0+14.10.20141010bzr2030pkg0vivid37+autopilot0/tests/unit-tests/thread/test_basic_thread_pool.cpp:178: Failure Value of: task3.thread_name() Expected: (is equal to "thread1") or (is equal to "thread2") Actual: "memcheck-arm-li" (of type std::string) disInstr(thumb): unhandled instruction: 0xDEFF 0xF893 [ FAILED ] BasicThreadPool.recycles_threads (212 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1391488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394362] Re: fd reception code is not exeception-safe when unexpected numbers of fds are received
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Low ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1394362 Title: fd reception code is not exeception-safe when unexpected numbers of fds are received Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: the easiest way to see this is to inspect mir::receive_data, or to run valgrind with track-fds = yes In the wild, this would only leak 1-4 fd's per error. Given the type of errors that would cause this, it would take a lot of rare errors before we hit the process fd limit. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1394362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394873] Re: mir_connection_create_surface callback is sometimes called twice on error
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1394873 Title: mir_connection_create_surface callback is sometimes called twice on error Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: I've just run into some fun behaviour. In mir_surface.cpp, in the surface constructor, if: server.create_surface(0, &message, &surface, gp::NewCallback(this, &MirSurface::created, callback, context)); throws (such as if the RPC mechanism detects a connection break) then the created callback is called on the partially constructed MirSurface that's just about to be destructed. mir_connection_create_surface catches this exception and then calls the callback *again*, with an newly constructed error MirSurface. This is likely to confuse API users :) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1394873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407557] Re: [regression] Mir utils can't run from the build tree any more
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407557 Title: [regression] Mir utils can't run from the build tree any more Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir utils can't run from the build tree any more... $ bin/mirping Could not connect to a display server. $ sudo bin/mirping Could not connect to a display server. $ sudo bin/mirout Could not connect to a display server. $ bin/mirout Could not connect to a display server. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1407557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396006] Re: Input/event driven clients may freeze indefinitely
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1396006 Title: Input/event driven clients may freeze indefinitely Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Input/event driven clients may freeze indefinitely. This is a more generalized form of bug 1379685 that can happen with any windowed app too. The issue is: if (!ready_to_composite_queue.empty()) drop_frame(std::move(lock)); may drop the newest available frame in some cases: (ready_to_composite_queue.size() == 1 && contains(current_compositor_buffer, buffers_sent_to_compositor)) So when this happens, we're dropping the latest frame without any guarantees that the client will redraw another. Because a perfectly efficient event-driven app will only redraw when something changes (e.g. input event) and won't redraw just because a new buffer is available. So giving a buffer back to the client won't wake it up. The simple answer is to ensure you only drop frames when it's proven that you're not dropping the newest one. Because the time to the next frame after that is completely unpredictable and indefinite... if (ready_to_composite_queue.size() > 1) drop_frame(std::move(lock)); // worst case: the newest frame still gets composited. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1396006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406073] Re: [regression] Binaries are no longer runnable on other machines (or in other directories)
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1406073 Title: [regression] Binaries are no longer runnable on other machines (or in other directories) Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Binaries are no longer runnable when copied to other hosts: # bin/mir_proving_server Failed to execute real binary .mir_proving_server-uninstalled: No such file or directory # ls -l bin/.mir_proving_server-uninstalled -rwxrwxr-x 1 dan dan 3064944 Dec 28 16:36 bin/.mir_proving_server-uninstalled and # ./mir_proving_server Failed to execute real binary .mir_proving_server-uninstalled: No such file or directory # ls -l .mir_proving_server-uninstalled -rwxrwxr-x 1 dan dan 3064944 Dec 28 16:36 .mir_proving_server-uninstalled and starting the hidden server directly works, but then clients can't find it: # bin/.mir_proving_server-uninstalled & # bin/.mir_demo_client_egltriangle-uninstalled Can't get connection # bin/.mir_demo_client_flicker-uninstalled Starting .mir_demo_client_flicker-uninstalled: /home/dan/bzr/mir/dev/examples/flicker.c:134: main: Assertion `mir_connection_is_valid(connection)' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401364] Re: CI test failure in multiple tests
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium
** Changed in: mir (Ubuntu)
Importance: Undecided => High
** Changed in: mir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1401364
Title:
CI test failure in multiple tests
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
Multiple tests fail in a similar fashion:
https://jenkins.qa.ubuntu.com/job/mir-vivid-amd64-ci/352/consoleFull
For example:
ClientLibraryThread.handles_no_signals fails due to memory leak
(valgrind)
8: [ RUN ] ClientLibraryThread.handles_no_signals
8: ==10098==
8: ==10098== HEAP SUMMARY:
8: ==10098== in use at exit: 10,826 bytes in 83 blocks
8: ==10098== total heap usage: 254,821 allocs, 254,738 frees, 16,598,040
bytes allocated
8: ==10098==
8: ==10098== 92 (64 direct, 28 indirect) bytes in 1 blocks are definitely
lost in loss record 63 of 83
8: ==10098==at 0x4C2B100: operator new(unsigned long) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
8: ==10098==by 0x5288C3C: allocate (new_allocator.h:104)
8: ==10098==by 0x5288C3C: allocate (alloc_traits.h:357)
8: ==10098==by 0x5288C3C:
__shared_count()>
>,
std::allocator()>
> >,
std::_Bind_simple()>
> (shared_ptr_base.h:616)
8: ==10098==by 0x5288C3C:
__shared_ptr()>
> >,
std::_Bind_simple()>
> (shared_ptr_base.h:1090)
8: ==10098==by 0x5288C3C:
shared_ptr()>
> >,
std::_Bind_simple()>
> (shared_ptr.h:316)
8: ==10098==by 0x5288C3C:
allocate_shared()>
>,
std::allocator()>
> >,
std::_Bind_simple()>
> (shared_ptr.h:588)
8: ==10098==by 0x5288C3C:
make_shared()>
>,
std::_Bind_simple()>
> (shared_ptr.h:604)
8: ==10098==by 0x5288C3C:
_M_make_routine()>
> (thread:196)
8: ==10098==by 0x5288C3C:
thread >
(thread:138)
8: ==10098==by 0x5288C3C: mir::client::rpc::StreamSocketTransport::init()
(stream_socket_transport.cpp:188)
8: ==10098==by 0x5289A62:
mir::client::rpc::StreamSocketTransport::StreamSocketTransport(mir::Fd const&)
(stream_socket_transport.cpp:41)
8: ==10098==by 0x527B894: mir::client::rpc::make_rpc_channel(std::string
const&, std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&) (make_socket_rpc_channel.cpp:55)
8: ==10098==by 0x5271DB3: operator()
(default_connection_configuration.cpp:92)
8: ==10098==by 0x5271DB3:
std::_Function_handler (),
mir::client::DefaultConnectionConfiguration::the_rpc_channel()::{lambda()#1}>::_M_invoke(std::_Any_data
const&) (functional:2025)
8: ==10098==by 0x5272648: operator() (functional:2439)
8: ==10098==by 0x5272648: operator() (cached_ptr.h:41)
8: ==10098==by 0x5272648:
mir::client::DefaultConnectionConfiguration::the_rpc_channel()
(default_connection_configuration.cpp:92)
8: ==10098==by 0x525DE95:
MirConnection::MirConnection(mir::client::ConnectionConfiguration&)
(mir_connection.cpp:108)
8: ==10098==by 0x52625EE: connect (mir_connection_api.cpp:78)
8: ==10098==by 0x52625EE: mir_connect (mir_connection_api.cpp:143)
8: ==10098==by 0x5CB7D1: ClientLibrary_creates_surface_Test::TestBody()
(test_client_library.cpp:180)
8: ==10098==by 0x7AB7A2:
HandleSehExceptionsInMethodIfSupported (gtest.cc:2078)
8: ==10098==by 0x7AB7A2: void
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2114)
8: ==10098==by 0x7A1403: testing::Test::Run() (gtest.cc:2151)
8: ==10098==by 0x7A1527: testing::TestInfo::Run() [clone .part.372]
(gtest.cc:2326)
8: ==10098==
8: ==10098== LEAK SUMMARY:
8: ==10098==definitely lost: 64 bytes in 1 blocks
8: ==10098==indirectly lost: 28 bytes in 2 blocks
8: ==10098== possibly lost: 426 bytes in 10 blocks
8: ==10098==still reachable: 10,308 bytes in 70 blocks
8: ==10098== suppressed: 0 bytes in 0 blocks
8: ==10098== Reachable blocks (those to which a pointer was found) are not
shown.
8: ==10098== To see them, rerun with: --leak-check=full --show-leak-kinds=all
8: ==10098==
8: ==10098== For counts of detected and suppressed errors, rerun with: -v
8: ==10098== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
8:
/tmp/buildd/mir-0.9.0+15.04.20141125bzr2141pkg0vivid331/tests/mir_test_framework/interprocess_client_server_test.cpp:90:
Failure
8: Value of: result.exit_code
8: Expected: is equal to 0
8: Actual: 1 (of type int)
8: ==10090==
8: ==10090== HEAP SUMMARY:
8: ==10090== in use at exit: 11,727 bytes in 86 blocks
8: ==10090== total heap usage: 258,445 allocs, 258,359 frees, 16,749,998
bytes allocated
8: ==10090==
8: ==10090== 92 (64 direct, 28 indirect) byte
[Touch-packages] [Bug 1264934] Re: Mir's compositor holds buffers (blocking clients) for the duration of the frame, even when not necessary.
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1264934 Title: Mir's compositor holds buffers (blocking clients) for the duration of the frame, even when not necessary. Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: RenderingOperator::operator() holds buffers (blocking clients) for the duration of the frame, even when not necessary. From what I can tell, the holding of the buffer as a "resource" till after the SwapBuffers is required for some APIs, such as glEGLImageTargetTexture2DOES used by Mir "hardware" buffers. However, Mir software buffers use a simple glTexImage2D which only does a synchronous copy of the data. So it's wasteful holding a reference to the buffer for any longer than the duration of the glTexImage2D call. This will directly affect the round-trip performance of mir_surface_swap_buffers() while bug 1253868 is unresolved. So in theory, just making our "saved resources" logic a little smarter could significantly improve clients ability to meet frame deadlines. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1264934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311699] Re: MirMotionEvent.action needs stronger typing (to MirMotionAction etc)
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium
** Changed in: mir (Ubuntu)
Importance: Undecided => Medium
** Changed in: mir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1311699
Title:
MirMotionEvent.action needs stronger typing (to MirMotionAction etc)
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
MirMotionEvent.action is currently an int for legacy android
compatibility reasons. We need to clean this up and use
MirMotionAction properly, unlike in examples...
MirMotionAction action =
static_cast(event.motion.action & ~0xff00);
OLD DESCRIPTION:
MirEvent::action is currently effectively an opaque value, as Mir headers do
not specify its meaning.
So event.h must either define counterparts to the android
AMOTION_EVENT_ACTION_* values below or split up the action and pointer
index into separate variables.
"""
/* Bit shift for the action bits holding the pointer index as
* defined by AMOTION_EVENT_ACTION_POINTER_INDEX_MASK.
*/
#define AMOTION_EVENT_ACTION_POINTER_INDEX_SHIFT 8
enum {
/* Bit mask of the parts of the action code that are the action itself.
*/
AMOTION_EVENT_ACTION_MASK = 0xff,
/* Bits in the action code that represent a pointer index, used with
* AMOTION_EVENT_ACTION_POINTER_DOWN and AMOTION_EVENT_ACTION_POINTER_UP.
Shifting
* down by AMOTION_EVENT_ACTION_POINTER_INDEX_SHIFT provides the actual
pointer
* index where the data for the pointer going up or down can be found.
*/
AMOTION_EVENT_ACTION_POINTER_INDEX_MASK = 0xff00,
"""
Right now in the "Qt compositor" code I had to resort to locally
defining those values, which is a hack:
""
// from android-input AMOTION_EVENT_ACTION_*, hidden inside mir bowels
// mir headers should define them
const int QtEventFeeder::MirEventActionMask = 0xff;
const int QtEventFeeder::MirEventActionPointerIndexMask = 0xff00;
const int QtEventFeeder::MirEventActionPointerIndexShift = 8;
""
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1311699/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398294] Re: DisplayLayout resizes a surface to 1x1 if you ask it to fullscreen a surface that's partially offscreen
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398294 Title: DisplayLayout resizes a surface to 1x1 if you ask it to fullscreen a surface that's partially offscreen Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: PlacementStrategy/DisplayLayout resizes a surface to 1x1 (and moves it to 0,0) if you ask it to fullscreen a surface that's partially offscreen To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350716] Re: CompositorReport as used by DefaultDisplayBufferCompositor can't measure render time
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium
** Changed in: mir (Ubuntu)
Importance: Undecided => Medium
** Changed in: mir (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1350716
Title:
CompositorReport as used by DefaultDisplayBufferCompositor can't
measure render time
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
CompositorReport as used by DefaultDisplayBufferCompositor can't
measure render time.
Presently we have:
// [A]
report->began_frame(this);
...
if (display_buffer.post_renderables_if_optimizable(renderable_list)) //
[B] before page flip
{
renderer->suspend();
report->finished_frame(true, this);
}
else
{
display_buffer.make_current();
renderer->set_rotation(display_buffer.orientation());
renderer->begin(); // TODO deprecatable now?
renderer->render(renderable_list);
display_buffer.post_update(); // swap buffers, [B], then page flip
renderer->end();
report->finished_frame(false, this);
}
// [C]
Compositor report correctly reports "frame time" as [C]-[A]. However a
more useful measure is render time which is [B]-[A]. But we can't do
that yet as we'd have to insert a reporting point in the middle of the
post_ functions (or split them) so as to not include page flipping
time in "render time", while still including the final eglSwapBuffers
(if any).
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1350716/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402160] Re: Leaks in death tests can cause subsequent tests in the same process to fail
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1402160 Title: Leaks in death tests can cause subsequent tests in the same process to fail Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: To reproduce: valgrind --error-exitcode=1 --trace-children=yes --leak-check=full --show-leak-kinds=definite --errors-for-leak-kinds=definite bin/mir_acceptance_tests --gtest_filter=ClientLibraryErrorsDeathTest*:ClientLibraryThread* The ClientLibraryThread tests should pass and not report any definite leaks. It's expected to get leaks from the DeathTests. Note that for me (and Daniel, see [1]), this is still a problem even with Christopher's fix ([2]). So, this is a real issue, just not the one that was blocking CI. I don't know why on some setups (e.g. Alan's) this fix seems to have no effect. Perhaps it was a combination of this leak and the one fixed by Chris that complicated the situation, and now that the other leak is fixed this will work properly on all setups. [1] https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526/comments/603009 [2] https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1402160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407558] Re: Mir reports vertical refresh rates slightly inaccurately
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407558 Title: Mir reports vertical refresh rates slightly inaccurately Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: mirout says: Output 19: Card 0, HDMI-A, connected, 1920x1200+0+0, used, on, 520mm x 330mm (24.2"), normal 1920x1200 60.0*+ 1600x1200 60.0 1680x1050 59.9 1280x1024 75.060.0 1152x864 75.0 1024x768 75.160.0 800x600 75.060.3 640x480 75.060.0 720x400 70.1 Actually that first 60.0 is more like 59.94. It's just that we've rounded the result, both in mirout and also in: src/platforms/mesa/real_kms_display_configuration.cpp:return round(vrefresh_hz * 10.0) / 10.0; Then again, it's normal for the industry to knowingly refer to 59.94Hz as "60Hz", or 23.976Hz as "24Hz" etc. So low priority for now. Maybe even Won't Fix... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1407558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406098] Re: [regression] lintian: E: mir-demos: binary-or-shlib-defines-rpath ...
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1406098 Title: [regression] lintian: E: mir-demos: binary-or-shlib-defines-rpath ... Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: [regression] lintian says: Now running lintian... E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_basic /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_cursors /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_display_config /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglcounter /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglflash /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglplasma /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_egltriangle /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_fingerpaint /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_flicker /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_multiwin /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_progressbar /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_prompt_session /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_release_at_exit /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_scroll /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_server /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_server_minimal /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_standalone_render_overlays /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_standalone_render_to_fb /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_proving_server /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407558] Re: Mir reports vertical refresh rates slightly inaccurately
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Low ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407558 Title: Mir reports vertical refresh rates slightly inaccurately Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: mirout says: Output 19: Card 0, HDMI-A, connected, 1920x1200+0+0, used, on, 520mm x 330mm (24.2"), normal 1920x1200 60.0*+ 1600x1200 60.0 1680x1050 59.9 1280x1024 75.060.0 1152x864 75.0 1024x768 75.160.0 800x600 75.060.3 640x480 75.060.0 720x400 70.1 Actually that first 60.0 is more like 59.94. It's just that we've rounded the result, both in mirout and also in: src/platforms/mesa/real_kms_display_configuration.cpp:return round(vrefresh_hz * 10.0) / 10.0; Then again, it's normal for the industry to knowingly refer to 59.94Hz as "60Hz", or 23.976Hz as "24Hz" etc. So low priority for now. Maybe even Won't Fix... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1407558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395405] Re: Mir fails to start when a TV is connected by HDMI [std::exception::what: Invalid or inconsistent display configuration]
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1395405 Title: Mir fails to start when a TV is connected by HDMI [std::exception::what: Invalid or inconsistent display configuration] Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir fails to start when a TV is connected by HDMI... $ sudo mir_demo_server_shell --display-config=single --vt 1 ERROR: /build/buildd/mir-0.8.0+14.10.20141010/src/platform/graphics/mesa/display.cpp(141): Throw in function virtual void mir::graphics::mesa::Display::configure(const mir::graphics::DisplayConfiguration&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Invalid or inconsistent display configuration $ sudo mir_demo_server_shell --display-config=sidebyside --vt 1 ERROR: /build/buildd/mir-0.8.0+14.10.20141010/src/platform/graphics/mesa/display.cpp(141): Throw in function virtual void mir::graphics::mesa::Display::configure(const mir::graphics::DisplayConfiguration&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Invalid or inconsistent display configuration To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1395405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274359] Re: Screen goes blank (black) briefly during display config changes which don't affect the display mode
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1274359 Title: Screen goes blank (black) briefly during display config changes which don't affect the display mode Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: The screen goes blank (black) briefly during display config changes, on desktop (mesa platform). For mode changes I think this is expected, but it also happens for non-mode changes like screen rotation and probably repositioning. TEST CASE: 1. Run mir_demo_server_shell 2. Start a client you can see on screen 3. Invoke a display config change with screen rotation: Ctrl+Alt+(arrow key) Expected: Instant rotation Observed: Screen blanks briefly before rotating. The blackness is very brief, but I think we can do better. By avoiding unnecessary destruction and reconstruction of mesa::DisplayBuffer's each time. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1274359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395762] Re: File descriptor leaks in tests using UsingStubClientPlatform
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1395762 Title: File descriptor leaks in tests using UsingStubClientPlatform Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: The stub implementation of mcl::ClientBuffer(Factory) leaks the fds passed to it through MirBufferPackage. These leaks cause the affected tests to hang after some number of iterations (--gtest_repeat) making stress testing difficult. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1395762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407783] Re: acceptance-tests FAIL: TestClientInput.hidden_clients_do_not_receive_pointer_events fails
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407783 Title: acceptance-tests FAIL: TestClientInput.hidden_clients_do_not_receive_pointer_events fails Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Failure observed during silo build : 43: Test command: /build/buildd/mir-0.10.0+15.04.20150105/obj-i686-linux-gnu/bin/mir_acceptance_tests "--gtest_filter=TestClientInput.*" 43: Test timeout computed to be: 9.99988e+06 43: [1420483369.681871] (II) SharedLibrary: Loading libmirplatform5driver.so 43: Running main() from command_line_server_configuration.cpp 43: Note: Google Test filter = TestClientInput.* 43: [==] Running 11 tests from 1 test case. 43: [--] Global test environment set-up. 43: [--] 11 tests from TestClientInput 43: [ RUN ] TestClientInput.clients_receive_key_input 43: [1420483369.688794] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_key_input (17 ms) 43: [ RUN ] TestClientInput.clients_receive_us_english_mapped_keys 43: [1420483369.705733] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_us_english_mapped_keys (15 ms) 43: [ RUN ] TestClientInput.clients_receive_motion_inside_window 43: [1420483369.720313] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_motion_inside_window (25 ms) 43: [ RUN ] TestClientInput.clients_receive_button_events_inside_window 43: [1420483369.745648] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_button_events_inside_window (15 ms) 43: [ RUN ] TestClientInput.multiple_clients_receive_motion_inside_windows 43: [1420483369.760227] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.multiple_clients_receive_motion_inside_windows (40 ms) 43: [ RUN ] TestClientInput.clients_do_not_receive_motion_outside_input_region 43: [1420483369.800193] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_do_not_receive_motion_outside_input_region (15 ms) 43: [ RUN ] TestClientInput.scene_obscure_motion_events_by_stacking 43: [1420483369.815204] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.scene_obscure_motion_events_by_stacking (24 ms) 43: [ RUN ] TestClientInput.hidden_clients_do_not_receive_pointer_events 43: [1420483369.839523] (II) DisplayServer: Mir version 0.10.0 43: /build/buildd/mir-0.10.0+15.04.20150105/tests/acceptance-tests/throwback/test_client_input.cpp:479: Failure 43: Actual function call count doesn't match EXPECT_CALL(client1.handler, handle_input(mt::MotionEventWithPosition(2, 2)))... 43: Expected: to be called once 43:Actual: never called - unsatisfied and active 43: [ FAILED ] TestClientInput.hidden_clients_do_not_receive_pointer_events (10014 ms) 43: [ RUN ] TestClientInput.clients_receive_motion_within_coordinate_system_of_window 43: [1420483379.853178] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_motion_within_coordinate_system_of_window (18 ms) 43: [ RUN ] TestClientInput.usb_direct_input_devices_work 43: [1420483379.870675] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.usb_direct_input_devices_work (37 ms) 43: [ RUN ] TestClientInput.send_mir_input_events_through_surface 43: [1420483379.908527] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.send_mir_input_events_through_surface (9 ms) 43: [--] 11 tests from TestClientInput (10229 ms total) 43: 43: [--] Global test environment tear-down 43: [==] 11 tests from 1 test case ran. (10230 ms total) 43: [ PASSED ] 10 tests. 43: [ FAILED ] 1 test, listed below: 43: [ FAILED ] TestClientInput.hidden_clients_do_not_receive_pointer_events 43: 43: 1 FAILED TEST 43/265 Test #43: mir_acceptance_tests.TestClientInput.* ***Failed 10.25 sec [1420483369.681871] (II) SharedLibrary: Loading libmirplatform5driver.so Running main() from command_line_server_configuration.cpp Note: Google Test filter = TestClientInput.* [==] Running 11 tests from 1 test case. [--] Global test environment set-up. [--] 11 tests from TestClientInput [ RUN ] TestClientInput.clients_receive_key_input [1420483369.688794] (II) DisplayServer: Mir version 0.10.0 [ OK ] TestClientInput.clients_receive_key_input (17 ms) [ RUN
[Touch-packages] [Bug 1402160] Re: Leaks in death tests can cause subsequent tests in the same process to fail
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1402160 Title: Leaks in death tests can cause subsequent tests in the same process to fail Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: To reproduce: valgrind --error-exitcode=1 --trace-children=yes --leak-check=full --show-leak-kinds=definite --errors-for-leak-kinds=definite bin/mir_acceptance_tests --gtest_filter=ClientLibraryErrorsDeathTest*:ClientLibraryThread* The ClientLibraryThread tests should pass and not report any definite leaks. It's expected to get leaks from the DeathTests. Note that for me (and Daniel, see [1]), this is still a problem even with Christopher's fix ([2]). So, this is a real issue, just not the one that was blocking CI. I don't know why on some setups (e.g. Alan's) this fix seems to have no effect. Perhaps it was a combination of this leak and the one fixed by Chris that complicated the situation, and now that the other leak is fixed this will work properly on all setups. [1] https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526/comments/603009 [2] https://code.launchpad.net/~raof/mir/fix-all-the-CI/+merge/244526 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1402160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407557] Re: [regression] Mir utils can't run from the build tree any more
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407557 Title: [regression] Mir utils can't run from the build tree any more Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir utils can't run from the build tree any more... $ bin/mirping Could not connect to a display server. $ sudo bin/mirping Could not connect to a display server. $ sudo bin/mirout Could not connect to a display server. $ bin/mirout Could not connect to a display server. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1407557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401373] Re: dpkg-shlibdeps: Lots of warnings about libmirplatformstub.so
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1401373 Title: dpkg-shlibdeps: Lots of warnings about libmirplatformstub.so Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: dpkg-shlibdeps: warning: symbol _ZN3mir8graphics30UserDisplayConfigurationOutputC1ERNS0_26DisplayConfigurationOutputE used by debian/mir-test-tools/usr/lib/x86_64-linux-gnu/libmirplatformstub.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK3mir8graphics20DisplayConfiguration5validEv used by debian/mir-test-tools/usr/lib/x86_64-linux-gnu/libmirplatformstub.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN3mir2FdC1ENS_10IntOwnedFdE used by debian/mir-test-tools/usr/lib/x86_64-linux-gnu/libmirplatformstub.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN3mir8graphics11BufferBasicC2Ev used by debian/mir-test-tools/usr/lib/x86_64-linux-gnu/libmirplatformstub.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZTIN3mir8graphics20DisplayConfigurationE used by debian/mir-test-tools/usr/lib/x86_64-linux-gnu/libmirplatformstub.so found in none of the libraries To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1401373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394362] Re: fd reception code is not exeception-safe when unexpected numbers of fds are received
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1394362 Title: fd reception code is not exeception-safe when unexpected numbers of fds are received Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: the easiest way to see this is to inspect mir::receive_data, or to run valgrind with track-fds = yes In the wild, this would only leak 1-4 fd's per error. Given the type of errors that would cause this, it would take a lot of rare errors before we hit the process fd limit. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1394362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403702] Re: [regression] demo-shell: Instead of moving surfaces they now fly off-screen
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1403702 Title: [regression] demo-shell: Instead of moving surfaces they now fly off- screen Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: [regression] demo-shell: Instead of moving surfaces they now fly off- screen. Test case: Start demo shell and a client. Try to drag it using Alt+drag. Expected: Surface moves with the mouse. Observed: Surface flies off-screen. I think this change is probably related: revno: 2165 [merge] author: Robert Carr committer: Tarmac branch nick: development-branch timestamp: Wed 2014-12-17 19:10:22 + message: Trivial refactoring in demo shell window_manager.cpp. Approved by Kevin DuBois, PS Jenkins bot, Alan Griffiths. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1403702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406098] Re: [regression] lintian: E: mir-demos: binary-or-shlib-defines-rpath ...
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1406098 Title: [regression] lintian: E: mir-demos: binary-or-shlib-defines-rpath ... Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: [regression] lintian says: Now running lintian... E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_basic /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_cursors /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_display_config /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglcounter /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglflash /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_eglplasma /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_egltriangle /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_fingerpaint /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_flicker /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_multiwin /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_progressbar /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_prompt_session /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_release_at_exit /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_client_scroll /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_server /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_server_minimal /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_standalone_render_overlays /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_demo_standalone_render_to_fb /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib E: mir-demos: binary-or-shlib-defines-rpath usr/bin/mir_proving_server /home/dan/bzr/mir/dev/obj-x86_64-linux-gnu/lib To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398294] Re: DisplayLayout resizes a surface to 1x1 if you ask it to fullscreen a surface that's partially offscreen
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398294 Title: DisplayLayout resizes a surface to 1x1 if you ask it to fullscreen a surface that's partially offscreen Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: PlacementStrategy/DisplayLayout resizes a surface to 1x1 (and moves it to 0,0) if you ask it to fullscreen a surface that's partially offscreen To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395762] Re: File descriptor leaks in tests using UsingStubClientPlatform
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1395762 Title: File descriptor leaks in tests using UsingStubClientPlatform Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: The stub implementation of mcl::ClientBuffer(Factory) leaks the fds passed to it through MirBufferPackage. These leaks cause the affected tests to hang after some number of iterations (--gtest_repeat) making stress testing difficult. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1395762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401365] Re: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1401365 Title: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Another CI blockage: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere dh_install: missing files, aborting debian/rules:60: recipe for target 'override_dh_install' failed To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1401365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391488] Re: [testfail] BasicThreadPool.recycles_threads in CI
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1391488 Title: [testfail] BasicThreadPool.recycles_threads in CI Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid- armhf/37/console [ RUN ] BasicThreadPool.recycles_threads /tmp/buildd/mir-0.8.0+14.10.20141010bzr2030pkg0vivid37+autopilot0/tests/unit-tests/thread/test_basic_thread_pool.cpp:178: Failure Value of: task3.thread_name() Expected: (is equal to "thread1") or (is equal to "thread2") Actual: "memcheck-arm-li" (of type std::string) disInstr(thumb): unhandled instruction: 0xDEFF 0xF893 [ FAILED ] BasicThreadPool.recycles_threads (212 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1391488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394221] Re: acceptance_tests are too chatty
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1394221 Title: acceptance_tests are too chatty Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: acceptance tests have started becoming obfuscated with messages that are not related to what is being tested: eg: [--] 3 tests from ServerSignal [ RUN ] ServerSignal.terminate_handler_is_called_for_SIGTERM [1416406602.185984] (II) UnknownComponent: Starting Mir server [1416406602.200318] (II) UnknownComponent: Stopping Mir Server [1416406602.204740] (II) UnknownComponent: Stopping Mir Server [ OK ] ServerSignal.terminate_handler_is_called_for_SIGTERM (22 ms) [ RUN ] ServerSignal.terminate_handler_is_called_for_SIGINT [1416406602.207911] (II) UnknownComponent: Starting Mir server [1416406602.221617] (II) UnknownComponent: Stopping Mir Server [1416406602.226197] (II) UnknownComponent: Stopping Mir Server [ OK ] ServerSignal.terminate_handler_is_called_for_SIGINT (22 ms) [ RUN ] ServerSignal.multiple_cleanup_handlers_are_called [1416406602.229390] (II) UnknownComponent: Starting Mir server [ OK ] ServerSignal.multiple_cleanup_handlers_are_called (198 ms) [--] 3 tests from ServerSignal (242 ms total) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1394221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382209] Re: [Enhancement] Add an API to lock surface orientation
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1382209 Title: [Enhancement] Add an API to lock surface orientation Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Sometimes, applications are written to take advantage of the entire surface of screen. So they need a way to tell MIR, the orientation they want for drawing themselves. This can be portrait for some, landscape for others, or even combinations. Without this feature, portrait application get distorted when running in a landscape oriented device. So, it would be nice to have an API, in MIR client, to precisely lock the orientation of the MirSurface used for drawing. My use case is a full-screen game, that require always Portrait Orientation. Another is a full-screen game that requires always Landscape. Better (future): - allow this even for non full-screen applications - allow combination like Portait+PortraitUpsideDown, or LandscapeLeft+LandscapeRight - allow to change the orientation when the application run (so not only when creating/requesting the surface). Remarks : - touch event may need to be translated into the correct coordinates system! To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1382209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384950] Re: Trusted prompts need to be part of the lifecycle
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1384950 Title: Trusted prompts need to be part of the lifecycle Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in pay-service package in Ubuntu: New Status in trust-store package in Ubuntu: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: After we fix bug #1355173, we'll be "leaking" trusted prompts in the sense that when an app gets unfocused (and potentially killed subsequently), the trusted prompts will be left running, not suspended with the app. We should apply the same rules to the whole app container (can we use ual? add the prompts to the pgroup/cgroup?). This needs an escape route, too, for trusted helpers to be able to kill prompts as they need to. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1384950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379685] Re: Full screen (bypassed) surfaces (e.g. GLMark2Test) are missing frames and appear to freeze or judder with swap interval 0
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1379685 Title: Full screen (bypassed) surfaces (e.g. GLMark2Test) are missing frames and appear to freeze or judder with swap interval 0 Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: I'm observing missing client frames when swap interval is set to zero. Test case (1): https://code.launchpad.net/~vanvugt/mir/wacky/+merge/237907 Test case (2): sudo bin/mir_performance_tests Expected: Perfect smoothness Observed: Constant slight visible judder during all the animations. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1379685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398296] Re: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398296 Title: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen/bypass a surface in multimonitor clone mode. ERROR: /home/dan/bzr/mir/fullscreen/src/platform/fatal/fatal.cpp(55): Throw in function void mir::fatal_error_except(const char*, ...) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Failed to get front buffer object Mesa only has a fixed limit of (four?) front framebuffer objects available. So somehow the combination of fullscreen bypass and multimonitor is making us ask for more than that... (?) Sorry I don't have a test case to reproduce it easily yet without using my own custom branch. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400218] Re: Surfaces can consume input events before they're visible.
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1400218 Title: Surfaces can consume input events before they're visible. Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Surfaces can consume input events before they're visible. This is because BasicSurface only checks the "hidden" flag and doesn't remember to check other factors that might make the surface invisible. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1400218/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400218] Re: Surfaces can consume input events before they're visible.
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1400218 Title: Surfaces can consume input events before they're visible. Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Surfaces can consume input events before they're visible. This is because BasicSurface only checks the "hidden" flag and doesn't remember to check other factors that might make the surface invisible. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1400218/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264934] Re: Mir's compositor holds buffers (blocking clients) for the duration of the frame, even when not necessary.
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1264934 Title: Mir's compositor holds buffers (blocking clients) for the duration of the frame, even when not necessary. Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: RenderingOperator::operator() holds buffers (blocking clients) for the duration of the frame, even when not necessary. From what I can tell, the holding of the buffer as a "resource" till after the SwapBuffers is required for some APIs, such as glEGLImageTargetTexture2DOES used by Mir "hardware" buffers. However, Mir software buffers use a simple glTexImage2D which only does a synchronous copy of the data. So it's wasteful holding a reference to the buffer for any longer than the duration of the glTexImage2D call. This will directly affect the round-trip performance of mir_surface_swap_buffers() while bug 1253868 is unresolved. So in theory, just making our "saved resources" logic a little smarter could significantly improve clients ability to meet frame deadlines. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1264934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274359] Re: Screen goes blank (black) briefly during display config changes which don't affect the display mode
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1274359 Title: Screen goes blank (black) briefly during display config changes which don't affect the display mode Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: The screen goes blank (black) briefly during display config changes, on desktop (mesa platform). For mode changes I think this is expected, but it also happens for non-mode changes like screen rotation and probably repositioning. TEST CASE: 1. Run mir_demo_server_shell 2. Start a client you can see on screen 3. Invoke a display config change with screen rotation: Ctrl+Alt+(arrow key) Expected: Instant rotation Observed: Screen blanks briefly before rotating. The blackness is very brief, but I think we can do better. By avoiding unnecessary destruction and reconstruction of mesa::DisplayBuffer's each time. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1274359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304257] Re: [enhancement] There should be a quit signal sent to sessions instead of killing them directly
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1304257 Title: [enhancement] There should be a quit signal sent to sessions instead of killing them directly Status in Mir: Fix Released Status in Qt integration with the Mir display server: New Status in Unity Mir: Confirmed Status in mir package in Ubuntu: Fix Released Status in system-image package in Ubuntu: Confirmed Status in unity-mir package in Ubuntu: Confirmed Bug description: The task manager currently kills (upstart-stops) the apps upon the user requesting it to stop. It should send a quit signal instead (and SIGCONT it first, if stopped), so that the app can shut down gracefully. A method to forcefully quit the app is needed, too, if it's not responding (or maybe even just timeout-based). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity-mir1 0.3+14.04.20140401.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 8 09:17:00 2014 SourcePackage: unity-mir UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1304257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1212753] Re: [i865] unity-system-compositor fails to start: Failed to choose ARGB EGL config
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1212753 Title: [i865] unity-system-compositor fails to start: Failed to choose ARGB EGL config Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: After installing unity-system-compositor it appears that it does not start, and in /var/log/lightdm/unity-system-compositor.log is ERROR: /build/buildd/mir-0.0.9+13.10.20130813/src/server/graphics/gbm/gbm_display_helpers.cpp(457): Throw in function void mir::graphics::gbm::helpers::EGLHelper::setup_internal(const mir::graphics::gbm::helpers::GBMHelper&, bool) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to choose ARGB EGL config ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-system-compositor 0.0.1+13.10.20130813.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic i686 ApportVersion: 2.12-0ubuntu3 Architecture: i386 Date: Thu Aug 15 17:36:12 2013 InstallationDate: Installed on 2013-08-15 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130815) MarkForUpload: True SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1212753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1216727] Re: Mir server crashed: Requesting handle for an unregistered channel
mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium ** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Critical ** Changed in: mir (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1216727 Title: Mir server crashed: Requesting handle for an unregistered channel Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: If I run mir_stress and a second app, just the act of moving the mouse around often causes the server to crash: terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' what(): Requesting handle for an unregistered channel TESTCASE: 1. Start mir_demo_server_shell 2. Start mir_stress 3. Start mir_demo_client_egltriangle 4. Move the mouse around, and drag egltriangle around (Alt+drag) Expected: Everything keeps running Observed: mir_demo_server_shell crashes To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1216727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403702] Re: [regression] demo-shell: Instead of moving surfaces they now fly off-screen
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1403702 Title: [regression] demo-shell: Instead of moving surfaces they now fly off- screen Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: [regression] demo-shell: Instead of moving surfaces they now fly off- screen. Test case: Start demo shell and a client. Try to drag it using Alt+drag. Expected: Surface moves with the mouse. Observed: Surface flies off-screen. I think this change is probably related: revno: 2165 [merge] author: Robert Carr committer: Tarmac branch nick: development-branch timestamp: Wed 2014-12-17 19:10:22 + message: Trivial refactoring in demo shell window_manager.cpp. Approved by Kevin DuBois, PS Jenkins bot, Alan Griffiths. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1403702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384950] Re: Trusted prompts need to be part of the lifecycle
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1384950 Title: Trusted prompts need to be part of the lifecycle Status in Mir: Fix Released Status in mir package in Ubuntu: New Status in pay-service package in Ubuntu: New Status in trust-store package in Ubuntu: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: After we fix bug #1355173, we'll be "leaking" trusted prompts in the sense that when an app gets unfocused (and potentially killed subsequently), the trusted prompts will be left running, not suspended with the app. We should apply the same rules to the whole app container (can we use ual? add the prompts to the pgroup/cgroup?). This needs an escape route, too, for trusted helpers to be able to kill prompts as they need to. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1384950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391975] Re: USC - mouse cursor on AMD graphics is drawing incorrectly
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1391975 Title: USC - mouse cursor on AMD graphics is drawing incorrectly Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: I've a Lenovo Flex 2 14D, which has an AMD APU. In Unity-System-Compositor, I noticed the mouse cursor does not draw correctly. See photo attached To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1391975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in The "G" Library - GLib: New Status in Mir: Fix Released Status in Mir 0.9 series: Triaged Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350716] Re: CompositorReport as used by DefaultDisplayBufferCompositor can't measure render time
** Changed in: mir
Status: Fix Committed => Fix Released
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1350716
Title:
CompositorReport as used by DefaultDisplayBufferCompositor can't
measure render time
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
CompositorReport as used by DefaultDisplayBufferCompositor can't
measure render time.
Presently we have:
// [A]
report->began_frame(this);
...
if (display_buffer.post_renderables_if_optimizable(renderable_list)) //
[B] before page flip
{
renderer->suspend();
report->finished_frame(true, this);
}
else
{
display_buffer.make_current();
renderer->set_rotation(display_buffer.orientation());
renderer->begin(); // TODO deprecatable now?
renderer->render(renderable_list);
display_buffer.post_update(); // swap buffers, [B], then page flip
renderer->end();
report->finished_frame(false, this);
}
// [C]
Compositor report correctly reports "frame time" as [C]-[A]. However a
more useful measure is render time which is [B]-[A]. But we can't do
that yet as we'd have to insert a reporting point in the middle of the
post_ functions (or split them) so as to not include page flipping
time in "render time", while still including the final eglSwapBuffers
(if any).
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1350716/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401365] Re: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1401365 Title: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Another CI blockage: dh_install: usr/bin/mir_demo_server exists in debian/tmp but is not installed to anywhere dh_install: missing files, aborting debian/rules:60: recipe for target 'override_dh_install' failed To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1401365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395405] Re: Mir fails to start when a TV is connected by HDMI [std::exception::what: Invalid or inconsistent display configuration]
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1395405 Title: Mir fails to start when a TV is connected by HDMI [std::exception::what: Invalid or inconsistent display configuration] Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Mir fails to start when a TV is connected by HDMI... $ sudo mir_demo_server_shell --display-config=single --vt 1 ERROR: /build/buildd/mir-0.8.0+14.10.20141010/src/platform/graphics/mesa/display.cpp(141): Throw in function virtual void mir::graphics::mesa::Display::configure(const mir::graphics::DisplayConfiguration&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Invalid or inconsistent display configuration $ sudo mir_demo_server_shell --display-config=sidebyside --vt 1 ERROR: /build/buildd/mir-0.8.0+14.10.20141010/src/platform/graphics/mesa/display.cpp(141): Throw in function virtual void mir::graphics::mesa::Display::configure(const mir::graphics::DisplayConfiguration&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Invalid or inconsistent display configuration To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1395405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396006] Re: Input/event driven clients may freeze indefinitely
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1396006 Title: Input/event driven clients may freeze indefinitely Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Input/event driven clients may freeze indefinitely. This is a more generalized form of bug 1379685 that can happen with any windowed app too. The issue is: if (!ready_to_composite_queue.empty()) drop_frame(std::move(lock)); may drop the newest available frame in some cases: (ready_to_composite_queue.size() == 1 && contains(current_compositor_buffer, buffers_sent_to_compositor)) So when this happens, we're dropping the latest frame without any guarantees that the client will redraw another. Because a perfectly efficient event-driven app will only redraw when something changes (e.g. input event) and won't redraw just because a new buffer is available. So giving a buffer back to the client won't wake it up. The simple answer is to ensure you only drop frames when it's proven that you're not dropping the newest one. Because the time to the next frame after that is completely unpredictable and indefinite... if (ready_to_composite_queue.size() > 1) drop_frame(std::move(lock)); // worst case: the newest frame still gets composited. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1396006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311699] Re: MirMotionEvent.action needs stronger typing (to MirMotionAction etc)
** Changed in: mir
Status: Fix Committed => Fix Released
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1311699
Title:
MirMotionEvent.action needs stronger typing (to MirMotionAction etc)
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
MirMotionEvent.action is currently an int for legacy android
compatibility reasons. We need to clean this up and use
MirMotionAction properly, unlike in examples...
MirMotionAction action =
static_cast(event.motion.action & ~0xff00);
OLD DESCRIPTION:
MirEvent::action is currently effectively an opaque value, as Mir headers do
not specify its meaning.
So event.h must either define counterparts to the android
AMOTION_EVENT_ACTION_* values below or split up the action and pointer
index into separate variables.
"""
/* Bit shift for the action bits holding the pointer index as
* defined by AMOTION_EVENT_ACTION_POINTER_INDEX_MASK.
*/
#define AMOTION_EVENT_ACTION_POINTER_INDEX_SHIFT 8
enum {
/* Bit mask of the parts of the action code that are the action itself.
*/
AMOTION_EVENT_ACTION_MASK = 0xff,
/* Bits in the action code that represent a pointer index, used with
* AMOTION_EVENT_ACTION_POINTER_DOWN and AMOTION_EVENT_ACTION_POINTER_UP.
Shifting
* down by AMOTION_EVENT_ACTION_POINTER_INDEX_SHIFT provides the actual
pointer
* index where the data for the pointer going up or down can be found.
*/
AMOTION_EVENT_ACTION_POINTER_INDEX_MASK = 0xff00,
"""
Right now in the "Qt compositor" code I had to resort to locally
defining those values, which is a hack:
""
// from android-input AMOTION_EVENT_ACTION_*, hidden inside mir bowels
// mir headers should define them
const int QtEventFeeder::MirEventActionMask = 0xff;
const int QtEventFeeder::MirEventActionPointerIndexMask = 0xff00;
const int QtEventFeeder::MirEventActionPointerIndexShift = 8;
""
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1311699/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398984] Re: Bootloop with system language Turkish on the Nexus 4
** Changed in: mir Status: Fix Committed => Fix Released ** Changed in: mir/0.9 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398984 Title: Bootloop with system language Turkish on the Nexus 4 Status in Mir: Fix Released Status in Mir 0.8 series: Triaged Status in Mir 0.9 series: Won't Fix Status in mir package in Ubuntu: Fix Released Status in mir package in Ubuntu RTM: Triaged Bug description: Lately, a member (Ümit) of the XDA Developers forum reported that his Nexus 4 always goes into a bootloop when he sets the system language to Turkish. It doesn't matter whether he sets it in the system settings wizard which is shown on first boot or in the system settings application. If he sets it in the system settings wizard, he won't get to see the OS after finishing the setup process, and if he changes the language in the system settings application, the phone will hang after a reboot. In any case, he will see the spinning "circle of friends" logo but the Unity8 dash will never appear. Here's the link to his first forum post regarding it issue. The discussion continues on the next few pages: http://forum.xda-developers.com/nexus-4/general/rom-ubuntu-touch-14-10-utopic-unico-t2324683/post57093935#post57093935 He's running build #10 in the stable Ubuntu RTM channel. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398296] Re: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1398296 Title: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen/bypass a surface in multimonitor clone mode. ERROR: /home/dan/bzr/mir/fullscreen/src/platform/fatal/fatal.cpp(55): Throw in function void mir::fatal_error_except(const char*, ...) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Failed to get front buffer object Mesa only has a fixed limit of (four?) front framebuffer objects available. So somehow the combination of fullscreen bypass and multimonitor is making us ask for more than that... (?) Sorry I don't have a test case to reproduce it easily yet without using my own custom branch. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401364] Re: CI test failure in multiple tests
** Changed in: mir
Status: Fix Committed => Fix Released
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1401364
Title:
CI test failure in multiple tests
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
Multiple tests fail in a similar fashion:
https://jenkins.qa.ubuntu.com/job/mir-vivid-amd64-ci/352/consoleFull
For example:
ClientLibraryThread.handles_no_signals fails due to memory leak
(valgrind)
8: [ RUN ] ClientLibraryThread.handles_no_signals
8: ==10098==
8: ==10098== HEAP SUMMARY:
8: ==10098== in use at exit: 10,826 bytes in 83 blocks
8: ==10098== total heap usage: 254,821 allocs, 254,738 frees, 16,598,040
bytes allocated
8: ==10098==
8: ==10098== 92 (64 direct, 28 indirect) bytes in 1 blocks are definitely
lost in loss record 63 of 83
8: ==10098==at 0x4C2B100: operator new(unsigned long) (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
8: ==10098==by 0x5288C3C: allocate (new_allocator.h:104)
8: ==10098==by 0x5288C3C: allocate (alloc_traits.h:357)
8: ==10098==by 0x5288C3C:
__shared_count()>
>,
std::allocator()>
> >,
std::_Bind_simple()>
> (shared_ptr_base.h:616)
8: ==10098==by 0x5288C3C:
__shared_ptr()>
> >,
std::_Bind_simple()>
> (shared_ptr_base.h:1090)
8: ==10098==by 0x5288C3C:
shared_ptr()>
> >,
std::_Bind_simple()>
> (shared_ptr.h:316)
8: ==10098==by 0x5288C3C:
allocate_shared()>
>,
std::allocator()>
> >,
std::_Bind_simple()>
> (shared_ptr.h:588)
8: ==10098==by 0x5288C3C:
make_shared()>
>,
std::_Bind_simple()>
> (shared_ptr.h:604)
8: ==10098==by 0x5288C3C:
_M_make_routine()>
> (thread:196)
8: ==10098==by 0x5288C3C:
thread >
(thread:138)
8: ==10098==by 0x5288C3C: mir::client::rpc::StreamSocketTransport::init()
(stream_socket_transport.cpp:188)
8: ==10098==by 0x5289A62:
mir::client::rpc::StreamSocketTransport::StreamSocketTransport(mir::Fd const&)
(stream_socket_transport.cpp:41)
8: ==10098==by 0x527B894: mir::client::rpc::make_rpc_channel(std::string
const&, std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&,
std::shared_ptr const&) (make_socket_rpc_channel.cpp:55)
8: ==10098==by 0x5271DB3: operator()
(default_connection_configuration.cpp:92)
8: ==10098==by 0x5271DB3:
std::_Function_handler (),
mir::client::DefaultConnectionConfiguration::the_rpc_channel()::{lambda()#1}>::_M_invoke(std::_Any_data
const&) (functional:2025)
8: ==10098==by 0x5272648: operator() (functional:2439)
8: ==10098==by 0x5272648: operator() (cached_ptr.h:41)
8: ==10098==by 0x5272648:
mir::client::DefaultConnectionConfiguration::the_rpc_channel()
(default_connection_configuration.cpp:92)
8: ==10098==by 0x525DE95:
MirConnection::MirConnection(mir::client::ConnectionConfiguration&)
(mir_connection.cpp:108)
8: ==10098==by 0x52625EE: connect (mir_connection_api.cpp:78)
8: ==10098==by 0x52625EE: mir_connect (mir_connection_api.cpp:143)
8: ==10098==by 0x5CB7D1: ClientLibrary_creates_surface_Test::TestBody()
(test_client_library.cpp:180)
8: ==10098==by 0x7AB7A2:
HandleSehExceptionsInMethodIfSupported (gtest.cc:2078)
8: ==10098==by 0x7AB7A2: void
testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) (gtest.cc:2114)
8: ==10098==by 0x7A1403: testing::Test::Run() (gtest.cc:2151)
8: ==10098==by 0x7A1527: testing::TestInfo::Run() [clone .part.372]
(gtest.cc:2326)
8: ==10098==
8: ==10098== LEAK SUMMARY:
8: ==10098==definitely lost: 64 bytes in 1 blocks
8: ==10098==indirectly lost: 28 bytes in 2 blocks
8: ==10098== possibly lost: 426 bytes in 10 blocks
8: ==10098==still reachable: 10,308 bytes in 70 blocks
8: ==10098== suppressed: 0 bytes in 0 blocks
8: ==10098== Reachable blocks (those to which a pointer was found) are not
shown.
8: ==10098== To see them, rerun with: --leak-check=full --show-leak-kinds=all
8: ==10098==
8: ==10098== For counts of detected and suppressed errors, rerun with: -v
8: ==10098== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
8:
/tmp/buildd/mir-0.9.0+15.04.20141125bzr2141pkg0vivid331/tests/mir_test_framework/interprocess_client_server_test.cpp:90:
Failure
8: Value of: result.exit_code
8: Expected: is equal to 0
8: Actual: 1 (of type int)
8: ==10090==
8: ==10090== HEAP SUMMARY:
8: ==10090== in use at exit: 11,727 bytes in 86 blocks
8: ==10090== total heap usage: 258,445 allocs, 258,359 frees, 16,749,998
bytes allocated
8: ==10090==
8: ==10090== 92 (64 direct, 28 indirect) bytes in 1 blocks are definitely
lost in loss record 64 of 86
[Touch-packages] [Bug 1406073] Re: [regression] Binaries are no longer runnable on other machines (or in other directories)
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1406073 Title: [regression] Binaries are no longer runnable on other machines (or in other directories) Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Binaries are no longer runnable when copied to other hosts: # bin/mir_proving_server Failed to execute real binary .mir_proving_server-uninstalled: No such file or directory # ls -l bin/.mir_proving_server-uninstalled -rwxrwxr-x 1 dan dan 3064944 Dec 28 16:36 bin/.mir_proving_server-uninstalled and # ./mir_proving_server Failed to execute real binary .mir_proving_server-uninstalled: No such file or directory # ls -l .mir_proving_server-uninstalled -rwxrwxr-x 1 dan dan 3064944 Dec 28 16:36 .mir_proving_server-uninstalled and starting the hidden server directly works, but then clients can't find it: # bin/.mir_proving_server-uninstalled & # bin/.mir_demo_client_egltriangle-uninstalled Can't get connection # bin/.mir_demo_client_flicker-uninstalled Starting .mir_demo_client_flicker-uninstalled: /home/dan/bzr/mir/dev/examples/flicker.c:134: main: Assertion `mir_connection_is_valid(connection)' failed. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407783] Re: acceptance-tests FAIL: TestClientInput.hidden_clients_do_not_receive_pointer_events fails
** Changed in: mir Status: Fix Committed => Fix Released ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1407783 Title: acceptance-tests FAIL: TestClientInput.hidden_clients_do_not_receive_pointer_events fails Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Failure observed during silo build : 43: Test command: /build/buildd/mir-0.10.0+15.04.20150105/obj-i686-linux-gnu/bin/mir_acceptance_tests "--gtest_filter=TestClientInput.*" 43: Test timeout computed to be: 9.99988e+06 43: [1420483369.681871] (II) SharedLibrary: Loading libmirplatform5driver.so 43: Running main() from command_line_server_configuration.cpp 43: Note: Google Test filter = TestClientInput.* 43: [==] Running 11 tests from 1 test case. 43: [--] Global test environment set-up. 43: [--] 11 tests from TestClientInput 43: [ RUN ] TestClientInput.clients_receive_key_input 43: [1420483369.688794] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_key_input (17 ms) 43: [ RUN ] TestClientInput.clients_receive_us_english_mapped_keys 43: [1420483369.705733] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_us_english_mapped_keys (15 ms) 43: [ RUN ] TestClientInput.clients_receive_motion_inside_window 43: [1420483369.720313] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_motion_inside_window (25 ms) 43: [ RUN ] TestClientInput.clients_receive_button_events_inside_window 43: [1420483369.745648] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_button_events_inside_window (15 ms) 43: [ RUN ] TestClientInput.multiple_clients_receive_motion_inside_windows 43: [1420483369.760227] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.multiple_clients_receive_motion_inside_windows (40 ms) 43: [ RUN ] TestClientInput.clients_do_not_receive_motion_outside_input_region 43: [1420483369.800193] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_do_not_receive_motion_outside_input_region (15 ms) 43: [ RUN ] TestClientInput.scene_obscure_motion_events_by_stacking 43: [1420483369.815204] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.scene_obscure_motion_events_by_stacking (24 ms) 43: [ RUN ] TestClientInput.hidden_clients_do_not_receive_pointer_events 43: [1420483369.839523] (II) DisplayServer: Mir version 0.10.0 43: /build/buildd/mir-0.10.0+15.04.20150105/tests/acceptance-tests/throwback/test_client_input.cpp:479: Failure 43: Actual function call count doesn't match EXPECT_CALL(client1.handler, handle_input(mt::MotionEventWithPosition(2, 2)))... 43: Expected: to be called once 43:Actual: never called - unsatisfied and active 43: [ FAILED ] TestClientInput.hidden_clients_do_not_receive_pointer_events (10014 ms) 43: [ RUN ] TestClientInput.clients_receive_motion_within_coordinate_system_of_window 43: [1420483379.853178] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.clients_receive_motion_within_coordinate_system_of_window (18 ms) 43: [ RUN ] TestClientInput.usb_direct_input_devices_work 43: [1420483379.870675] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.usb_direct_input_devices_work (37 ms) 43: [ RUN ] TestClientInput.send_mir_input_events_through_surface 43: [1420483379.908527] (II) DisplayServer: Mir version 0.10.0 43: [ OK ] TestClientInput.send_mir_input_events_through_surface (9 ms) 43: [--] 11 tests from TestClientInput (10229 ms total) 43: 43: [--] Global test environment tear-down 43: [==] 11 tests from 1 test case ran. (10230 ms total) 43: [ PASSED ] 10 tests. 43: [ FAILED ] 1 test, listed below: 43: [ FAILED ] TestClientInput.hidden_clients_do_not_receive_pointer_events 43: 43: 1 FAILED TEST 43/265 Test #43: mir_acceptance_tests.TestClientInput.* ***Failed 10.25 sec [1420483369.681871] (II) SharedLibrary: Loading libmirplatform5driver.so Running main() from command_line_server_configuration.cpp Note: Google Test filter = TestClientInput.* [==] Running 11 tests from 1 test case. [--] Global test environment set-up. [--] 11 tests from TestClientInput [ RUN ] TestClientInput.clients_receive_key_input [1420483369.688794] (II) DisplayServer: Mir version 0.10.0 [ OK ] TestClientInput.clients_receive_key_input (17 ms) [ RUN ] TestClientInput.clients_receive_us_english_mapped_keys
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
No updates? Is there any way I can help diagnose this issue? -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics
filip, I will have to investigate that. There could be any number of reasons why desktop-next doesn't work for you. But I'm confident we've solved the Mir reasons here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics Status in Mir: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Based on this bug: https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1376612 , this is not a regression; the same error occurs in earlier versions of the package too. ** Tags removed: verification-failed verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1400203 Title: libsystemd-login sd_login_monitor_new not working Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Utopic: Fix Committed Bug description: [Impact] The systemd login monitoring library (API: sd_login_monitor_new(3)) is not functional in Utopic. This library is a dependency in NetworkManager, for tracking user sessions. As a result, my laptop does not reconnect to the network after a suspend/resume cycle. There was a patch to fix this in the older, Trusty Tahr version of systemd (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-monitor-no-machine.patch). The patch isn't in the utopic systemd (208-8ubuntu8). This was discovered in a Gnome Fallback session, but I think this KDE issue may be the same thing: https://bugs.kde.org/show_bug.cgi?id=340568 Note: This behavior is only seen when "All users may connect to this network" is un-selected in NetworkManager. NOTE: in order to get a fully working network, I also had to make a change to the upstart script, see: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205 [Test Case] A short C program to demonstrate sd_login_monitor_new is attached to the bug, to demonstrate whether sd_login_monitor_new() is working. To do an end-to-end test, you can stop NetworkManager, re-run it with "NetworkManager --no-daemon", and look for the "Error getting login monitor:" error message. [Regression Potential] Fixing this simply means applying a patch which shipped along with Trusty Tahr's systemd. Since it was widely used already, adding it to Utopic does not appear overly risky. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working
Verified the sd-test.c program, using systemd 208-8ubuntu8.2 in utopic- proposed. -- 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/1400203 Title: libsystemd-login sd_login_monitor_new not working Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Utopic: Fix Committed Bug description: [Impact] The systemd login monitoring library (API: sd_login_monitor_new(3)) is not functional in Utopic. This library is a dependency in NetworkManager, for tracking user sessions. As a result, my laptop does not reconnect to the network after a suspend/resume cycle. There was a patch to fix this in the older, Trusty Tahr version of systemd (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-monitor-no-machine.patch). The patch isn't in the utopic systemd (208-8ubuntu8). This was discovered in a Gnome Fallback session, but I think this KDE issue may be the same thing: https://bugs.kde.org/show_bug.cgi?id=340568 Note: This behavior is only seen when "All users may connect to this network" is un-selected in NetworkManager. NOTE: in order to get a fully working network, I also had to make a change to the upstart script, see: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205 [Test Case] A short C program to demonstrate sd_login_monitor_new is attached to the bug, to demonstrate whether sd_login_monitor_new() is working. To do an end-to-end test, you can stop NetworkManager, re-run it with "NetworkManager --no-daemon", and look for the "Error getting login monitor:" error message. [Regression Potential] Fixing this simply means applying a patch which shipped along with Trusty Tahr's systemd. Since it was widely used already, adding it to Utopic does not appear overly risky. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408747] Re: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1376612 *** https://bugs.launchpad.net/bugs/1376612 ** This bug has been marked a duplicate of bug 1376612 package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: pam-auth-update dies in debconf -- 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/1408747 Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Installed with gui updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libpam-systemd:amd64 208-8ubuntu8.2 Uname: Linux 3.16.6-031606-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Jan 8 13:12:51 2015 DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu8.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-09-18 (476 days ago) InstallationMedia: This SourcePackage: systemd Title: package libpam-systemd:amd64 208-8ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1408747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.3.3
---
apparmor-easyprof-ubuntu (1.3.3) vivid; urgency=medium
* ubuntu/{music,pictures,video}_files*: temporarily allow read access to
global SD card user directory (LP: #1392368). This can be removed once
there is a proper API for apps to find the SD card label.
-- Jamie StrandbogeThu, 08 Jan 2015 14:24:42 -0600
** Changed in: apparmor-easyprof-ubuntu (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-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1392368
Title:
Support storing and viewing photos on an SD card
Status in Camera App:
In Progress
Status in the base for Ubuntu mobile products:
In Progress
Status in Gallery App:
In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Fix Released
Status in camera-app package in Ubuntu:
Fix Released
Status in gallery-app package in Ubuntu:
Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
In Progress
Status in camera-app package in Ubuntu RTM:
In Progress
Status in ciborium package in Ubuntu RTM:
New
Status in gallery-app package in Ubuntu RTM:
In Progress
Bug description:
If an SD card is present we will use it as extended storage for the device.
The camera and gallery apps need to be able to access this storage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1392368/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Changed in: sudo (Ubuntu Precise) Status: New => Invalid ** Changed in: eglibc (Ubuntu Precise) Status: New => Invalid ** Changed in: libnss-ldap (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in eglibc source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in eglibc source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in eglibc source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in eglibc source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in eglibc source package in Precise: Invalid Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: Invalid Status in sudo source package in Precise: Invalid Status in eglibc source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Confirmed Status in libgcrypt11 package in Debian: Confirmed Status in libnss-ldap package in Debian: Confirmed Status in sudo package in Debian: Confirmed Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 & #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Tags removed: glucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in eglibc source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in eglibc source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in eglibc source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in eglibc source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in eglibc source package in Precise: Invalid Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: Invalid Status in sudo source package in Precise: Invalid Status in eglibc source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Confirmed Status in libgcrypt11 package in Debian: Confirmed Status in libnss-ldap package in Debian: Confirmed Status in sudo package in Debian: Confirmed Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 & #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd
** Package changed: openldap (Debian) => libnss-ldap (Debian) ** Bug watch removed: Debian Bug tracker #545414 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545414 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/423252 Title: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd Status in libgcrypt: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in libgcrypt11 package in Ubuntu: Fix Released Status in eglibc source package in Lucid: Invalid Status in libgcrypt11 source package in Lucid: Fix Released Status in libnss-ldap source package in Lucid: Invalid Status in sudo source package in Lucid: Invalid Status in eglibc source package in Maverick: Invalid Status in libgcrypt11 source package in Maverick: Won't Fix Status in libnss-ldap source package in Maverick: Invalid Status in sudo source package in Maverick: Invalid Status in eglibc source package in Natty: Invalid Status in libgcrypt11 source package in Natty: Invalid Status in libnss-ldap source package in Natty: Invalid Status in sudo source package in Natty: Invalid Status in eglibc source package in Oneiric: Invalid Status in libgcrypt11 source package in Oneiric: Invalid Status in libnss-ldap source package in Oneiric: Invalid Status in sudo source package in Oneiric: Invalid Status in eglibc source package in Precise: New Status in libgcrypt11 source package in Precise: Fix Released Status in libnss-ldap source package in Precise: New Status in sudo source package in Precise: New Status in eglibc source package in Karmic: Invalid Status in libgcrypt11 source package in Karmic: Won't Fix Status in libnss-ldap source package in Karmic: Invalid Status in sudo source package in Karmic: Invalid Status in gnutls26 package in Debian: Confirmed Status in libgcrypt11 package in Debian: Confirmed Status in libnss-ldap package in Debian: Confirmed Status in sudo package in Debian: Confirmed Bug description: SRU Request: [Impact] As heavily outlined in the amount of comments in this bug the impact is detrimental to both community and enterprise users alike. [Development Fix] Howard Chu released a patch in #73 which was later confirmed in #106 & #108 as a resolution. [Stable Fix] Patch from #73 can be applied cleanly to Lucid and new distributions. [Test Case] On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd' field to anything with 'ldap' as the first item breaks the ability to become root using 'su' and 'sudo' as anyone but root. Default nsswitch.conf: passwd: compat group: compat shadow: compat matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# Modified nsswitch.conf with 'ldap' before 'compat': passwd: ldap compat group: ldap compat shadow: ldap compat matt@box:~$ sudo uname -a sudo: setreuid(ROOT_UID, user_uid): Operation not permitted matt@box:~$ su - Password: setgid: Operation not permitted Modified nsswitch.conf with 'ldap' after 'compat': passwd: compat ldap group: compat ldap shadow: compat ldap matt@box:~$ sudo uname -a [sudo] password for matt: Linux box 2.6.31-9-server #29-Ubuntu SMP Sun Aug 30 18:37:42 UTC 2009 x86_64 GNU/Linux matt@box:~$ su - Password: root@box:~# The same arrangements in nsswitch.conf work as expected in Jaunty and earlier releases. [Regression Potential] This should be minimal as the code change only addresses the duplicating global_init during thread callbacks. Lucid Release Note: == NSS via LDAP+SSL breaks setuid applications like sudo == Upgrading systems configured to use ldap over ssl as the first service in the nss stack (in nsswitch.conf) leads to a broken nss resolution for setuid applications after the upgrade to Lucid (for example sudo would stop working). There isn't any simple workaround for now. One option is to switch to libnss-ldapd in place of libnss-ldap before the upgrade. Another one consists in using nscd before the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/libgcrypt/+bug/423252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1051935] Re: Fails with SystemError when too many files are open
Just occurred in Trusty as well. ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1051935 Title: Fails with SystemError when too many files are open Status in Python-APT: New Status in gdebi package in Ubuntu: Fix Released Status in oneconf package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in gdebi source package in Precise: Confirmed Status in oneconf source package in Precise: Confirmed Status in python-apt source package in Precise: Fix Released Status in ubiquity source package in Precise: Fix Released Status in gdebi source package in Saucy: Fix Released Status in oneconf source package in Saucy: Fix Released Status in python-apt source package in Saucy: Fix Released Status in ubiquity source package in Saucy: Won't Fix Bug description: [Impact] * Failure to complete installation. [Test Case] * At times, apt cache can run out of file descriptors as seen in this bug and its duplicates. * There is no clear-cut way to reproduce it in ubiquity, but there is a significant amount of crash reports submit, which dropped off after the proposed fix has been applied. [Regression Potential] * The proposed fix has been well tested in trusty both automated & manual testing and does not regress on any configuration. [Other Info] This error occurs each time I try to install a .deb file with Gdebi in Ubuntu 12.10, after the deb installation finishes. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gdebi 0.8.5build1 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 17 15:33:34 2012 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120914) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb'] SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/python-apt/+bug/1051935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card
** Branch linked: lp:ubuntu/vivid-proposed/apparmor-easyprof-ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1392368 Title: Support storing and viewing photos on an SD card Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in Gallery App: In Progress Status in apparmor-easyprof-ubuntu package in Ubuntu: In Progress Status in camera-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu RTM: In Progress Status in camera-app package in Ubuntu RTM: In Progress Status in ciborium package in Ubuntu RTM: New Status in gallery-app package in Ubuntu RTM: In Progress Bug description: If an SD card is present we will use it as extended storage for the device. The camera and gallery apps need to be able to access this storage. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1392368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card
apparmor-easyprof-ubuntu 1.2.40 is in rtm silo 10 and passes tests. Needs QA signoff. Once that happens, custom tarball needs to be regenerated after copying to 14.09. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1392368 Title: Support storing and viewing photos on an SD card Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in Gallery App: In Progress Status in apparmor-easyprof-ubuntu package in Ubuntu: In Progress Status in camera-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in apparmor-easyprof-ubuntu package in Ubuntu RTM: In Progress Status in camera-app package in Ubuntu RTM: In Progress Status in ciborium package in Ubuntu RTM: New Status in gallery-app package in Ubuntu RTM: In Progress Bug description: If an SD card is present we will use it as extended storage for the device. The camera and gallery apps need to be able to access this storage. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1392368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404068] Re: No internet connection with Huawei E3272 4G modem
I have tried to use that page, but was not helpful (nor especially
clear).
In *my* lsusb there is no 14fe id, nor 157c id. In my syslog there is a
line stating that usb_modeswitch *did* switched the modem - without any
udevrules-patching. ("usb_modeswitch: switched to 12d1:1506 on 1/3")
(Was it an incorrect switching?..)
That I cannot interpret well: "the connection will appear in your panel as it
would if you would insert an ethernet cable". I never insert ethernet cables, I
have solely the mobile net, in the panel nothing appeared.
What I did was: in Network Connections, Add, Mobile Broadband, then either
appeared there (in the combo) a "Huawei Broadband device" or such (I have no
screenshot), or not - did not seem to matter. In either way, my old modem
worked. And the new did not. I selected Hungary, Telenor, "mobilinternet" plan,
and disabled roaming (and left all others at the default).
Was this method wrong? What would be the appropriate method to set up (add)
this modem in network manager?
"See the usb_modeswitc_data package for details. [] You may update it" -
I have tried to temporarily use my old modem (connect to the network),
issue an apt-get update and apt-get install usb_modeswitch_data, but
there was no such package, could not search for it, failed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1404068
Title:
No internet connection with Huawei E3272 4G modem
Status in modemmanager package in Ubuntu:
New
Status in usb-modeswitch package in Ubuntu:
Incomplete
Bug description:
There is no internet connection. My mobile broadband LTE modem is Huawei
E3272. Attached a syslog.
Ubuntu 14.10
modemmanager 1.2.0-1
This might contain useful information:
http://askubuntu.com/questions/525965/huawei-e3272-ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1404068/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408748] Re: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1408748 Title: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in rsyslog package in Ubuntu: Confirmed Bug description: Installed with gui updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: rsyslog 7.4.4-1ubuntu11.1 Uname: Linux 3.16.6-031606-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Jan 8 13:12:56 2015 DuplicateSignature: package:rsyslog:7.4.4-1ubuntu11.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-09-18 (476 days ago) InstallationMedia: This SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1408748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 832150] Re: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher
** No longer affects: ayatana-design -- 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/832150 Title: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in compiz source package in Oneiric: Fix Released Status in unity source package in Oneiric: Won't Fix Bug description: TEST CASE: 1. Start a session (restarting Unity didn't do the trick). 2. Start gnome-terminal or gedit and maximize it (doesn't matter how, also works with other applications). RESULT: * The launcher does not reveal (hide mode 2 - "Dodge Window"). I'm not sure how, but it will eventually start working again after some window dragging/maximizing. Using Nux r483 and Unity r1628. =Original Report= Hello i am testing Ubuntu 11.10 alpha3 and i have a problem with unity. When i open a window, firefox for example, i cannot see the launcher when i move my cursor on the left side as i used to. This problem is not happening when i use unity2d. I can see the launcher by pressing alt+f1. I didn't had a clean install, i mean i upgraded to Ubuntu 11.10. Unity's package version is 4.8.2-0ubuntu4. Thank you in advance Vassilis ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,gnomecompat,imgpng,vpswitch,commands,grid,obs,compiztoolbox,place,mousepoll,move,regex,wall,session,unitymtgrabhandles,wobbly,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell] Date: Tue Aug 23 19:14:50 2011 InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1) SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/832150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 862339] Re: Grid placement is offset by 1px
** No longer affects: ayatana-design ** Changed in: unity (Ubuntu) Status: New => Fix Released -- 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/862339 Title: Grid placement is offset by 1px Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Released Status in Compiz Main Plugins: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Window placement is offset by 1px when the grid plugin maximizes a window TESTCASE Semi-maximize two terminals There should be no visible gap between them To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/862339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 866752] Re: Sometimes configure events are missed and windows move slow as a result
** Changed in: unity (Ubuntu) Status: New => Fix Released ** No longer affects: ayatana-design -- 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/866752 Title: Sometimes configure events are missed and windows move slow as a result Status in Compiz: Fix Released Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in compiz source package in Oneiric: Fix Released Status in unity source package in Oneiric: Won't Fix Bug description: Our current method of tracking configure events is error prone since it's liable to interference from other plugins. A better solution is to use X Request serials like metacity does, since this is not prone to be interfered with. TESTCASE Move windows around, maximize, unmaximize, semi-maximize, use alt-tab Windows shouldn't move slowly To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/866752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 549560] Re: Mic input don't work after installation on hd (Toshiba A100-259/ATI IXP SB4x0 HD/ALC861)
It seems to me that the fix was released but in the linux package not the alsa-driver package. ** Changed in: alsa-driver (Ubuntu) Status: Fix Committed => Invalid ** Changed in: alsa-driver (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => 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/549560 Title: Mic input don't work after installation on hd (Toshiba A100-259/ATI IXP SB4x0 HD/ALC861) Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in alsa-driver source package in Lucid: Invalid Status in linux source package in Lucid: Fix Released Bug description: Lucid beta1, Toshiba A100, mic input is not working after hd installation, in a live cd session works fine. Problem is solved adding "options snd-hda-intel position_fix=1" in alsa-base.conf. Bug is present since karmic but in karmic also audio was looping/repeating (see #391114) now this is solved. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davide 4367 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16' Mixer name : 'Realtek ALC861' Components : 'HDA:11c13026,11790001,00100700 HDA:10ec0861,1179ff10,00100300' Controls : 11 Simple ctrls : 8 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 PackageArchitecture: all ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Tags: lucid Uname: Linux 2.6.32-17-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/549560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 586347] Re: 0x104d9069 needs LPIB quirk
It seems to me that the fix was released but in the linux package not the alsa-driver package. ** Changed in: alsa-driver (Ubuntu) Status: Fix Committed => Invalid ** Changed in: alsa-driver (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => 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/586347 Title: 0x104d9069 needs LPIB quirk Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in alsa-driver source package in Lucid: Invalid Status in linux source package in Lucid: Fix Released Bug description: Listening to music (in this case via rhythmbox) results in stuttering sound. This happens once in a while (every 1min or so) on low load and increases when there is a lot of disk activity. Using the driver version 2.6.32-22.201005210601 from audio-dev-ppa. Problem does not appear with the official lucid drivers in linux- backports-modules-alsa-lucid-generic (2.6.32.22.23). I'm using the dev version for nvidia hdmi-support. my alsa-info.sh output: http://www.alsa- project.org/db/?f=b8502df177229c979aa475c0aaad0a02c2825b23 dmesg get's filled with these (not in accordance with stuttering): [ 1761.476830] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, format=0x4011 [ 1761.476844] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x4011 [ 1761.493735] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x4011 [ 1761.513715] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, format=0x4011 [ 1761.513726] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x4011 [ 1761.533673] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x4011 Happy to debug further! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/586347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 576160] Re: [SigmaTel STAC9228] Recording problem
It seems to me that the fixes were released but in the linux package not
the alsa-driver package.
** Changed in: alsa-driver (Ubuntu Lucid)
Status: Confirmed => Invalid
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => 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/576160
Title:
[SigmaTel STAC9228] Recording problem
Status in alsa-driver package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in alsa-driver source package in Lucid:
Invalid
Status in linux source package in Lucid:
Fix Released
Bug description:
none of my mics are working. Cant use audacity or skype. Made sure
all inputs were on.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Compiled on Apr 29 2010 for kernel 2.6.32-22-generic (SMP).
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: me 2184 F pulseaudio
/dev/snd/pcmC0D0c: me 2184 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7ffc000 irq 32'
Mixer name : 'SigmaTel STAC9228'
Components : 'HDA:83847616,102801f7,00100201'
Controls : 32
Simple ctrls : 22
Date: Wed May 5 20:56:53 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64
(20100419.1)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [SigmaTel STAC9228] Recording problem
dmi.bios.date: 12/16/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0Y012C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA10:bd12/16/2008:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn0Y012C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MXG071
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/576160/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 196277] Re: A GNOME login without keypress dosn't set GNOME keyboard settings
Is this really fixed? I do see this bug or a variant on Trusty, please see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1408539 and advice. -- 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/196277 Title: A GNOME login without keypress dosn't set GNOME keyboard settings Status in Dell Inspiron Mini with Custom Dell UI: Fix Released Status in libxklavier - XKB foundation libary: Invalid Status in X.Org X server: Fix Released Status in libgnomekbd package in Ubuntu: Invalid Status in libxklavier package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-input-keyboard package in Ubuntu: Invalid Status in libgnomekbd source package in Hardy: Invalid Status in libxklavier source package in Hardy: Invalid Status in xorg source package in Hardy: Invalid Status in xorg-server source package in Hardy: Invalid Status in xserver-xorg-input-keyboard source package in Hardy: Invalid Status in libgnomekbd package in Baltix: Invalid Status in Fedora: Fix Released Status in openSUSE: Fix Released Bug description: (This report used to cover two separate but similar looking bugs. We split them now, and here we describe one of the two bugs. The other bug, Bug #251443, has to do with some shortcuts to switch between layouts not working. An example is the Alt+AltGr shortcut). If you enable autologin (it is in the settings, System/Administration/Login window/Security/Enable Automatic Login), then any settings about your keyboard layout including the shortcut to switch between layouts do not work on your next reboot. In other words, the system ignores any keyboard layout settings that have been configured in GNOME. This issue has been reported upstream (Freedesktop Project), and the link is shown above. A good description of the root of the problem is at this post by Peter Hutterer, http://lists.freedesktop.org/archives/xorg/2008-July/036947.html "setting the keyboard without a device flag changes the VCK. On the first keypress of a device however this setting is overwritten by the keyboard that is actually being used. If you hit a key before gnome sets the keyboard layout, the phys. keyboard's settings are already copied into the VCK and thus gnome can overwrite them again. consecutive keypresses don't overwrite it again, since the phys. keyboard doesn't change. "The correct solution here is to let gnome set the keyboard settings on each physical device they apply to." A workaround is to run "setxkbmap" (command line utility), which reapplies the layout settings in GNOME. Another workaround is to make a small change in the Keyboard layout settings, something that implicitly reapplies the settings from GNOME. For example, you can change the order of the layouts, then change them back. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-mini/+bug/196277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384278] Re: Impossible to change enter button without unfocusing the textfield
** Also affects: ubuntu-keyboard (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ubuntu-keyboard
Status: New => Fix Committed
** Changed in: ubuntu-keyboard (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-keyboard
Status: Fix Committed => In Progress
** Changed in: ubuntu-keyboard (Ubuntu RTM)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1384278
Title:
Impossible to change enter button without unfocusing the textfield
Status in Ubuntu Keyboard:
In Progress
Status in ubuntu-keyboard package in Ubuntu:
In Progress
Status in ubuntu-keyboard package in Ubuntu RTM:
In Progress
Bug description:
In webbrowser app we want to change enter icon on keyboard following
what's the address in the addressbar. So if the url in addressbar is
the same of page url we want the reload icon, if not we want the enter
icon.
Unfortunately to change icon we need to reload the keyboard, and to do
this we need to unfocus and focus again the textfield, that isn't a
viable way.
This is the code I tried, and it isn't calculate in realtime
InputMethod.extensions: {
"enterKeyIconSource": actionStatus == "reload" ? "reload" :
"keyboard-enter"
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1384278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
