How can you use 5.1.10r112026 with virtualbox 5.0.24?
I don't know what that active VNC extension is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms
can you please remove --purge virtualbox-ext-pack and try again?
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647505
Hi, I sponsored it, even if the package increased its size for about 1MB.
The patch was sane enough, a cherry-pick from later releases, and just a new
tool added
(I also melded both changelogs, to see if the new dependencies were carrying
new hidden tools/flags).
the package is now in unapproved
please purge it and install it again
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638757
Title:
package
crw-rw-rw- 1 root root 10, 54 nov 30 10:14 /dev/vboxdrvu
please try sudo chmod 666 /dev/vboxdrvu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms
it seems to be not building
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/11521054
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
B
oh... did you upgrade your extpack package too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module
failed to build
please run
ls /dev/vbox* -lh
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module
failed to build
To manage
I'm setting it to incomplete, because with the vboxvideo driver loaded in the
kernel, I can't reproduce this issue anymore
(I might even not able to reproduce it because of my new laptop with different
hw configuration)
** Changed in: kbd (Ubuntu)
Status: Confirmed => Incomplete
**
*** This bug is a duplicate of bug 1443853 ***
https://bugs.launchpad.net/bugs/1443853
** This bug has been marked a duplicate of bug 1443853
Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted
display
--
You received this bug notification because you are a member
and virtualbox starts?
(my bad, I deleted virtualbox from costamagnagianfranco-ppa some hours ago, I
moved the new build to virtualbox-ppa only)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
setting the severity to critical, I really think we should fix this bug,
if we can find somebody understanding the console-setup bits
** Changed in: console-setup (Ubuntu)
Importance: Undecided => High
** Changed in: kbd (Ubuntu)
Importance: Undecided => High
** Changed in: virtualbox
please try ppa:costamagnagianfranco/costamagnagianfranco-ppa, I did some
changes.
And please report exactly what you get after
modprobe vboxdrv
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tcpdump 4.8 needs fixes before being merged
** Changed in: tcpdump (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624633
Title:
[yakkety+1] please merge
Public bug reported:
Please sync daemontools 1:0.76-6.1 (universe) from Debian unstable
(main)
Explanation of the Ubuntu delta and why it can be dropped:
* Merge with debian, remaining diff:
- add upstartification
* Fix upstart job as not in event.d anymore (LP: #688054)
I think the
why this patch is not upstream? I don't see it in the google protobuf github
repo
https://github.com/google/protobuf/blob/master/src/google/protobuf/stubs/common.cc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please try 5.1.10? I just uploaded it to my ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1: virtualbox kernel module
failed
also, don't try virtualbox-source, remove it and use virtualbox-dkms,
since this one should support kernels up to 4.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608716
Title:
virtualbox-dkms
Too late, precise is mostly EOL now... sorry
** Changed in: policyd-weight (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245069
Title:
Please
Hi unfortunately you can't mix vbox from oracle with the ext pack from
Ubuntu, specially for different major releases.
G.
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I would try with 16.04 or higher versions
** Changed in: libwebsockets (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634873
Title:
Segfault in
** Changed in: tomcat8 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624632
Title:
Sync tomcat8 8.0.36-3 (main) from Debian unstable (main)
To
** Package changed: boinc-app-seti (Ubuntu) => boinc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610317
Title:
setiathome fails to start
To manage notifications about this bug go to:
Yes, this is a boinc issue probably, but I don't think there is a sane way to
do such check, on seti upgrade, specially when seti has so few upgrades.
such link is not handled at all by boinc-app-seti package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
the icon file is not there,
"The icon is not available in a suitable size (at least 64x64px)"
there is no suitable icon size
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575338
Title:
Gnome
patch welcome :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575338
Title:
Gnome Software catalog entry missing for Pidgin
To manage notifications about this bug go to:
Public bug reported:
First, thanks for the git-git import new feature :)
"# git-build-recipe format 0.4 deb-version {debupstream}-0~{revtime}
lp:~costamagnagianfranco/boinc/+git/trunk master"
this is the recipe:
https://code.launchpad.net/~costamagnagianfranco/+recipe/boinc-daily
code:
libghc-xmonad-contrib-dev is now installable.
ghc6 is gone long time ago
** Changed in: xmonad-contrib (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
should be fixed since a lot of time
** Changed in: hdbc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/401379
Title:
can't install hdbc package
should be working now, even if yesod init seems deprecated.
** Changed in: haskell-yesod (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995151
Title:
it works now to me
** Changed in: hdbc-sqlite3 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/518709
Title:
Missing shared library for
should be fixed with new haskell-yesod in zesty
** Changed in: haskell-persistent (Ubuntu)
Status: New => Fix Released
** Changed in: haskell-yesod-bin (Ubuntu)
Status: New => Fix Released
** Changed in: haskell-yesod-core (Ubuntu)
Status: New => Fix Released
--
You
fixed in yakkety+
** Changed in: shellcheck (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: shellcheck (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
exactly, it is called cabal-debian now
** Changed in: haskell-debian (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055716
Title:
In
should be available and stable now
** Changed in: haskell-platform (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047678
Title:
haskell-platform &
does this happen with newer ubuntu releases?
** Changed in: haskell-mtl (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/455988
Title:
package
Can you please open a bug in Debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407229
Title:
binary package name must be libghc-haskell-src-exts-dev
To manage notifications about this bug go
I'm trying to reassign to apt then :)
** Package changed: virtualbox-ext-pack (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642353
Title:
package virtualbox-ext-pack
thanks to you!
sorry for the long wait for this fix, but I always hope about a new
upstream release, and kernel breaks various times in RC releases, so it
would require a lot of uploads probably useless for most people (and
time consuming)
G.
--
You received this bug notification because you
** Summary changed:
- Yakkety version of transcode needed (removal causes unmet depdendencies)
+ Yakkety version of transcode needed (removal causes unmet dependencies)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dino99, yesterday linux4.9 reached zesty, so I'll fix it in a few
seconds
** Changed in: virtualbox (Ubuntu)
Status: Invalid => New
** Changed in: virtualbox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
https://launchpad.net/ubuntu/+source/virtualbox/5.1.8-dfsg-7~build1@dino99,
yesterday linux4.9
please test zesty-proposed in a few minutes (~1 hour)
** Changed in: virtualbox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: virtualbox (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642163
Title:
virtualbox-dkms 5.1.8-dfsg-6build1: virtualbox kernel module
I can't reproduce, I did test it and even if I can't create a qt quick2
project because I have a too old qt version, I could create a qt
application, a qt console application, qtwidgets, qtquick,
qtquickcontrols, and every window was correctly opened, with working
menu, mouse clicks and so on.
I
I moved it back to new, but likely nobody will look at it, and will be closed
in today+5 years or so.
Setting it to incomplete might trigger some answers (even if such failures are
really rare with cmake)
** Changed in: cmake (Ubuntu)
Status: Incomplete => New
--
You received this bug
I don't know how to reproduce :/
** Changed in: cmake (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641687
Title:
/usr/bin/cmake-
Public bug reported:
Availability:
- Already in universe and available on applicable archs.
Rationale:
- Required by cmake 3.7
Security:
- one single CVE according to changelog, dated 2015
Quality assurance:
- Should work without configuration.
- No debconf questions.
- One single Debian, not
Please use apport-collect to report such bugs, even if I think the reason is
not in the Ubuntu repositories but somewhere else
did you manually install some external software?
** Changed in: haskell-hoogle (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
seems a bug somewhere else
insserv: Starting smfpd depends on plymouth and therefore on system facility
`$all' which can not be true!
insserv: Starting smfpd depends on plymouth and therefore on system facility
`$all' which can not be true!
insserv: Starting smfpd depends on plymouth and
You have to use virtualbox-source if you want to play with kernels not
in the repo.
** Changed in: virtualbox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
why not! attached
** Changed in: tcpdump (Ubuntu)
Status: Incomplete => New
** Attachment added: "debdiff2"
https://bugs.launchpad.net/ubuntu/+source/tcpdump/+bug/1624633/+attachment/4774486/+files/debdiff2
--
You received this bug notification because you are a member of Ubuntu
stop mixing ppa and the official one
** Changed in: codeblocks (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639462
Title:
package codeblocks-contrib (not
** Changed in: boinc-app-seti (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610317
Title:
setiathome fails to start
To manage notifications about
emacs25 seems fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634930
Title:
emacs24 fails to build on ppc64el
To manage notifications about this bug go to:
sigh
** Summary changed:
- please move virtualbox-ext-pack to universe
+ please move virtualbox-ext-pack to multiverse
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: virtualbox-ext-pack (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624694
Title:
please move virtualbox-ext-pack to multiverse
To manage
Can you please try and post the log of
dpkg-reconfigure virtualbox-dkms?
thanks
** Changed in: virtualbox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gammaray (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474856
Title:
gammaray fails to build against Qt 5.5
To manage
Just install virtualbox-guest-dkms if you don't need X11
** Changed in: virtualbox-guest-additions-iso (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638954
** No longer affects: virtualbox (Ubuntu)
** Changed in: virtualbox-guest-additions-iso (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638797
Title:
The
I pinged Ubuntu-x-swat team over irc and subscribed it to this bug :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636728
Title:
[MIR] khronos-opencl-clhpp
To manage notifications about this bug
will ask upstream to fix, I can't tweak the iso file
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638797
Title:
The message for
Hi Michael
>I get that this is just a package split, so the content is the same and
doesn't need the same >rigorous check. But still, a few questions:
please don't take this assumption as granted,
$ pull-debian-source khronos-opencl-headers 2.0~svn32091-2
$ pull-debian-source
I think nothing, but I would appreciate @Eric to give his opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620037
Title:
Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main)
To
marking as fix released due to comment 5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454586
Title:
package lirc 0.8.6-0ubuntu2 kernel oops on removal
To manage notifications about this bug go
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)
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)
1101 - 1200 of 4711 matches
Mail list logo
