I do not have that problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1382462
Title:
10de:0dfa Desktop/windows painted incorrectly in dual monitor
configuration
Status
** Branch linked: lp:ubuntu/vivid-proposed/webbrowser-app
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1407709
Title:
Google Maps and Here Maps should handle cust
** Changed in: webbrowser-app
Status: Confirmed => In Progress
** Changed in: webbrowser-app
Assignee: (unassigned) => Florian Boucault (fboucault)
** Branch linked: lp:~fboucault/webbrowser-app/white_splash
** Also affects: webbrowser-app (Ubuntu)
Importance: Undecided
Sta
If it's something that is not NM backend specific but Qt networking in
general, it would be an useful data point if Qt 5.4.0 works similarly or
not, see https://wiki.ubuntu.com/Touch/QtTesting. If it would work
better, we'd know there's something between 5.3 and 5.4 fixing the
issue, in qtbase.
--
@andyrock
My output of apt-cache policy unity:
unity:
Installed: 7.0.0daily13.06.19~13.04-0ubuntu1
Candidate: 7.0.0daily13.06.19~13.04-0ubuntu1
Version table:
*** 7.0.0daily13.06.19~13.04-0ubuntu1 0
500 http://old-releases.ubuntu.com/ubuntu/ raring-updates/main amd64
Packages
Unfortunately the patched version of Qt from landing-001 didn't help
with our issue with smartscopesproxy (I've tested on an older image #73
on mako; it's important to test on an old image because we've recently
switched to netcpp in smartscopesproxy to avoid these networking
issues).
--
You rece
Support for intent URIs in the container is about to land in vivid.
WARNING: apps shouldn’t be updated until the support for intent URIs in
the container lands in RTM too!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to url-d
I'm afraid the crash file got corrupted somehow, do you still have it on
your device? Does apport-cli /path/to/file complete?
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Changed in: unity8 (Ubuntu)
Status: In Progress => Triaged
--
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/1408263
Title:
Edge gestures still get lost
Status in u
No real reason for this mako-only bug to happen comes to mind. My advise
is to trace back the event to the source, first by lighting up
QtUbuntu's input.cc to spew out all events before pushing them to the
client, and also mirclient's input delivery loop to see if it is
actively dropping the events
** Changed in: mir
Milestone: 0.11.0 => 0.12.0
--
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/1270245
Title:
Backward frame jumps on mali (Nexus 10 & krillin)
Status in M
** Changed in: mir
Milestone: 0.11.0 => 0.12.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 m
That's weird. j de lima, at a terminal please enter "apport-collect
1416588" (without quotes) to attach the relevant files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.
This is what happens when the bug starts to show:
On the Nexus 4, the edge drag areas are 36 pixels wide. When you do a
left edge drag, the touch-press event hits the screen at x=45, so
already past the left edge drag area (launcherDragArea), as this log
snippet shows:
"""
- EdgeDragAreas
The ccsm fix does (partly) work. The screen is painted alright, but the
mouse lags on the 2nd screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1382462
Title:
10de:0dfa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bug
The attachment "Dependencies.txt" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-murra
Public bug reported:
We have already createtd a rmt (14.10) image for the developers contest
in China. Due to some limitation of the Sina weibo API, it wrongly
returns the message type (text/plain) which is incorrect for json
content. Mardy has fixed the issue, and it is finally landed to vivid.
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6e1bf7ab998e30b23202192b5b47c119e7a3697d
** Changed in: systemd (Ubuntu)
Assignee: Didier Roche (didrocks) => Sebastien Bacher (seb128)
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug no
Here's the screencast demonstrating how the desktop performed BEFORE
gnome3-team staging PPA upgrade:
https://www.youtube.com/watch?v=0LhKhdgKHiQ
and AFTER such upgrade:
https://www.youtube.com/watch?v=7pMasD4SfdQ
--
You received this bug notification because you are a member of Ubuntu
Touch s
I built touch-debug packages of unity8 to get as much output as possible
for this.
Interesting data point: playing music seems to trigger this more often -
suspicion is not allowing the device to fully suspend increases the
chance to get this bug.
To get the debug-enabled unity8:
$ wget http://p
@Jussi,
Could you help to put it into trusty? Thanks!
** Changed in: oem-priority
Status: Fix Released => New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority/trusty
Importance: Undecided => High
** Changed in: oem-priority
I have tried this on several ubuntu 14.04 machines now
the result is always the same
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1415701
Title:
apt is unable to handle CDRO
WORKAROUND:
Switch to a different VT (other than X or Mir) before switching to Mir. That
will avoid triggering the bug. It only happens if you're coming from the X VT.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ub
Also confirmed it doesn't matter which version of Mir I try; the bug is
still present. This one is all kernel.
** Changed in: mir
Milestone: 0.12.0 => None
** Changed in: mir
Status: Confirmed => Invalid
** Changed in: mir (Ubuntu)
Status: Confirmed => Invalid
** Summary chang
301 - 326 of 326 matches
Mail list logo
