Bug#982299: Re. RTSP streams are not displayed with version 3.0.12 on Debian Sid

Oh, that is a bad news. :( Would you please tell me if you have any plan to rewrite some code to play RTSP stream again? It is a very fine function. Best regards, Gulfstream

Bug#982368: Re: Bug#982368: VLC can not play rtsp stream after upgraded to 3.0.12-2

Oh, that is a bad news. :( Would you please tell me if you have any plan to rewrite some code to play RTSP stream again? It is a very fine function. Best regards, Gulfstream > -原始邮件- > 发件人: "Sebastian Ramacher" > 发送时间: 2021-02-09 21:29:00 (星期二) > 收件人: gulfstream ,

Bug#964849: Re: 回复：Bug#964849: "Invalid data found when processing input" got when using ffmpeg

Thanks for your suggest. I got the reason which another software was installed with another ffmpeg, and set PATH point to it. Now I solved it. Thank you again! Best regards, Gulfstream > -原始邮件- > 发件人: "Jonas Smedegaard" > 发送时间: 2020-07-11 15:11:54 (星期六) > 收件人:

Bug#958304: Can not make Epson L1800 work

Hello, the epson-inkjet-printer-201312w need LSB which is abandoned by Debian. So it is not be used in Debian 10. Would you please tell me how to use the epson-inkjet-printer-201312w in Debian without LSB? Thank you very much! Best regards, Gulfstream

Bug#954203: Re: Bug#954203: Client splash and exit after login in

Thanks for your reply! My next question is How to connect the xrdp server using remmina client? I don't find where to set the glyph cache. And When will the bug be resolve? Thank again! Best regards, Gulfstream > -原始邮件- > 发件人: "Bernhard Übelacker" > 发送时间: 2020-03-21 19:07:38

Bug#954158: Re: Re: Bug#954158: Re: Bug#954158: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome

I looked through the folder /usr/bin just now, and found the xrdp is also in the folder /usr/bin # ls xr* xrandr xrdb xrdp-dis xrdp-genkeymap xrdp-keygen xrdp-sesadmin xrdp-sesrun xrefresh So the message in the vnc log fle is so strange. > -原始邮件- > 发件人: "Ola Lundqvist" >

Bug#954158: Re: Bug#954158: Re: Bug#954158: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome

But when I start vnc with root, the smae log is also got: 18/03/20 20:21:01 Xvnc version TightVNC-1.3.9 18/03/20 20:21:01 Copyright (C) 2000-2007 TightVNC Group 18/03/20 20:21:01 Copyright (C) 1999 AT Laboratories Cambridge 18/03/20 20:21:01 All Rights

Bug#954158: Re: Bug#954158: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome

I installed xrdp with apt-get, so its path is default of debian. $ whereis xrdp xrdp: /usr/sbin/xrdp /usr/lib/x86_64-linux-gnu/xrdp /etc/xrdp /usr/share/xrdp /usr/share/man/man8/xrdp.8.gz -原始邮件- 发件人:"Ola Lundqvist" 发送时间:2020-03-18 16:29:28 (星期三) 收件人: wg...@china.com,

Bug#954158: Re: Bug#954158: tightvncserver output a blank screen with gray color under gnome

Hi, I am glad to receive your reply. I have checked the xstartup which in the folder ~/.vnc. It is created by tightvncserver automatically. It is as below, #!/bin/sh xrdb $HOME/.Xresources xsetroot -solid grey #x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

Bug#925944: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot

Hi, I found that the gnome-shell extension can not show the status of laptop cell charging. So I reinstalled the laptop-mode-tools, and changed the wired interface name from "eth0" to "enp0s31f6" in the file /etc/laptop-mode/conf.d/ethernet.conf as advice from Ritesh. Then, I reboot several

Bug#952506: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot

> -原始邮件- > 发件人: "Ritesh Raj Sarraf" > 发送时间: 2020-02-27 01:56:04 (星期四) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: 925...@bugs.debian.org > 主题: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name > maybe changed when reboot > > Control: serverity -1 important

Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot

OK, thank you very much! I will wait for all things are fine again! Thank you again! > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 23:09:22 (星期三) > 收件人: wg...@china.com, 952...@bugs.debian.org, > laptop-mode-to...@packages.debian.org > 抄送: > 主题: Re: Bug#952506: Re: Bug#952506:

Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot

As your recommendation, I removed the laptop-mode-tools, it seems that wired interface' name is correct for several boot. But if there is no laptop-mode-tools, how I using its function for saving power to laptop? Thank you! > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 22:22:44

Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot

Yes, I have noticed it, but I don't know what thing is using eth0 early in the boot process. This bug did not exist several days ago. > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 22:18:47 (星期三) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: > 主题: Re: Bug#952506: Re:

Bug#952506: Wired interface name maybe changed when reboot

When the wired interface was be named enp0s31f6: udevadm info /sys/class/net/enp0s31f6 P: /devices/pci:00/:00:1f.6/net/enp0s31f6 L: 0 E: DEVPATH=/devices/pci:00/:00:1f.6/net/enp0s31f6 E: INTERFACE=enp0s31f6 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=3512520 E:

Bug#952506: Wired interface name maybe changed when reboot

To the wired net interface, "eth0" was named is more often than new style "enp0s31f6".

Bug#952506: Wired interface name maybe changed when reboot

btw, the wireless interface is correct, its name is always "wlp0s20f3".

Bug#952497: Wired network interface can not be managed by Network-Manager

Hi, I notice that the wired interface's name maybe be changed while rebooting. Sometimes the wired interface's name is "enp0s31f6", sometimes it is "eth0". The Network Manager can manage the wired interface if wired interface's name is "enp0s31f6". The Network Manager can not manage the wired

Bug#939505: Cannot access secondary GPU - error: [XORG] (EE)

more information: After I install package xserver-xorg-input-mouse, I got another error message. If I run optirun, the error message is: $ optirun glxgears [ 502.952517] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [ 502.952549] [ERROR]Aborting because fallback start is

Bug#939489: Cannot access secondary GPU - error: [XORG] (EE)

more information: After I install package xserver-xorg-input-mouse, I got another error message. If I run optirun, the error message is: $ optirun glxgears [ 502.952517] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) [ 502.952549] [ERROR]Aborting because fallback start is

Bug#939505: more information

When I run opengl program with optirun or primusrun, the program can not run and I got a error message as below: $ optirun freecad [ 614.056579] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0) [ 614.056596] [ERROR]Aborting

Bug#939489: more information

When I run opengl program with optirun or primusrun, the program can not run and I got a error message as below: $ optirun freecad [ 614.056579] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0) [ 614.056596] [ERROR]Aborting

Bug#930563: Re: Bug#930563: Can not start freecad

Hello Bernhard, Thanks for your reply! I have install the proprietary nvidia drivers and it runs well. The output of commands which you list as below, > ldd /usr/bin/freecad linux-vdso.so.1 (0x7ffe69ae5000) libhdf5_openmpi.so.103 =>

Bug#877519: Re: Re: Bug#877519: Re: Re: Re: Bug#877519: Bluetooth mouse suspend while using cell

Yes, this is after I added the device ID in the configuration file. -原始邮件- 发件人:"Ritesh Raj Sarraf" 发送时间:2017-10-12 18:14:39 (星期四) 收件人: wg...@china.com 抄送: 877...@bugs.debian.org 主题: Re: Re: Bug#877519: Re: Re: Re: Bug#877519: Bluetooth mouse suspend while using cell

Bug#877519: Re: Bug#877519: Re: Re: Re: Bug#877519: Bluetooth mouse suspend while using cell

Hi, the log information is: Oct 12 15:10:04 athena dbus-daemon[541]: [system] Activating service name='org.blueman.Mechanism' requested by ':1.97' (uid=4 pid=7478 comm="/usr/bin/python3 /usr/bin/blueman-applet ") (using servicehelper) Oct 12 15:10:04 athena org.blueman.Mechanism[541]:

Bug#877519: Re: Re: Re: Bug#877519: Bluetooth mouse suspend while using cell

Hi, I am so sorry for reply late. My bluetooth dongle is embedded, so I can not plug/unplug it for accquire the debug information. > -原始邮件- > 发件人: "Ritesh Raj Sarraf" > 发送时间: 2017-10-06 16:24:33 (星期五) > 收件人: wg...@china.com > 抄送: 877...@bugs.debian.org > 主题: Re: Re:

Bug#877519: Re: Re: Bug#877519: Bluetooth mouse suspend while using cell

The device informations about bluetooth are list as below which got by lsusb -v. And I do not known how to get to debug information about laptop-mode-tools. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB

Bug#877519: Re: Bug#877519: Bluetooth mouse suspend while using cell

> -原始邮件- > 发件人: "Ritesh Raj Sarraf" > 发送时间: 2017-10-02 22:36:05 (星期一) > 收件人: gulfstream , 877...@bugs.debian.org > 抄送: > 主题: Re: Bug#877519: Bluetooth mouse suspend while using cell > > Control: tag -1 +moreinfo > > Hello, > > On Mon, 2017-10-02 at