Comments page #1 of 3 pages

  • Broken a lot. Even when opening a new tab, new tab shows some error. gmail, slack cannot be seen. chrome://settings/ cannot be seen either.

    karma: -1
  • Unless this LXDE F31 live is broken.

    karma: +1
  • I see some similar issue here. When I try changing the resolution of a laptop display with xrandr, the display gets black and never get back.

    karma: -1 critpath: -1
  • #1707223 is now fixed, thank you.

    karma: +1 #1707223: +1
  • Unfortunately already pushed into stable, however fedpkg co --branches does not work. Filed as #1707223

    karma: -1 clone distgit repository: -1
  • Still fails:

     問題 1: package samba-dc-libs-2:4.10.2-1.fc30.x86_64 requires libkadm5srv_mit.so.11()(64bit), but none of the providers can be installed
      - package samba-dc-libs-2:4.10.2-1.fc30.x86_64 requires libkadm5srv_mit.so.11(kadm5srv_mit_11_MIT)(64bit), but none of the providers can be installed
      - cannot install both libkadm5-1.17-14.fc30.x86_64 and libkadm5-1.17-4.fc30.x86_64
      - cannot install both libkadm5-1.17-4.fc30.x86_64 and libkadm5-1.17-14.fc30.x86_64
      - cannot install the best update candidate for package samba-dc-libs-2:4.10.2-0.fc30.x86_64
      - cannot install the best update candidate for package libkadm5-1.17-4.fc30.x86_64
    

    https://koji.fedoraproject.org/koji/buildinfo?buildID=1258877 , especially https://kojipkgs.fedoraproject.org//packages/samba/4.10.2/1.fc30/data/logs/x86_64/root.log says that samba-4.10.2-1.fc30 is rebuilt with krb5-devel-1.17-4.fc30.x86_64 , not -14.fc30. You have to submit override tag for krb5-1.17-14.fc30 and then rebuild samba.

    karma: -1
  • I will advice to specify soversion explicitly in spec file.

  •  Problem 1: package samba-dc-libs-2:4.10.2-0.fc30.x86_64 requires libkadm5srv_mit.so.11()(64bit), but none of the providers can be installed
      - package samba-dc-libs-2:4.10.2-0.fc30.x86_64 requires libkadm5srv_mit.so.11(kadm5srv_mit_11_MIT)(64bit), but none of the providers can be installed
      - cannot install both libkadm5-1.17-14.fc30.x86_64 and libkadm5-1.17-4.fc30.x86_64
      - cannot install both libkadm5-1.17-4.fc30.x86_64 and libkadm5-1.17-14.fc30.x86_64
      - cannot install the best update candidate for package samba-dc-libs-2:4.10.2-0.fc30.x86_64
      - cannot install the best update candidate for package libkadm5-1.17-4.fc30.x86_64
     Problem 2: problem with installed package samba-dc-libs-2:4.10.2-0.fc30.x86_64
      - package samba-dc-libs-2:4.10.2-0.fc30.x86_64 requires libkadm5srv_mit.so.11()(64bit), but none of the providers can be installed
      - package samba-dc-libs-2:4.10.2-0.fc30.x86_64 requires libkadm5srv_mit.so.11(kadm5srv_mit_11_MIT)(64bit), but none of the providers can be installed
      - cannot install both libkadm5-1.17-14.fc30.x86_64 and libkadm5-1.17-4.fc30.x86_64
      - cannot install both libkadm5-1.17-4.fc30.x86_64 and libkadm5-1.17-14.fc30.x86_64
      - package krb5-devel-1.17-14.fc30.x86_64 requires libkadm5(x86-64) = 1.17-14.fc30, but none of the providers can be installed
      - cannot install the best update candidate for package krb5-devel-1.17-4.fc30.x86_64
    
    karma: -1
  • Umm.. cannot understand what "works" means here... The above "Automated Tests" already complains about missing "perl(GitLab::API::v4::Constants)" dependency. And F-30 is broken as well.

    karma: -1
  • # rpm -Fvh --test python2-configparser-3.7.1-1.fc29.noarch.rpm 
    Verifying...                          ################################# [100%]
    Preparing...                          ################################# [100%]
        file /usr/lib/python2.7/site-packages/backports/__init__.py from install of python2-configparser-3.7.1-1.fc29.noarch conflicts with file from package python2-backports-1.0-15.fc29.x86_64
        file /usr/lib/python2.7/site-packages/backports/__init__.pyc from install of python2-configparser-3.7.1-1.fc29.noarch conflicts with file from package python2-backports-1.0-15.fc29.x86_64
        file /usr/lib/python2.7/site-packages/backports/__init__.pyo from install of python2-configparser-3.7.1-1.fc29.noarch conflicts with file from package python2-backports-1.0-15.fc29.x86_64
    

    F-30 is broken as well.

    karma: -1
  • So bodhi can accept positive karma from those who edited the update?

  • error: Failed dependencies:
        wine-mono = 4.7.3 is needed by wine-4.2-1.fc29.x86_64
    

    rawhide is broken as well.

    karma: -1
  • For now +1 to rescue xfce live

    karma: +1
  • As I wrote in https://bugzilla.redhat.com/show_bug.cgi?id=1634386 , my system was firstly Fedora 25 system. Now my system (HP spectre) boots fine.

    karma: +1 #1631989: +1
  • Looks like now people using Fedora 27 are seeing some surprising result that lots of packages are to be removed due to this upgrade .... https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/L3P42MRVMD24L7UIOQWGCVJ3FAVEPZJ4/

  • dvipdfmx dies with this update:

    $ dvipdfmx foo.dvi 
    foo.dvi -> foo.pdf
    [1
    kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+231/600 --dpi 831 gbm
    mktexpk: Running gsftopk gbm 831
    gsftopk(k) version 1.19.2
    gs died due to signal 11
    
    grep: gbm.log: そのようなファイルやディレクトリはありません
    mktexpk: `gsftopk gbm 831' failed to make gbm.831pk.
    kpathsea: Appending font creation commands to missfont.log.
    
    dvipdfmx:warning: Could not locate a virtual/physical font for TFM "gbm".
    dvipdfmx:warning: >> This font is mapped to a physical font "gbm".
    dvipdfmx:warning: >> Please check if kpathsea library can find this font: gbm
    dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...
    dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...
    
    Output file removed.
    

    Reverting to the previous updates-pushed ones makes dvipdfmx work again.

    karma: -1
  • Ah, works well with "real" machine HP spectre - perhaps vbox is not compatible yet.

    karma: +1 critpath: +1
  • LXDE on vbox does not work at all with this kernel. I cannot drag window after clicking window titile bar, and sees some other issue. I will check if such issue happens even on "real" (i.e. no vbox) machine.

    karma: -1