Bug#944758: Problem solved
Reason was either some amdgpu-pro package or updating libegl to git version.
Bug#944758: xserver-xorg-video-amdgpu version too old
Package: xserver-xorg-video-amdgpu Version: 19.1.0-1 The version is not compatible with xserver-xorg-core 2:1.20.4-1. Does not boot to desktop.
Bug#942487: [Pkg-rust-maintainers] Bug#942487: rust-web-sys: Provides header is more than 256K long and it breaks reprepro...
On Thu, 17 Oct 2019 10:06:00 + Ximin Luo wrote: > Control: tags -1 + wontfix > Debian should remove this kind of packages immediately. No way to make a Debian Sid installer with Simple-CDD now. The Rust language is for people who make null pointer and buffer overflow bugs and those people should not program anything. This bug proves my point: rust programmers can break even the Debian repository. A nice bomb this package is.
Bug#939781: Please include Navi10 firmware files
Package: firmware-amd-graphics Version: 20190717-2 Can you include firmware files for the AMD Navi10 card in to the firmware-amd-graphics package? https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/ The Linux kernel 5.3 has support for the Navi10 card. The Oibaf ppa Mesa master bionic version works with Debian Sid so Mesa support is available too.
Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.61.1-2
There are same errors when trying to install wine32 4.0-2 from the Debian repository. On Tue, 23 Jul 2019 17:27:37 -0700 James Lu wrote: > Hi, > > It looks like you're trying to install the Wine packages from WineHQ, > which are not the same ones provided by Debian. It doesn't look like > the WineHQ repository has been updated for Bullseye yet, so it's > likely you'll have to wait for them to add those missing builds. > > Best, > James > > On 2019-07-23 5:02 p.m., fin4478 fin4478 wrote: > > Package: wine32 > > Version: 4.0-2 > > > > To prevent warnings in the file .xsession-errors with the Xfce > > 4.13.3 desktop libglib2.0-0 must be updated to the version 2.60. > > This removes wine and many of its libraries. Reinstalling wine > > shows the following problems: > > xfce@optipc:~$ sudo aptitude install winehq-staging > > The following NEW packages will be installed: > > acl{a} glib-networking:i386{a} gstreamer1.0-plugins-base:i386{a} > > libasound2-plugins:i386{a} libatk-bridge2.0-0:i386{a} > > libatk1.0-0:i386{a} libatspi2.0-0:i386{a} libavcodec58:i386{a} > > libbz2-1.0:i386{a} libcairo-gobject2:i386{a} libcolord2:i386{a} > > libcroco3:i386{a} libgdbm-compat4:i386{a} libgdbm6:i386{a} > > libgdk-pixbuf2.0-0:i386{a} libgstreamer-plugins-base1.0-0:i386{a} > > libgstreamer1.0-0:i386{a} libgtk-3-0:i386{a} libharfbuzz0b:i386{a} > > libieee1284-3{a} libieee1284-3:i386{a} libjson-glib-1.0-0:i386{a} > > libmariadb3:i386{a} libpango-1.0-0:i386{a} > > libpangocairo-1.0-0:i386{a} libpangoft2-1.0-0:i386{a} > > libpci3:i386{a} libperl5.28:i386{a} librest-0.7-0:i386{a} > > librsvg2-2:i386{a} librsvg2-common:i386{a} libsane{a} > > libsane:i386{a} libsane-common{a} libsensors-config{ab} > > libsensors5{a} libsensors5:i386{a} libsnmp-base{a} libsnmp30{a} > > libsnmp30:i386{a} libsoup-gnome2.4-1:i386{a} libsoup2.4-1:i386{a} > > sane-utils{a} update-inetd{a} wine-staging{a} wine-staging-amd64{a} > > wine-staging-i386:i386{a} winehq-staging The following packages > > will be REMOVED: bind9-host{u} cgroupfs-mount{u} dkms{u} > > fonts-wine{u} geoip-database{u} gtk2-engines-xfce{u} > > i965-va-driver:i386{u} intel-media-va-driver:i386{u} > > libasyncns0:i386{u} libavahi-common-data:i386{u} libavahi-core7{u} > > libavcodec57:i386{u} libavutil55:i386{u} libbind9-161{u} > > libcom-err2:i386{u} libdaemon0{u} libdatrie1:i386{u} libdns1104{u} > > libexif12:i386{u} libexo-1-0{u} libfaudio0{u} libflac8:i386{u} > > libfstrm0{u} libgcrypt20:i386{u} libgd3:i386{u} libgeoip1{u} > > libgeos-3.7.1{u} libgmp10:i386{u} libgomp1:i386{u} libgpm2:i386{u} > > libgsoap-2.8.75{u} libgtksourceview-3.0-1{u} > > libgtksourceview-3.0-common{u} libhogweed4:i386{u} libice6:i386{u} > > libicu63:i386{u} libigdgmm9:i386{u} libintl-perl{u} > > libintl-xs-perl{u} libisc1100{u} libisccc161{u} libisccfg163{u} > > libjbig0:i386{u} libjim0.77{u} libk5crypto3:i386{u} > > libkeybinder-3.0-0{u} libkeyutils1:i386{u} libkrb5support0:i386{u} > > libllvm7{u} libltdl7:i386{u} liblwres161{u} liblz4-1:i386{u} > > libmbim-glib4{u} libmbim-proxy{u} libmodule-find-perl{u} > > libmodule-scandeps-perl{u} libnettle6:i386{u} libnotify-bin{u} > > libnuma1:i386{u} libp11-kit0:i386{u} libpixman-1-0:i386{u} > > libproc-processtable-perl{u} libprotobuf-c1{u} libqmi-glib5{u} > > libqmi-proxy{u} libreadline7{u} libsasl2-2:i386{u} > > libsasl2-modules:i386{u} libsasl2-modules-db:i386{u} libsm6:i386{u} > > libsndfile1:i386{u} libsndio7.0:i386{u} libsort-naturally-perl{u} > > libsoxr0:i386{u} libstb0{u} libstb0:i386{u} libswresample2:i386{u} > > libsystemd0:i386{u} libtasn1-6:i386{u} libterm-readkey-perl{u}
Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.61.1-2
I am using the version 2.61.1-2 from the experimental repository and it does have the i386 version. I did notice that the i386 version is missing with the version 2.60. I was unsure when I wrote this bug report and used the 2.60 number.
Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.60
Package: wine32 Version: 4.0-2 To prevent warnings in the file .xsession-errors with the Xfce 4.13.3 desktop libglib2.0-0 must be updated to the version 2.60. This removes wine and many of its libraries. Reinstalling wine shows the following problems: xfce@optipc:~$ sudo aptitude install winehq-staging The following NEW packages will be installed: acl{a} glib-networking:i386{a} gstreamer1.0-plugins-base:i386{a} libasound2-plugins:i386{a} libatk-bridge2.0-0:i386{a} libatk1.0-0:i386{a} libatspi2.0-0:i386{a} libavcodec58:i386{a} libbz2-1.0:i386{a} libcairo-gobject2:i386{a} libcolord2:i386{a} libcroco3:i386{a} libgdbm-compat4:i386{a} libgdbm6:i386{a} libgdk-pixbuf2.0-0:i386{a} libgstreamer-plugins-base1.0-0:i386{a} libgstreamer1.0-0:i386{a} libgtk-3-0:i386{a} libharfbuzz0b:i386{a} libieee1284-3{a} libieee1284-3:i386{a} libjson-glib-1.0-0:i386{a} libmariadb3:i386{a} libpango-1.0-0:i386{a} libpangocairo-1.0-0:i386{a} libpangoft2-1.0-0:i386{a} libpci3:i386{a} libperl5.28:i386{a} librest-0.7-0:i386{a} librsvg2-2:i386{a} librsvg2-common:i386{a} libsane{a} libsane:i386{a} libsane-common{a} libsensors-config{ab} libsensors5{a} libsensors5:i386{a} libsnmp-base{a} libsnmp30{a} libsnmp30:i386{a} libsoup-gnome2.4-1:i386{a} libsoup2.4-1:i386{a} sane-utils{a} update-inetd{a} wine-staging{a} wine-staging-amd64{a} wine-staging-i386:i386{a} winehq-staging The following packages will be REMOVED: bind9-host{u} cgroupfs-mount{u} dkms{u} fonts-wine{u} geoip-database{u} gtk2-engines-xfce{u} i965-va-driver:i386{u} intel-media-va-driver:i386{u} libasyncns0:i386{u} libavahi-common-data:i386{u} libavahi-core7{u} libavcodec57:i386{u} libavutil55:i386{u} libbind9-161{u} libcom-err2:i386{u} libdaemon0{u} libdatrie1:i386{u} libdns1104{u} libexif12:i386{u} libexo-1-0{u} libfaudio0{u} libflac8:i386{u} libfstrm0{u} libgcrypt20:i386{u} libgd3:i386{u} libgeoip1{u} libgeos-3.7.1{u} libgmp10:i386{u} libgomp1:i386{u} libgpm2:i386{u} libgsoap-2.8.75{u} libgtksourceview-3.0-1{u} libgtksourceview-3.0-common{u} libhogweed4:i386{u} libice6:i386{u} libicu63:i386{u} libigdgmm9:i386{u} libintl-perl{u} libintl-xs-perl{u} libisc1100{u} libisccc161{u} libisccfg163{u} libjbig0:i386{u} libjim0.77{u} libk5crypto3:i386{u} libkeybinder-3.0-0{u} libkeyutils1:i386{u} libkrb5support0:i386{u} libllvm7{u} libltdl7:i386{u} liblwres161{u} liblz4-1:i386{u} libmbim-glib4{u} libmbim-proxy{u} libmodule-find-perl{u} libmodule-scandeps-perl{u} libnettle6:i386{u} libnotify-bin{u} libnuma1:i386{u} libp11-kit0:i386{u} libpixman-1-0:i386{u} libproc-processtable-perl{u} libprotobuf-c1{u} libqmi-glib5{u} libqmi-proxy{u} libreadline7{u} libsasl2-2:i386{u} libsasl2-modules:i386{u} libsasl2-modules-db:i386{u} libsm6:i386{u} libsndfile1:i386{u} libsndio7.0:i386{u} libsort-naturally-perl{u} libsoxr0:i386{u} libstb0{u} libstb0:i386{u} libswresample2:i386{u} libsystemd0:i386{u} libtasn1-6:i386{u} libterm-readkey-perl{u} libv4lconvert0:i386{u} libva-drm1:i386{u} libva-x11-1:i386{u} libva1:i386{u} libvdpau-va-gl1:i386{u} libvdpau1:i386{u} libvncserver1{u} libvpx4:i386{u} libwebpmux2:i386{u} libwnck-common{u} libwnck22{u} libx264-148:i386{u} libx265-95:i386{u} libxcb-render0:i386{u} libxcb-shm0:i386{u} libxcb-xfixes0:i386{u} libxfce4ui-utils{u} libxpm4:i386{u} libxtst6:i386{u} libzstd1:i386{u} mesa-va-drivers:i386{u} mesa-vdpau-drivers:i386{u} needrestart{u} runc{u} tini{u} usb-modeswitch{u} usb-modeswitch-data{u} va-driver-all:i386{u} vdpau-driver-all:i386{u} xfce4-appfinder{u} 0 packages upgraded, 48 newly installed, 110 to remove and 15 not upgraded. Need to get 173 MB of archives. After unpacking 1,145 MB will be used. The following packages have unmet dependencies: libx265-165:i386 : Depends: libnuma1:i386 (>= 2.0.11) but it is not going to be installed libkrb5-3:i386 : Depends: libcom-err2:i386 (>= 1.43.9) but it is not going to be installed Depends: libk5crypto3:i386 (>= 1.15~beta1) but it is not going to be installed Depends: libkeyutils1:i386 (>= 1.5.9) but it is not going to be installed Depends: libkrb5support0:i386 (= 1.17-5) but it is not going to be installed libgssapi-krb5-2:i386 : Depends: libcom-err2:i386 (>= 1.43.9) but it is not going to be installed Depends: libk5crypto3:i386 (>= 1.16) but it is not going to be installed Depends: libkeyutils1:i386 (>= 1.4) but it is not going to be installed Depends: libkrb5support0:i386 (>= 1.15~beta1) but it is not going to be installed libgphoto2-port12:i386 : Depends: libltdl7:i386 (>= 2.4.6) but it is not going to be installed libdbus-1-3:i386 : Depends: libsystemd0:i386 but it is not going to be installed libldap-2.4-2:i386 : Depends: libsasl2-2:i386 (>= 2.1.27+dfsg) but it is not going to be installed libgphoto2-6:i386 : Depends:
Bug#925411: kernel-package: Not suitable for release
On Sat, 6 Apr 2019 07:28:18 + fin4478 fin4478 wrote: > On Sun, 24 Mar 2019 23:23:58 + Ben Hutchings > wrote: > > > > > The simple alternative is already included in the kernel tree > > itself: > > > > make bindeb-pkg > > > > So no more the make-kpkg command available in future Debian? > > The best kernel for AMD graphics users is this: > https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-5.2-wip > > What is the replacement command for this? > fakeroot make-kpkg -j 12 --initrd kernel_image kernel_headers > > make -j 12 bindeb-pkg You need to distribute the linux-libc-dev package with the linux-image package probably.
Bug#925411: kernel-package: Not suitable for release
On Sun, 24 Mar 2019 23:23:58 + Ben Hutchings wrote: > > The simple alternative is already included in the kernel tree itself: > > make bindeb-pkg > So no more the make-kpkg command available in future Debian? The best kernel for AMD graphics users is this: https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-5.2-wip What is the replacement command for this? fakeroot make-kpkg -j 12 --initrd kernel_image kernel_headers
Bug#925132: The sid installer does not use the user profile
Package: simple-cdd Version: 0.6.6 The command: build-simple-cdd --dist sid --local-packages /home/xfce/Downloads/cd/debs/ --profiles desktop produces a Debian Sid installer and ignores --profiles desktop. The installer uses the linux-image-4.19.0-4 kernel and does not work for a buster installer.
Bug#924386: No kernel modules found when using the Debian Buster installer
Package: debian-cd Version: 3.1.23 Regression: When installing a custom Debian Buster CD created with simple-cdd, the installer uses the 4.19.0-3-amd64 kernel, no kernel modules can be found and the installation fails. When installing a custom Debian Sid CD created with simple-cdd, the installer does not use the simple-cdd profile and the resulted installer is the same as the official Debian installer. I use the following command: build-simple-cdd --dist buster --local-packages /home/xfce/Downloads/cd/debs/ --profiles desktop
Bug#915939: Updating libasound2-data overwrites alsa.conf
Package: libasound2-data Version: 1.1.7-2 Many people use Alsa only with Debian and with Hifi speakers connected to analog out of the motherboard. However the audio device 0 is hdmi audio and you need to change it in /usr/share/alsa/alsa.conf: defaults.ctl.card 2 defaults.pcm.card 2 Many other Debian packages asks confirmation from the user when updating configuration files. The libasound2-data package should do the same.
Bug#905263: Buggy dependencies in i386 version
Package: libpcre3 Version: 2:8.39-11 Buggy dependencies in i386 version. Prevents to install wine-staging to Debian sid. With aptitude and selecting no to default solution you can fix this. xfce@unassigned:~$ sudo sudo aptitude install libpcre3:i386 The following NEW packages will be installed: libpcre3:i386{b} 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 339 kB of archives. After unpacking 710 kB will be used. The following packages have unmet dependencies: libpcre3 : Breaks: libpcre3:i386 (!= 2:8.39-10) but 2:8.39-11 is to be installed libpcre3:i386 : Breaks: libpcre3 (!= 2:8.39-11) but 2:8.39-10 is installed The following actions will resolve these dependencies: Keep the following packages at their current version: 1) libpcre3:i386 [Not Installed] Accept this solution? [Y/n/q/?] n
Bug#904795: No kernel in the Debian buster installer
Package: debian-installer Version: 20180610 When I make a installer cd with simplecdd with the --dist buster flag, there is no kernel available in the installer. With --dist sid there is kernel available, but steam and wine-staging fails to install due to dependency problems, so I want try with --dist buster. Here is the picture of the installer: http://s000.tinyupload.com/?file_id=02467361958696419153
Bug#902881: [debian-installer] Cannot partition disk in Testing installer
Same thing happens when using my own Debian buster or sid distribution installer made with simple-cdd. Please fix the kernel that the installer uses.
Bug#899033: kdenlive does not install to sid because of dependencies
Kdenlive installs after updating sid. So close this bug.
Bug#899033: kdenlive does not install to sid because of dependencies
Package: kdenlive Version: 18.04.1-1 The kdenlive package depends on the kded5 package. When trying to install the kded5 package there is dependency errors. sudo aptitude install kded5 The following NEW packages will be installed: kded5 libfam0{a} libkf5config-bin{a} libkf5configcore5{ab} libkf5coreaddons5{ab} libkf5crash5{ab} libkf5dbusaddons5{ab} libkf5service-bin{ab} libkf5service-data{a} libkf5service5{ab} 0 packages upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/783 kB of archives. After unpacking 3,046 kB will be used. The following packages have unmet dependencies: libkf5dbusaddons5 : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed libkf5service-bin : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed libkf5configcore5 : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed libkf5coreaddons5 : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed libkf5service5 : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed libkf5crash5 : Breaks: kded5 (< 5.46) but 5.45.0-1 is to be installed System: Host: ryzenpc Kernel: 4.16.0-rc7+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid
Bug#879642: Info received (simple-cdd is unusable)
Simple-cdd produces an image with options in: /usr/share/debian-cd/tools/apt-selection: -o Acquire::AllowInsecureRepositories=true \ -o Acquire::AllowDowngradeToInsecureRepositories=true \ and with this pc: System:Host: fujitsu Kernel: 4.15.0-2-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: laptop System: FUJITSU SIEMENS product: ESPRIMO Mobile V5505 Some errors in the terminal: xfce@fujitsu:~/Downloads/cd$ build-simple-cdd --local-packages /home/xfce/Downloads/cd/debs/ --profiles desktop 2018-04-19 10:12:07 ERROR distcheck: exited with code 64 2018-04-19 10:12:07 ERROR Last 2 lines of standard error: 2018-04-19 10:12:07 ERROR distcheck:: Fatal error in module common/input.ml: 2018-04-19 10:12:07 ERROR distcheck:: Input file /home/xfce/Downloads/cd/tmp/cd-build/buster/CD1/dists/buster/contrib/binary-amd64/Packages.gz does not exists. /home/xfce/Downloads/cd/images/debian-testing-amd64-CD-1.iso
Bug#879642: simple-cdd is unusable
Simple-cdd is unusable at least with the arm64 platform. I updated my Debian testing to latest packages and the process stops at the very beginning to reprepo errors: xfce@amlogic:~/Downloads/cd$ build-simple-cdd --local-packages /home/xfce/Downloads/cd/debs/ --profiles desktop 2018-04-19 06:28:38 ERROR reprepro: updating package lists exited with code 255 2018-04-19 06:28:38 ERROR Last 5 lines of standard error: 2018-04-19 06:28:38 ERROR reprepro: updating package lists: aptmethod got 'http://ftp.be.debian.org/debian/dists/buster-updates/InRelease' 2018-04-19 06:28:38 ERROR reprepro: updating package lists: aptmethod got 'http://ftp.be.debian.org/debian/dists/buster/InRelease' 2018-04-19 06:28:38 ERROR reprepro: updating package lists: aptmethod got 'http://ftp.be.debian.org/debian/dists/buster/InRelease' 2018-04-19 06:28:38 ERROR reprepro: updating package lists: aptmethod got 'http://ftp.be.debian.org/debian/dists/buster/InRelease' 2018-04-19 06:28:38 ERROR reprepro: updating package lists: There have been errors! 2018-04-19 06:28:38 ERROR reprepro failed with exit code: 255
Bug#879642: simple-cdd: build-simple-cdd fails with unsigned local repository
How to avoid these errors with Debian testing/sid when using -o Acquire::AllowInsecureRepositories=true : xfce@amlogic:~/Downloads/cd$ build-simple-cdd --dist sid --local-packages /home/xfce/Downloads/cd/debs/ --profiles desktop 2018-04-19 01:44:43 ERROR build/debian-cd exited with code 2 2018-04-19 01:44:43 ERROR Last 5 lines of standard error: 2018-04-19 01:44:43 ERROR build/debian-cd: ERROR: The certificate of 'd-i.debian.org' is not trusted. 2018-04-19 01:44:43 ERROR build/debian-cd: ERROR: The certificate of 'd-i.debian.org' hasn't got a known issuer. 2018-04-19 01:44:43 ERROR build/debian-cd: ERROR: The certificate of 'd-i.debian.org' was signed using an insecure algorithm. 2018-04-19 01:44:43 ERROR build/debian-cd: Failed to start disc 1, error 1280 2018-04-19 01:44:43 ERROR build/debian-cd: make: *** [image-trees] Error 5 2018-04-19 01:44:43 ERROR build/debian-cd exited with code 2, full log can be found in /home/xfce/Downloads/cd/tmp/log/build-debian-cd
Bug#895975: Permission denied when using usb memory
Package: simple-cdd Version: 0.6.5 Severity: normal I am running Debian Sid from a 32GB class 10 microsd card and using a second 64GB card for the simple-cdd. I am waiting to get my new ssd from China for my new PC build and want to build my own distribution for it meanwhile. Running simple-cdd fails when started from a usb drive: xfce@unassigned:/media/xfce/7E31-3D8F/cd$ build-simple-cdd --dist sid --local-packages /media/xfce/7E31-3D8F/cd/debs/ --profiles desktop Traceback (most recent call last): File "/usr/bin/build-simple-cdd", line 658, in scdd.build_mirror() File "/usr/bin/build-simple-cdd", line 270, in build_mirror self.run_tool("mirror", tool) File "/usr/bin/build-simple-cdd", line 367, in run_tool tool.run() File "/usr/lib/python3/dist-packages/simple_cdd/tools/mirror_reprepro.py", line 276, in run self.run_script() File "/usr/lib/python3/dist-packages/simple_cdd/tools/base.py", line 124, in run_script logfd=fd) File "/usr/lib/python3/dist-packages/simple_cdd/utils.py", line 84, in run_command proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE, env=env) File "/usr/lib/python3.6/subprocess.py", line 709, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/media/xfce/7E31-3D8F/cd/tmp/log/mirror-reprepro'
Bug#891656: Adblockers fail to start
Package: chromium Version: 65.0.3325.74-1 and others Chromium from the Debian sid and experimental repository causes adblockers to fail to start. Install one of these: https://chrome.google.com/webstore/search/adblock I have signal 11 SEGV_MAPERR when logging is enabled: xfce@ryzen5pc:~/Downloads/git$ chromium --enable-logging --v=1 [7464:7494:0227/134956.921431:ERROR:in_progress_cache_impl.cc(93)] Could not read download entries from file because there was a read failure. [7464:7505:0227/134957.071911:ERROR:connection_factory_impl.cc(379)] Failed to connect to MCS endpoint with error -21 [7518:7518:0227/134957.092703:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process. Received signal 11 SEGV_MAPERR ff00 #0 0x560ef24e837e #1 0x560ef0d46f4f #2 0x560ef24e8737 #3 0x7f8884312f50 #4 0x7f8878909010 #5 0x7f88792369be std::__cxx11::basic_string<>::compare() #6 0x560ef300eb50 #7 0x560ef216dc1d #8 0x560ef2178a95 #9 0x560ef3fd54ee #10 0x560ef3e348d4 #11 0x560ef3e3f413 #12 0x560ef4fb737f #13 0x560ef4fb7b33 #14 0x560ef4e94a8d #15 0x560ef1903ad7 #16 0x560ef198ce7e #17 0x560ef198db76 #18 0x3a0be188431d r8: 7fff17cd70f8 r9: 7fff17cd7120 r10: 696c6769626b6b67 r11: 6e6f63692f6d6f64 r12: 7fff17cd70d8 r13: 560ef58bc746 r14: 7fff17cd7298 r15: 7fff17cd7148 di: ff00 si: 560ef58bc746 bp: 0001 bx: 560ef7785ee8 dx: 0001 ax: 0001 cx: 0746 sp: 7fff17cd6f88 ip: 7f8878909010 efl: 00010246 cgf: 002b0033 erf: 0004 trp: 000e msk: cr2: ff00 [end of stack trace] Calling _exit(1). Core file will not be generated. I made a bug report to bugs.chromium.org and they wrote: " We have no control over how Debian builds and distributes their flavor of Chromium. Please report this bug to Debian instead. "
Bug#891284: xfce4-session: verbose logging is always enabled
Package: xfce4-session Version: 4.12.1-6 This bug is marked fixed in upstream (see here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886855) and it is not fixed in 4.12.1-6. Version 4.13 package is needed
Bug#886855: confirming in sid
Same thing in sid. 4.13 version is available in git but not even packages in experimental. I did try to run git master but got: .xsession-errors: (xfce4-session:1832): Gtk-ERROR **: 11:53:25.090: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported dmesg: Feb 11 10:18:23 ryzen5pc kernel: [4.070662] traps: xfce4-session[1832] trap int3 ip:7f319df1b761 sp:7fff36a01dc0 error:0 in libglib-2.0.so.0.5501.0[7f319deca000+113000] Setting export GTK_PATH=/etc/gtk-3.0 before building did not help.
Bug#889483: libegl1 disables amdgpu drm with Buster mesa
Reopen this bug, the log file shows that this bug is for Debian Buster Mesa.
Bug#889483: libegl1 package disables amdgpu direct rendering
Package: libegl1 Version: 1.0.0-2 The presence of this package disables 2d and 3d hardware acceleration of the Mesa amdgpu driver: [ 6.245] (EE) AMDGPU(0): eglGetDisplay() failed [ 6.245] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. [ 6.452] (II) AMDGPU(0): Front buffer pitch: 7680 bytes [ 6.452] (==) AMDGPU(0): DRI3 disabled [ 6.452] (==) AMDGPU(0): Backing store enabled [ 6.452] (WW) AMDGPU(0): Direct rendering disabled [ 6.452] (II) AMDGPU(0): 2D and 3D acceleration disabled [ 6.452] (==) AMDGPU(0): DPMS enabled [ 6.452] (==) AMDGPU(0): Silken mouse enabled [ 6.453] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 6.489] (--) RandR disabled [ 6.491] (II) SELinux: Disabled on system [ 6.491] (II) AIGLX: Screen 0 is not DRI2 capable [ 6.491] (EE) AIGLX: reverting to software rendering [ 6.499] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [ 6.500] (II) IGLX: Loaded and initialized swrast [ 6.500] (II) GLX: Initialized DRISWRAST GL provider for screen 0 Many Debian buster mesa packages can not install with Oibaf ppa Mesa packages any more, because depends versions use = instead of >=. This happened about 26.1.2018. xfce@ryzen5pc:~$ inxi -bM System:Host: ryzen5pc Kernel: 4.15.0-rc8+ x86_64 bits: 64 Desktop: Xfce 4.12.4 Distro: Debian GNU/Linux buster/sid Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-K v: Rev X.0x serial: N/A UEFI [Legacy]: American Megatrends v: 3401 date: 12/04/2017 CPU: 6 core AMD Ryzen 5 1600 Six-Core (-MT-MCP-) speed/max: 2727/3375 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Polaris11] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,ati,radeon,amdgpu (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: llvmpipe (LLVM 5.0, 128 bits) version: 3.3 Mesa 17.3.3 Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 Drives:HDD Total Size: 256.1GB (66.9% used) Info: Processes: 242 Uptime: 7 min Memory: 737.0/7976.9MB
Bug#882838: r8168-dkms fails to compile
Package: r8168-dkms Version: 8.045.08-1 /var/lib/dkms/r8168/8.045.08/build/r8168_n.c:22967:9: error: implicit declaration of function ‘setup_timer’; did you mean ‘sk_stop_timer’? [-Werror=implicit-function-declaration] setup_timer(timer, rtl8168_esd_timer, (unsigned long)dev); ^~~ sk_stop_timer cc1: some warnings being treated as errors sudo dpkg -i linux-headers-4.15.0-rc1_4.15.0-rc1-10.00.Custom_amd64.deb timer.h api has changed in the kernel 4.15-rc1. Modify the r8168_n.c file to use timer_setup function.
Bug#867816: Apt arm64 problem with chroot to arm64
Package: apt Version: 1.5~beta Apt-get fails with this version, but not with 1.4.6. I do Debian testing Xfce SD card images for the Amlogic S912 TV box. There is /usr/bin/qemu-aarch64-static in the destination file system. Armbian distribution build script uses the following command in lib/deboostrap-ng.sh: eval 'LC_ALL=C LANG=C chroot $CACHEDIR/$SDCARD /bin/bash -c "DEBIAN_FRONTEND=noninteractive apt-get -y -q -m \ $apt_extra $apt_extra_progress --no-install-recommends install $PACKAGE_LIST"' After installing successfully several packages, in the logs there is: Selecting previously unselected package gnome-icon-theme. Preparing to unpack .../070-gnome-icon-theme_3.12.0-2_all.deb ... Unpacking gnome-icon-theme (3.12.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-sQZDkO/070-gnome-icon-theme_3.12.0-2_all.deb (--unpack): corrupted filesystem tarfile - corrupted package archive And apt-get fails to install any additional packages. I debootstrapped Debian base system using stretch where is apt 1.4.6. Then chroot works ok with testing packages.
Bug#867779: Re:Re: Bug#867779
The problem is in Apt package. I debootstrapped Debian base system with stretch where is apt 1.4.6. Then chroot works ok with testing packages.
Bug#867779: Re: Bug#867779
Package apt did have a new version today, problems with long package lists and dependencies in chroot environment? Armbian uses Debian Jessie. I monitored the building process, it uses very little RAM while running, perl scripts take 100% cpu time often. Debian system partition has 16.5GB free, my home partition has 50GB free, the build temp disk image file is 3GB.
Bug#867779: gnome-icon-theme_3.12.0-2_all.deb - corrupted package archive with chroot to arm64
Package: gnome-icon-theme Version: 3.12.0-2 Before today there was no problems but today with unchanged build system: I do Debian testing Xfce SD card images for the Amlogic S912 TV box. There is /usr/bin/qemu-aarch64-static in the destination file system. Armbian distribution build script uses the following command in lib/deboostrap-ng.sh: eval 'LC_ALL=C LANG=C chroot $CACHEDIR/$SDCARD /bin/bash -c "DEBIAN_FRONTEND=noninteractive apt-get -y -q -m \ $apt_extra $apt_extra_progress --no-install-recommends install $PACKAGE_LIST"' After installing successfully several packages, in the logs there is: Selecting previously unselected package gnome-icon-theme. Preparing to unpack .../070-gnome-icon-theme_3.12.0-2_all.deb ... Unpacking gnome-icon-theme (3.12.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-sQZDkO/070-gnome-icon-theme_3.12.0-2_all.deb (--unpack): corrupted filesystem tarfile - corrupted package archive And apt-get fails to install any additional packages. I tried several repositories, no help. The package installs fine when reinstalling it with Synaptic in Amlogic S912 TV box. Image build system is Debian testing Xfce amd64 that I have not updated recently.
Bug#861666: UTF-8 does not help
When the automount did not work, I did have set: CONFIG_FAT_DEFAULT_IOCHARSET="ascii" FAT_DEFAULT_UTF8=y
Bug#861666: CONFIG_FAT_DEFAULT_IOCHARSET should be iso8859-1 not ascii
Package: linux-image Version: 4.9 Stock Debian testing Xfce does not auto mount usb memory sticks when CONFIG_FAT_DEFAULT_IOCHARSET is ascii. Creating a custom kernel where it is iso8859-1, Xfce Settings/Removable Devices and Media check boxes works as they should.
Bug#765109: Amd Kaveri: no amd compatible card found
I tried Stretch with kernel 4.2.0 and fglrx-driver 1:15.9-2. After installation booting failed 2 times: missing xorg.conf (aticonfig did not work) and amdpcsdb.default in /etc/ati folder. I copied the missing files from xorg.conf.backups and from Catalyst sources. The driver could install driver at /dev/card0, but still claimed that no compatible card. It looks like the package is not tested with integrated graphics. Mine is A8-7600. Using Catalyst 15.9 from Amd site with ubuntu patches and kernel 4.1.6 works fine.
Bug#795192: Mousepad hangs X when browsing 2 large files
I have similar symptoms with debian stretch and latest testing updates installed. My X starts to freeze, i can close windows but not do anything else. Opening a menu stays on the screen and if I type sudo reboot to the xfceterminal, nothing happens. I need to reboot to solve the situation, ctrl+alt+f1 or ssh does not work. So far gEdit works better. It is funny that text editor hangs my machine but Tomb Raider 2013 windows game works fine.
Bug#799244: Algortihm does not work like in: libkmod-module: fix return code in error path
Plaa plaa, read kernel documentation: CONFIG_AUTOFS4_FS: The automounter is a tool to automatically mount remote file systems on demand. This implementation is partially kernel-based to reduce overhead in the already-mounted case; this is unlike the BSD automounter (amd), which is a pure user space daemon. To use the automounter you need the user-space tools from <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also want to answer Y to "NFS file system support", below. To compile this support as a module, choose M here: the module will be called autofs4. You will need to add "alias autofs autofs4" to your modules configuration file. If you are not a part of a fairly large, distributed network or don't have a laptop which needs to dynamically reconfigure to the local network, you probably do not need an automounter, and can say N here. Millions of home computers are not in a large distributed network, so systemd politics is stupid. Every unneeded module and message slows your computer. On Fri, 18 Sep 2015 11:05:51 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 18.09.2015 um 02:53 schrieb Michael Biebl: > > Am 18.09.2015 um 02:01 schrieb fin4478 fin4478: > >> "This is already part of > >> v226" > >> > >> Im trying to get rid of boot messages: Using lastest kmod > >> https://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/?id=114ec87c85c35a2bd3682f9f891e494127be6fb5 > >> > >> fixes this: > >> systemd[1]: Failed to insert module 'kdbus' > >> > >> But using systemd 266 throws: > >> systemd[1]: Failed to insert module 'autofs4' > >> > >> I have made 2 custom kernel for 2 Debian Stretch PC. Kernel 4.1.3 and 4.3 > >> and I disabled autofs in kernel configuration, same happens in both > >> systems. Setting LogLevel=crit in /etc/systemd/system.conf has no effect. > >> > >> >From the systemd code you can see that blacklisting autofs4 might help, > >> >but there is no sense to blacklist modules that do not exist in the > >> >kernel. > > > > This is deliberate, autofs4 has the "warn_if_unavailable" flag set, > > kdbus hasn't. > > Nothing to fix here, especially downstream. > > As for further explanation: systemd provides a unit type called > automount [1] which requires autofs support from the kernel. Without > that support, that functionality is broken. systemd even ships automount > units by default. > The warning is thus appropriate, since the user might accidentally have > disabled autofs in the kernel. > > Michael > > > > [1] http://www.freedesktop.org/software/systemd/man/systemd.automount.html > [2] $ systemctl list-units --type=automount > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? >
Bug#799244: Do from git:Revert "kmod-setup: don't print warning on -ENOSYS" (aka systemd[1]: Failed to insert module 'autofs4')
Package: systemd Version: 226-2 Please do this: https://github.com/systemd/systemd/commit/e04658277d531763a5cbbb6e212041a35e0d9ff4 A lot of home computers (and embedded devices) do not need nfs and autofs, so it is a good idea to disable unneeded features in custom kernels. All visible messages slows boot process.
Bug#799244: Algortihm does not work like in: libkmod-module: fix return code in error path
"This is already part of v226" Im trying to get rid of boot messages: Using lastest kmod https://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/?id=114ec87c85c35a2bd3682f9f891e494127be6fb5 fixes this: systemd[1]: Failed to insert module 'kdbus' But using systemd 266 throws: systemd[1]: Failed to insert module 'autofs4' I have made 2 custom kernel for 2 Debian Stretch PC. Kernel 4.1.3 and 4.3 and I disabled autofs in kernel configuration, same happens in both systems. Setting LogLevel=crit in /etc/systemd/system.conf has no effect. From the systemd code you can see that blacklisting autofs4 might help, but there is no sense to blacklist modules that do not exist in the kernel.
Bug#796471: kmod should check for breakage on new kernels
You need to patch Catalyst when using new kernels. Consult /var/lib/dkms/fglrx/15.7/build/make.log, there you can see compilation errors. New Catalyst 5.19 work fine with kernel 4.1.3 after patching. See text and comments of my video: https://www.youtube.com/watch?v=O-tBdO7KUlo On Sat, 22 Aug 2015 08:22:52 +0200 m...@linux.it (Marco d'Itri) wrote: > On Aug 22, Richard Jasminwrote: > > > when new kernels come out sometimes there is kmod breakage. There is no > > known > > reason for this as headers are installed during the updating process. > This is not related in any way to kmod. > Please ask for help on your favourite end users support channel. > > -- > ciao, > Marco
Bug#787691: RFP: bluetooth-transfer -- simple bluetooth file transfer (opp) application
Package: wnpp Severity: wishlist URL: https://www.youtube.com/watch?v=O-juJokINp4 License: GPL Programming Lang: Python -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Edit blueman-sendto to kill obexd
To terminate obexd after file transfer to make obex-data-server receive again, add to the blueman-master/apps/blueman-sendto the following: from subprocess import check_output class SendTo: def do_send(self): def on_result(sender, res): ret = check_output([pidof,obexd]) os.system(kill + ret) Gtk.main_quit() -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: About blueman-obexd from github
Today we find out that blueman-obexd branch from github does not need obex-data-server anymore. I can confirm that it works with my edited bluez 2.28. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: pulseaudio and obexd also affects obex opp
Here is what i have done to get blueman 1.99v2, obex-data-server 0.4.6 and bluez 5.28 source code to receive photos from phone with two different computers (dualcore intel and quadcore amd) with kernel 3.16 and 3.19. 1.Download Bluez 5 source and add --compat flag to src/bluetooth.service.in file to bluetoothd start in bluez5 sources and run ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --enable-library Unit Description=Bluetooth service Documentation=man:bluetoothd(8) After=network.target Service Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd --compat Restart=on-failure RestartSec=3 #NotifyAccess=main #WatchdogSec=10 CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE LimitNPROC=1 Install WantedBy=multi-user.target Alias=dbus-org.bluez.service 2. edit sdpd-server.c to set more access rights: chmod(SDP_UNIX_PATH, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH); To make obexd work, add the following path to obexd/src/org.bluez.obex.service : Exec=/usr/local/libexec/bluetooth/obexd and cp org.bluez.obex.service /usr/share/dbus-1/services/ 3. run make and make install as root and then enable bluez: systemctl daemon-reload systemctl enable bluetooth.service systemctl start bluetooth.service 4. If the bluetooth system is unstable to receive photos from phone, compile openobex and obex-data-server against your bluez library: http://www.linuxfromscratch.org/blfs/view/svn/general/openobex.html http://www.linuxfromscratch.org/blfs/view/svn/general/obex-data-server.html After this do: sudo ln /usr/lib/libopenobex.so.1.7.1 /usr/lib/libopenobex.so.1 Also pulseaudio is needed for bluez. However it can cause problems with file transfers, so set autospawn=off in /etc/pulse/client.conf and use alsa for other audio. 5. Download blueman-master.zip from github, unzip it, run autogen.sh and make. As root run make install. PowerManager plugin has a setting that puts bluetooth on. 6. Now you can use the blueman after reboot immediately without any clicking to receive photos from the phone. If you send a file to phone with obexd, you must kill obexd before obex-data-server can receive files from phone again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768573: more documentation in the UI needed install Synaptic
Package: installation-reports Boot method: CD Image version:cdimage.debian.org/cdimage/jessie_di_beta_2/i386/iso-cd/debian-jessie-DI-b2-i386-xfce-CD-1.iso Date: 2014-10-03 18:55 Machine: E2160@3Ghz@AsusP5QldPro,2GB@800Mhz, GT440, SSDNow 120GB Processor:E2160@3Ghz Memory:2GB@800Mhz Partitions: /dev/sda1 ext4 22216 26400560 79053868 26% / Output of lspci -knn (or lspci -nn):00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e21] (rev 03) 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40] 00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 [8086:3a4a] 00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] 00:1d.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35] 00:1d.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a36] 00:1d.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 [8086:3a3a] 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 90) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIB (ICH10) LPC Interface Controller [8086:3a18] 00:1f.2 SATA controller [0106]: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller [8086:3a22] 00:1f.3 SMBus [0c05]: Intel Corporation 82801JI (ICH10 Family) SMBus Controller [8086:3a30] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GF108 High Definition Audio Controller [10de:0bea] (rev a1) 02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments: Tell users that if enabling network update it might take _several hours_ to download updated packages, so it is preferred to have Disable Network Update selected. Then installation is fast and take 10 minutes or so, because it fetch packages from CD. Explain what is installed when selecting Debian Desktop and Linux System tools. Have Synaptic automatically installed, if only Xfce desktop is selected. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont5
I inspected the source of bluez5 and obex-data-server and it seems that obex-data-server can not find or connect to bluez5 internal SDP server. See bluez-5.24/src/sdpd-server.c and obex-data-server-0.4.6/src/ods-bluez.c That is why we have in /var/log/syslog Nov 4 12:02:18 debian obex-data-server[16446]: **Warning: Couldn't connect to SDP server Nov 4 12:02:18 debian obex-data-server[16446]: **Warning: Could not add SDP record for server (/org/openobex/server1), closing server A test program is obex-data-server-0.4.6/test/ods-server-test.py. Create a desktop launcher with following command edited to suit your filesystem and local bluetooht address: /home/debian/Downloads/obex-data-server-0.4.6/test/ods-server-test.py -l 00:15:83:3E:F0:66 opp /home/debian/Public This program does not work if started in terminal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont5
I inspected the source of bluez5 and obex-data-server and it seems that obex-data-server can not find or connect to bluez5 internal SDP server A reason for this might be deprecated gnome thread functions when compiling latest obex-data-server source. http://wiki.muiline.com/obex-data-server I have no skill or intrested to learn gnome programming. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont2
I did debug obex-data-server and edited the source a bit. I found the following in syslog: Nov 3 09:57:38 debian obex-data-server[1848]: **Warning: Couldn't connect to SDP server (Jessietesting) Nov 3 09:57:38 debian obex-data-server[1848]: **Warning: Could not add SDP record for server (/org/openobex/server1), closing server when the obex-data-server starts with obex-data-server-0.4.6/data/obex-data-server.service edited to: [D-BUS Service] Name=org.openobex Exec=/usr/bin/obex-data-server --no-daemon --log --debug First warning comes from obex-data-server-0.4.6/src/ods-bluez.c: static sdp_session_t* sdp_session_get (const gchar *device, gboolean create_new) { SdpSessionRecords *recs; sdp_session_t *session; bdaddr_t src; if (sdp_session_list (recs = g_hash_table_lookup (sdp_session_list, device))) { return recs-session; } if (!create_new) return NULL; str2ba (device, src); //session = sdp_connect (src, BDADDR_ANY, SDP_RETRY_IF_BUSY); session = sdp_connect( BDADDR_ANY, BDADDR_LOCAL, SDP_RETRY_IF_BUSY ); if (!session) { g_warning (Couldn't connect to SDP server (Jessietesting)); /*char buf[50]; memset(buf, 0, sizeof(buf)); strcpy(buf,device); g_warning (buf);*/ return NULL; } return session; } As you see i have tried several sdp_connect calls and i noticed by default device is 00:00:00:00:00:00. I feel that this problem is something to do with systemd as it is a big system change from wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont3
In jessie repos, gnome-bluetooth gives you send binary, nothing to receive. I installed bluedevil ,and it is not working either, a familiar message in syslog when trying to send a picture from phone: Nov 3 12:00:49 debian systemd-udevd[159]: Network interface NamePolicy= disabled on kernel commandline, ignoring. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont4
Bluedevil is using obexd as you see. I get this after rebooting machine to clear state and no blueman stuff running, only bluedevil and obexd. In pc side i can see a progress bar starting and ending and phone belives that file was succefully send. The file does not appear in user specified download folder and you se that the connection is broken at some point of transmission. Nov 3 12:17:44 debian obexd[1081]: CONNECT(0x0), (null)(0x) Nov 3 12:17:44 debian obexd[1081]: CONNECT(0x0), (null)(0x0) Nov 3 12:17:44 debian obexd[1081]: PUT(0x2), (null)(0x) Nov 3 12:17:44 debian obexd[1081]: PUT(0x2), CONTINUE(0x10) Nov 3 12:17:50 debian obexd[1081]: DISCONNECT(0x1), (null)(0x) Nov 3 12:17:50 debian obexd[1081]: DISCONNECT(0x1), SUCCESS(0x20) Nov 3 12:17:50 debian obexd[1081]: disconnected: Transport got disconnected Nov 3 12:17:50 debian bluetoothd[769]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Nov 3 12:17:50 debian systemd-udevd[161]: Network interface NamePolicy= disabled on kernel commandline, ignoring. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont5
Yes, with bluedevil obex-data-server is needed. Bluedevil downloaded my pictures, but they went my homedir, not to directories you see in the Configure-KDE module. So bluedevil kind a like solved this problem, it is easier to use bluedevil than command line. However after reboot it did not work, by killing bluedevil and starting again it did. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757633: Blueman broken in jessie beta 2 xfce 32-bit, cont
I also compiled and installed latest bluez from http://www.bluez.org/download/ Now i have some action in /var/log/syslog. Each time i try to send a file from android 4.1 phone, i have the following: Nov 2 11:38:29 debian systemd-udevd[157]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Nov 2 11:38:41 debian systemd-udevd[157]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Above i tried to send 2 times, so 2 messages. Google does not help me to get forward of this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org