[Bug 1529452] Re: Gallery app asks for same image multiple times at different sizes

[Michi Henning]

BTW, it would probably be helpful to set the thumbailer trace to include
hits in dbus.log when debugging this. Just run

gsettings set com.canonical.Unity.Thumbnailer log-level 2

(Without this, the log only shows misses and errors.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529452

Title:
  Gallery app asks for same image multiple times at different sizes

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1529452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537252] [NEW] Xenial Server daily ISO boot in text mode interface isn't working - kind of loop

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Robie Basak (racb):

Guys,

 It is not possible to use the textmode with latest Xenial ISO...


 Steps to reproduce:

 1- Download it:

 cd ~ ; wget http://cdimage.ubuntu.com/ubuntu-server/daily/current
/xenial-server-amd64.iso;

 2- Boot it by running: kvm -cdrom ~/xenial-server-amd64.iso -m 1024 ;

 3- Wait for first screen, the one you choose your language, then, hit
ESC;

 4- Press ESC again, to leave graphical boot menu;

 5- Hit "OK" button, to enter text interface;

 6- At "boot:" prompt, type something...

 7- Hit ENTER;

 8- BOOM! It goes back to graphical boot menu! Where it should
accepted the commands you typed on step 6...


 Ubuntu 14.04 behaves differently, it accepts the command and boot proceeds.

 This problem is specially bad for automating Ubuntu builds when using
Packer, for example, if you take a look here:

https://github.com/thasmo/packer.templates/blob/master/template/ubuntu-14.04.json

 ...at line 27, it works like a charm but, if you update this
ubuntu-14.04.json file to, lets say, "ubuntu-16.04.json", then, it
will not work!

 Because Packer "types" commands via VNC automatically, and it "hit"
ENTER in the end (line 27), which doesn't work and it goes back to
graphical boot menu... :-/

After researching a bit on this problem, I think that it is a syslinux
bug, or something around it, so, I'm opening it here...

Thanks!
Thiago

** Affects: syslinux (Ubuntu)
 Importance: High
 Status: Triaged

-- 
Xenial Server daily ISO boot in text mode interface isn't working - kind of loop
https://bugs.launchpad.net/bugs/1537252
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to the bug report.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1537424] Re: out-of-bounds read in ./MagickCore/quantum-private.h:266

[Moshe Kaplan]

** Summary changed:

- heap-buffer-overflow in ./MagickCore/quantum-private.h:266
+ out-of-bounds read in ./MagickCore/quantum-private.h:266

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537424

Title:
  out-of-bounds read in ./MagickCore/quantum-private.h:266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1537424/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538723] [NEW] rsyslog user process faults on s390x

[Dimitri John Ledkov]

Public bug reported:

[   38.553696] User process fault: interruption code 003b ilc:3 in 
lmnsd_gtls.so[3ff9120+8000]
[   38.553701] failing address:  TEID: 0800
[   38.553703] Fault in primary space mode while using user ASCE.
[   38.553706] AS:0001b6d4c1c7 R3:0024 
[   38.553710] CPU: 3 PID: 4218 Comm: in:imtcp Tainted: GE   
4.3.0-6-generic #17-Ubuntu
[   38.553711] task: 0001f2e60a78 ti: 0001dafc4000 task.ti: 
0001dafc4000
[   38.553712] User PSW : 070520018000 03ff91202f8e
[   38.553713]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
   User GPRS: 03ff897fd1b8 0050  

[   38.553715]   
03ff6c003c90
[   38.553715]0001   

[   38.553716]03ff91c9c000 03ff897fd1b8 03ff91202f78 
03ff897fd048
[   38.553721] User Code: 03ff91202f7c: e54cd001mvhi
0(%r13),1
  03ff91202f82: e310d0080024stg 
%r1,8(%r13)
 #03ff91202f88: e54cd011mvhi
16(%r13),1
 >03ff91202f8e: e31020580004lg  
%r1,88(%r2)
  03ff91202f94: a729lghi%r2,0
  03ff91202f98: e310d0180024stg 
%r1,24(%r13)
  03ff91202f9e: e54cd020mvhi
32(%r13),0
  03ff91202fa4: e340f114lg  
%r4,272(%r15)
[   38.553730] Last Breaking-Event-Address:
[   38.553731]  [<03ff9104bb66>] 0x3ff9104bb66

** Affects: rsyslog (Ubuntu)
 Importance: High
 Status: New


** Tags: s390x

** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => High

** Tags added: s390x

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538723

Title:
  rsyslog user process faults on s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1538723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537422] Re: out-of-bounds read in coders/meta.c:465

[Moshe Kaplan]

** Summary changed:

- heap-buffer-overflow in coders/meta.c:465
+ out-of-bounds read in coders/meta.c:465

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537422

Title:
  out-of-bounds read in coders/meta.c:465

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1537422/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537421] Re: out-of-bounds read in coders/sun.c:175

[Moshe Kaplan]

** Summary changed:

- heap-buffer-overflow in coders/sun.c:175
+ out-of-bounds read in coders/sun.c:175

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537421

Title:
  out-of-bounds read in coders/sun.c:175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1537421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537423] Re: out-of-bounds read in ./MagickCore/pixel-accessor.h:234

[Moshe Kaplan]

** Summary changed:

- heap-buffer-overflow in ./MagickCore/pixel-accessor.h:234
+ out-of-bounds read in ./MagickCore/pixel-accessor.h:234

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537423

Title:
  out-of-bounds read in ./MagickCore/pixel-accessor.h:234

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1537423/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538724] Re: GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (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/1538724

Title:
  GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1538724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538724] [NEW] GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3

[Chris Johnston]

Public bug reported:

After installing Firefox, I'm receiving the following crash:

Add-ons: ubufox%40ubuntu.com:3.2,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:44.0
BuildID: 20160126223146
CrashTime: 1453922984
EMCheckCompatibility: true
EventLoopNestingLevel: 1
FramePoisonBase: 70dea000
FramePoisonSize: 4096
GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3
InstallTime: 1453922031
Notes: OpenGL: Mesa project: www.mesa3d.org -- Mesa GLX Indirect -- 1.3 Mesa 
4.0.4 -- texture_from_pixmap

ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 285
StartupTime: 1453922983
TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20160126223146","version":"44.0","vendor":"Mozilla","platformVersion":"44.0","xpcomAbi":"x86_64-gcc3","hotfixVersion":null},"partner":{"distributionId":"canonical","distributionVersion":"1.0","partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":64454,"virtualMaxMB":null,"cpu":{"count":8,"cores":4,"vendor":"GenuineIntel","family":6,"model":62,"stepping":4,"l2cacheKB":null,"l3cacheKB":10240,"speedMHz":null,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2"]},"os":{"name":"Linux","version":"3.14.32--grs-ipv6-64","locale":"en-GB"},"hdd":{"profile":{"model":null,"revision":null},"binary":{"model":null,"revision":null},"system":{"model":null,"revision":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"adapters":[{"description":"Mesa
 project: www.mesa3d.org -- Mesa GLX Indirect","vendorID":"Mesa project: 
www.mesa3d.org","deviceID":"Mesa GLX 
Indirect","subsysID":null,"RAM":null,"driver":null,"driverVersion":"1.3 Mesa 
4.0.4","driverDate":null,"GPUActive":true}],"monitors":[],"features":{"compositor":"none"}}},"settings":{"blocklistEnabled":true,"e10sEnabled":false,"telemetryEnabled":false,"isInOptoutSample":false,"locale":"en-US","update":{"channel":"release","enabled":true,"autoDownload":true},"userPrefs":{"browser.newtabpage.enhanced":true},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":false},"profile":{"creationDate":16827},"addons":{"activeAddons":{"ubu...@ubuntu.com":{"blocklisted":false,"description":"Ubuntu
 modifications for Firefox","name":"Ubuntu 
Modifications","userDisabled":false,"appDisabled":false,"version":"3.2","scope":8,"type":"extension","foreignInstall":true,"hasBinaryComponents":false,"installDay":16696,"updateDay":16696,"signedState":2}},"theme":{"id":"{972ce4c6-7e08-4474-a285-3208198ce6fd}","blocklisted":false,"description":"The
 default 
theme.","name":"Default","userDisabled":false,"appDisabled":false,"version":"44.0","scope":4,"foreignInstall":false,"hasBinaryComponents":false,"installDay":16827,"updateDay":16827},"activePlugins":[{"name":"iTunes
 Application Detector","version":"","description":"This plug-in detects the 
presence of iTunes when opening iTunes Store URLs in a web page with 
Firefo","blocklisted":false,"disabled":false,"clicktoplay":true,"mimeTypes":["application/itunes-plugin"],"updateDay":16188}],"activeGMPlugins":{"gmp-gmpopenh264":{"version":null,"userDisabled":false,"applyBackgroundUpdates":1}},"activeExperiment":{},"persona":null}}
Theme: classic/1.0
Throttleable: 1
Vendor: Mozilla
Version: 44.0
useragent_locale: en-US

This report also contains technical information about the state of the
application when it crashed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 44.0+build3-0ubuntu0.14.04.1
Uname: Linux 3.14.32--grs-ipv6-64 x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
BuildID: 20160126223146
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Channel: Unavailable
Date: Wed Jan 27 15:11:31 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2014-04-16 (651 days ago)
InstallationMedia:

IpRoute:
 default via 192.99.20.254 dev eth0
 169.254.0.0/16 dev eth0  scope link  metric 1000
 192.99.20.0/24 dev eth0  proto kernel  scope link  src 192.99.20.23
 192.168.100.0/24 dev virbr1  proto kernel  scope link  src 192.168.100.1
Locales: extensions.sqlite corrupt or missing
Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
PrefSources: prefs.js
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/sh
Profiles: Profile0 (Default) - LastVersion=44.0/20160126223146
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2
RfKill: 

[Bug 1538639] Re: live usb won't install ubuntu on windows 7

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the instructions at
https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry
your installation with new media.  In the event that is is not in fact
an error with your installation media please set the bug's status back
to New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

** Tags added: ident-mismatch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538639

Title:
  live usb won't install ubuntu on windows 7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1538639/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538724] Re: GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3

[Chris Johnston]

** Bug watch added: Mozilla Bugzilla #1243491
   https://bugzilla.mozilla.org/show_bug.cgi?id=1243491

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1243491
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538724

Title:
  GraphicsCriticalError: |[0][GFX1]: Unknown cairo format 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1538724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537213] Re: out-of-bounds read in coders/hdr.c:622

[Moshe Kaplan]

** Summary changed:

- heap-buffer-overflow in coders/hdr.c:622
+ out-of-bounds read in coders/hdr.c:622

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537213

Title:
  out-of-bounds read in coders/hdr.c:622

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1537213/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538727] [NEW] Gnome Subtitles crashes when opening a video

[François Tissandier]

Public bug reported:

When opening MP4 videos, Gnome Subtitles crashes immediately. It's not
the case with all videos. But all the MP4 are failing.

*** stack smashing detected ***: gnome-subtitles terminated

Native stacktrace:

gnome-subtitles() [0x4b5bc0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10) [0x7fb85a079d10]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fb859cd4267]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7fb859cd5eca]
/lib/x86_64-linux-gnu/libc.so.6(+0x78c53) [0x7fb859d17c53]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c) [0x7fb859db7e8c]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0) [0x7fb859db7e30]
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstfaad.so(+0x21c2) 
[0x7fb826dfa1c2]
/usr/lib/x86_64-linux-gnu/libgstaudio-0.10.so.0(+0x134eb) 
[0x7fb8351964eb]

/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(gst_pad_set_caps+0x18f) 
[0x7fb837673dff]
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(+0x57bcb) 
[0x7fb837675bcb]
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(gst_pad_push+0x1e8) 
[0x7fb837679628]

/usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0(gst_base_parse_push_frame+0xcd0) 
[0x7fb836b3f680]
/usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0(+0x14ae0) 
[0x7fb836b40ae0]
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(+0x57b31) 
[0x7fb837675b31]
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(gst_pad_push+0x1e8) 
[0x7fb837679628]

/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstcoreelements.so(+0x21ff7) 
[0x7fb838d1bff7]
/usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0(+0x80fb3) 
[0x7fb83769efb3]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x712fe) [0x7fb854a4e2fe]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x70965) [0x7fb854a4d965]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76aa) [0x7fb85a0706aa]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fb859da5eed]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Opération non permise.
No threads.

=
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=

** Affects: gnome-subtitles (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538727

Title:
  Gnome Subtitles crashes when opening a video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-subtitles/+bug/1538727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537252] Re: Xenial Server daily ISO boot in text mode interface isn't working - kind of loop

[Diogo Matsubara]

*** This bug is a duplicate of bug 1505839 ***
https://bugs.launchpad.net/bugs/1505839

** This bug has been marked a duplicate of bug 1505839
   Unable to install from text mode interface

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1537252

Title:
  Xenial Server daily ISO boot in text mode interface isn't working -
  kind of loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1537252/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1535491] Re: uefi instalation

[Phillip Susi]

The relevant error seems to be: grub-install: error: cannot find EFI
directory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535491

Title:
  uefi instalation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1535491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537252] Re: Xenial Server daily ISO boot in text mode interface isn't working - kind of loop

[Diogo Matsubara]

*** This bug is a duplicate of bug 1505839 ***
https://bugs.launchpad.net/bugs/1505839

** This bug has been marked a duplicate of bug 1505839
   Unable to install from text mode interface

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537252

Title:
  Xenial Server daily ISO boot in text mode interface isn't working -
  kind of loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1537252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1505839] Re: Unable to install from text mode interface

[Diogo Matsubara]

This is still an issue on Xenial, I'm setting this to high and targeting
to 16.04 milestone as per Robie's triage of the dupe (bug 1537252)

** Changed in: debian-installer (Ubuntu)
Milestone: None => ubuntu-16.04

** Changed in: debian-installer (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to a duplicate bug report (1537252).
https://bugs.launchpad.net/bugs/1505839

Title:
  Unable to install from text mode interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1538731] Re: hdparm APM_level is changing to 1 automaticly

[Sergey Skripnick]

> modified.conffile..etc.apm.event.d.20hdparm: [modified]

I've just changed APMD_SPINDOWN=255. No effect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538731

Title:
  hdparm APM_level is changing to 1 automaticly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1538731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538737] [NEW] Unable to access latest cloud images on AWS

[Craig Bruce]

Public bug reported:

I'm trying to launch 14.04.3 from one of the images listed on http
://cloud-images.ubuntu.com/releases/trusty/release/

However, AWS tells me I don't have permission to access the selected
AMI. Have these AMIs been made public?

Specifically in us-east-1 ami-7a715710 and ami-3e7f5954 are not
available.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538737

Title:
  Unable to access latest cloud images on AWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1538737/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521691] Re: Ability to manually rearrange items in the Activities Overview display of currently open windows - feature request

[Nikita Yerenkov-Scott]

Thanks for the advice! I will create an account there ASAP and start
filing my reports there too! And then link them here of course! ;)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521691

Title:
  Ability to manually rearrange items in the Activities Overview display
  of currently open windows - feature request

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1521691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1537472] Re: Synaptics touchpad not recognised - OK on linux-image-3.13.0-74-generic 3.13.0-74.118

[John Leake]

Hi Chris (or any one else),

I have a question about the Ubuntu bug fixing process.

Since what is being asked of me is beyond my capabilities, then I am
unable to mark the bug an New. Does this mean that the status will just
stay as Incomplete until it expires like lots of similar confirmed bugs ?

Best regards,

John Leake

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537472

Title:
  Synaptics touchpad not recognised - OK on linux-
  image-3.13.0-74-generic  3.13.0-74.118

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537472/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1531824] Re: Xorg freeze

[Phill]

Tested the daily ISO:
xenial-desktop-amd64.iso
Mon, 25 Jan 2016 07:58:31 GMT
SHA256SUM: c6dcbd93724704d217e08a75167f0c2188e2847507b782e9127adba017b3fca2
This booted from the DVD but there was widespread video corruption. The shadows 
on windows had a scan-line effect, although it was more than one pixel per 
line. Most text was heavily corrupted beyond being able to guess what the words 
were but sometimes righted themselves on hover. So I guess the boot issue is 
fixed but it has its own problems. Should I raise another bug report for this?

Back to the issue at hand: 3.18.0-031800-generic has worked flawlessly
for days now without freezing, so there's a fix for this issue between
somewhere 3.16 and 3.18, unfortunately 3.17 has some major video
corruption so I'm not sure how to proceed.

Ta

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531824

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521691] Re: Ability to manually rearrange items in the Activities Overview display of currently open windows - feature request

[Nikita Yerenkov-Scott]

Thanks for the advice! I will create an account there ASAP and start
filling my reports there too! And then link them here of course! ;)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521691

Title:
  Ability to manually rearrange items in the Activities Overview display
  of currently open windows - feature request

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1521691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1536327] Re: [Lenovo G50-30] freezes

[Marko Lazic]

Christopher M. Penalver, i will do that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536327

Title:
  [Lenovo G50-30] freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1518291] Re: visual bug in messaging app in landscape mode

[dgoosens]

solved now 
thanks a lot!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518291

Title:
  visual bug in messaging app in landscape mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518291/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538710] Re: USB devices do not work after booting with mouse plugged on Dell desktop

[Vagner]

Christopher,

I've installed the kernel linux-
image-4.5.0-040500rc1-generic_4.5.0-040500rc1.201601241731_amd64.deb on
the links you described and the issue does not happen any more.

Thanks for the info.

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.5-rc1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538710

Title:
  USB devices do not work after booting with mouse plugged on Dell
  desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538710/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1480349] Re: Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

[Colin Ian King]

@Srinivas,

systemd uses targets which serve a similar purpose as runlevels, to
change this on a running system one uses sysemctl

1. To list different target types use:

systemctl list-units --type=target

multi-user.target  is equivalent to run level 3
graphical.target is equivalent to run level 5

2. Edit the thermald service config:

/lib/systemd/system/thermald.service

and set WantedBy=graphical.target

run:

sudo systemctl enable thermald.service

and this will setup the symlinks to enable this service on the
graphical.target target level

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480349

Title:
  Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 &
  E5-1650 v3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1480349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 393094] Re: network manager ppp timeout

[Wolf Rogner]

I just read the syslog excerpt above.

I recently had a similar issue in 15.10 and want to share my experience:

The symptoms: Timeouts and connection termination after some minutes. I
used openconnect vpn connector.

After several experiments I figured the source of the problem being that
my home network is a class A network (10.x.x.x) and the destination
network is a class A network (10.x.x.x) as well.

Keep alive packets follow the routing table and in my case, this included the 
default route pointing to my router.
The router tunnels the vpn connection but does not route it which means that 
keep alives will not reach the remote endpoint and the connection runs into 
timeouts.

I found no solution to this issue other than using an alternative
network connection (using mobile modem which issues a different home IP
address 172.16.x.x). Now the connection is stable and keep alives are
forwarded correctly.

Note: Even static routes do not help as the endpoint of the vpn tunnel
has rolling IP addresses.

Why do I believe there is a connection?

see:
Jun 28 11:30:06 xb pppd[3306]: Cannot determine ethernet address for proxy ARP
Jun 28 11:30:06 xb pppd[3306]: local IP address 10.113.214.1
<
Jun 28 11:30:06 xb pppd[3306]: remote IP address 10.64.64.64  
<

I hope this helps

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/393094

Title:
  network manager ppp timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/393094/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535524] Re: Ubuntu won't install bootloader to /dev/sda. UEFI crap

[Phillip Susi]

You booted the installation cd in bios mode instead of UEFI mode.  You
need to boot it in UEFI mode.


** Changed in: grub-installer (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/1535524

Title:
  Ubuntu won't install bootloader to /dev/sda.  UEFI crap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1535524/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535933] Re: Selecting Windows shows a frozen fuzzy screen

[Phillip Susi]

** Package changed: grub (Ubuntu) => grub2 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535933

Title:
  Selecting Windows shows a frozen fuzzy screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1535933/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1494514] Re: When the screen timeout is set to one minute, the screen doesn't dim before going off

[Pat McGowan]

Still busted and we recommend 1 min for security

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => kevin gunn (kgunn72)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494514

Title:
  When the screen timeout is set to one minute, the screen doesn't dim
  before going off

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi

[Launchpad Bug Tracker]

** Branch linked: lp:~andreas-pokorny/mir/fix-1538632

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538632

Title:
  ui freezes when simultaneously moving mouse & plug/unplug hdmi

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1538632/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1536024] Re: installing OS fails

[Phillip Susi]

wattos is not an official Ubuntu flavor and so is not supported here.


** Changed in: ubiquity (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/1536024

Title:
  installing OS fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1536024/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1531794] Re: package grub-efi-amd64 2.02~beta2-9ubuntu1.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Phillip Susi]

** Changed in: grub2 (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/1531794

Title:
  package grub-efi-amd64 2.02~beta2-9ubuntu1.7 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1531794/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[maelcum]

Yes indeed, it doesn't work because ignoring close events cancels
logout. Damn.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Alexey Chernov]

(In reply to Andreas Hartmetz from comment #29)
> We cannot change Qt in a way that breaks existing applications. Qt5 has not
> exactly just been released, and commercial customers value stability very
> much. Some of them even pay for Qt licenses, which is good for all Qt users,
> so really, we should not make things worse for them.

The same way commercial customers or applications would be affected with
API changes. I think, this issue (and fix) more concerns the environment
than the application itself.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

[Penk Chen]

** Changed in: usensord (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433590

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1433590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

(In reply to Alexey Chernov from comment #23)

> Comments like this clearly don't help
Seriously, you asked for breaking clients because that's what you'd "like" to 
do - what did you expect to hear? That's simply not an acceptable stance.

> Never mentioned minor update or particular version. Please don't distort.
So you meant to schedule this for Qt6?

> Users were already hit when the significant part of functionality important
> for someone's every day use case is broken.
Let's be honest: session restorage is apparently relevant for only a minority 
of users.
Loosing your data is however relevant for everyone. And the latter is the by 
far more severe issue. Restarting applications is merely an annoyance, loosing 
your work is truely expensive.

Also there's absolutely NO reason why we should not care about both -
except that you'd "like" to break client code and risk data loss for
some reason that completely escapes me.

> Still better than a couple of API methods like
"enableSpecifiedBehaviour()"

I fully agree on that proposal to be of little help - it will be mostly
ignored or used w/o accounting the implications.

> Once again: we all could already apply the fix of Andreas and be busy fixing
> the necessary applications rather than keep discussing here.

It does NOT only affect KDE applications, there're hundreds of Qt applications 
which might have adopted this pattern - or simply don't care about session 
management itfp.
Also the proper order is to fix and roll out clients, *then* remove the 
deprecated upstream code. That's why "=> Qt6" for this approach.

> On the Qt6 release you would say that everyone already rely on the
> workaround there was in Qt5 etc. etc.

No. Because you would tell people during Qt5 don't do this and don't rely on it 
because it's not gonna work with Qt6, so that when things are ported to Qt6, 
client code has to be fixed.
Breaking it now and depending client behavior on whether it's linked against Qt 
5.6 or Qt 5.7 is plain wrong and begging for trouble.

> I just kindly remind your description of current Plasma 5 and it's
> application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30.
Off topic? This was a global statement. Session management in particular is a 
different thing:
few people seem to really care about restoring sessions.

> In a couple of years
We'll have seen Qt6 and this removed, but even if not - it doesn't matter.
The QGuiApplication code will have a "// TODO Qt6" comment and the client code 
does not care about why there's a close event (which might be rejected, thus 
not causing eg. deletion anyway)


> The only arguable point is whether it's safe to have it fixed now or should
> another (possible API-changing) workaround should be added instead.

No.
Actually I propose to fix the "workaround" already present in QGuiApplication 
by turning "close()" into just sendind a close event (for that's actually the 
desired action) and by this fix session storage and maintain data protection 
with the present approaches.

Breaking that behavior may happen for Qt6, anything else will be
perceived as regression.

On a sidenote:
QGuiApplication::commitDataRequest() may be the "preferred" hook, but there's 
actually nothing that explicitly forbids "fake a close in addition", notably 
since it will trigger similar, if not equal client code.
Given the status quo, I'd probably even just remove the commitDataRequest 
signal in Qt6 and rely only on faking close events - why should client code 
have to care about two different "aboutToClose" signals? Sounds stupid to me.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #26)
> (In reply to Alexey Chernov from comment #25)
> 
> > According to what?
> According to "This is not fixed in years and each and every session
> management code was ported as "#if 0""
> If there was some relevant interest, it would be fixed long time, since it's
> really not that hard.

Rather interesting indicator. Why don't you apply it to Qt5 or KF5 then?
What a selective vision :)

> > > Loosing your data is however relevant for everyone. And the latter is the 
> > > by
> > > far more severe issue. Restarting applications is merely an annoyance,
> > > loosing your work is truely expensive.
> 
> > Hey, how could session management be "apparently relevant for only a
> > minority of users", but fixes in its behaviour be crucial for a lot of them?
> [...]
> > Fully agree here, but we should confirm that nobody said in the beggining
> > that upstream changes were about to break session management for KF5
> > applications. It was just broken.
> 
> Errr... what?
> Session management (in terms of "please restore the desktop as I left it")
> doesn't seem very important, but if you click "logout" and *booom*, gone is
> your work of the last two hours because the application had no chance (or,
> well, listened to the wrong events) to ask you to save it, that's pretty
> important...

Hmmm... so session management "doesn't seem very important", but
there're applications which expect a) to be closed gently, and also b)
to have an opportunity to interact to the user the very special way, so
that the rest of the world is waiting for them and doesn't logout, but
it's surely not session management. Nice. Following this way we have, I
think, thousands of apps which don't use X, kernel etc. and other not so
important stuff.

> We're apparently talking past each other.
> There're two steps:
> a) logout, clients ask to save your stuff. That works (because of the close
> event)
> b) login, clients should restart. That's broken (because the close event is
> not just an event, but the window "illegally" being withdrawn during logout)
> 
> You propse to fix (b) by breaking (a) and I'm trying to convince you that
> this is a really bad idea.

The matter is just that if you like the fruitful results of some service
or protocol, you need to follow the rules of it. If you violate them and
currently it just works, it's natural that anyone can change something
internally and you are going to fail. Rather atomic thing.

My proposal is just to have library code of Qt following the proper
interaction process, which is expected by anyone who haven't read this
discussion and just wants to support session management in the
application. Nothing against any workarounds in KSMServer, KF wrappers
or anywhere else downstream.

> > bugs which should be fixed either in library and its clients. It's better to
> > fix them when no one really relies on the stability too much. It looks like
> > this time is now for KF5-based application and environment.
> Yes, we should fix KMainWindow now (if faking close events is finally not
> considered a permanent behavior despite the majority of clients will
> probably do that in return to the data commit request - with a fair share
> actually just calling close() ...) but that has absolutely no implications
> on whether it's ok to easily break away from established (even though maybe
> wrong) behavior.

There's no one accepted fix of Qt to fix anything against.
There's a way to fix applications to interact with session manager properly 
though and add some fixes and workarounds to make it work somehow, at least 
with any local Qt patch. According to the comments of 
https://codereview.qt-project.org/#/c/146566/, that's something what Andreas is 
doing.

> > No, that's just postponing and messing up the whole problem. If, as you
> > stated, almost no one implemented easy and pretty simple interaction
> > appeared in Qt5, even less would care of possible bugs and corner cases of
> > the workaround, more complex protocol with close event you propose. There
> > would be just another argument that it's just too messy, not to mention
> > already existing argument that no one uses session management.
> 
> Sorry, but I really cannot read any sense into this paragraph.
> Please try to rephrase it. The above isn't English grammar at all.

Again. Please try to reread it: https://www.kde.org/code-of-conduct/.
Hopefully, it's English would impress you more.

> > It won't be fixed until it's broken
> So you demand to jeopardize userdata because otherwise code won't be fixed.
> Sorry, but there's no way you're ever gonna convince me in this.
> Any solution that builds upon "jeopardize userdata" is not a solution at
> all. It's malicious.

Just one workaround to close the clients gently (with timeout or whatever) in 
session server would save anyone who is afraid of "jeopardize userdata". I just 
don't want this apparently kind purpose of preserving good old behaviour to 

[Bug 1446865]

[Thomas-luebking]

How exactly did you try the kwrite crashing workaround? Just by sending a 
zombie closeEvent?
Do you still have a backtrace?

(Let's say it's legit for a leaf widget to assume that the close event
it doesn't ignore() will cause a close with all implications on future
user interaction, data deletion and stuff, but it's not necessarily good
style.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

For a KMainWindow solution, one should not require a nasty global
eventfilter on the application - handling KMainWindow::closeEvent()
should be sufficient, but there might be an additional pitfall on modal
windows (ie. if there's already a save dialog, we might have to
forcefully activate that to cause user interaction)

However, as long as QGuiApplication cancels the session lougout as long
as any close event is ignored, this cannot be applied either (ie. still
requires your new patch to Qt) and, of course, this doesn't provide a
solution for Qt5 either - session management on Qt5 will remain broken
forever and just some KDE applications work around that. That's a pretty
crappy situation :-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1089013] Re: clvm startup script requires cman

[Billy Olsen]

** Patch removed: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552897/+files/xenial_lp1089013.debdiff

** Patch removed: "wily debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552898/+files/wily_lp1089013.debdiff

** Patch removed: "debdiff for trusty"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4552899/+files/trusty_lp1089013.debdiff

** Patch added: "wily patch"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4557920/+files/lp1089013_wily.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089013

Title:
  clvm startup script requires cman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1089013] Re: clvm startup script requires cman

[Billy Olsen]

** Patch added: "trusty patch"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+attachment/4557921/+files/lp1089013_trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089013

Title:
  clvm startup script requires cman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538727] Re: Gnome Subtitles crashes when opening a video

[Pedro Castro]

Can you indicate which Ubuntu and Gnome Subtitles versions you are
using, and how you installed Gnome Subtitles?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538727

Title:
  Gnome Subtitles crashes when opening a video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-subtitles/+bug/1538727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1480269] Re: Scrolling is slow and jerky

[Michi Henning]

I can confirm that switching to grid view fixes the problem.

** Changed in: thumbnailer (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480269

Title:
  Scrolling is slow and jerky

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1480269/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538731] [NEW] hdparm APM_level is changing to 1 automaticly

[Sergey Skripnick]

Public bug reported:

Calling 'hdparm -B 255 /dev/sdb' seems take effect:

# hdparm -B /dev/sdb

/dev/sdb:
 APM_level  = off

But in few minutes hdd is spinning down and

# hdparm -B /dev/sdb

/dev/sdb:
 APM_level  = 1

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: hdparm 9.43-1ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 27 22:25:07 2016
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-22ubuntu2
 powermgmt-base 1.31+nmu1
InstallationDate: Installed on 2015-11-02 (86 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: hdparm
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apm.event.d.20hdparm: [modified]
mtime.conffile..etc.apm.event.d.20hdparm: 2016-01-27T15:51:39.218897

** Affects: hdparm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538731

Title:
  hdparm APM_level is changing to 1 automaticly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1538731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

[Dan Streetman]

Matt,

I think it's fine that upstream has demoted the BUG_ON, as I haven't
heard anyone report this with a kernel later than 3.13; I assume
whatever is causing it is fixed in later kernels.

At this point there's not much more I can do, as I can't reproduce it
and don't have much debug info on exactly what/why the zone's pfn range
becomes incorrect.  If you or anyone has any info on how to reproduce
this, or you have a system where it's reproducable, please let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497428

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538730] [NEW] bug 1454310 changed incorrectly

[Janos G. Komaromi]

Public bug reported:

I reported a bug a year ago, #1454310 and then somebody changed it to
"invalid". I don't understand why this was done. The problem is still
there. I realize this is a free software, but at the same time I'm
willing to help make this better in whichever way I could. So please,
re-instate it as a valid bug and investigate.

Let me know how I can help resolve this.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538730

Title:
  bug 1454310 changed incorrectly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1538730/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1515067] Re: Redundant requests for artist art

[Michi Henning]

This is behaving much better now, thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515067

Title:
  Redundant requests for artist art

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1515067/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 746508] Re: apt-check uses too much resources (starts too many processes)

[Gannet]

The same is in Wily.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746508

Title:
  apt-check uses too much resources (starts too many processes)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/746508/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1505839] Re: Unable to install from text mode interface

[Diogo Matsubara]

This is still an issue on Xenial, I'm setting this to high and targeting
to 16.04 milestone as per Robie's triage of the dupe (bug 1537252)

** Changed in: debian-installer (Ubuntu)
Milestone: None => ubuntu-16.04

** Changed in: debian-installer (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505839

Title:
  Unable to install from text mode interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538736] [NEW] setproctitle causes apache mod_wsgi to crash

[Jared Biel]

Public bug reported:

When python-setproctitle is installed alongside mod_wsgi and the wsgi
application imports setproctitle it causes apache to segfault every time
a request comes in to that wsgi vhost.

GDB output:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  fix_argv (argv=0x0, argc=0) at src/setproctitle.c:124
124 src/setproctitle.c: No such file or directory.
Traceback (most recent call last):
  File 
"/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
from libstdcxx.v6.printers import register_libstdcxx_printers

This was fixed in version 1.1.1 (https://github.com/dvarrazzo/py-
setproctitle/issues/9) I recommend that this fix be backported to the
14.04 version of setproctitle.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-setproctitle 1.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
Uname: Linux 3.19.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jan 27 20:34:46 2016
Ec2AMI: ami-9c1f8ef4
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: m4.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: python-setproctitle
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-setproctitle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ec2-images trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538736

Title:
  setproctitle causes apache mod_wsgi to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setproctitle/+bug/1538736/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1517093] Re: HTM builtins aren't treated as compiler barriers on powerpc

[Matthias Klose]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517093

Title:
  HTM builtins aren't treated as compiler barriers on powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1517093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538727] Re: Gnome Subtitles crashes when opening a video

[François Tissandier]

Ubuntu 15.10
Gnome Subtitles 1.2, installed from the software center.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538727

Title:
  Gnome Subtitles crashes when opening a video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-subtitles/+bug/1538727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1497024] Re: release upgrades should jump over unsupported releases

[mirak]

so what must we do when we want to do-release-upgrade on trusty to go to
15.10 ???

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497024

Title:
  release upgrades should jump over unsupported releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1497024/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1484265] Re: Blank screen (instead of splash screen) during boot on Thinkpad T60 with Radeon graphics

[Erik Brangs]

This is fixed for me in Ubuntu 15.10.

** Changed in: plymouth (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/1484265

Title:
  Blank screen (instead of splash screen) during boot on Thinkpad T60
  with Radeon graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1484265/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538741] Re: Xorg freeze

[Erik Brangs]

** Attachment added: "dmesg.txt from frozen system, acquired via SSH"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538741/+attachment/4557955/+files/lenovo-t60-freeze-dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538741

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538741/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538741] [NEW] Xorg freeze

[Erik Brangs]

Public bug reported:

I've looked at the page at
https://wiki.ubuntu.com/X/Troubleshooting/Freeze and can reproduce the
bug at will by entering the command

sleep 1; xset s activate

that's mentioned on the page. The freeze occurs when the screen content
reappears after moving the cursor. Cursor is still movable but clicking
has no effect.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Jan 27 21:37:53 2016
DistUpgraded: 2016-01-11 19:25:27,198 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
MachineType: LENOVO 2007QPG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic 
root=UUID=2a7cf7e8-4927-4e73-a6d3-e783efe97779 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to wily on 2016-01-11 (16 days ago)
dmi.bios.date: 09/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE3WW (2.23 )
dmi.board.name: 2007QPG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007QPG:pvrThinkPadT60:rvnLENOVO:rn2007QPG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2007QPG
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Jan 27 21:17:51 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze ubuntu wily

** Attachment added: "Xorg.0.log from frozen system, acquired via SSH"
   
https://bugs.launchpad.net/bugs/1538741/+attachment/4557929/+files/lenovo-t60-freeze-Xorg.0.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538741

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538741/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1494514] Re: When the screen timeout is set to one minute, the screen doesn't dim before going off

[Pat McGowan]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494514

Title:
  When the screen timeout is set to one minute, the screen doesn't dim
  before going off

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1514522] Re: music apps doesn't find any files

[Michi Henning]

** Also affects: mediascanner2 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514522

Title:
  music apps doesn't find any files

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1514522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1

[Dave Chiluk]

** Patch removed: "lp1535349.trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+attachment/4556038/+files/lp1535349.trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349

Title:
  `df /dev/sda1` no longer reports information for /dev/sda1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

(In reply to Alexey Chernov from comment #30)
> The same way commercial customers or applications would be affected with API
> changes.

How an ABI styable API extension could affect anyone is frankly beyond
me - I doubt it will help to resolve the problem but there's really no
problem with it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

(In reply to Andreas Hartmetz from comment #27)

> We can, however, implement a workaround in KDE (and then fix our stuff when
> something breaks):
>  [...]
> Now which repository should that go in? It would be ugly to copy and paste
> the necessary code around - it should be roughly ten lines.

That's some sort of problem.
KXmlGui/KMainWindow would cover most™ cases, but certainly not all.

The idea of KF5 is to merely optionally extend Qt and the QPA plugin would 
affect every Qt application.
Since this will however also require to fix the application wrt listening to 
the datacommit request itfp, this could only apply to the fixed cases - which 
would for a general fix then be KMainWindow, calling queryClose() on this 
occasion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #24)
> (In reply to Alexey Chernov from comment #23)
> 
> > Comments like this clearly don't help
> Seriously, you asked for breaking clients because that's what you'd "like"
> to do - what did you expect to hear? That's simply not an acceptable stance.

No one here presents any absolutely true point, otherwise there were no
discussion. I just wrote my point of view and emphasized that it's just
mine and not some ultimate truth.

> > Never mentioned minor update or particular version. Please don't distort.
> So you meant to schedule this for Qt6?

No. I just stated that I didn't mention any particular version, no other
implications. As to your question, I'd prefer properly test the patch,
including success scenario for the default not-aware-of-session-
management application, and release it as soon as possible.

> > Users were already hit when the significant part of functionality important
> > for someone's every day use case is broken.
> Let's be honest: session restorage is apparently relevant for only a
> minority of users.

According to what? Your assumption? It's not too evident for me, sorry.

> Loosing your data is however relevant for everyone. And the latter is the by
> far more severe issue. Restarting applications is merely an annoyance,
> loosing your work is truely expensive.

Hey, how could session management be "apparently relevant for only a
minority of users", but fixes in its behaviour be crucial for a lot of
them? Don't you contradict with yourself in these two points?

Anyway, it's very subjective and I wouldn't argue on what's more
important. I agree that data loss is the worst thing which could happen.
I just think it doesn't mean it should result in some messy API or
library code when someone's relying on the undocumented side-effects.
Just because it will surely lead to more bugs and more data loss in the
future. It's just the bugs which should be fixed either in library and
its clients. It's better to fix them when no one really relies on the
stability too much. It looks like this time is now for KF5-based
application and environment.

> Also there's absolutely NO reason why we should not care about both - except
> that you'd "like" to break client code and risk data loss for some reason
> that completely escapes me.

No, that's just postponing and messing up the whole problem. If, as you
stated, almost no one implemented easy and pretty simple interaction
appeared in Qt5, even less would care of possible bugs and corner cases
of the workaround, more complex protocol with close event you propose.
There would be just another argument that it's just too messy, not to
mention already existing argument that no one uses session management.

> > Still better than a couple of API methods like "enableSpecifiedBehaviour()"
> 
> I fully agree on that proposal to be of little help - it will be mostly
> ignored or used w/o accounting the implications.

Ok.

> > Once again: we all could already apply the fix of Andreas and be busy fixing
> > the necessary applications rather than keep discussing here.
> 
> It does NOT only affect KDE applications, there're hundreds of Qt
> applications which might have adopted this pattern - or simply don't care
> about session management itfp.
> Also the proper order is to fix and roll out clients, *then* remove the
> deprecated upstream code. That's why "=> Qt6" for this approach.

Fully agree here, but we should confirm that nobody said in the
beggining that upstream changes were about to break session management
for KF5 applications. It was just broken. Since we have what we have,
there's no other way than to start fixing it on both sides. I think
nobody is against if it would be synchronized.

> > On the Qt6 release you would say that everyone already rely on the
> > workaround there was in Qt5 etc. etc.
> 
> No. Because you would tell people during Qt5 don't do this and don't rely on
> it because it's not gonna work with Qt6, so that when things are ported to
> Qt6, client code has to be fixed.

Oh, you're too optimistic here. Why it's still not fixed during porting
on Qt5? Only because it just works. It won't be fixed until it's broken
or would be planned to fix as we discussed above.

> Breaking it now and depending client behavior on whether it's linked against
> Qt 5.6 or Qt 5.7 is plain wrong and begging for trouble.

That's again due to your assumption that session management is of lower
priority. I'm pretty sure there would be packages that would require
just most recent Qt version, and it would be acceptable. What's wrong in
relying on changes in recent Qt release and informing the maintainer of
it with more strict requirement? There're backports if someone is
interested in special cases.

> > I just kindly remind your description of current Plasma 5 and it's
> > application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30.
> Off topic? This was a global statement. Session management in particular 

[Bug 1446865]

[maelcum]

We cannot change Qt in a way that breaks existing applications. Qt5 has
not exactly just been released, and commercial customers value stability
very much. Some of them even pay for Qt licenses, which is good for all
Qt users, so really, we should not make things worse for them.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1446865]

[maelcum]

You can't just send fake close events to clients that don't expect that.
That... technique... is a KDE specialty. KDE applications are written to
deal with it. In the general case, though, it is legitimate to start
destroying internal data structures in a close event, and it is
legitimate not to expect more than one close event before the window is
actually closed. Case in point: fixing KMainWindow and KApplication to
restore their KDE4 behavior (I have locally tested Qt and KDE patches to
that effect) makes Kate crash on logout.

Changing behavior but not API is *worse* than adding API that optionally
changes behavior - it silently breaks expectations of existing software.

We can, however, implement a workaround in KDE (and then fix our stuff when 
something breaks):
At the end of the slot handling commitDataRequest(), install an event filter on 
the QGuiApplication, which nicely filters ALL events to everything (TODO: check 
that - otherwise we'd just install an event filter on all toplevel windows). In 
that filter, check whether QGuiApplication::isSavingSession() is still true: if 
so, filter out and ignore() all CloseEvents. If not, have the the filter 
uninstall and delete itself for performance reasons. If you look at 
QWidgetPrivate::close_helper(), you see that it always sends a close event to 
ask windows if they agree to be closed, and they can always refuse.

Now which repository should that go in? It would be ugly to copy and
paste the necessary code around - it should be roughly ten lines.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

Fun fact (though you likely already know) - KApplication::commitData(.)
*did* send a fake close event to everything but KMainWindow ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Alexey Chernov]

I'm actually aware of the problem with session management since last
summer, now I've upgraded my stuff to have more KF5-based applications
and suprisingly found it still just doesn't work. So I've dived deeper
into it this time, reading all the discussion here and last part of bug
#341930, both Andreas's change proposals and the thread in the mailing-
list.

I likely agree with comment #18 of Andreas and in my point of view it is
the following:

1. As a whole it's a massive regression since KDE4 which affects all Qt5
applications, most of which behave correctly as a session clients. Even
server parts of both KWin and KSMServer now behave correctly, thanks to
Thomas's fixes, I think. But as a whole it just doesn't work at all.

2. This problem is caused by some bug in processing session management
messages in Qt, which earlier wasn't a big pain and could be avoided,
but due to significant changes in the whole interaction process, in the
API etc. now it can't be avoided and lead to (1).

3. There's initial change (https://codereview.qt-
project.org/#/c/142232/) by Andreas, which perfectly fixes the problem
with any observable problems. It also fixes a fault in the session
management protocol implementation for at least two OSs, which is good
for Qt itself.

4. There could be potentially affected client applications which: a)
were already been ported to/written for Qt5; b) process some valuable
data which shouldn't be lost; c) would like to use session management to
prevent loss of unsaved data; d) still don't care to follow session
management protocol correctly and just exploit old hacks and errors in
its implementation, which exist historically, but now is moved to a new
place. Unfortunately, this term is a little objectless since it wasn't
mentioned any real-life application like this.

5. I completely don't like the proposed way to preserve the
compatibility with (4) and make the use case of broken session
management client implementation legal and default, but also try to
allow proper-written apps to still survive somehow, adding some strange
workarounds to Qt as closing all the windows, but not too much, or API
properties to enable proper processing of SM messages.

To sum it all up, I've applied the patch (3) and have all the session
management things back again without any other changes to KDE or
whatever, it's already released versions (KF-5.18.0, Plasma-5.5.3,
applications-15.12.1). I'll also test Windows behaviour with some toy
application. Unless any problems arise, I see no reason why this tiny
and simple (and right) fix isn't applied and merged.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1

[Dave Chiluk]

Here's an updated patch with proper attribution, and references to the
upstream commits.  I decided to do a backport of the relevant portions
of df.c from vivid as that is already known to work well rather than
attempt to follow the endless trail of patches that exist upstream.
That being said I did document the commit id's that relate to the areas
of code that were used in the dep3 header.

I would now appreciate some review and sponsorship of this patch.

** Patch added: "lp1535349.trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+attachment/4557958/+files/lp1535349.trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349

Title:
  `df /dev/sda1` no longer reports information for /dev/sda1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

> 5. I completely don't like the proposed way to preserve the compatibility 
> with (4) and make 
> the use case of broken session management client implementation legal and 
> default, but 
> also try to allow proper-written apps to still survive somehow, adding some 
> strange 
> workarounds to Qt as closing all the windows, but not too much, or API 
> properties to enable 
> proper processing of SM messages.

No ofense, but what you "like" is completely irrelevant.
You propose to intentionally break clients by library changes in some minor 
update, to teach developers to do right, but while you might aim their face, 
you're gonna hit the users (and probably yours)

We had that (I kindly remind of the qDeleteAll fix ...) and it cooked up
hell.

commitDataRequest hardly shows up in lxr.kde.org, what means it's
probably not used at all and aboutToQuit (which isn't used but could
come to rescue) isn't used too much either.

The BY FAR! omnipresent pattern is to listen to queryClose() which is 
called/emitted on -guess what- close events from KMainWindow.
And that's for pretty much sure why the (wrong) behavior in QSessionManager 
exists.

Is this behavior correct? No.
Does this matter? NO!

It's ok to spam a #warning that this behavior is shit and deprecate and
kill it for Qt6 and we might even bail out (aka "fix") KMainWindow
applications NOW by invoking queryClose() on
QGuiApplicationPrivate::commitData() but regardless, we MUST assume this
to be a global default pattern that applications (also beyond KDE) rely
on (also because it's absolutely natural to intercept closing to save
data and not think of closing on session end could be something entirely
different - actually the illegal behavior happens to be the most sane
one...)

Now, *actually* closing windows to test interaction on session end is of
course just as wrong - if the user cancels the logout by such incident,
we should not have closed random other windows before (letting alone
that it causes this but) - therefore I frankly do not understand what's
so complicated about just faking a close event to serve the present
"save your stuff" pattern in a majority in clients without causing the
destructive close itself which may not only be a bit premature, but also
triggers this bug.

It's the least invasive solution that does not require everyone to
signal "yes, i can sessionmanagement" (what's not gonna happen) and we
don't risk loosing the users data (or breaking the ability to cancel the
logout)

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1446865

Title:
  KDE5/Qt5 does not support session restoration

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1446865]

[Thomas-luebking]

(In reply to Alexey Chernov from comment #25)

> According to what?
According to "This is not fixed in years and each and every session management 
code was ported as "#if 0""
If there was some relevant interest, it would be fixed long time, since it's 
really not that hard.

> > Loosing your data is however relevant for everyone. And the latter is the by
> > far more severe issue. Restarting applications is merely an annoyance,
> > loosing your work is truely expensive.

> Hey, how could session management be "apparently relevant for only a
> minority of users", but fixes in its behaviour be crucial for a lot of them?
[...]
> Fully agree here, but we should confirm that nobody said in the beggining
> that upstream changes were about to break session management for KF5
> applications. It was just broken.

Errr... what?
Session management (in terms of "please restore the desktop as I left it") 
doesn't seem very important, but if you click "logout" and *booom*, gone is 
your work of the last two hours because the application had no chance (or, 
well, listened to the wrong events) to ask you to save it, that's pretty 
important...

We're apparently talking past each other.
There're two steps:
a) logout, clients ask to save your stuff. That works (because of the close 
event)
b) login, clients should restart. That's broken (because the close event is not 
just an event, but the window "illegally" being withdrawn during logout)

You propse to fix (b) by breaking (a) and I'm trying to convince you
that this is a really bad idea.

> bugs which should be fixed either in library and its clients. It's better to
> fix them when no one really relies on the stability too much. It looks like
> this time is now for KF5-based application and environment.
Yes, we should fix KMainWindow now (if faking close events is finally not 
considered a permanent behavior despite the majority of clients will probably 
do that in return to the data commit request - with a fair share actually just 
calling close() ...) but that has absolutely no implications on whether it's ok 
to easily break away from established (even though maybe wrong) behavior.
 
> No, that's just postponing and messing up the whole problem. If, as you
> stated, almost no one implemented easy and pretty simple interaction
> appeared in Qt5, even less would care of possible bugs and corner cases of
> the workaround, more complex protocol with close event you propose. There
> would be just another argument that it's just too messy, not to mention
> already existing argument that no one uses session management.

Sorry, but I really cannot read any sense into this paragraph.
Please try to rephrase it. The above isn't English grammar at all.
 
> It won't be fixed until it's broken
So you demand to jeopardize userdata because otherwise code won't be fixed.
Sorry, but there's no way you're ever gonna convince me in this.
Any solution that builds upon "jeopardize userdata" is not a solution at all. 
It's malicious.

> I'm pretty sure there would be packages that would require just
> most recent Qt version, and it would be acceptable.
And jeopardize userdata. What exactly should this help in this case?

> What's wrong in relying on changes in recent Qt release
That you are not. "Recent Qt releases" start to jeopardize userdata because (no 
way) all Qt client code has been fixed, ie. distros must not use Qt 5.7 until 
all client code releases picked up the change.

> In this way all the bugfixes should be postponed till Qt6
If a bugfix is *very* likely gonna break more things more badly than it fixes 
and there is absolutely no need to take this risk? Yes, avoid that fix and come 
up with a more robust interim solution.

> By the way, are you completely sure your changes won't break any clients?
> What if someone relies exactly on the current code?
Err, on the close event? Well, that's exactly what I suggest to preserve.
You're not gonna see more from a ::close() call in client code (it's no virtual 
and not invoked as slot)

> In the opposite, close event or aboutToClose do mean closing
> and quitting,  but don't imply any data interactions (as it's too late)
Errr, no. Please read the Qt API docs.
You simply ::ignore() the close event and nothing is gonna be closed or changed.

That's why it's massively intercepted to ask users to save stuff - what's also 
explicitly suggested in the API docs.
And that's why somebody considered it a good idea to explicitly close windows 
on session end, what it's just not. That "somebody" actually wanted to trigger 
and check the result of the event, but not really close windows. And that's 
what I'm proposing to deal with the situation.

The justification for QGuiApplication::commitDataRequest() though is,
that a QGuiApplication doesn't necessarily have any windows at all and
still wants to save stuff on logout (and of course before the SIGTERM)

=
Completely untested patch (not even a build attempt) for Qt 5.6:

[Bug 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #22)
> > 5. I completely don't like the proposed way to preserve the compatibility 
> > with (4) and make
> > the use case of broken session management client implementation legal and 
> > default, but
> > also try to allow proper-written apps to still survive somehow, adding some 
> > strange
> > workarounds to Qt as closing all the windows, but not too much, or API 
> > properties to enable
> > proper processing of SM messages.
>
> No ofense, but what you "like" is completely irrelevant.

Comments like this clearly don't help the discussion or solving the
problem, especially when you start your reply with them. I won't answer
you the same style, but given that it's not the first one from you, my
earnest request to you is to please respect each other and avoid such
comments in future. In case of any questions feel free to consult
https://www.kde.org/code-of-conduct/. Thank you.

> You propose to intentionally break clients by library changes in some minor
> update

Never mentioned minor update or particular version. Please don't
distort.

> to teach developers to do right

No intention to do it, but any specs probably means something like that.

> but while you might aim their face, you're gonna hit the users (and
probably yours)

Users were already hit when the significant part of functionality
important for someone's every day use case is broken. I just can't get
why it's OK to break everything for one part of users and ultimately
save broken implementation to preserve some ephemeral compatibility for
another. That's probably the biggest question for me in this thread.
Maybe I'm wrong and those who use sessions are somewhat less important
than users that sometimes save their data on quitting? It's worth
mentioning then, and I'll immediately give up.

> We had that (I kindly remind of the qDeleteAll fix ...) and it cooked up
> hell.

Still better than a couple of API methods like
"enableSpecifiedBehaviour()" or deleting and trying to catch SIGSEGV,
right?)

> commitDataRequest hardly shows up in lxr.kde.org, what means it's probably
> not used at all and aboutToQuit (which isn't used but could come to rescue)
> isn't used too much either.
>
> The BY FAR! omnipresent pattern is to listen to queryClose() which is
> called/emitted on -guess what- close events from KMainWindow.
> And that's for pretty much sure why the (wrong) behavior in QSessionManager
> exists.

If it wasn't done before for some reason, it's better to just fix the
applications, especially given that you don't need any changes in Qt to
have just the same functionality with the new approach. If it's still
too much to change while porting to Qt5/KF5, I really wonder what
porting is.

Once again: we all could already apply the fix of Andreas and be busy
fixing the necessary applications rather than keep discussing here.

> Is this behavior correct? No.
> Does this matter? NO!
>
> It's ok to spam a #warning that this behavior is shit and deprecate and kill
> it for Qt6

On the Qt6 release you would say that everyone already rely on the
workaround there was in Qt5 etc. etc. That's an endless story. By the
way, do you really think it's so much major change that it can't be
changed before Qt6? Seriously, with no API change and with just removing
unexpected actions?

> and we might even bail out (aka "fix") KMainWindow applications
> NOW by invoking queryClose() on QGuiApplicationPrivate::commitData() but
> regardless, we MUST assume this to be a global default pattern that
> applications (also beyond KDE) rely on (also because it's absolutely natural
> to intercept closing to save data and not think of closing on session end
> could be something entirely different - actually the illegal behavior
> happens to be the most sane one...)

I just kindly remind your description of current Plasma 5 and it's
application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30. It
was written months ago, but nothing changed too dramatically from then.

Even if the proper fix could break some apps, they all are *already in*
transition process, Wayland is just around the corner with another
transition process, so now it's the perfect time to fix something to
make it finally working properly rather than make life easier for now
and have this pain for years again and again.

>
> Now, *actually* closing windows to test interaction on session end is of
> course just as wrong - if the user cancels the logout by such incident, we
> should not have closed random other windows before (letting alone that it
> causes this but) - therefore I frankly do not understand what's so
> complicated about just faking a close event to serve the present "save your
> stuff" pattern in a majority in clients without causing the destructive
> close itself which may not only be a bit premature, but also triggers this
> bug.
>
> It's the least invasive solution that does not require everyone to signal
> "yes, i can sessionmanagement" (what's not 

[Bug 1524058] Re: Fix SConf.Streamer to work with non-unicode input on Python 2.x

[Yury V. Zaytsev]

Hi Martin, thank you for your help!

I've enabled -proposed on my trusty machine, upgraded to the new version
and then performed the test as described in this bug report. It worked
for me now out of the box and I couldn't identify any problems with the
new package... so, I think, it's good to go.

All the best!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524058

Title:
  Fix SConf.Streamer to work with non-unicode input on Python 2.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scons/+bug/1524058/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1536175] Re: The installer fail to install Ubuntu 16.04 on uefi systems

[Phillip Susi]

Can you try again?  Can you run the check disc and memtest options from
the boot menu?  Can you install 15.10 on this system ok?


** Changed in: ubiquity (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/1536175

Title:
  The installer fail to install Ubuntu 16.04 on uefi systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1536175/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi

[Andreas Pokorny]

** Description changed:

  confirmed to happen in latest image with usc0.3 and previous images with
  usc0.2
  
  steps
  1) flash ubuntu-touch/rc-proposed/ubuntu-pd
  2) connect bt mouse and see unity8 go into windowed mode
  3)  move mouse about screen while at the same time connect slimport hdmi cable
  
  ui will then freeze but seems content, let it sit for 30 min no reboot or 
restart, no crash files, power button does not do anything.
  It's also possible to have the slimport already connected - move mouse around 
disconnect, the ui will freeze altho in this case unity8 always seems to 
restart.
  
  There are no usc crash files.
+ 
+ The problem is a dead lock on the Display/DisplaySyncGroup mutexes
+ between CompositingFunctor->SystemWindowManager->GraphicsDisplayLayout
+ and DisplayInputRegion.
+ 
+ Thread 6 (Thread 0xb0dff3d0 (LWP 1530)):
+ #0  0xb6cd5d44 in __libc_do_syscall () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #1  0xb6cd395c in __lll_lock_wait () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #2  0xb6ccf19e in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #3  0xb6426f02 in __gthread_mutex_lock (__mutex=0x1b34f14)
+ at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
+ No locals.
+ #4  lock (this=0x1b34f14) at /usr/include/c++/4.9/mutex:135
+ No locals.
+ #5  lock_guard (__m=..., this=0xb0dfeaf0) at /usr/include/c++/4.9/mutex:377
+ No locals.
+ #6  mir::graphics::android::Display::configuration (this=0x1b34ef8)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display.cpp:231
+ lock = {_M_device = @0x1b34f14}
+ #7  0xb6e656ca in mir::shell::GraphicsDisplayLayout::place_in_output 
(this=, id=..., 
+ rect=...)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/graphics_display_layout.cpp:72
+ config = std::unique_ptr 
containing 0xb6eb69c8
+ placed = false
+ #8  0xb6e6a888 in mir::shell::SystemCompositorWindowManager::add_display 
(this=0x1d07b24)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/system_compositor_window_manager.cpp:1
output_id = 
+ rect = {top_left = {x = {value = 0}, y = {value = 0}}, size = {width 
= {value = 768}, height = {
+   value = 1280}}}
+ surface = std::shared_ptr (count 3, weak 4) 0x0
+ __for_range = 
+ lock = {_M_device = @0x1d07b3c}
+ #9  0xb6e1ab32 in operator() (buffer=..., __closure=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #10 std::_Function_handler::_M_invoke(std::_Any_data 
const&, mir::graphics::DisplayBuffer&) (__functor=..., __args#0=...)
+ at /usr/include/c++/4.9/functional:2039
+ No locals.
+ #11 0xb64288a8 in operator() (__args#0=..., this=0xb0dfeca0) at 
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #12 
mir::graphics::android::DisplayGroup::for_each_display_buffer(std::function const&) (this=0x1b35024, f=...)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display_group.cpp:51
+ __for_range = std::map with 1 elements = {
+   [mir::graphics::android::DisplayName::primary] = 
std::unique_ptr containing 
0x1c0db40}
+ lk = {_M_device = 0x1b35028, _M_owns = true}
+ #13 0xb6e1b896 in operator() (__closure=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #14 PairedCalls (deleter=, creator=, 
this=0xb0dfec84)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:33
+ No locals.
+ #15 
paired_calls, 
mir::compositor::CompositingFunctor::operator()():: > 
(deleter=, creator=)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:66
+ No locals.
+ #16 mir::compositor::CompositingFunctor::operator() (this=0x1d112d8)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:98
+ disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac
+ display_registration = {deleter = {__this = 0x1d112d8, 
+ __disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac}, 
owner = true}
+ compositor_registration = 
+ compositors = std::vector of length 1, capacity 1 = {std::tuple 
containing = {[1] = 0x1c0db40, 
+ [2] = std::unique_ptr 
containing 0xb0499848}}
+ lock = {_M_device = 0xb0402c44, _M_owns = true}
+ #17 0xb6e8aa58 in operator() (this=0xb0dfed84) at 
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #18 execute (this=0xb0dfed84)
+ at 
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/thread/basic_thread_pool.cpp:40
+ No locals.
+ #19 operator() 

[Bug 1026450] Re: Pangolin installer problem

[Phillip Susi]

It can't just install to the disk chosen to install Ubuntu to since in a
dual disk situation, the system still boots from the first disk.  I
believe the issue of the usb stick being detected as sda instead of the
first hard disk was fixed some time ago, but precise is ancient and you
should not be putting into new systems.  Please try with 14.04.


** Changed in: debian-installer (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: ubiquity (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/1026450

Title:
  Pangolin installer problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1523637] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-01-27 16:14 EDT---
I did another install with latest netboot image (Jan 26).  It  did not change 
the behavior, and failed in the same way.  I again deleted /dev/sda from the 
installer's view and let it complete.  The attached sosreport is from that 
install test.

Is there some special install option I should be passing in order to get
it to pick up your latest partman-prep update?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523637

Title:
  grub-installer fails due to alternate disk partition error - 14.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1523637/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1523637] sosreport from Jan 27 install test

[bugproxy]

--- Comment (attachment only) From ru...@us.ibm.com 2016-01-27 16:11 
EDT---


** Attachment added: "sosreport from Jan 27 install test"
   
https://bugs.launchpad.net/bugs/1523637/+attachment/4557959/+files/sosreport-p824l.133698-20160127124308.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523637

Title:
  grub-installer fails due to alternate disk partition error - 14.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1523637/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1536429] Re: Installer crashed after drive partitioning (starting the Time Zone screen).

[Phillip Susi]

Your USB stick is corrupt; you will need to recreate it and may want to
verify it using the "check disc" option at the boot menu.


** Changed in: ubiquity (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/1536429

Title:
  Installer crashed after drive partitioning (starting the Time Zone
  screen).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1536429/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001230] Re: Normall install with usb stick in slot fails to install mbr

[Phillip Susi]

I'm afraid the description here is too incomplete to be able to work
with.  Given the age of this bug I'm going to close it.  If it actually
is still a problem for you, please provide a more detailed description.


** Changed in: ubiquity (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/1001230

Title:
  Normall install with usb stick in slot fails to install mbr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1001230/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538635] Re: Dependency typo

[Robert Ancell]

lightdm-greeter is actually a provides field for a greeter - so all three 
greeters provide one. We should probably just correct this field to:
Recommends: lightdm-greeter

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538635

Title:
  Dependency typo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1538635/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1

[Dave Chiluk]

** Description changed:

- It appears that the latest version of coreutils uploaded to trusty-
- updates has a regression in it.  We have scripting that checks how much
- space we have left on a partition using `df /dev/sda1`. Using coreutils
- 8.21-1ubuntu5.1, we can do the following:
+ [Impact]
+ 
+  * df fails to process devices that are specified on the command line.
+ 
+ [Test Case]
+ 
+  * Actual
+ $ df -h /dev/sda1
+ Filesystem  Size  Used Avail Use% Mounted on
+ udev1.8G  8.0K  1.8G   1% /dev
+ 
+  * Expected
+ $ df -h /dev/sda1
+ Filesystem  Size  Used Avail Use% Mounted on
+ /dev/sda1   9.9G  978M  8.5G  11% /
+ 
+ [Regression Potential]
+ 
+  * This patch is a partial backport of functions as they exist in vivid
+ to help minimize the regression potential.
+ 
+  * That being said I had to do some backporting so as to avoid ui changes.
+  
+  * This once again significantly changes the mount search and matching
+logic within df, but it is localized to df.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ 
+  Original Description---
+ It appears that the latest version of coreutils uploaded to trusty-updates 
has a regression in it.  We have scripting that checks how much space we have 
left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we 
can do the following:
  
  $ df -h /dev/sda1
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sda1   9.9G  978M  8.5G  11% /
  
  This is a valid way of using the tool per the manpage: "If  an argument
  is the absolute file name of a disk device node containing a mounted
  file system, df shows the space available on that file system rather
  than on the file system containing the device node"
  
  It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this,
  however. We now get output for the udev filesystem that is mounted at
  /dev, instead of the device we pass in.
  
- $ df -h /dev/sda1 
+ $ df -h /dev/sda1
  Filesystem  Size  Used Avail Use% Mounted on
  udev1.8G  8.0K  1.8G   1% /dev
  
  This is both a behaviour change, and contravenes the manpage, so it
  would be good to get this fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535349

Title:
  `df /dev/sda1` no longer reports information for /dev/sda1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538751] [NEW] Small VMs can run out of memory during initramfs creation

[Robert C Jennings]

Public bug reported:

Micro instances (600MB RAM) will fail to update their kernel packages
(possibly breaking other security updates) since xz will consume a large
% of the system's memory by default - leaving not much RAM for actual
running processes. This also risks a mis-targeted oomkiller.

This is GCE-specific - xz compression is only used due to /etc
/initramfs-tools/conf.d/99-gce.conf

** Affects: gce-utils (Ubuntu)
 Importance: Critical
 Assignee: Robert C Jennings (rcj)
 Status: In Progress

** Summary changed:

- Small VMs can easily run out of memory during initramfs creation
+ Small VMs can run out of memory during initramfs creation

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538751

Title:
  Small VMs can run out of memory during initramfs creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1538751/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538677] Re: Please merge 1.9.10-1 (main) from Debian Unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package nginx - 1.9.10-1ubuntu1

---
nginx (1.9.10-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:  (LP: #1538677)
- debian/patches/ubuntu-branding.patch: add Ubuntu branding (refreshed)
- d/{control,rules,nginx-core.*}: add new binary package for main,
  nginx-core, which contains only source-tarball-included modules
  and no third-party modules.
- debian/tests/control: add nginx-core test.
- debian/control:
  - drop luajit from Build-Depends as it is in universe.
  - Remove HTTP/2 references in package descriptions, per Ubuntu
Security Team mandate to disable HTTP/2 support.
- debian/rules:
  - Disable HTTP/2 module support in all flavors, per Ubuntu Security
Team mandate.
- debian/apport/source_nginx.py: Add apport hooks for additional bug
  information gathering.
- debian/nginx-common.install: Add install rule for apport hooks.
  * Additional bugs fixed by this merge:
- nginx-common should not depend on python (LP: #1480513)

 -- Thomas Ward   Tue, 27 Jan 2016 12:52:00 -0500

** Changed in: nginx (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1538677

Title:
  Please merge 1.9.10-1 (main) from Debian Unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1538677/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1523637] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-01-27 16:21 EDT---
BTW:  I did do another install with apt-setup/proposed=true in place, but it 
also failed in the same way.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523637

Title:
  grub-installer fails due to alternate disk partition error - 14.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1523637/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1407952] Re: CVE-2014-9428

[Steve Beattie]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407952

Title:
  CVE-2014-9428

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407952/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538677] Re: Please merge 1.9.10-1 (main) from Debian Unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package nginx - 1.9.10-1ubuntu1

---
nginx (1.9.10-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:  (LP: #1538677)
- debian/patches/ubuntu-branding.patch: add Ubuntu branding (refreshed)
- d/{control,rules,nginx-core.*}: add new binary package for main,
  nginx-core, which contains only source-tarball-included modules
  and no third-party modules.
- debian/tests/control: add nginx-core test.
- debian/control:
  - drop luajit from Build-Depends as it is in universe.
  - Remove HTTP/2 references in package descriptions, per Ubuntu
Security Team mandate to disable HTTP/2 support.
- debian/rules:
  - Disable HTTP/2 module support in all flavors, per Ubuntu Security
Team mandate.
- debian/apport/source_nginx.py: Add apport hooks for additional bug
  information gathering.
- debian/nginx-common.install: Add install rule for apport hooks.
  * Additional bugs fixed by this merge:
- nginx-common should not depend on python (LP: #1480513)

 -- Thomas Ward   Tue, 27 Jan 2016 12:52:00 -0500

** Changed in: nginx (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/1538677

Title:
  Please merge 1.9.10-1 (main) from Debian Unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1538677/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1480513] Re: nginx-common should not depend on python

[Launchpad Bug Tracker]

This bug was fixed in the package nginx - 1.9.10-1ubuntu1

---
nginx (1.9.10-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:  (LP: #1538677)
- debian/patches/ubuntu-branding.patch: add Ubuntu branding (refreshed)
- d/{control,rules,nginx-core.*}: add new binary package for main,
  nginx-core, which contains only source-tarball-included modules
  and no third-party modules.
- debian/tests/control: add nginx-core test.
- debian/control:
  - drop luajit from Build-Depends as it is in universe.
  - Remove HTTP/2 references in package descriptions, per Ubuntu
Security Team mandate to disable HTTP/2 support.
- debian/rules:
  - Disable HTTP/2 module support in all flavors, per Ubuntu Security
Team mandate.
- debian/apport/source_nginx.py: Add apport hooks for additional bug
  information gathering.
- debian/nginx-common.install: Add install rule for apport hooks.
  * Additional bugs fixed by this merge:
- nginx-common should not depend on python (LP: #1480513)

 -- Thomas Ward   Tue, 27 Jan 2016 12:52:00 -0500

** Changed in: nginx (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/1480513

Title:
  nginx-common should not depend on python

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1480513] Re: nginx-common should not depend on python

[Launchpad Bug Tracker]

This bug was fixed in the package nginx - 1.9.10-1ubuntu1

---
nginx (1.9.10-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:  (LP: #1538677)
- debian/patches/ubuntu-branding.patch: add Ubuntu branding (refreshed)
- d/{control,rules,nginx-core.*}: add new binary package for main,
  nginx-core, which contains only source-tarball-included modules
  and no third-party modules.
- debian/tests/control: add nginx-core test.
- debian/control:
  - drop luajit from Build-Depends as it is in universe.
  - Remove HTTP/2 references in package descriptions, per Ubuntu
Security Team mandate to disable HTTP/2 support.
- debian/rules:
  - Disable HTTP/2 module support in all flavors, per Ubuntu Security
Team mandate.
- debian/apport/source_nginx.py: Add apport hooks for additional bug
  information gathering.
- debian/nginx-common.install: Add install rule for apport hooks.
  * Additional bugs fixed by this merge:
- nginx-common should not depend on python (LP: #1480513)

 -- Thomas Ward   Tue, 27 Jan 2016 12:52:00 -0500

** Changed in: nginx (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1480513

Title:
  nginx-common should not depend on python

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1480513/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494514] Re: When the screen timeout is set to one minute, the screen doesn't dim before going off

[kevin gunn]

** No longer affects: ubuntu-system-settings (Ubuntu)

** No longer affects: unity8 (Ubuntu)

** Changed in: unity-system-compositor
   Importance: Undecided => High

** Changed in: unity-system-compositor
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494514

Title:
  When the screen timeout is set to one minute, the screen doesn't dim
  before going off

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538756] [NEW] Trusty update to v3.13.11-ckt33 stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v3.13.11-ckt33 upstream 
stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://kernel.ubuntu.com/ubuntu/linux.git

TEST CASE: TBD

   The following patches from the v3.13.11-ckt33 stable release
shall be applied:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538756

Title:
  Trusty update to v3.13.11-ckt33 stable release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1497024] Re: release upgrades should jump over unsupported releases

[Brian Murray]

@mirak - you should wait for 15.04 to be unsupported then a "normal"
upgrade from 14.04 will be to 15.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1497024

Title:
  release upgrades should jump over unsupported releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1497024/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1290031] Re: Support japanese language

[Peter Rasmussen]

Hi,I just updated my mobile to the latest Ubuntu build (20160123-115651) and 
the problem still exists.
The problem is that I can show Japanese characters, but I can't enter them.On 
my Ubuntu based laptop I can enter Japanese characters, so I hope to do the 
same on my mobile.よろしくお願いします。
Thank you for your support!Best regards,Peter 

  From: tmtvl 
 To: peterleifrasmus...@yahoo.com 
 Sent: Wednesday, January 27, 2016 9:13 PM
 Subject: [Bug 1290031] Re: Support japanese language
   
Okay, it's been a while since the last activity, what's going on?

If you could outline what still needs fixing, I'll take a look at it.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1290031

Title:
  Support japanese language

Status in ubuntu-keyboard:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  Please support to input japanese language from ubuntu-keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290031

Title:
  Support japanese language

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538755] Re: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newCon

[Michi Henning]

This doesn't look like a thumbnailer problem per se. Seems like it just
exposed an issue in Qt networking code.

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: thumbnailer (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538755

Title:
  /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-
  
service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1538755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538755] [NEW] /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newC

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding thumbnailer.  This problem was most recently seen with version
2.3+15.04.20151102.2-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4d8506d5cef09939bd7de656ced14576d34f1e9a
contains more details.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: thumbnailer (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538755

Title:
  /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-
  
service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1538755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1536311] Re: gedit does not accept input in document window

[Christopher Townsend]

@penk,

I will have to make the change in Libertine itself, but yes it can be
done.

I just hope that there aren't any other future surprise environment
variable changes that affect applications running in the container:)

** Also affects: libertine
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine
   Status: New => In Progress

** Changed in: libertine
   Importance: Undecided => Critical

** Changed in: libertine
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
   Status: New => In Progress

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Critical

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: puritine
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536311

Title:
  gedit does not accept input in document window

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538727] Re: Gnome Subtitles crashes when opening a video

[Pedro Castro]

François, I suggest that you install version 1.3 which comes with support for 
GStreamer 1.0.
Gnome Subtitles 1.3 will only be available in the official repositories in 
Ubuntu 16.04, but you can install it for your Ubuntu version from the Webupd8 
PPA:
http://www.ubuntuupdates.org/ppa/webupd8?dist=wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538727

Title:
  Gnome Subtitles crashes when opening a video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-subtitles/+bug/1538727/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538760] [NEW] battery icon gone

[Teo]

Public bug reported:

Usually the power/battery indicator works as expected.
However, now I turned on my laptop while not connected to AC power, and there 
is no battery icon at all.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 27 22:10:15 2016
InstallationDate: Installed on 2013-10-11 (838 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: indicator-power
UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago)

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538760

Title:
  battery icon gone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1538764] [NEW] needs dependency on python-novaclient

[Robert Bruce Park]

Public bug reported:

This is what happens if you run juju without python-novaclient
installed:

$ juju bootstrap
Bootstrap failed, cleaning up the environment.
ERROR there was an issue examining the environment: authentication failed.

Please ensure the credentials are correct. A common mistake is
to specify the wrong tenant. Use the OpenStack "project" name
for tenant-name in your environment configuration.


Took me some fiddling to figure out I needed python-novaclient installed for 
juju to even bootstrap. The package should definitely have a dependency on 
python-novaclient so that when i install juju it brings that in.

** Affects: juju
 Importance: Undecided
 Status: New

** Affects: juju (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: juju (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1538764

Title:
  needs dependency on python-novaclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1538764/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1538759] [NEW] When RabbitMQ cluster service restarts, other OpenStack services do not gracefully recover

[Javier Diaz Jr]

Public bug reported:

In MOS 6.1:

When RabbitMQ cluster recovers from a failure (whatever the case may be), other 
OpenStack services like the following had to be restarted as well to get our 
environment stable again:
- nova-conductor
- nova-scheduler
- nova-compute (on compute nodes)
- ceilometer-collector

As of now I believe the issue might be due to the potential disabling of
heartbeats. If heartbeats are disabled then if RabbitMQ goes down
ungracefully all nova services have no way of knowing RabbitMQ went
down. When a connection to a socket is cut off completely, the receiving
side doesn't know that the connection has dropped, so you can end up
with a half-open connection. The general solution for this in linux is
to turn on TCP_KEEPALIVES but given that RabbitMQ has the heartbeat
feature built in I think enabling this would be the way to go.

Perhaps building upon this bug would be a wise idea:
https://bugs.launchpad.net/fuel/+bug/1447559

Alternatively, I have found a solution provided by an escalations
engineer in a custom patch to a customer.

This patch  would be applied to the oslo.utils (on which oslo.messaging
depends) library on compute nodes and controllers.

File to update: /usr/lib/python2.7/dist-packages/oslo.utils/excutils.py

This could be done with going to /usr/lib/python2.7/dist-
packages/oslo.utils/ and running patch < oslo_utils2.diff

After that restart nova-compute service by running/etc/init.d/nova-
compute restart.

My proposal is that we investigate the reasoning behind the first
solution. Additionally, I think this patch should make its way to MOS
6.1 MU5 or other.

** Affects: mos
 Importance: Undecided
 Status: New


** Tags: nova oslo.messaging

** Attachment added: "oslo-patch"
   
https://bugs.launchpad.net/bugs/1538759/+attachment/4557961/+files/oslo_utils2.diff

** Description changed:

- When RabbitMQ cluster recovers from a failure (whatever the case may be), 
other OpenStack services like the following had to be restarted as well to get 
our environment stable again: 
- - nova-conductor 
- - nova-scheduler 
- - nova-compute (on compute nodes) 
+ When RabbitMQ cluster recovers from a failure (whatever the case may be), 
other OpenStack services like the following had to be restarted as well to get 
our environment stable again:
+ - nova-conductor
+ - nova-scheduler
+ - nova-compute (on compute nodes)
  - ceilometer-collector
  
  As of now I believe the issue might be due to the potential disabling of
  heartbeats. If heartbeats are disabled then if RabbitMQ goes down
  ungracefully all nova services have no way of knowing RabbitMQ went
  down. When a connection to a socket is cut off completely, the receiving
  side doesn't know that the connection has dropped, so you can end up
  with a half-open connection. The general solution for this in linux is
  to turn on TCP_KEEPALIVES but given that RabbitMQ has the heartbeat
  feature built in I think enabling this would be the way to go.
  
  Perhaps building upon this bug would be a wise idea:
  https://bugs.launchpad.net/fuel/+bug/1447559
  
  Alternatively, I have found a solution provided by an escalations
  engineer in a custom patch to a customer.
  
  This patch  would be applied to the oslo.utils (on which oslo.messaging
  depends) library on compute nodes and controllers.
  
  File to update: /usr/lib/python2.7/dist-packages/oslo.utils/excutils.py
  
  This could be done with going to /usr/lib/python2.7/dist-
  packages/oslo.utils/ and running patch < oslo_utils2.diff
  
  After that restart nova-compute service by running/etc/init.d/nova-
  compute restart.
  
- 
- My proposal is that we investigate the reasoning behind the first solution. 
Additionally, I think this patch should make its way to MOS 6.1 MU5 or other.
+ My proposal is that we investigate the reasoning behind the first
+ solution. Additionally, I think this patch should make its way to MOS
+ 6.1 MU5 or other.

** Also affects: oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: oslo.messaging (Ubuntu)

** Description changed:

+ In MOS 6.1:
+ 
  When RabbitMQ cluster recovers from a failure (whatever the case may be), 
other OpenStack services like the following had to be restarted as well to get 
our environment stable again:
  - nova-conductor
  - nova-scheduler
  - nova-compute (on compute nodes)
  - ceilometer-collector
  
  As of now I believe the issue might be due to the potential disabling of
  heartbeats. If heartbeats are disabled then if RabbitMQ goes down
  ungracefully all nova services have no way of knowing RabbitMQ went
  down. When a connection to a socket is cut off completely, the receiving
  side doesn't know that the connection has dropped, so you can end up
  with a half-open connection. The general solution for this in linux is
  to turn on TCP_KEEPALIVES but given that RabbitMQ has the heartbeat
  feature built in I think enabling this would be the way to go.