On Wednesday 24 September 2014 00:09:24 you wrote:
Changes:
ofono (1.15-1) unstable; urgency=medium
.
* New upstream release. (Closes: #759516)
Thanks :-)
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
Package: parcimonie
Version: 0.8.3-1
Severity: important
In the usage instruction from the man page I should check the output of
parcimonie --verbose for misconfiguration or bugs.
The output I'm getting suggest that it's not working (I think):
$ parcimonie --verbose
Reference bless( do{\(my $o =
Hi!
On Friday 07 November 2014 12:12:31 intrigeri wrote:
Could you please apply the following patch to
/usr/share/perl5/App/Parcimonie/Role/HasEncoding.pm and retry?
@@ -24,7 +24,7 @@ with 'App::Parcimonie::Role::HasCodeset';
use namespace::clean;
has 'encoding' = (
-isa=
On Friday 07 November 2014 12:47:53 intrigeri wrote:
I'm going to apply this change, put a new upstream release out, upload
to Debian, and ask the release team for a freeze exception.
Excellent, thanks!
I noticed the 'weird' value of locale too.
Going to dive into that now (but that's not
On Friday 07 November 2014 13:02:47 Diederik de Haas wrote:
I noticed the 'weird' value of locale too.
Going to dive into that now (but that's not your problem)
I tracked down the root cause of the issue and it was indeed related to
locale/charmap.
I have 2 locales on my system (en_US.UTF-8
On Saturday 22 November 2014 12:53:55 Jose David wrote:
Is there any way to check the reason nvidia-driver was installed?
aptitude why nvidia-driver
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
reopen 757941
notfixed 2.19-12
thanks
I just tested the supposedly fixed versions, but it turned out not to fix the
issue of DNS resolving.
# aptitude versions ~ilibc-bin ~ibusybox-static
Package busybox-static:
i 1:1.22.0-9 testing,unstable
On Sunday 09 November 2014 22:01:05 Aurelien Jarno wrote:
The bug *is* fixed in libc6 2.19-12, that said busybox-static version
1.22.0-9 is still statically against an older libc6. That's why you
still see the problem.
This should be fixed in busybox-static version 1:1.22.0-9+b1, which
On Tuesday 11 November 2014 11:38:16 joachim wrote:
The simplest possible testcase is:
- creating two textfiles
- making a zip-archive of one of these file
- using 'right-click-functionality' in dolphin Compress as ZIP-Archive
- opening archive with ark and trying to add other textfile
Package: busybox-static
Version: 1:1.22.0-11
Severity: important
This is basically the same error as with bug #757941, but it was
reassigned to glibc and fixed there. As Aurelien Jarno correctly stated
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757941#120
it was indeed fixed with
Bug nr 768926 is filed against qemu-user-static, and was supposedly fixed with
busybox version 1.22.0-10
My guess is that that upload was supposed to fix bug nr 768876 and not 768926
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
Package: ark
Version: 4:4.14.2-2
Followup-For: Bug #770840
I just encountered this bug too. Downloaded and opened .deb file and
then data.tar.gz within that. Then closed the .deb file - crash.
Stacktrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library
What needs to be done further so that busybox transitions into testing?
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
On Wednesday 03 December 2014 22:02:15 Michael Tokarev wrote:
Since #769129 [1] has been closed, I opened #771208
Ok, thanks. I'll follow that bug then.
Cheers,
Diederik
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
On Thu, 27 Nov 2014 17:00:03 +0100 Cyril Brulebois k...@debian.org wrote:
(Putting on my d-i RM fedora.)
#768876 is tagged jessie-ignore so I'm really unconvinced by the
debian/rules changes.
At this stage, I'd rather see the security fix only.
Wouldn't that entail that #769190 would NOT
On Thursday 11 December 2014 08:52:05 Ivo De Decker wrote:
#768876 is tagged jessie-ignore so I'm really unconvinced by the
debian/rules changes.
It is jessie-ignore just to be non-RC. The fun with static linking
and bugs it discovered shows that proper Built-Using field is really
Just wanted to let you know that I'm experiencing this issue too.
I first noticed the issue several months ago (don't know how long though,
likely more then 6) and noticed the same thing with suspend to disk.
With the nouveau driver suspend to ram did work, but suspend to disk failed
with that
On Tuesday 23 December 2014 15:23:40 Jean Parpaillon wrote:
I am looking for a sponsor for my package averell
* Package name: averell
Version : 1.0a-1
Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License
Package: cdebootstrap
Version: 0.6.4
Severity: important
It is currently not possible to install a testing/stretch system using
cdebootstrap(-static) and it would be nice if it could.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500,
On Sat, 21 Feb 2015 10:49:21 +0100 Kurt Roeckx k...@roeckx.be wrote:
If you just change it to prefer the default server ordering you
should already have a decent list, but it prefers AES256 over
AES128 while there is no need for that.
AFAICT EFF disagrees:
On Thursday 02 July 2015 16:14:21 Martin Steigerwald wrote:
I think this is a transitional issue, until the switch to Plasma 5 / KF 5
is complete.
No, not really.
Apparently a Breaks+Replaces is needed. See for example Bug#789674
signature.asc
Description: This is a digitally signed message
Package: debtags
Version: 2.0
Severity: important
While doing 'aptitude safe-upgrade debtags' dpkg errors out in the
configure stage:
# aptitude safe-upgrade debtags
The following packages will be REMOVED:
libept1.4.12{u}
The following packages will be upgraded:
debtags
1 packages
Downgrade the breeze packages to the version in testing will likely fix it.
See also #794581, #794809 and #794573
signature.asc
Description: This is a digitally signed message part.
forwarded 794055 https://bugs.kde.org/show_bug.cgi?id=345403
thanks
On Thursday 06 August 2015 07:01:51 Antonio Russo wrote:
I've also hit this bug, and so have others:
http://comments.gmane.org/gmane.comp.kde.devel.konsole/22762
Let's tag it accordingly
signature.asc
Description: This is a
On Sunday 16 August 2015 09:16:54 Christian PERRIER wrote:
That is likely the cause. I wouldn't be surprised if it would work if you
also had the testing repos in your /etc/apt/sources.list
Sadly, no.
It may still be possible, but then you would probably have to downgrade a
whole bunch
On Wednesday 19 August 2015 15:05:12 Peter Marschall wrote:
Downgrading those packages to stable is not possible, asd these packages
were introduced after the last release only.
You could downgrade those packages to a previous version by using
snapshot.debian.org
signature.asc
Description:
On Sunday 23 August 2015 09:45:09 Harrison Metzger wrote:
[UPGRADE] libkdecorations2-5:amd64 4:5.3.2-1 - 4:5.3.2-2
[UPGRADE] libkdecorations2private5:amd64 4:5.3.2-1 - 4:5.3.2-2
Those are likely the component versions that are given you troubles.
Downgrading those to version 4:5.3.2-1 will
I just got the upgraded packages and I can confirm that this does make
systemsettings unusable.
Clicking on the 'System Settings' menu item doesn't do anything.
When trying to start it from the command line, I got something similar to the
original bug reporter:
$ systemsettings5
Package: libnepomuk4
Version: 4:4.14.2-5
Severity: wishlist
I wanted to upgrade various libraries from the unstable version to the
experimental version in the hope that it would solve some odd behaviour
in dolphin's Places section (which it did).
But doing that I had to uninstall various nepomuk
Since KeePassX 2.0~beta1-1 is in experimental, it looks like this bug can be
closed.
signature.asc
Description: This is a digitally signed message part.
On Sunday 02 August 2015 14:04:25 Dominik George wrote:
Attached is what I could get in terms of backtrace, but some -dbg
packages appear to be missing.
Installing libglib2.0-0-dbg, qtbase5-dbg, kdelibs5-dbg and kded5-dbg should
get you a more detailed backtrace.
signature.asc
Description:
Try whether installing qml-module-org-kde-kwindowsystem has an effect
signature.asc
Description: This is a digitally signed message part.
On Wednesday 05 August 2015 15:36:09 Tsu Jan wrote:
This is an excerpt from The Debian Administrator's Handbook, section
1.6.3, Migration to Testing:
Do you realize how EXTREMELY condescending just that statement alone is?
And this is just one example which shows how rude (=opposite of polite)
There's another bug related to breeze, but it seems to not show up because it
was 'done': https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794573
It was filed against a different binary package, but (afaik) the same source
package.
signature.asc
Description: This is a digitally signed message
I had this problem too, until I upgraded some packages to their version in
experimental. If I had to make a guess, I think it's kde-runtime, but since I
now have quite a number of packages from experimental, I'm not sure.
So the good news is that a fixed version is available and packed for
Package: kdeconnect
Version: 0.8-1
Severity: important
Since the upgrade of various KDE packages to Plasma 5/KF5, kdeconnect
stopped working.
Upstream seems to support Plasma 5/KF5 and it looks like the Debian
kdeconnect repo also has various things in place for Plasma 5/KF5, but
(apparently)
If you have breeze version 4:5.3.2-4 then that's likely your problem.
Downgrading to the version in testing should fix that.
signature.asc
Description: This is a digitally signed message part.
reopen 794573
thanks
I'm reopening this bug, since I'm experiencing this too (just send a msg
confirming this bug) and just got another person in #debian-kde which ran into
this issue too.
While the gcc-5 transition may be the cause, there should be a RC bug against
breeze to prevent it from
On Friday 07 August 2015 16:36:10 Maurizio Avogadro wrote:
And I'm still wondering how could the small changes in breeze between
-3 and -4 cause such issues...
Updated build daemon with gcc-5 (I think)
signature.asc
Description: This is a digitally signed message part.
On Friday 14 August 2015 12:27:37 Pascal Raton wrote:
*** Reporter, please consider answering these questions, where appropriate
***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this
Forwarding it to the bug report so others can see/use the info as well.
-- Forwarded Message --
Subject: Fwd: Re: Bug#795471: kdegames: no possibility to launch kdegames
Date: Friday 14 August 2015, 19:47:41
From: pc p@orange.fr
To: didi.deb...@cknow.org Diederik de Haas
reassign 794087 src:qtbase-opensource-src
thanks
First of all, I can confirm this bug.
The odd thing is though that it does work in (for example) kate and vim in
konsole, but not in kcalc.
When searching the web for this issue I found various, but conflicting,
information. I'll describe them
Please reply to the bug report and not me personally.
On Saturday 15 August 2015 11:01:32 pc wrote:
I'm very disapointed but with export PATH=$PATH:/usr/games in the bash
file /~/.config/plasma-workspace/env/path.sh, this bashloopcontinuously
with one processor core used to 100%.
On Saturday 15 August 2015 20:03:35 Christian Perrier wrote:
(reporting as important because I'm unsure about the ongoing
transition to Plasma 5)
That is likely the cause. I wouldn't be surprised if it would work if you also
had the testing repos in your /etc/apt/sources.list
signature.asc
On Saturday 15 August 2015 19:35:59 pr1vacy.matt...@cryptolab.net wrote:
I understand SDDM is 'the future' to some people(mostly the systemd
fanbois) but since when do we not have the right to choose our dm?
No one has denied you that choice.
All that was said is that it is not a proper
Package: pidgin
Version: 2.10.11-1
Severity: normal
KDE Plasma 5 no longer supports xembed based system tray icons and
therefor I can't minimize pidgin to the system tray any more.
By using libappindicator1 this should be fixed.
See
On Tuesday 21 July 2015 15:34:13 Ari Pollak wrote:
According to that page, it seems like there would just need to be patches
applied at the GTK level.
I believe that pidgin should be compiled with support for libappindicator for
it to work. I installed libappindicator1 and that didn't solve
Install the kio package to see whether that solves your issue.
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
On Tuesday 14 July 2015 14:35:21 you wrote:
Still not working with kio package. Only see me, others computers are
missing.
You should always send the reply to the bug report, so others can see what
solutions have been tried.
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a
On Tuesday 21 July 2015 12:49:39 Salvo Tomaselli wrote:
I can run a binary located in /usr/bin or in /bin but i can't run binaries
in ~/bin that are in my $PATH and can be executed if I use a terminal.
Please check the value of $PATH as it has changed on my system (I don't know
why though).
On Thursday 16 July 2015 00:19:59 Dmitry Smirnov wrote:
I wonder if upstream having plans to decommission akonadi as it seems to be
our only hope unless they manage to magically fix it...
Apparently some work is underway with Akonadi Next
https://community.kde.org/KDE_PIM/Akonadi_Next
--
GPG:
severity 802656 grave
thanks
On Thursday 22 October 2015 17:53:43 Lisandro Damián Nicanor Pérez Meyer
wrote:
> > dolphin doesn't start as it can't find a Qt plugin:
> [snip]
> > After manually installing libqt5xcbqpa5 it was starting again.
>
> Do you have Recommendations disabled?
On Wednesday 28 October 2015 17:13:14 Gary Dale wrote:
> "Failed to bring up the login screen" is as it says. The screen gets
> switched into graphical mode (blank) but nothing ever displays on it. I
> can bring up a TTY using an alt-Fkey combination but nothing graphical.
Have you checked
forwarded 804717 https://bugs.kde.org/show_bug.cgi?id=355190
thanks
On Wednesday 11 November 2015 12:16:30 Alex Henry wrote:
> Forwarded to upstream bug-tracking system as per maintainer request
> https://bugs.kde.org/show_bug.cgi?id=355190
Updated Debian bug accordingly.
signature.asc
forwarded 804716 https://bugs.kde.org/show_bug.cgi?id=355189
thanks
On Wednesday 11 November 2015 12:15:55 Alex Henry wrote:
> Thank you, I have forwarded the bugs. This one to
> https://bugs.kde.org/show_bug.cgi?id=355189
Updated Debian bug accordingly.
signature.asc
Description: This is a
Package: glx-alternative-nvidia
Version: 0.7.1
Severity: normal
I haven't rebooted yet so I don't know if it will cause problems, but it
does seem odd that on my amd64 a package from armhf is installed as
dependency instead of the one from my 'native' architecture.
Probably a shortcoming of
On Sunday 15 November 2015 11:27:09 Andreas Beckmann wrote:
> > I haven't rebooted yet so I don't know if it will cause problems, but it
> > does seem odd that on my amd64 a package from armhf is installed as
> > dependency instead of the one from my 'native' architecture.
>
> That's weird, but
ckages glx-alternative-nvidia depends on:
ii glx-alternative-mesa 0.7.1
ii glx-diversions0.7.1
ii update-glx0.7.1
The maintainer of that package was able to confirm this behavior.
-- Package-specific info:
** Environment settings:
DEBEMAIL="didi.deb...@cknow.org"
DEBF
forwarded 804883 https://github.com/owncloud/client/issues/3888
thanks
On Thursday 12 November 2015 17:36:41 Soeren D. Schulze wrote:
> The issue has been reported upstream:
> https://github.com/owncloud/client/issues/3888
Updated Debian bug accordingly.
signature.asc
Description: This is a
Package: docker.io
Version: 1.8.2~ds1-2
Followup-For: Bug #799386
Just got an updated docker.io package and the installation of it failed:
Job for docker.service failed because the control process exited with
error code. See "systemctl status docker.service" and "journalctl -xe"
for details.
Package: kactivities
Version: 5.15.0-1
Followup-For: Bug #803451
Saw this bug come by in the ML and checked for myself and noticed the
same issue, only with a newer version of QT. Thus I'm filing this report
so that it's known to also happen with QT 5.5.
-- System Information:
Debian Release:
On Sunday 01 November 2015 14:52:16 Lisandro Damián Nicanor Pérez Meyer wrote:
> This is probably due to #802811, please update your system and try again.
Not in my case, it's still segfaulting here:
$ dmesg | grep kactivitymanage
[ 183.490848] kactivitymanage[1656]: segfault at 7f904f07ecd0 ip
On Tuesday 03 November 2015 23:15:11 Tianon Gravi wrote:
> I'd love to hear suggestions for what we could do at the src:docker.io
> package level WRT this, but I don't see many options.
Change /etc/default/docker as Eric Cooper indicated:
DOCKER_OPTS="--storage-driver overlay"
With that, the
I interpreted the upstream discussion as just closed, not fixed. The reasoning
seems to be in line with what David wrote in message #10
Therefor I've removed the fixed-upstream tag.
signature.asc
Description: This is a digitally signed message part.
On Friday 23 October 2015 19:22:49 Eric Valette wrote:
> I has a working bletooth setup with kde 5.4.2. Audio speaker connexion was
> always working. Since upgrade to qt 5.5.1, I first have a message
> saying to device are not discoverable by default, but even after
> fixing this, it seems
On Saturday 31 October 2015 22:28:30 Eric Valette wrote:
> Now it connects correctly each time. Dunno what has changed (because of
> course I did the remove device before when desesperately tried to make
> it work again).
Feel free to close the bug in that case ;-)
signature.asc
Description:
On Wednesday 14 October 2015 14:56:13 Robi Malik wrote:
> Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
> options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1,
> blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1,
> swapBehavior 2,
On Wednesday 14 October 2015 15:38:34 Robi Malik wrote:
> > See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948
>
> Confirmed: I can fix the problem by adding myself (and
> presumably all users that want to login) to the video group.
That's not exactly the solution/workaround that was
On Wednesday 07 October 2015 13:42:19 Manuel Bilderbeek wrote:
> I can't use gdm3 anymore. So I also can't easily use gnome or my whole
> desktop anymore
Try this:
adduser Debian-gdm video
signature.asc
Description: This is a digitally signed message part.
Package: kdiff3
Version: 0.9.98-2
Severity: normal
With KDE Frameworks 5 based dolphin (15.08) the integration of kdiff3 no
longer works. If I want to diff 2 files in kdiff3 I now have to start kdiff3
and select file 1 and 2. When the integration did work it was just a
matter of selecting both
Package: kde-config-gtk-style
Version: 4:5.3.2-1
Severity: grave
Justification: renders package unusable
When I upgraded this package to 4:5.3.2-1 it disappeared from System
Settings.
I then did a downgrade to the version in testing and it came back. While
keeping System Settings - Application
Hi Jeremy,
On Wednesday 08 July 2015 00:24:02 Jeremy Lainé wrote:
What version of systemsettings are you running?
Still on 4:4.11.13-2 since the latest version made systemsettings not work at
all for me (couple of days ago).
If kde-config-gtk-style would need systemsettings version 4:5.3.2-2,
I just installed plasma-pa and when I rebooted I have two applets too.
Do you have that package too?
signature.asc
Description: This is a digitally signed message part.
On Thursday 03 September 2015 10:30:51 Martin Steigerwald wrote:
> And indeed only kwalletd not kwalletd5 was running. That was due to the fact
> that libkf5wallet-bin which contains the necessary binary was not
> installed.
>
> Not sure exactly where, but somewhere there needs to be at least a
>
On Friday 04 September 2015 15:53:23 Guillaume Dupuy wrote:
> Le 04/09/2015 15:30, Agustin Martin a écrit :
> > Hi, This may well be the same gstreamer1.0-plugins-bad problem
> > reported in http://bugs.debian.org/797227.
>
> Indeed, updating gstreamer1.0-plugins-bad to the experimental version
>
On Sunday 13 September 2015 16:45:54 M G Berberich wrote:
> setting the default size in the profile settings no longer
> works. konsole always starts with 80×31.
This looks like a duplicate of 794055. Can you confirm or deny that?
signature.asc
Description: This is a digitally signed message
Package: yakuake
Version: 2.9.9-1
Severity: minor
This package depends on konsole while it actually should depend on
konsole4-kpart. Since konsole depends on konsole4-kpart (now) on my
architecture it is not a problem, but it would be more correct to depend
on konsole4-kpart.
-- System
affects 794055 yakuake
thanks
I believe this bug is also the reason that yakuake doesn't retain it's width
setting. With me it always reverts back to 80%
signature.asc
Description: This is a digitally signed message part.
affects 794055 - yakuake
thanks
On Monday 14 September 2015 12:41:58 Scott Kitterman wrote:
> > I believe this bug is also the reason that yakuake doesn't retain it's
> > width setting. With me it always reverts back to 80%
>
> I think this is unlikely since yakuake is KDE 4 and konsole is Kf5.
Package: yakuake
Version: 2.9.9-1
Severity: normal
When you change the width, height or both settings of the yakuake window
and then log out and back in again, the width and height setting are
back to the defaults (80% width, 50% height).
I don't know whether there is a relationship between this
On Wednesday 16 September 2015 12:44:02 Lisandro Damián Nicanor Pérez Meyer
wrote:
> > qt5.5 has an abi blocker for things that link against its private symbols,
> > so Konsole outputthings that depend on qtbase-abi-5-4-2 will need to be
> > recompiled against the new qt version.
> >
> >
reassign 798146 src:qtbase-opensource-src
severity 798146 minor
merge 798146 794087
forwarded 798146 https://bugs.kde.org/show_bug.cgi?id=344638
thanks
This is the same bug as #794087 and thus merging them.
It should be resolved with src:qtbase-opensource-src version 5.5.1, but that's
not yet
On Monday 28 September 2015 23:19:30 Aigars Mahinovs wrote:
> I can confirm that the issue rescribed in bug #800327 is real and the
> workaround of adding Debian-gdm user to the video group works.
That workaround was also posted on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948 and the
On Saturday 26 September 2015 10:47:13 Guy Roussin wrote:
> adduser sddm video
This fixed the issue for me too.
signature.asc
Description: This is a digitally signed message part.
On Tuesday 29 September 2015 09:31:09 Luca Boccassi wrote:
> I believe it's a side effect of a new feature introduced by nvidia-driver
> 340.93-2 and glx-alternatives 0.6 combined, namely the auto-generation of
> the xorg.conf and the auto-loading of the necessary kernel modules.
I already have
On Wednesday 30 September 2015 21:39:50 Marc wrote:
> I've a Nvidia graphic card with Nvidia non-free driver.
adduser sddm video
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948 and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800051
signature.asc
Description: This is a digitally
On Saturday 03 October 2015 15:50:00 Mario Blättermann wrote:
> With a newly created user, this doesn't happen, so I assume the config
> files are damaged. Purging ~/.local/share/dolphin wasn't successful,
> after each start (and crash) the folder is back again.
With KF5 most settings are now
> I think the problems started after an upgrade of the NVidia drivert to
> 340.93-X.
adduser sddm video
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799948 and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800051 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800550
On Monday 05 October 2015 21:20:25 Debian FTP Masters wrote:
> Source: glx-alternatives
> Binary: glx-diversions glx-alternative-mesa glx-alternative-nvidia
> glx-alternative-fglrx Architecture: source
> Version: 0.6.1
> Distribution: unstable
> ...
> * Temporarily disable the
Now that 4.7.0 and even 4.7.1 are released, it looks to me that this bug can
be closed.
signature.asc
Description: This is a digitally signed message part.
severity 799948 grave
thanks
I specified severity grave in reportbug, but apparently this wasn't retained,
thus raising it back to grave.
signature.asc
Description: This is a digitally signed message part.
Package: glx-diversions
Version: 0.5.1
Severity: normal
Earlier today I upgraded to version 0.6.0 of glx-diversions and
glx-alternative-mesa and glx-alternative-nvidia and after a reboot the
sddm-greeter crashed which made it impossible to start my KDE Plasma 5
desktop.
After downgrading to
On Friday 25 September 2015 01:12:58 Diederik de Haas wrote:
> It wasn't a problem to log into a console with Ctl+Alt+F1 and is how I
> collected various info from the boot process, see attachments.
> The last line from kern.log seems particular relevant.
My guess was correct.
With
On Thursday 24 September 2015 23:35:50 Hynek Vychodil wrote:
> $ aptitude search ~ikwin
> i A kwin-common
> i A kwin-data
> i A kwin-style-breeze
> i A kwin-wayland
> i A kwin-x11
> i A libkwin4-effect-builtins1
> i A libkwineffects6
> i A libkwinglutils6
> i A libkwinxrenderutils6
> i A
What does 'aptitude search ~ikwin' return?
signature.asc
Description: This is a digitally signed message part.
On Saturday 26 September 2015 03:16:08 Alf Gaida wrote:
> Sep 26 02:57:44 razorbox sddm-greeter[2582]: Failed to create OpenGL context
> for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize
> 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
> alphaBufferSize -1,
On Friday 25 September 2015 12:44:17 Diederik de Haas wrote:
> What was funny though is that after the kdm login screen and providing my
> credentials, it seemed to switch over to sddm.
Apparently not sddm, as that was now purged, but likely something from breeze.
> I'll now purge sdd
On Friday 25 September 2015 01:12:58 Diederik de Haas wrote:
> > Does any other display manager work with 0.6.0? (kdm seems to work for
> > me with the changes from 0.6.0).
>
> I'll now (also) install kdm
I installed kdm and selected that as the default ... and it didn't cra
On Friday 25 September 2015 12:05:04 you wrote:
> nvidia-* update from 340.93-1 to 340.93-2 occured at the same time on my
> machine, but reverting back to 340.93-1 did not solve de problem.
To solve the problem I had to revert back to glx-diversions 0.5.1.
But in order to do so, it _seemed_ that
On Tuesday 06 October 2015 11:54:15 Andy Wood wrote:
> Package: sddm
> ...
> Reboot after installing nvidia 340.93-3 (latest testing version).
See https://bugs.debian.org/799948
(workaround "adduser sddm video")
signature.asc
Description: This is a digitally signed message part.
101 - 200 of 1659 matches
Mail list logo
