** Changed in: lirc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1623512
Title:
Fix for Play/Pause key on some MCE remotes
Status in lirc
Good news: I have a had a small eureka moment that results my computer
fully booted with graphics hardware fully accelerated. Bad news: it is
still a workaround -- I still can't push power button and boot up
normally.
Here is the workaround sequence -- it requires another computer that can
ssh
The root cause here seems to be that the lircd.conf file was updated
together with lirc. From the new version 0.9.4 (zesty) the remote
definitions are not longer part of the lirc package, so this just cannot
happen. So, from a lirc perspective this bug is solved by the
lirc-0.8.4c changelog.
That
Thanks! I probably won't have time to do that, but I'll try to remember
if I do.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1623512
Title:
Fix for Play/Pause key on some MCE remotes
** Changed in: lirc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1012165
Title:
lirc_wpc8769l is not being built due to a compile error
You can test using the ppa at https://launchpad.net/~leamas-
alec/+archive/ubuntu/lirc-0.9.4. Don't forget the message if you
upgrade, the update requires configuration changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
You can test using the ppa at https://launchpad.net/~leamas-
alec/+archive/ubuntu/lirc-0.9.4. Don't forget the message if you
upgrade, the update requires configuration changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
You can test using the ppa at https://launchpad.net/~leamas-
alec/+archive/ubuntu/lirc-0.9.4. Don't forget the message if you
upgrade, the update requires configuration changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
You can use the packages in the ppa at https://launchpad.net/~leamas-
alec/+archive/ubuntu/lirc-0.9.4 for testing; these are identical to the
zesty package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
While we are on it: when the dropout occurs, has the lircd daemon died?
In this situation, what does 'ps -ef | grep lircd' tell us?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1200733
@rykien:
Seems like a bug in the driver for the SMBus controller. i2cdetect should show
the headphone amplifier at address 0x73.
I've tested init-headphone with Ubuntu 16.04.1 (you have to add the
acpi_enforce_resources=lax boot parameter!) and 16.10 live images without
problems. Maybe the bug
As Sebastien, I had the same trouble with an ASRock Q1900-ITX (BIOS set to
P1.70 03/31/2016) over XUbuntu 16.04
. No freezes any more after renaming /usr/lib/xorg/modules/extensions/libglx.so
file.
(fresh install, not updated) Hope an updated GLX package.
Trouble (freeze PC) only with Parole
On Tue, Nov 01, 2016 at 10:48:08AM -, Launchpad Bug Tracker wrote:
> So I was wondering if Ubuntu devs can leave out that particular patch
> when building this package for Ubuntu - if it doesn't cause more harm,
> which I doubt.
The patch is there for a reason - otherwise you can't delete on
Public bug reported:
I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.
I've reported this bug (or marked as "it affects me") in a couple of
other places before I've finally discovered that this is the package
that's causing this problem, which unfortunately has been around for a
** Changed in: lirc (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1388583
Title:
15c2:0038 Unable to boot from S5 with Soundgraph iMon IR module
As visible in description, this is a problem in the lirc_serial kernel
module which means that this bug should be reassigned to the kernel
(despite it's name, the lirc_serial module is actually part of the
kernel.)
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
** Changed in: lirc
Will this fix be available in Ubuntu 16.10?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1568679
Title:
Can't connect bluetooth device with on/off switch in control
As the Bluetooth stack is working these days, even on the 64-bit edition of
Ubuntu 16.04.1 LTS, most of the recommendations to aggressively reinstall or
reconfigure seem obsolete indeed:
http://askubuntu.com/questions/131570/how-do-you-make-ubuntu-accept-files-sent-over-bluetooth
BTW already an issue upstream:
http://unix.stackexchange.com/questions/202773/bluetooth-file-transfer-
issue-in-debian-jessie
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-user-share in Ubuntu.
** Changed in: libimobiledevice (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/1623666
Title:
iOS10 will not connect to Ubuntu
*** This bug is a duplicate of bug 1568679 ***
https://bugs.launchpad.net/bugs/1568679
** Changed in: unity-control-center (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 1568679
Can't connect bluetooth device with on/off switch in control center
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
Status in
You can test using the ppa at https://launchpad.net/~leamas-
alec/+archive/ubuntu/lirc-0.9.4. Don't forget the message if you
upgrade, the update requires configuration changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in
This looks indeed weird. You have a Winbond 8769L and tries to use the
lirc_wpc8769l kernel module, which should present data from your remote
on /dev/lirc0. However, this kernel module has been dropped, it never
made the transition process when the kernel modules was moved from lirc
to the
I have a Nokia J Bluetooth headset (BH-806) that connects to my Meizu
Pro 5 Ubuntu phone OTA-13 but no sound is directed to the headset during
calls or during music playing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
marking as fix released due to comment 5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/454586
Title:
package lirc 0.8.6-0ubuntu2 kernel oops on removal
Status in lirc package in
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
You can also try it from my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/996953
Title:
lirc
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I agree, I tested lirc in a pbuilder chroot environment
** Changed in: lirc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1092677
Title:
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Package changed: lirc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1247410
Title:
lirc not working / kernel bug
Status in Linux:
New
Status in linux
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Changed in: lirc (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1407474
Title:
Unknown hardware: Feature Integration Technology Inc. (Fintek)
** Tags added: ppa yakkety
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1635847
Title:
Please build libreoffice-systray package (re-enable quickstarter) -
sync with Debian
** Description changed:
- From a private bug:
- "Currently, NVIDIA and modesetting drivers are using same output names, that
creates confusion for xrandr clients like gnome-setting-daemon or xrandr
utility.
+ [Impact]
+ Currently, NVIDIA and modesetting drivers are using same output names, that
The vivid backport of the plugin seems problematic at this point, it
uses several new core location features from 5.6. Regarding "rtm" as in
"next stable platform", this is already fixed in xenial-overlay.
** Changed in: qtlocation-opensource-src (Ubuntu RTM)
Status: In Progress => Fix
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
*** This bug is a duplicate of bug 1203483 ***
https://bugs.launchpad.net/bugs/1203483
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
*
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
*** This bug is a duplicate of bug 1203483 ***
https://bugs.launchpad.net/bugs/1203483
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
*
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
This bug was fixed in the package lirc - 0.9.4c-4
---
lirc (0.9.4c-4) unstable; urgency=low
* Team upload.
* Upload to unstable.
* Resolves (new bugs) LP: #1636355, LP: #1636353
* Resolves (old bugs) LP: #1497266, LP: #1565070, LP: #1395570,
LP: #1393056, LP: #1310508,
SRU bugs = bug #1595177 and bug #1638021
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1637801
Title:
Incorrect Russian translation of "apt list --upgradeable" results
Status in
Ah right. It's fixed in 1.2.13 and newer, so see the relevant SRU bugs
for those.
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gettext in Ubuntu.
I believe that is a libimobiledevice issue which restricts
ciphersuites/protocol versions. Please verify by trying the patch for
libimobiledevice at:
https://gitlab.com/gnutls/gnutls/issues/145#note_17677611
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 1203483 ***
https://bugs.launchpad.net/bugs/1203483
** This bug has been marked a duplicate of bug 1203483
package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 128
--
You
** Also affects: lirc (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: lirc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lirc (Ubuntu Xenial)
Status: New => Triaged
** Changed in: lirc (Ubuntu Xenial)
Importance: Undecided =>
*** This bug is a duplicate of bug 1203483 ***
https://bugs.launchpad.net/bugs/1203483
** This bug has been marked a duplicate of bug 1203483
package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 128
--
You
Regarding my post #24, I think a better workaround, instead of changing
.Xmodmap,
is to add the following line to the file:
~/.xinputrc
xinput set-button-map "ImPS/2 Generic Wheel Mouse" 1 2 3 5 4 6 7
in this way only the two-finger scrolling direction of the unrecognized
touchpad will be
I reported the issue to the GnuTLS project -
https://gitlab.com/gnutls/gnutls/issues/145
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/1623666
Title:
iOS10 will not connect
** Tags added: xenial
** Also affects: gnutls28 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/1623666
Title:
iOS10
201 - 295 of 295 matches
Mail list logo
