** Attachment added: "Screenshot after rescalling from 1.00 to 0.99 back to
1.00"
https://bugs.launchpad.net/ubuntu/+bug/1895299/+attachment/5410122/+files/Screenshot%20after%20rescalling%201_00-0_99-1_00.png
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
Same with me, problem showed up after upgrading from 19.04 version.
Uncommenting lines mentioned in #13 did not work for me (ASUS UX301L).
Extremely annoying.
--
You received this bug notification becaus
(In reply to Michel Dänzer from comment #8)
> Mesa doesn't really need explicit thread affinity at all. All it wants is
> that certain sets of threads run on the same CPU module; it doesn't care
> which particular CPU module that is. What's really needed is an API to
> express this affinity between
** Bug watch added: Debian Bug tracker #911148
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148
** Also affects: hash-it via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
It works with 18.04 and does not work with 16.04
It connects with other gates of VPN provider but not with this one I have set.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.
VPN provider wrote to me that everything is ok on their side.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1803316
Title:
VPN connection is stopped
Status in ne
Hi,
I install each new update/upgrade. VPN works if my mate uses it using MacOS.
VPN does not work with Ubuntu 18.04 and 16.04 (only this OS I use). I've
checked it in two different networks.
I used every possible setting using NetworkManager.
I've checked each possible solutions using StackOverf
Public bug reported:
>From a few days I cannot connect via VPN, It worked from a few months
*sudo apt policy network-manager*
network-manager:
Installed: 1.2.6-0ubuntu0.16.04.3
Candidate: 1.2.6-0ubuntu0.16.04.3
Versions:
*** 1.2.6-0ubuntu0.16.04.3 500
500 http://ftp.agh.edu.pl/ubu
I'm on 18.04.01 LTS, and I have this issue.
I was searching for this shortcut to be disabled.
--
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/1508146
Title:
Alt+left/right
You can try "git am -3 ...". If that doesn't help, then I don't know.
--
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/1432949
Title:
r300 Mesa driver not loading with KMS enab
MI type 1, 27 bytes
System Information
Manufacturer: FUJITSU
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-2089-E511-8681-742B62ED267C
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-
TC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> sudo dmidecode -t 1
> # dmidecode 3.1
> Getting SMBIOS data from sysfs.
> SMBIOS 2.7 present.
>
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: FUJITSU
> Product Name: LIFE
n
Manufacturer: FUJITSU
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-2089-E511-8681-742B62ED267C
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS
Best Regards,
Marek
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-2089-E511-8681-742B62ED267C
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS
Best Regards,
Marek
To manage notifications about this bug go to:
htt
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS
Best Regards,
Marek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
I would just like to inform you that this bug appear since last CentOS 7.4
update, 7.3 was ok.
https://bugs.centos.org/view.php?id=13916
Maybe it should be reported to Systemd Issues ?
** Bug watch added: bugs.centos.org/ #13916
https://bugs.centos.org/view.php?id=13916
--
You received this
had somebody tryed sound with kernel 4.12 ??
--
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/1563110
Title:
No sound on Asus e200ha, intel sst with cx2072x codec
Statu
I believe this is the common problem with bug:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1612367
But I agree marking bug as critical is more appropriate. Maybe it would
be better to merge and raise the importance of the original bug to
Critical?
--
You received this bug notification
I also have the GPS not working problem. My phone is bq Aquaris E5, I
have OTA 13 installed. I don't even have the "Using GPS, anonymized Wi-
Fi and cellular network info" option present in my settings menu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
I can't bisect the problem, because for the two kernels I build, suspend was
broken and the PC didn't wake up from 2nd suspend :-(
I also tried 4.9-rc6 (albeit on an Arch Linux), which shows the same bug.
** Package changed: xorg (Ubuntu) => linux-lts-xenial (Ubuntu)
--
You received this bug no
So I applied this "big hammer" solution of the patch to the Trusty
(14.04) Xenial HWE kernel (4.4.0-47.68~14.04.1) and this fixes the bug.
I'll give it some more testing, while bisecting v4.0 to v4.1.
** Bug watch added: freedesktop.org Bugzilla #98832
https://bugs.freedesktop.org/show_bug.cgi?
$ git bisect log
# bad: [89e419960fb6a260f6a112821507d516117d5aa1] Linux 4.1.4
# good: [c8bde72f9af412de57f0ceae218d648640118b0b] Linux 4.1.3
git bisect start 'v4.1.4' 'v4.1.3'
# good: [e0cf83cc3de0341d8cabbb23097ad85f5ce97a11] drm/qxl: Do not leak memory
if qxl_release_list_add fails
git bisect
Hmm - so I'm not sure what's going on here. I started bisecting v4.1 ..
v4.2.8 and I couldn't find a working version in 6-7 bisects and when I
checked rest of the commit set in the bisect, it couldn't find any
commits to drivers/gpu?!
So I decided to test Ubuntu mainline kernels a little bit more
So I downloaded some kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D
Working: linux-image-4.1.35-040135-generic_4.1.35-040135.201610241431_amd64.deb
Broken: linux-image-4.2.7-040207-generic_4.2.7-040207.201512091533_amd64.deb
--
You received this bug notification because you
While keeping the Xenial HWE stack on Ubuntu Trusty (14.04), I tried
various installed HWE kernels.
It seems it really broke with the Wily kernel (4.2.0.42.34). The Vivid
kernel (3.19.0.74.56) has survived multiple resume cycles, while Wily
instantly created the problem.
--
You received this bug
Now I tried all the Trusty HWEs and it seems to have started with Wily.
xserver-xorg-video-radeon-lts-wily 1:7.5.0+git20150819-0ubuntu1~trusty1
linux-image-generic-lts-wily 4.2.0.42.34
xserver-xorg-core-lts-wily 2:1.17.2-1ubuntu9.1~trusty1
mesa-lts-wily 11.0.2-1ubuntu4~trusty1
I had once wrong co
I couldn't reproduce the problem with Trusty (14.04) using its original
HWE stack (AKA Kernel 3.13).
--
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/1643843
Title:
Distorted c
This is just a display problem - a snapshot is correct, so it really
looks like a radeon driver problem, instead of an xorg problem.
The wrong colors are always different, so every cycle produces a
different result. For a photo as background it almost looks like modern
art ;-)
--
You received th
** Attachment added: "Correct Unity desktop"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+attachment/4781463/+files/photo_desktop_ok.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https
Public bug reported:
When waking up the system from a suspend-resume cycle, the display most times
shows distorted colours.
As a workaround one can switch to the linux console (VT) and back to fix the
display.
Alternatively triggering DPMS also fixes the problem (xset dpms force off ;
sleep 0.1
Not sure whether it is same bug, but today there was no ringing on
incoming call. Just only seen incoming call on a display. BQ E4.5 with
OTA13.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtmultimedia-opensource-
src in U
in_restore -i lvm_meta_dump -o /dev/mapper/vg02-pool0meta2
lvconvert --thinpool vg02/pool0 --poolmetadata vg02/pool0meta2
--
Kind Regards
Marek Grzybowski
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Public bug reported:
I do not know more.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libnl-3-200 (not installed)
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Th
I might be doing something broken, but it still seems broken to me on
Ubuntu 16.04 on Raspberry PI despite having these fixes applied.
Package versions:
systemd: 229-4ubuntu7
udev: 229-4ubuntu7
Could you please take a look if I'm not doing something stupid (I
hopefully attached the relevant info)
I never used headphones, music applications nor bluetooth and I
experience it also. It should not be related to the above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bug
Fixed by 172bfdaa9e80342ade3f023f72d455d76713b866. Closing.
--
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/1432949
Title:
r300 Mesa driver not loading with KMS enabled
Statu
(In reply to Michel Dänzer from comment #29)
> That piglit sanity is failing with the patch may confirm my suspicion that
> something doesn't add up yet I'm afraid: Since the kernel driver and
> xf86-video-ati EXA code are using the same hardware formats for
> display/rendering with BE & LE, I was
At this stage I just need a confirmation that more than 60% of apps work
and show correct colors (mainly games). I don't expect all apps to be
perfect right now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Created attachment 123370
final fix?
Could you please test this patch?
--
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/1432949
Title:
r300 Mesa driver not loading with KMS en
I would recommend not to have system-wide proxy settings, but proxy
setting for every connection. Since there could be different proxy
servers in different locations. Each WiFi AP should have his own proxy
settings saved. This also implies gui setup for proxy.
--
You received this bug notificatio
I agree this bug was partially solved by OTA-9. But only the part
concerning displaying SIM when call is received. The part concerning
different ringtones per SIM (or ideally per contact per SIM) was not
solved. Also the information I would expect to be seen in call log in
the first sight, not to c
This bug is still present in Fedora 23 x86_64 and pulseaudio-7.1-1
My machine was sending ~ 180KB/s to 224.0.0.56 until I unchecked "Enable
Multicast/RTP sender" in paprefs.
For peace of mind, I ended up adding "unload-module module-rtp-send
source=rtp.monitor" into /etc/pulse/default.pa
--
You
I have Nexus 4 with latest radio, yesterday I flashed the phone with bq-
aquaris.en channel and it was not working. Maybe it would get the
location eventually but if no location is acquired after 5 minutes, I
consider it not working. I'm very much interested in knowing if anyone
from Ubuntu team is
I went through the patch written by me and unfortunately I can not make
it so that it returns the same result as before. I've separated axes in
which it searches for immediate up/down/left/right neighbours, sorted
them and found the neighbours by single pass (+ number of possible
neighbour candidat
I confirm the bug is fixed in OTA-5.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1462090
Title:
Calling to numbers formatted with slash results in Call failed
The bug is concerning telephony-service. See https://bugs.launchpad.net
/canonical-devices-system-image/+bug/1462090. It is fixed in OTA-5.
** Changed in: dialer-app (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtorganizer5-eds in
Ubuntu.
https://bugs.launchpad.net/bugs/1446054
Title:
syncevol
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1462090
Title:
Calling
** Also affects: telephony-service
Importance: Undecided
Status: New
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Public bug reported:
When I call to numbers which are formatted with slash '/', I get call
failed. For example when I try to call +421 2 xxx xx xxx or 02 xxx xx
xxx I get call failed, because numbers are automatically formatted as
+421 2/xxx xxx xx or 02/xxx xxx xx.
This is probably caused by inc
This is probably on telephony-service to handle the slash character,
since I found regexp [p+*#(),;-] in libtelephonyservice/phoneutils.cpp
for nondialable digits removal, which should probably read [p+*#/(),;-].
I am going to file a bug against telephony-service.
--
You received this bug notific
Could someone assign the Critical importance to this bug? It is basic
functionality to place a calls. If I did not have a SIM card in VPN and
use the hack above I would not be able place calls to Slovak fixed line
numbers. Not everybody has such SIM. It is 100% reproducible and
probably caused by p
** Changed in: dialer-app (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1453942
Title:
Calling to some numbers results in Call
** Changed in: dialer-app (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1453506
Title:
cannot pick incoming call
Status in di
I am also affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1453506
Title:
cannot pick incoming call
Status in dialer-app package in Ubuntu:
New
Bug descript
Moreover the dialed number is not added to the recent call list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1453942
Title:
Calling to some numbers results in Call f
Public bug reported:
When I try to call some numbers I cannot place the call and get Call
failed message.
After some investigation a think this is related to automatically adding the
slash '/' sign into the number. When I call number 02 xxx xx xxx, the number is
formatted 02/xxx xxx xx and the
(In reply to Behdad Esfahbod from comment #9)
> Patchset is now upstream in FreeType.
Thank you very much for all the effort you've put into this!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bu
I'm closing this since it seems to be already fixed (by
http://cgit.freedesktop.org/poppler/poppler/commit/?id=f3a1b765bd6a58d327a80feedbe30e1c0792076e
and
http://cgit.freedesktop.org/poppler/poppler/commit/?id=5056e33e01ce0f7db1a5401b7b38d30e84eedf69).
--
You received this bug notification becau
k at this already?
Regards
Marek
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1199571
Title:
Huge multi-threading violations in cairo
Status in libcairo - cairo vector
Can anyone help? I'm not a computer geek - need SIMPLE instructions on
how to regain sound
--
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/1367118
Title:
[System Produc
Public bug reported:
Using Ubuntu 13.10 - have tried re-loading alsa driver but no success -
still no sound from monitor speakers. Have looked at sound card
information BUT do not know what to look for! Am a total beginner with
OS
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.
62 matches
Mail list logo
