[Bug 1278837] Re: KDE screensaver process keeps running in the background, eating graphics card resources

2014-02-11 Thread Roman
Just discovered that this bug also affects NVidia cards. The screensaver
itself never shows up, but its process silently runs in the background,
even after the screen is ulocked.

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

Title:
  KDE screensaver process keeps running in the background, eating
  graphics card resources

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

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


[Bug 1278837] Re: KDE screensaver process keeps running in the background, eating graphics card resources

2014-02-11 Thread Harald Sitter
Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the
KDE program itself, and not with our KDE packages. While we appreciate
your issue, it would be better if it was tracked at
https://bugs.kde.org, so that the KDE developers can deal with this
speedily and have direct communication with you as the reporter for more
effective debugging.

Thanks!

** Changed in: kdebase-workspace (Ubuntu)
   Status: New = Invalid

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

Title:
  KDE screensaver process keeps running in the background, eating
  graphics card resources

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

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


[Bug 1278882] [NEW] kde-developer-sdk should demote subversion to suggests

2014-02-11 Thread Harald Sitter
Public bug reported:

subversion is neither the recommend nor the preferred nor the common version 
control system for kde development. unless a developer also does 
artwork(oxygen), translation(l10n) or admin older parts of the kde web sites 
(www) they will not ever need to use subversion.
for third party developers additionally subversion is completely useless 
because you need to get a server somewhere, while git (the default) can be used 
just fine locally without a server making it useful regardless.

subversion should be demoted to suggests.

** Affects: meta-kde (Ubuntu)
 Importance: Low
 Assignee: Rohan Garg (rohangarg)
 Status: Triaged


** Tags: kubuntu

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

Title:
  kde-developer-sdk should demote subversion to suggests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1278882/+subscriptions

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


[Bug 1278880] [NEW] kde-developer-sdk should not depend on python-rbtools

2014-02-11 Thread Harald Sitter
Public bug reported:

even upstream considers manual diffing and easy and acceptable way to
work with reviewboard

http://techbase.kde.org/Development/Review_Board#Using_Review_Board_the_easy_way

should be demoted to suggests

** Affects: meta-kde (Ubuntu)
 Importance: Low
 Assignee: Rohan Garg (rohangarg)
 Status: Triaged


** Tags: kubuntu

** Description changed:

  even upstream considers manual diffing and easy and acceptable way to
  work with reviewboard
  
  
http://techbase.kde.org/Development/Review_Board#Using_Review_Board_the_easy_way
+ 
+ should be demoted to suggests

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

Title:
  kde-developer-sdk should not depend on python-rbtools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1278880/+subscriptions

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


[Bug 1278881] [NEW] kde-developer-sdk shoudl not depend on kdesrc-build

2014-02-11 Thread Harald Sitter
Public bug reported:

kdesrc-build is only useful when building a whole pile of kde hosted
software locally, which except for KDE's own platform engineers no one
ever needs to do.

in fact, I think I only ever used kdesrc-build once in a my life and
that was when kde4 was in it's super early days.

should be demoted to suggests

** Affects: meta-kde (Ubuntu)
 Importance: Low
 Assignee: Rohan Garg (rohangarg)
 Status: Triaged


** Tags: kubuntu

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

Title:
  kde-developer-sdk shoudl not depend on kdesrc-build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1278881/+subscriptions

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


[Bug 1278912] [NEW] Wrong graph legend for network manager

2014-02-11 Thread Hồng Quân
Public bug reported:

In the graph of network manager in KDE, the blue one is for receiving,
green is for sending, but the legend indicate reversely (green for
receiving).

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: plasma-desktop 4:4.11.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Feb 11 22:54:12 2014
InstallationDate: Installed on 2013-11-03 (100 days ago)
InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: kde-workspace
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kde-workspace (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy third-party-packages

** Attachment added: Screenshot
   
https://bugs.launchpad.net/bugs/1278912/+attachment/3977206/+files/Desktop%202_140.png

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

Title:
  Wrong graph legend for network manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1278912/+subscriptions

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


[Bug 1278912] Re: Wrong graph legend for network manager

2014-02-11 Thread Harald Sitter
Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the
KDE program itself, and not with our KDE packages. While we appreciate
your issue, it would be better if it was tracked at
https://bugs.kde.org, so that the KDE developers can deal with this
speedily and have direct communication with you as the reporter for more
effective debugging.

Thanks!

** Changed in: kde-workspace (Ubuntu)
   Status: New = Invalid

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

Title:
  Wrong graph legend for network manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1278912/+subscriptions

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


[Bug 1278329] Re: [FFe] Qt 5.2

2014-02-11 Thread Scott Kitterman
What's blocking this from landing now?  This has waited far too long in
my opinion.  I'm afraid we have so many rules about the development
release working perfectly now that it's almost impossible to use for
development.  This is in Debian Testing already.

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

Title:
  [FFe] Qt 5.2

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

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


[Bug 1278912] Re: Wrong graph legend for network manager

2014-02-11 Thread Hồng Quân
Do you that program's name? I open it from the taskbar but don't know
its name to report to KDE.

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

Title:
  Wrong graph legend for network manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1278912/+subscriptions

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


[Bug 1279069] [NEW] Systemsetting crashed when using Driver Manager for Kubuntu

2014-02-11 Thread Andreas Hencke
Public bug reported:

I first reported the crash (bug) via drkonqi, my fault. But here what
happened and the Backtrace. Hope it helps!

Application: systemsettings (4.12.2)
KDE Platform Version: 4.12.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-8-generic x86_64
Distribution: Ubuntu Trusty Tahr (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
I've installed the kubuntu-driver-manager package. After installation I started 
Systemsettings Driver Manager for Kubuntu. It worked well until I clicked on 
refresh driver list because Systemsetting crashed immediately

-- Backtrace:
Application: Systemeinstellungen (systemsettings), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f893bfb07c0 (LWP 8492))]

Thread 3 (Thread 0x7f891e6c6700 (LWP 8493)):
#0  0x7f8938f9b74d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f8931ee8d64 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8931ee8e6c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8939723836 in QEventDispatcherGlib::processEvents 
(this=0x7f89180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7f89396f509f in QEventLoop::processEvents 
(this=this@entry=0x7f891e6c5de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f89396f5395 in QEventLoop::exec (this=this@entry=0x7f891e6c5de0, 
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f89395f1c4f in QThread::exec (this=this@entry=0xd38b60) at 
thread/qthread.cpp:537
#7  0x7f89396d6813 in QInotifyFileSystemWatcherEngine::run (this=0xd38b60) 
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f89395f431f in QThreadPrivate::start (arg=0xd38b60) at 
thread/qthread_unix.cpp:349
#9  0x7f89323c2182 in start_thread (arg=0x7f891e6c6700) at 
pthread_create.c:312
#10 0x7f8938fa8b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f891cede700 (LWP 8534)):
#0  0x7f8931f2931a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f8931f29659 in g_mutex_lock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8931ee85fb in g_main_context_query () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8931ee8cd2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f8931ee908a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f891d3e4ff6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7f8931f0dc35 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f89323c2182 in start_thread (arg=0x7f891cede700) at 
pthread_create.c:312
#8  0x7f8938fa8b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f893bfb07c0 (LWP 8492)):
[KCrash Handler]
#6  Module::refreshDriverList (this=0x1174320) at 
/build/buildd/kubuntu-driver-manager-14.04ubuntu1/src/Module.cpp:207
#7  0x7f893970a868 in QMetaObject::activate (sender=sender@entry=0xdd5b60, 
m=m@entry=0x7f893ae3a290 QAbstractButton::staticMetaObject, 
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff5de25af0) 
at kernel/qobject.cpp:3539
#8  0x7f893a9b30f2 in QAbstractButton::clicked (this=this@entry=0xdd5b60, 
_t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
#9  0x7f893a7169f3 in QAbstractButtonPrivate::emitClicked 
(this=this@entry=0xfabf30) at widgets/qabstractbutton.cpp:548
#10 0x7f893a717b63 in QAbstractButtonPrivate::click 
(this=this@entry=0xfabf30) at widgets/qabstractbutton.cpp:541
#11 0x7f893a717c4c in QAbstractButton::mouseReleaseEvent (this=0xdd5b60, 
e=0x7fff5de25fe0) at widgets/qabstractbutton.cpp:1123
#12 0x7f893a3b450a in QWidget::event (this=0xdd5b60, event=0x7fff5de25fe0) 
at kernel/qwidget.cpp:8376
#13 0x7f893a364e2c in QApplicationPrivate::notify_helper 
(this=this@entry=0x9b6e00, receiver=receiver@entry=0xdd5b60, 
e=e@entry=0x7fff5de25fe0) at kernel/qapplication.cpp:4567
#14 0x7f893a36b5dd in QApplication::notify (this=this@entry=0x7fff5de26830, 
receiver=receiver@entry=0xdd5b60, e=e@entry=0x7fff5de25fe0) at 
kernel/qapplication.cpp:4110
#15 0x7f893b071aaa in KApplication::notify (this=0x7fff5de26830, 
receiver=0xdd5b60, event=0x7fff5de25fe0) at 
../../kdeui/kernel/kapplication.cpp:311
#16 0x7f89396f64cd in QCoreApplication::notifyInternal 
(this=0x7fff5de26830, receiver=receiver@entry=0xdd5b60, 
event=event@entry=0x7fff5de25fe0) at kernel/qcoreapplication.cpp:953
#17 0x7f893a36ad93 in sendEvent (event=optimized out, receiver=optimized 
out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0xdd5b60, 
event=event@entry=0x7fff5de25fe0, alienWidget=alienWidget@entry=0xdd5b60, 
nativeWidget=nativeWidget@entry=0xabded0, 
buttonDown=buttonDown@entry=0x7f893ae4c578 qt_button_down, 
lastMouseReceiver=..., 

[Bug 1260514] Re: please improve font rendering (with howto)

2014-02-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kubuntu-settings (Ubuntu)
   Status: New = Confirmed

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

Title:
  please improve font rendering (with howto)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1260514/+subscriptions

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


[Bug 344522]

2014-02-11 Thread Kurt Hindenburg
KDE 4.13 code freezes are coming up in next few weeks - if anyone is
compiling from source please test
https://git.reviewboard.kde.org/r/115628/

Please comment about the GUI options, etc...  It has the basic code to
allow profile col/row settings.

Konsole Settings-Configure Konsole-General-Use current window size on next 
startup
1. Enabled - ignores all profile size settings - uses previous window size
2. Disabled - profile size settings are used - set via Edit Current Profile 1st 
tab

Only new windows will use new col/row/size settings.
There are likely situations that are not covered.
There is also an issue where the rows is sometimes -1 the expected.

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

Title:
  konsole in KDE 4.2 (Intrepid) do not respect size settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/344522/+subscriptions

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


[Bug 1277997] Re: Kubuntu Install fail on new Dell XPS8700: partman error 141: No matching physical volumes found

2014-02-11 Thread Timothee Groleau
I finally managed to install Kubuntu on my XPS 8700 by following
instructions from this guide:
http://ubuntuone.com/2MQe9Wi5POr46RIqVVdZVm

Basically I needed to disable Intel's Rapid Storage Technology
'acceleration' before the installer could find the disk.

The pdf guide also recommended to change the sata controller from raid
to ahci. but that step was *not* necessary in my case.

Note that *after* installation, I could re-enable Intel's Rapid Storage
Technology and grub still worked. I can boot to both windows and
kubuntu!

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

Title:
  Kubuntu Install fail on new Dell XPS8700: partman error 141: No
  matching physical volumes found

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

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


[Bug 1277997] Re: Kubuntu Install fail on new Dell XPS8700: partman error 141: No matching physical volumes found

2014-02-11 Thread Phillip Susi
By Rapid Storage Technology, do you mean you are using it to have an ssd
cache a hd?  If so, enabling it after installing Ubuntu is likely to
lead to corruption since Linux does not understand the caching feature,
so if it works at all, it will be bypassing the cache.  Also Linux does
not care whether the controller is set to raid or ahci mode; it treats
them both the same.  That setting only makes a difference to the bios
fake raid support, and the Windows driver.

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

Title:
  Kubuntu Install fail on new Dell XPS8700: partman error 141: No
  matching physical volumes found

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

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


[Bug 1279194] [NEW] nvidia graphics card not detected

2014-02-11 Thread Peter Liedler
Public bug reported:

I am using a nvidia graphics card on my asus u36s which is detected by
jockey, but not by kubuntu-driver-manager:

01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce GT
520M] (rev a1)

** Affects: kubuntu-driver-manager
 Importance: Undecided
 Status: New

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

Title:
  nvidia graphics card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-driver-manager/+bug/1279194/+subscriptions

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


[Bug 1277997] Re: Kubuntu Install fail on new Dell XPS8700: partman error 141: No matching physical volumes found

2014-02-11 Thread Timothee Groleau
Thanks for your answer Phillip. Yes a 32GB ssd caches a hd in the XPS
8700.

I can boot to kubuntu now. How can I tell if it is bypassing the cache,
or if I am at risk of corruption later?

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

Title:
  Kubuntu Install fail on new Dell XPS8700: partman error 141: No
  matching physical volumes found

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

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


[Bug 1278329] Re: [FFe] Qt 5.2

2014-02-11 Thread Timo Jyrinki
You're correct that development release is now kept releasable each day,
and each daily Ubuntu Touch image should be flawless
(http://ci.ubuntu.com/smokeng/trusty/touch/). The new CI Train
integration does not allow code merges to trunks unless they don't
regress those results.

The effects of the development method may not have been discussed enough
after the CI Airline vUDS discussion in November, from which the
current method has evolved. Everything is now worked in silos until they
are perfect, and there are tools to allow that. With Qt it's more manual
ensuring but still similar to smaller components. Parallel work until
all but polishing problems are fixed.

The current Qt 5.2.x blockers include:
- QA team has started testing 5.2.0, but only this week we've gotten tools to 
create system images using the PPA to be able to get more automated testing
- No multimedia related apps work yet because of lacking qtmultimedia-touch 
(Multimedia team is working on this)
- Some critical bugs making Touch images unusable like the inability to turn 
the screen back on once it has blanked
- The V4 engine is seen a bit risky considering the already identified bugs, so 
the complete 5.2.1 release seems better all around
- 5.2.1 has not been tested yet by QA team. The packaging syncs I've done with 
5.2.1 may cause some rebuild problems since the mkspecs directory changed.
- Debian has part of the 5.2.1 in experimental now, with more coming. I'd like 
to see all of 5.2.1 syncable from Debian for those modules that can be synced 
(most of them).

Lastly, the process of uploading and building the 20 Qt modules and
rebuilding 80 source packages, taking into account the dependencies and
architectures, may take several days in case there are any last minute
surprises that weren't noticed even with careful preparation.

All in all, 2.5 weeks from now sounds like something when pieces could
fall together. I'm putting 5.2.1 into use right now, which should be the
start of the final push.

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

Title:
  [FFe] Qt 5.2

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

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


Re: [Bug 1278329] Re: [FFe] Qt 5.2

2014-02-11 Thread Scott Kitterman
Starting next cycle, Kubuntu will be a major user of Qt5.  Landing the major 
Qt5 revision just days before, or maybe even after, feature freeze, is totally 
unworkable.  I think we're likely not to introduce KDE Frameworks 5 packages 
in this development cycle, but to do post-release backports once it's more 
mature, so it turns out not to have a major impact for 14.04, but something 
better will have to be thought out for U.

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

Title:
  [FFe] Qt 5.2

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

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