LMDE Breakages (Tracking SID)

Archived topics about LMDE 1 and LMDE 2
Locked
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

wayne128 wrote:
autocrosser wrote: Hi Wayne!!!

Came up #1 on a google search: https://bbs.archlinux.org/viewtopic.php?id=145075 Looks to "fix" your problem--Tell me if that works.....
.
hi autocrosser,

i read this
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.
but struggle on how to do systemctl reenable slim.service :oops:

Edit: oops.. what am i doing?
this installation has lightdm, I change to autologin via lightdm
no slim installed.. so i guess i just ignore the slim-service as it does no harm :!: ??
Substitute your display manager for "slim"-- GDM, etc.... So it "should" be systemctl reenable ligntdm.service (not really sure about that---I use reenable gdm.service )
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
woodsman
Level 4
Level 4
Posts: 305
Joined: Tue May 11, 2010 10:22 pm

Re: LMDE Breakages (Tracking SID)

Post by woodsman »

i hope you know this thread are for those people who track Debian unstable repos or tracking Debian sid
Ah. No, I did not know that. Now I do. :)

I thought the thread was some kind of LMDE mega thread for reporting bugs and issues. Sorry!
If you must install gphoto2 and hardinfo
I downloaded the deb files and used apt-get. hardinfo installed with no problems but gphoto2 puked with dependency errors. I did not pursue as I had other things to do.
So the few things we normally do are:
I have experience testing with another project. I hope eventually to be able to do the same here. Just not today or in the near future. :)
GeneBenson
Level 4
Level 4
Posts: 352
Joined: Fri Sep 17, 2010 9:55 pm

Re: LMDE Breakages (Tracking SID)

Post by GeneBenson »

Hi autocrosser,

I'm on Systemd. I had a boot.log with SysV and bootlogd. After switching to Systemd boot.log was no longer updated. So I removed bootlogd, but still nothing. Oh well. :cry:
autocrosser wrote:
GeneBenson wrote:Hi autocrosser,

Thanks for the quick reply. I just asked because I don't have a boot.log at all. :?
Well-- As soon as you goto SystemD you will.... ;)

And I highly recommend the pdf & link I posted on the bottom of page 6 to anyone that wants to get more than the basic config out of it....I'm glad we didn't go with Upstart (no flamewars intended....)
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

@wayne:

Code: Select all

wayne@hp8000:~$ dmesg | grep error
[    0.236260] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
wayne@hp8000:~$ dmesg | grep fail
[    0.236250] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
[    0.236254] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f744ff98), AE_ALREADY_EXISTS (20131115/psparse-536)
[    0.236264] acpi PNP0A08:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
[    5.584464] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
wayne@hp8000:~$ 
it looks better now :3
as you can see, the only wrong with systemd is that it unable to start display-manager.service. it's basicly just a warn message. if your display manager work just fine you can ignore it. as for the critical chain result, since you need samba on your system nothing can be done here.
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

For test and comparison purpose, I uninstall Modem manager and Samba/samba-common-bin

capture data for comparison

Code: Select all

wayne@hp8000:~$ dmesg |tail
[   11.951997] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   11.979010] FS-Cache: Loaded
[   12.016985] FS-Cache: Netfs 'nfs' registered for caching
[   12.081677] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   14.488163] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   14.592090] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   14.592214] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   15.261826] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input16
[   17.644865] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[   17.644999] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
wayne@hp8000:~$ 

Code: Select all

wayne@hp8000:~$ dmesg | grep fail
[    0.236251] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
[    0.236255] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f744ff98), AE_ALREADY_EXISTS (20131115/psparse-536)
[    0.236264] acpi PNP0A08:00: _OSC failed (AE_ALREADY_EXISTS); disabling ASPM
wayne@hp8000:~$ 

Code: Select all

wayne@hp8000:~$ systemd-analyze
Startup finished in 3.829s (kernel) + 14.061s (userspace) = 17.890s
wayne@hp8000:~$ 

Code: Select all

wayne@hp8000:~$ systemd-analyze blame
          5.513s acpi-support.service
          4.466s exim4.service
          4.013s lightdm.service
          3.849s avahi-daemon.service
          3.777s systemd-logind.service
          3.422s bootlogs.service
          2.954s acpi-fakekey.service
          2.641s keyboard-setup.service
          2.082s live-config.service
          1.631s sys-kernel-debug.mount
          1.629s dev-hugepages.mount
          1.576s dev-mqueue.mount
          1.381s rsyslog.service
          1.373s hdparm.service
          1.344s rpcbind.service
          1.308s networking.service
          1.306s systemd-modules-load.service
          1.297s console-screen.service
           902ms lm-sensors.service
           777ms systemd-udev-trigger.service
           774ms saned.service
           705ms systemd-tmpfiles-setup-dev.service
           671ms cron.service
           563ms systemd-tmpfiles-setup.service
           529ms upower.service
           442ms udev-finish.service
           442ms nfs-common.service
           437ms minissdpd.service
           364ms swapfile.swap
           345ms systemd-remount-fs.service
           342ms systemd-sysctl.service
           324ms sys-fs-fuse-connections.mount
           310ms systemd-user-sessions.service
           303ms console-setup.service
           278ms systemd-fsck-root.service
           221ms console-kit-daemon.service
           177ms console-kit-log-system-start.service
           116ms udisks2.service
           109ms polkitd.service
            99ms systemd-update-utmp-runlevel.service
            93ms alsa-restore.service
            89ms smartmontools.service
            76ms motd.service
            75ms nmbd.service
            74ms glances.service
            48ms hddtemp.service
            46ms systemd-tmpfiles-clean.service
            41ms systemd-udevd.service
            40ms samba-ad-dc.service
            19ms rc-local.service
            12ms pppd-dns.service
             3ms systemd-journal-flush.service
             3ms network-manager.service
             2ms systemd-random-seed-load.service
             2ms live.service
             2ms run-user.mount
             2ms live-tools.service
             1ms run-lock.mount
             1ms smbd.service
wayne@hp8000:~$ 
graphical.target @13.960s
└─multi-user.target @13.960s
└─acpi-support.service @8.446s +5.513s
└─basic.target @8.406s
└─sockets.target @8.406s
└─dbus.socket @8.406s
└─sysinit.target @8.390s
└─nfs-common.service @7.948s +442ms
└─rpcbind.target @7.948s
└─rpcbind.service @6.603s +1.344s
└─network.target @6.602s
└─networking.service @5.294s +1.308s
└─local-fs.target @5.038s
└─run-rpc_pipefs.mount @8.265s
└─local-fs-pre.target @5.035s
└─systemd-remount-fs.service @4.689s +345ms
└─keyboard-setup.service @2.047s +2.641s
└─systemd-udevd.service @2.005s +41ms
└─systemd-tmpfiles-setup-dev.service @1.299s +705ms
└─systemd-journald.socket @1.217s
└─-.mount @1.217s
wayne@hp8000:~$


hmm.. better but lost functionality compared with old sysv-init.
however the tools using commands are cool. :mrgreen:


I know, per GregE, etc, there is a better way to cut boot time :lol:
waiting for available cash to buy a reasonable SSD :idea:
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GeneBenson wrote:Hi autocrosser,

I'm on Systemd. I had a boot.log with SysV and bootlogd. After switching to Systemd boot.log was no longer updated. So I removed bootlogd, but still nothing. Oh well. :cry:
Interesting---

I don't remember doing anything special--my boot.log updates as I would expect. I'll look into it...
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

wayne128 wrote:

hmm.. better but lost functionality compared with old sysv-init.
however the tools using commands are cool. :mrgreen:


I know, per GregE, etc, there is a better way to cut boot time :lol:
waiting for available cash to buy a reasonable SSD :idea:
I just got a Samsung 840 256G from Newegg for $159 shipped--more than enough to run anything you want... I've been seeing the 120G ones going for around $100. You just need to setup trim & offload temp files to a normal drive....
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

GeneC wrote:Try #2
Still not working.
Try #3
Finally joined the club... :lol: There was something missing or broken in my old SID install. I downloaded the daily "Jessie" XFCE iso, installed and upgraded to SID, and systemd installed fine, and booted as it should. If I find out what was broke or missing in my old install, i'll post in case its an issue for others. (Could have been the kernel.. I was using a Siduction RC 3.15.xx)..?

=========

A nice bootup speed improvement.

Code: Select all

gene@debian:~$ systemd-analyze
Startup finished in 3.692s (kernel) + 6.305s (userspace) = 9.997s

Code: Select all

gene@debian:~$ systemd-analyze blame
          2.525s keyboard-setup.service
          2.219s exim4.service
          2.054s bootlogs.service
          1.669s NetworkManager.service
          1.661s ModemManager.service
          1.533s accounts-daemon.service
          1.489s lightdm.service
          1.477s udisks2.service
          1.442s avahi-daemon.service
          1.432s systemd-logind.service
          1.291s ntp.service
           608ms rsyslog.service
           591ms console-setup.service
           496ms hddtemp.service
           493ms cron.service
           492ms systemd-modules-load.service
           454ms saned.service
           404ms dev-mqueue.mount
           403ms dev-hugepages.mount
           395ms sys-kernel-debug.mount
           352ms hdparm.service
           337ms console-kit-log-system-start.service
           295ms nfs-common.service
           284ms systemd-udev-trigger.service
           248ms networking.service
           199ms upower.service
           181ms systemd-fsck-root.service
           155ms systemd-udevd.service
           147ms rtkit-daemon.service
           145ms systemd-tmpfiles-setup-dev.service
           142ms udev-finish.service
           121ms pulseaudio.service
           120ms systemd-user-sessions.service
           114ms kbd.service
           106ms lm-sensors.service
            81ms rc-local.service
            80ms rpcbind.service
            75ms systemd-sysctl.service
            74ms polkitd.service
            68ms dev-disk-by\x2duuid-24e0680a\x2de72f\x2d4aac\x2da3fd\x2dc0792174fdd3.swap
            50ms console-kit-daemon.service
            45ms systemd-update-utmp-runlevel.service
            38ms systemd-random-seed-load.service
            38ms alsa-restore.service
            27ms systemd-tmpfiles-setup.service
            16ms motd.service
            12ms systemd-remount-fs.service
            10ms pppd-dns.service
             3ms systemd-journal-flush.service
             1ms run-user.mount
             1ms run-lock.mount
             1ms sys-fs-fuse-connections.mount
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

@wayne: you don't have to uninstall it :3
simply disable the service to start at boot via 'systemctl disable <servicename>'. since samba is still using sysvinit (it doesn't have systemd native service file yet) you can also use sysv-rc-conf to disable it. with this method you can activate samba only when it needed.

come to think of it, I guess I have the worst boot time here. samba activated:

Code: Select all

systemd-analyze 
Startup finished in 3.932s (kernel) + 26.559s (userspace) = 30.491s

systemd-analyze blame 
         14.472s nmbd.service
         14.053s samba-ad-dc.service
GregE
Level 4
Level 4
Posts: 472
Joined: Sun Jan 16, 2011 6:24 am
Location: Melbourne, Australia

Re: LMDE Breakages (Tracking SID)

Post by GregE »

Wayne,

I am using LightDM and Gnome Shell 3.12 and systemd from experimental. I load Samba as I need it for my home network. My boot time is accelerated by the SSD, but even with an HDD Samba does not really delay boot significantly. It is so fast it was a surprise the first time it booted. When I use GDM my boot time is nearly a minute and Gnome Shell does not function correctly. That is GDM from experimental. I await updates to see if I can get GDM back, but for the moment all is well.

Code: Select all

systemd-analyze blame 

           696ms nmbd.service
           668ms samba-ad-dc.service
           557ms sssd.service
           393ms keyboard-setup.service
           391ms NetworkManager.service
           329ms loadcpufreq.service
           314ms systemd-fsck-root.service
           302ms hdparm.service
           287ms lvm2.service
           267ms ModemManager.service
           224ms accounts-daemon.service
           223ms tor.service
           200ms lightdm.service
           194ms avahi-daemon.service
           193ms systemd-logind.service
           158ms ntp.service
           143ms alsa-restore.service
           136ms smbd.service
           134ms kdm.service
            77ms rsyslog.service
            76ms console-setup.service
            71ms networking.service
            69ms bootlogs.service
plus more
They are all milliseconds, not seconds

And just to rub it in

Code: Select all

systemd-analyze
Startup finished in 1.192s (kernel) + 1.625s (userspace) = 2.818s
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Hmmm...

I'm all Experimental sources---running a normal desktop--& I'm running GDM3. Mounting my backup install & the "fall-back" install, so my times are slower....still, SSDs really make a difference......

Code: Select all

systemd-analyze blame

          4.027s plymouth-start.service
          1.215s apache2.service
           839ms systemd-fsck@dev-disk-by\x2duuid-7d134d4b\x2d020c\x2d4c69\x2da8
           716ms hddtemp.service
           629ms systemd-fsck@dev-disk-by\x2duuid-083a8b7a\x2d334c\x2d4567\x2dbb
           585ms nmbd.service
           552ms samba-ad-dc.service
           435ms systemd-fsck@dev-disk-by\x2duuid-0eba7eb5\x2da57a\x2d402d\x2da9
           434ms systemd-fsck@dev-disk-by\x2duuid-92f3ffaa\x2d19b8\x2d4006\x2d8a
           432ms systemd-fsck@dev-disk-by\x2duuid-d27ad08b\x2d78b4\x2d44de\x2da9
           328ms mnt-Mint16home.mount
           294ms NetworkManager.service
           265ms accounts-daemon.service
           178ms bluetooth.service
           176ms avahi-daemon.service
           163ms systemd-logind.service
           125ms systemd-fsck@dev-disk-by\x2duuid-1e6c9958\x2dcc1c\x2d4fd0\x2db9
           123ms packagekit.service
           115ms smbd.service
            92ms keyboard-setup.service
            87ms polkit.service
            84ms systemd-fsck-root.service
            82ms alsa-restore.service
            80ms console-setup.service
            80ms media-Storage.mount
            73ms networking.service
            70ms ntp.service
            70ms rsyslog.service
            69ms systemd-modules-load.service
            68ms kmod-static-nodes.service
            67ms systemd-udev-trigger.service
            65ms nfs-common.service
            64ms sys-kernel-debug.mount
            64ms dev-hugepages.mount
            55ms dev-mqueue.mount
            51ms udisks2.service
            50ms systemd-sysctl.service
            49ms binfmt-support.service
            36ms colord.service
            36ms hdparm.service
            28ms rpcbind.service
            28ms lm-sensors.service
            27ms bootlogs.service
            26ms minissdpd.service
            26ms plymouth-quit.service
            26ms plymouth-quit-wait.service
            24ms console-kit-daemon.service
            23ms nvidia-kernel.service
            23ms sysfsutils.service
            19ms kbd.service
            18ms user@1001.service
            17ms gdomap.service
            16ms mnt-Mint16.mount
            14ms systemd-tmpfiles-setup-dev.service
            11ms gdm3.service
            11ms motd.service
            11ms smartmontools.service
            11ms home.mount
            11ms plymouth-read-write.service
            10ms rtkit-daemon.service
             9ms console-kit-log-system-start.service
             9ms user@113.service
             9ms systemd-hostnamed.service
             9ms systemd-random-seed.service
             8ms systemd-remount-fs.service
             7ms upower.service
             7ms proc-sys-fs-binfmt_misc.mount
             7ms saned.service
             7ms systemd-user-sessions.service
             5ms systemd-tmpfiles-setup.service
             4ms dev-disk-by\x2duuid-96a36798\x2d9c4b\x2d4c48\x2db5a6\x2df7d951a
             4ms systemd-localed.service
             4ms rc-local.service
             3ms pulseaudio.service
             3ms mnt-MintEX2home.mount
             3ms mnt-MintEX2.mount
             2ms systemd-udevd.service
             2ms tmp.mount
             1ms systemd-update-utmp.service
             1ms udev-finish.service
             1ms systemd-journal-flush.service
             1ms systemd-update-utmp-runlevel.service
             1ms run-user.mount
             1ms sys-fs-fuse-connections.mount
             1ms run-lock.mount
I'm not feeling TOO bad.....

Code: Select all

systemd-analyze
Startup finished in 2.227s (kernel) + 5.439s (userspace) = 7.667s
I could get the time "almost" down by removing Plymouth......
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GregE wrote:When I use GDM my boot time is nearly a minute and Gnome Shell does not function correctly. That is GDM from experimental. I await updates to see if I can get GDM back, but for the moment all is well.
I'm not sure why we are having such "mileage" differences with GDM3. Maybe there is a depend that is not quite right on your system?

My current load time for that service is: 11ms gdm3.service & I see yours is: 200ms lightdm.service Not sure whats going on there.....
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

Hi Gene,

Congratulation, you got it.
your boot time is very good. may be you have 8 core CPU plus 16G RAM? :mrgreen:
Last edited by wayne128 on Wed Apr 30, 2014 7:26 am, edited 1 time in total.
GregE
Level 4
Level 4
Posts: 472
Joined: Sun Jan 16, 2011 6:24 am
Location: Melbourne, Australia

Re: LMDE Breakages (Tracking SID)

Post by GregE »

autocrosser wrote:
GregE wrote:When I use GDM my boot time is nearly a minute and Gnome Shell does not function correctly. That is GDM from experimental. I await updates to see if I can get GDM back, but for the moment all is well.
I'm not sure why we are having such "mileage" differences with GDM3. Maybe there is a depend that is not quite right on your system?

My current load time for that service is: 11ms gdm3.service & I see yours is: 200ms lightdm.service Not sure whats going on there.....
You are correct, I think. My system is damaged somewhere. I even tried installing KDE and KDM and then removing as much of Gnome and Xfce as I could and running autoremove to clean up orphaned lib files. KDE booted quickly and ran perfectly. I then started again and re-installed Gnome Shell. Yet, it is still the same. Once 3.12 is in testing and systemd has had a few weeks to settle I will grab a snapshot and start again.

Then again it is just fine with LightDM and I am happily using Gnome 3.12. I am watching my LMDE + testing Xfce machine to see what happens when systemd hits testing. I suspect it will be painless.

:)
GeneC
Level 7
Level 7
Posts: 1598
Joined: Fri Sep 03, 2010 1:59 pm
Location: Maine, USA

Re: LMDE Breakages (Tracking SID)

Post by GeneC »

wayne128 wrote:Hi Gene,

Congratulation, you got it.
your boot time is very good. may be you have 8 core CPU plus 16G RAM? :mrgreen:
Hi Wayne... :)
Nope! ONLY 4 core and 12GB ram... :lol:

Code: Select all

gene@xubuntu:~$ inxi -CI
CPU:       Quad core AMD Phenom II X4 955 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4a svm) 
           Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz 3: 800.00 MHz 4: 800.00 MHz
Info:      Processes: 207 Uptime: 1:01 Memory: 1004.9/12016.9MB Client: Shell (bash) inxi: 1.9.17 
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

GeneC wrote: Finally joined the club... :lol:
A nice bootup speed improvement.
Looks good!!
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
autocrosser
Level 4
Level 4
Posts: 436
Joined: Tue Dec 28, 2010 5:00 pm
Location: Eagle Point, Oregon

Re: LMDE Breakages (Tracking SID)

Post by autocrosser »

Heres my trim script for anyone using SSD...just name it trim--mod as needed & put it in /etc/cron.daily....

Code: Select all

#!/bin/sh
LOG=/var/log/trim.log
echo "*** $(date -R) ***" >> $LOG
fstrim -v / >> $LOG
fstrim -v /home >> $LOG
fstrim -v /mnt/MintEX2 >> $LOG
fstrim -v /mnt/MintEX2home >> $LOG
"Let's nobody be dead today----Looks very bad on my report" One of my favorite lines from AVATAR :)
Linux User# 395230
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

sid d-u yesterday kill my pulseaudio. I forget what exactly got updated on that date but any program require pulseaudio won't start until pulse got killed. the good news, removing pulse will fix this issue. the bad news, after one day tinkering with my laptop I found that pulseaudio is dead but I can't debug it at all. dmesg simply tells nothing and 'pulseaudio -vvvv' command got freezed in the middle without any usefull information.
wayne128
Level 10
Level 10
Posts: 3412
Joined: Tue Jul 13, 2010 12:15 am

Re: LMDE Breakages (Tracking SID)

Post by wayne128 »

fully d-u a while ago. kernel is now 3.14-1

no issue.. listening and playing media file from NAS with vlc...

Code: Select all

root@hp8000:/home/wayne# uname -a
Linux hp8000 3.14-1-686-pae #1 SMP Debian 3.14.2-1 (2014-04-28) i686 GNU/Linux
root@hp8000:/home/wayne# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@hp8000:/home/wayne# 
kurotsugi
Level 6
Level 6
Posts: 1026
Joined: Fri Jan 25, 2013 3:54 am

Re: LMDE Breakages (Tracking SID)

Post by kurotsugi »

that's a lucky you :3
I've been tried reinstall pulse several times. I've also been swinging from sid to jessie to test jessie > sid upgrade and the result is always same. pulse dead. let see if it could survive while in testing for 10 days later.
Locked

Return to “LMDE Archive”