Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

  1. #11
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,968

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Quote Originally Posted by giulio_buccini View Post
    I simply saw the notification of new updates available from the notification-panel in the bottom bar. Then, I just clicked on "install updates". That's all...
    Officially, Tumbleweed users should never ever click on install updates in the notification widget. Traditionally, TW can only be properly upgraded by using zypper dup. Last I heard, changing that was a work in progress. Until that project completes, updating does not apply to TW. Every release of TW is considered a new release, subject only to upgrading, which is recommended to be done from one of the vttys (outside of X), so that a restart of X because of the upgrade cannot abort the upgrade process.

    If you actually intended to be running TW, all those 15.0 repos should have been removed.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  2. #12
    Join Date
    Sep 2012
    Posts
    5,317

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Quote Originally Posted by mrmazda View Post
    TW can only be properly upgraded by using zypper dup. Last I heard, changing that was a work in progress. Until that project completes
    This project (whatever you mean here) has completed months ago - PackageKit recognizes Tumbleweed and performs equivalent of "zypper dup" since 2019-02-14.

  3. #13
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,968

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Quote Originally Posted by arvidjaar View Post
    This project (whatever you mean here) has completed months ago - PackageKit recognizes Tumbleweed and performs equivalent of "zypper dup" since 2019-02-14.
    That's the project I meant. With PackageKit should use "zypper dup" instead of "zypper up" on Tumbleweed remaining an open bug I wouldn't consider the project complete. It hasn't appeared on https://news.opensuse.org/ yet either.

    Anyway, it would not likely be relevant to a mixed repo mess as this thread's OP apparently has.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  4. #14
    Join Date
    Feb 2010
    Location
    Munich (Germany)
    Posts
    137

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    I don't know if there is a previous "snapshot" available. I heard something about Snapper, but I have no practical knowledge of it. Anyway I will check it today.

    P.S.
    Sometimes I remember the old times when all you have is the autoexec.bat...
    O.S. = Linux 3.4.11-2.16-desktop x86_64
    Desktop = KDE 4.8.5 (4.8.5) "release 2"
    Distribution = openSUSE 12.2 (x86_64)

  5. #15
    Join Date
    Feb 2010
    Location
    Munich (Germany)
    Posts
    137

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Here the output of snapper list:
    Code:
    Type   | #  | Pre # | Date                     | User | Cleanup | Description                | Userdata     
    -------+----+-------+--------------------------+------+---------+----------------------------+--------------
    single | 0  |       |                          | root |         | current                    |              
    single | 1  |       | Sat Dec 15 13:33:01 2018 | root |         | first root filesystem      |              
    pre    | 43 |       | Thu Mar 14 19:45:53 2019 | root | number  | zypp(zypper)               | important=yes
    post   | 46 | 43    | Thu Mar 14 19:50:47 2019 | root | number  |                            | important=yes
    pre    | 60 |       | Sun Apr 21 13:00:47 2019 | root | number  | zypp(zypper)               | important=yes
    post   | 61 | 60    | Sun Apr 21 13:15:53 2019 | root | number  |                            | important=yes
    pre    | 62 |       | Sun Apr 21 13:56:32 2019 | root | number  | zypp(packagekitd)          | important=yes
    post   | 63 | 62    | Sun Apr 21 14:00:25 2019 | root | number  |                            | important=yes
    pre    | 66 |       | Fri May 31 11:46:33 2019 | root | number  | zypp(zypper)               | important=yes
    pre    | 75 |       | Fri May 31 12:46:25 2019 | root | number  | zypp(packagekitd)          | important=yes
    post   | 76 | 75    | Fri May 31 12:54:54 2019 | root | number  |                            | important=yes
    pre    | 77 |       | Wed Jun  5 15:32:26 2019 | root | number  | zypp(packagekitd)          | important=no 
    post   | 78 | 77    | Wed Jun  5 15:33:02 2019 | root | number  |                            | important=no 
    pre    | 79 |       | Thu Jun  6 18:37:52 2019 | root | number  | zypp(packagekitd)          | important=no 
    post   | 80 | 79    | Thu Jun  6 18:38:07 2019 | root | number  |                            | important=no 
    pre    | 81 |       | Thu Jun  6 23:29:39 2019 | root | number  | yast OneClickInstallWorker |              
    pre    | 82 |       | Thu Jun  6 23:31:15 2019 | root | number  | zypp(ruby.ruby2.5)         | important=no 
    post   | 83 | 82    | Thu Jun  6 23:31:20 2019 | root | number  |                            | important=no 
    post   | 84 | 81    | Thu Jun  6 23:31:23 2019 | root | number  |                            |              
    pre    | 85 |       | Fri Jun  7 10:48:28 2019 | root | number  | zypp(packagekitd)          | important=yes
    post   | 86 | 85    | Fri Jun  7 12:16:07 2019 | root | number  |                            | important=yes
    The system doesn't boot from 7 June, so I think I should apply the command undochange 85..86 (i.e. the last change). Or it would be safer to go more back in time?
    O.S. = Linux 3.4.11-2.16-desktop x86_64
    Desktop = KDE 4.8.5 (4.8.5) "release 2"
    Distribution = openSUSE 12.2 (x86_64)

  6. #16
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,968

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Given that 1-click is the probable root cause of your trouble, I'd first try to find out what 1-click was used to install, then choose to go back to 80, and after confirming the system is OK, update 15.1, then add in conventional fashion (yast or zypper) whatever 1-click was used to install.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  7. #17
    Join Date
    Feb 2010
    Location
    Munich (Germany)
    Posts
    137

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Here some outputs.

    snapper diff 80..81:
    Code:
    --- /.snapshots/80/snapshot/etc/cups/subscriptions.conf    2019-06-06 18:34:30.195229363 +0200
    +++ /.snapshots/81/snapshot/etc/cups/subscriptions.conf    2019-06-06 23:26:09.980856084 +0200
    @@ -1,5 +1,5 @@
     # Subscription configuration file for CUPS v2.2.7
    -# Written by cupsd on 2019-06-06 18:34
    +# Written by cupsd on 2019-06-06 23:26
     NextSubscriptionId 56
     <Subscription 55>
     Events job-state-changed job-created job-completed job-stopped job-config-changed job-progress server-restarted server-started server-stopped server-audit
    @@ -7,6 +7,6 @@
     Recipient dbus://
     LeaseDuration 3600
     Interval 0
    -ExpirationTime 1559842439
    +ExpirationTime 1559859938
     NextEventId 1
     </Subscription>
    --- /.snapshots/80/snapshot/etc/cups/subscriptions.conf.O    2019-06-05 22:27:44.807059031 +0200
    +++ /.snapshots/81/snapshot/etc/cups/subscriptions.conf.O    2019-06-06 22:27:49.976360153 +0200
    @@ -1,3 +1,12 @@
     # Subscription configuration file for CUPS v2.2.7
    -# Written by cupsd on 2019-06-05 22:27
    -NextSubscriptionId 55
    +# Written by cupsd on 2019-06-06 22:27
    +NextSubscriptionId 56
    +<Subscription 55>
    +Events job-state-changed job-created job-completed job-stopped job-config-changed job-progress server-restarted server-started server-stopped server-audit
    +Owner mila
    +Recipient dbus://
    +LeaseDuration 3600
    +Interval 0
    +ExpirationTime 1559856438
    +NextEventId 1
    +</Subscription>

    snapper diff 81..82 :

    Code:
    --- /.snapshots/81/snapshot/etc/zypp/repos.d/http-download.opensuse.org-9ebb6e9a.repo    1970-01-01 01:00:00.000000000 +0100
    +++ /.snapshots/82/snapshot/etc/zypp/repos.d/http-download.opensuse.org-9ebb6e9a.repo    2019-06-06 23:31:07.588387109 +0200
    @@ -0,0 +1,7 @@
    +[http-download.opensuse.org-9ebb6e9a]
    +name=openSUSE:Factory
    +enabled=1
    +autorefresh=1
    +baseurl=http://download.opensuse.org/tumbleweed/repo/oss/
    +type=rpm-md
    +keeppackages=0
    So, as I see, there was minor changes applied with the "1-click-installer". Something related to cups (print management?).
    On the other hand, commands like

    snapper diff 79..80
    snapper diff 85..86


    produces tons of rows/changes (I have to press CTRL-C to stop the screen text from scrolling).

    Anyway, I think I will go for restoring the snapshot #80 to stay on the safe side.
    Should I use

    snapper undochange 80..86

    or the sequence

    snapper undochange 85..86
    snapper undochange 84..85
    snapper undochange 83..84
    snapper undochange 82..83
    snapper undochange 81..82
    snapper undochange 80..81


    ???
    The documentation is not clear about that.
    O.S. = Linux 3.4.11-2.16-desktop x86_64
    Desktop = KDE 4.8.5 (4.8.5) "release 2"
    Distribution = openSUSE 12.2 (x86_64)

  8. #18
    Join Date
    Feb 2010
    Location
    Munich (Germany)
    Posts
    137

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    Boom!
    Problem solved!
    After executing the command snapper undochange 85..86 the system boot normally!
    I have my notebook back again.
    Everything works normally as before, all applications runs properly, and the NetworkManager is launched at the boot without problems.

    Two important facts as result:

    1. the option to run Tumbleweed is disappeared from the boot list when I turn on the notebook
    2. I have received (again) the notification of 1148 updates available for my Leap 15 system (see the image below)

    Why the heck I receive a notification of updates that will try (again) to transform my Leap 15 into a Tumbleweed system???
    There is a valid reason for that?
    No Guru can respond me?




    P.S.
    I have deleted the snapshot #85 and @86 by using the command snapper delete 85 86
    O.S. = Linux 3.4.11-2.16-desktop x86_64
    Desktop = KDE 4.8.5 (4.8.5) "release 2"
    Distribution = openSUSE 12.2 (x86_64)

  9. #19
    Join Date
    Feb 2010
    Location
    Munich (Germany)
    Posts
    137

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    P.P.S
    I have no tumbleweed repos listed in my system:
    Code:
    linux-2fqt:/home/mila # zypper lr 
    Repository priorities are without effect. All enabled repositories share the same priority.
    
    #  | Alias                               | Name                                    | Enabled | GPG Check | Refresh
    ---+-------------------------------------+-----------------------------------------+---------+-----------+--------
     1 | http-download.opensuse.org-9ebb6e9a | openSUSE:Factory                        | Yes     | (r ) Yes  | Yes    
     2 | openSUSE-Leap-15.0-1                | openSUSE-Leap-15.0-1                    | Yes     | (r ) Yes  | No     
     3 | repo-debug                          | openSUSE-Leap-15.0-Debug                | No      | ----      | ----   
     4 | repo-debug-non-oss                  | openSUSE-Leap-15.0-Debug-Non-Oss        | No      | ----      | ----   
     5 | repo-debug-update                   | openSUSE-Leap-15.0-Update-Debug         | No      | ----      | ----   
     6 | repo-debug-update-non-oss           | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----   
     7 | repo-non-oss                        | openSUSE-Leap-15.0-Non-Oss              | Yes     | (r ) Yes  | Yes    
     8 | repo-oss                            | openSUSE-Leap-15.0-Oss                  | Yes     | (r ) Yes  | Yes    
     9 | repo-source                         | openSUSE-Leap-15.0-Source               | No      | ----      | ----   
    10 | repo-source-non-oss                 | openSUSE-Leap-15.0-Source-Non-Oss       | No      | ----      | ----   
    11 | repo-update                         | openSUSE-Leap-15.0-Update               | Yes     | (r ) Yes  | Yes    
    12 | repo-update-non-oss                 | openSUSE-Leap-15.0-Update-Non-Oss       | Yes     | (r ) Yes  | Yes
    O.S. = Linux 3.4.11-2.16-desktop x86_64
    Desktop = KDE 4.8.5 (4.8.5) "release 2"
    Distribution = openSUSE 12.2 (x86_64)

  10. #20
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,798

    Default Re: Tumbleweed stuck on boot after upgrading to Linux 5.1.7-1

    You have factory which for all intent and purpose is Tumblweed

    As long as you have that the update will want to upgrade you to TW

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •