Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

First to break Jessie wins!

Here you can discuss every aspect of Debian. Note: not for support requests!
Message
Author
mikshaw
Posts: 6
Joined: 2013-01-12 14:42

Re: First to break Jessie wins!

#21 Post by mikshaw »

Yay! In addition to not being able to use the 3.8 kernel, my apt is now hosed, and aptitude is recommending the removal of 108 packages that were working fine yesterday (and many of which i simply refuse to live without). I'm thinking of maybe dumping jessie/sid and installing a fresh jessie...the thought of going through that just a few months after my last install is pretty loathsome though. Maybe i'll just wait and see if my apt problems are due to a cockup in the repo....

robertbiloute
Posts: 34
Joined: 2013-01-08 16:04

Re: First to break Jessie wins!

#22 Post by robertbiloute »

I had several problems these days, then I made a /etc/apt/preferences file with testing as high priority and sid as a second choice, then apt-get upgrade several times.
This triggered several downgrading of packages from sid to testing, some packages were removed, but now it seems everything is back to normal and I could reinstall the few packages that were removed during the upgrade.
Debian testing on a DELL latitude E6530 + XFCE + compiz

User avatar
edbarx
Posts: 5401
Joined: 2007-07-18 06:19
Location: 35° 50 N, 14 º 35 E
Been thanked: 2 times

Re: First to break Jessie wins!

#23 Post by edbarx »

robertbiloute wrote:I had several problems these days, then I made a /etc/apt/preferences file with testing as high priority and sid as a second choice, then apt-get upgrade several times.
This triggered several downgrading of packages from sid to testing, some packages were removed, but now it seems everything is back to normal and I could reinstall the few packages that were removed during the upgrade.
A very good hint. Thanks for sharing. :)

In my case, I am better off using Jessie because Wheezy's kernel fails to turn on the laptop's display backlight.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.

mikshaw
Posts: 6
Joined: 2013-01-12 14:42

Re: First to break Jessie wins!

#24 Post by mikshaw »

I ended up doing aptitude --full-resolver safe-upgrade, which removed 245 packages in order to resolve what i think was an architecture conflict. That seemed a bit drastic, but now, after reinstalling several of my day-to-day apps, my system is back to being simply stuck with a 3rd party kernel for a while, and otherwise running smoothly.

robertbiloute
Posts: 34
Joined: 2013-01-08 16:04

Re: First to break Jessie wins!

#25 Post by robertbiloute »

hmpf... today I had an upgrade (inside testing) to libglib2.0-0 version 2.36.1-2 build 1 and it seems the random crash are back again (still a segfault)
Debian testing on a DELL latitude E6530 + XFCE + compiz

robertbiloute
Posts: 34
Joined: 2013-01-08 16:04

Re: First to break Jessie wins!

#26 Post by robertbiloute »

Debian testing on a DELL latitude E6530 + XFCE + compiz

TonyVanDam
Posts: 67
Joined: 2013-05-17 19:22

Re: First to break Jessie wins!

#27 Post by TonyVanDam »

As of Wednesday morning, 5/29/2013, I discontinued using Wheezy (READ: Debian Stable really does get boring rather quickly! :shock: :lol: ) and upgraded to Jessie.

Apart from not having sound in xGalaga anymore, Jessie is still solid thus far. Since LXDE is my DE of choice, I cannot comment on any possible breakage with the other DEs.

As for WMs, Openbox & Fluxbox are stable. 8)

User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: First to break Jessie wins!

#28 Post by llivv »

I looked at downgrading a sid install to jessie, but there were only a few admin packages that needed downgrading.
I looked at downgrading it to stable and there were so many packages that need to be downgraded ( can you say libs ) that I just put the sources.list back to sid.

What is considered breaking jessie?
breaking jessie in?
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.

confuseling
Posts: 2121
Joined: 2009-10-21 01:03

Re: First to break Jessie wins!

#29 Post by confuseling »

Breaking Jessie... Oh, I don't know.

Bonus points for:
Corrupted data
Can't boot
Damaged hardware
Wailing
Gnashing of teeth

We'll know it when we see it. :)

----

Some peculiarity going on with KDE apps on my system at the minute...

Code: Select all

% dolphin
dolphin(32558): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_trash'.
" 
dolphin(32558): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_file'.
" 
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(32558)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
The Forum's search box is terrible. Use site specific search, e.g.
https://www.google.com/search?q=site%3A ... terms+here

TonyVanDam
Posts: 67
Joined: 2013-05-17 19:22

Re: First to break Jessie wins!

#30 Post by TonyVanDam »

So far, Jessie is as stable on my desktop as Wheezy was before the dist-upgrade. No chance of breakages whatsoever.

At this point, you would have to "throw cautions in the wind" and dist-upgrade to Sid if you really want to break anything. I dare to say that Jessie might be the best Debian Testing ever. :mrgreen: Am I wrong?!?

sej7278
Posts: 225
Joined: 2011-06-11 17:03

Re: First to break Jessie wins!

#31 Post by sej7278 »

I guess something like gnome-greeter is broken as I just boot to a bunch of "ACPID: client disconnected messages" as of just now. switching to a TTY and running startx gets me into gnome just fine, booting into 3.8 kernel doesn't fix it, so its not nvidia drivers, 3.9 kernel or gnome3.

nothing at all useful in the logs, in fact most of the logs haven't been touched other than gdm3 and xorg.

list of packages just dist-upgraded, i recall a minor warning about dconf, any ideas how to fix?

edit: another update last night fixed it, was one of the dconf/libc updates i guess.

Code: Select all

gcc-4.8-base:amd64 4.8.1-1
libstdc++6:amd64 4.8.1-1
libc-bin:amd64 2.17-4
libgcc1:amd64 1:4.8.1-1
libc-bin:amd64 2.17-4
fontconfig:amd64 2.9.0-7.1
install-info:amd64 5.1.dfsg.1-3
man-db:amd64 2.6.3-7
libglib2.0-0:amd64 2.36.1-2build1
hicolor-icon-theme:all 0.12-1
gnome-menus:amd64 3.8.0-1
desktop-file-utils:amd64 0.21-1
mime-support:all 3.54
gconf2:amd64 3.2.5-1+build1
libx32gcc1:amd64 1:4.8.1-1
lib32gcc1:amd64 1:4.8.1-1
libx32stdc++6:amd64 4.8.1-1
libitm1:amd64 4.8.1-1
libgomp1:amd64 4.8.1-1
libx32gomp1:amd64 4.8.1-1
libx32quadmath0:amd64 4.8.1-1
lib32stdc++6:amd64 4.8.1-1
libquadmath0:amd64 4.8.1-1
libgfortran3:amd64 4.8.1-1
libx32itm1:amd64 4.8.1-1
libobjc4:amd64 4.8.1-1
lib32quadmath0:amd64 4.8.1-1
lib32gomp1:amd64 4.8.1-1
lib32itm1:amd64 4.8.1-1
libarchive13:amd64 3.1.2-7
libdconf1:amd64 0.16.0-3
linux-image-3.9-1-amd64:amd64 3.9.4-1
poppler-data:all 0.4.6-4
wget:amd64 1.14-2
acpica-tools:amd64 20130517-1
dconf-service:amd64 0.16.0-3
dconf-gsettings-backend:amd64 0.16.0-3
dconf-cli:amd64 0.16.0-3
dconf-editor:amd64 0.16.0-3
dconf-tools:all 0.16.0-3
libpanel-applet-4-0:amd64 3.4.2.1-5
gir1.2-panelapplet-4.0:amd64 3.4.2.1-5
libtotem-plparser17:amd64 3.4.5-1
gir1.2-totem-plparser-1.0:amd64 3.4.5-1
gnome-panel-data:all 3.4.2.1-5
gnome-panel:amd64 3.4.2.1-5
iasl:all 20130517-1
libgssdp-1.0-3:amd64 0.14.3-1
linux-headers-3.9-1-common:amd64 3.9.4-1
linux-kbuild-3.9:amd64 3.9.4-1
linux-headers-3.9-1-amd64:amd64 3.9.4-1
linux-headers-amd64:amd64 3.9+49
linux-image-amd64:amd64 3.9+49
python-dbus-dev:all 1.2.0-2
python-dbus:amd64 1.2.0-2
libc-bin:amd64 2.17-4
man-db:amd64 2.6.3-7
hicolor-icon-theme:all 0.12-1
libglib2.0-0:amd64 2.36.1-2build1

Post Reply