[Desktop-packages] [Bug 1978731] [NEW] verbosity cannot be increased (“debug” option broken)
Public bug reported: When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. This is the output I see either way: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== I know that some people get more verbosity because I see posts showing more verbosity, like the output in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489243 At first I thought I was encountering this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639368 But I think that bug is different because Beraldo Costa Leal gets just one line of output (not even the standard output). In any case, these bugs are similar and should perhaps be examined at the same time. ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1978731 Title: verbosity cannot be increased (“debug” option broken) Status in ppp package in Ubuntu: New Bug description: When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. This is the output I see either way: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== I know that some people get more verbosity because I see posts showing more verbosity, like the output in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489243 At first I thought I was encountering this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639368 But I think that bug is different because Beraldo Costa Leal gets just one line of output (not even the standard output). In any case, these bugs are similar and should perhaps be examined at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1978731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978451] [NEW] The PPP daemon has died: A modem hung up the phone (exit code = 16) → LCP: timeout sending Config-Requests
Public bug reported: /etc/wvdial.conf: ===8<-- [Dialer Defaults] StupidMode = 1 Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 +FCLASS=0 [Dialer Orange] Init3 = AT+CGDCONT=1,"IP","mworld.be",,0,0 Phone = *99# Mcc = 206 Mnc = 10 Username = '' Password = '' Carrier Check = off -->8=== execution: ===8<-- $ eject /dev/sr0 $ wvdial Orange --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","mworld.be",,0,0 AT+CGDCONT=1,"IP","mworld.be",,0,0 OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 360 --> Carrier detected. Waiting for prompt. --> Don't know what to do! Starting pppd and hoping for the best. --> Starting pppd at… --> Pid of pppd: 84797 --> Using interface ppp0 --> Disconnecting at… --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds -->8=== From the error codes list in “man pppd”: 16 The link was terminated by the modem hanging up. /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== The modem is a Huawei E220. I added “debug” to /etc/ppp/options but this failed to increase verbosity in /var/log/messages. When another machine connects to the same wireless broadband provider, CHAP is automatically negotiated and successfully used, FWIW. ** Affects: wvdial (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wvdial in Ubuntu. https://bugs.launchpad.net/bugs/1978451 Title: The PPP daemon has died: A modem hung up the phone (exit code = 16) → LCP: timeout sending Config-Requests Status in wvdial package in Ubuntu: New Bug description: /etc/wvdial.conf: ===8<-- [Dialer Defaults] StupidMode = 1 Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 +FCLASS=0 [Dialer Orange] Init3 = AT+CGDCONT=1,"IP","mworld.be",,0,0 Phone = *99# Mcc = 206 Mnc = 10 Username = '' Password = '' Carrier Check = off -->8=== execution: ===8<-- $ eject /dev/sr0 $ wvdial Orange --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","mworld.be",,0,0 AT+CGDCONT=1,"IP","mworld.be",,0,0 OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 360 --> Carrier detected. Waiting for prompt. --> Don't know what to do! Starting pppd and hoping for the best. --> Starting pppd at… --> Pid of pppd: 84797 --> Using interface ppp0 --> Disconnecting at… --> The PPP daemon has died: A modem hung up the phone (exit code = 16) --> man pppd explains pppd error codes in more detail. --> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information. --> Auto Reconnect will be attempted in 5 seconds -->8=== From the error codes list in “man pppd”: 16 The link was terminated by the modem hanging up. /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== The modem is a Huawei E220. I added “debug” to /etc/ppp/options but this failed to increase verbosity in /var/log/messages. When another machine connects to the same wireless broadband provider, CHAP is automatically negotiated and successfully used, FWIW. To manage notifications about this bug go to:
[Desktop-packages] [Bug 580437] Re: wvdial returns with Huawei E160E error NO CARRIER
Your config does not contain: Carrier Check = off You probably need to add that line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wvdial in Ubuntu. https://bugs.launchpad.net/bugs/580437 Title: wvdial returns with Huawei E160E error NO CARRIER Status in wvdial package in Ubuntu: Confirmed Bug description: Binary package hint: wvdial This error is not limited to wvdial, network-manager cannot either connect with similar errors. Wvdial however seems to give better logging information, so I'll attach log with hopefully relevant information. I have access to a Windows machine where the device works, so it is possible to connect with it. I have a Huawei E160E from Finnish provider Saunalahti. All the AT commands seems to go through, but when trying to connect wvdial returns NO CARRIER, and tries to connect again, never succeeding. I have tried using both /dev/ttyUSB0 and /dev/ttyUSB1 both giving the same errors. The wvdial.conf has been received from http://linux.fi/index.php/Wvdial#Saunalahti in to which I've added some debugging AT commands. [Dialer defaults] Modem = /dev/ttyUSB0 Init1 = ATZ Init2 = ATI Init3 = AT+GMR Init4 = AT+CSQ Init5 = AT^SYSINFO Init6 = AT+COPS? Init7 = AT+CGREG? Init8 = AT+CGDCONT=1,"IP","internet.saunalahti" Phone = *99***1# Stupid Mode = 1 Username = " " Password = " " ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: wvdial 1.60.3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 14 13:15:24 2010 ProcEnviron: SHELL=/bin/zsh PATH=(custom, user) LANG=en_US.utf8 SourcePackage: wvdial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/580437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946079] Re: ppmraw device no longer produces output (regression)
Upstream report: https://bugs.ghostscript.com/show_bug.cgi?id=704500 ** Bug watch added: Ghostscript (AFPL) Bugzilla #704500 http://bugs.ghostscript.com/show_bug.cgi?id=704500 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1946079 Title: ppmraw device no longer produces output (regression) Status in ghostscript package in Ubuntu: New Bug description: In version 9.26, the following command worked as expected -- it produces a ppm file: $ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA -sPageList=4 -o /tmp/raster.ppm vector.pdf But in ghostscript version 9.53.3, that command produces no PPM file, and the terminal output is empty. That is, there is no error, warning, or indication of progress. FWIW, the PDF in my tests was produced by LaTeX. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1946079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946079] [NEW] ppmraw device no longer produces output (regression)
Public bug reported: In version 9.26, the following command worked as expected -- it produces a ppm file: $ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA -sPageList=4 -o /tmp/raster.ppm vector.pdf But in ghostscript version 9.53.3, that command produces no PPM file, and the terminal output is empty. That is, there is no error, warning, or indication of progress. FWIW, the PDF in my tests was produced by LaTeX. ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1946079 Title: ppmraw device no longer produces output (regression) Status in ghostscript package in Ubuntu: New Bug description: In version 9.26, the following command worked as expected -- it produces a ppm file: $ gs -sDEVICE=ppmraw -q -r600 -sPAPERSIZE=a4 -dFIXEDMEDIA -sPageList=4 -o /tmp/raster.ppm vector.pdf But in ghostscript version 9.53.3, that command produces no PPM file, and the terminal output is empty. That is, there is no error, warning, or indication of progress. FWIW, the PDF in my tests was produced by LaTeX. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1946079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938548] Re: screen capture broken; ImageMagick "import" command fails
** Description changed: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. + + This bug is mirrored here: + + https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1938556 + + Most likely ImageMagick is the culprit. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1938548 Title: screen capture broken; ImageMagick "import" command fails Status in xwayland package in Ubuntu: New Bug description: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. This bug is mirrored here: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1938556 Most likely ImageMagick is the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1938548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938548] [NEW] screen capture broken; ImageMagick "import" command fails
Public bug reported: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1938548 Title: screen capture broken; ImageMagick "import" command fails Status in xwayland package in Ubuntu: New Bug description: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1938548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937311] [NEW] copy-dir-locals-to-file-locals-prop-line command does nothing in LaTeX mode
Public bug reported: When in latex-mode with a latex source file in the buffer, running: M-x copy-dir-locals-to-file-locals-prop-line does nothing. It doesn't matter whether there is an existing line with -*- -*- or not. It's a bit annoying, because there are 4 latex engines to choose from in the configuration menu, and it would be convenient to be able to make emacs choose the correct engine for the file at hand (because different files work with different engines). Discovered on GNU Emacs 27.1 ** Affects: emacs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1937311 Title: copy-dir-locals-to-file-locals-prop-line command does nothing in LaTeX mode Status in emacs package in Ubuntu: New Bug description: When in latex-mode with a latex source file in the buffer, running: M-x copy-dir-locals-to-file-locals-prop-line does nothing. It doesn't matter whether there is an existing line with -*- -*- or not. It's a bit annoying, because there are 4 latex engines to choose from in the configuration menu, and it would be convenient to be able to make emacs choose the correct engine for the file at hand (because different files work with different engines). Discovered on GNU Emacs 27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1937311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936953] [NEW] evince no longer renders grayscale DjVu docs
Public bug reported: Evince used to have no problem showing a grayscale djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 presents an error: 'Unable to open document "grayscale_sample.djvu". File type DjVu image (image/gnd.djvu) is not supported.' Now evince can only render bilevel DjVu images. To reproduce, start with a grayscale *.pgm file. Use ImageMagick if needed to obtain one, as follows: $ convert logo: sample_grayscale.pgm Convert to djvu: $ c44 sample_grayscale.pgm sample_grayscale.djvu Finally: $ evince sample_grayscale.djvu (broken) ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1936953 Title: evince no longer renders grayscale DjVu docs Status in evince package in Ubuntu: New Bug description: Evince used to have no problem showing a grayscale djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 presents an error: 'Unable to open document "grayscale_sample.djvu". File type DjVu image (image/gnd.djvu) is not supported.' Now evince can only render bilevel DjVu images. To reproduce, start with a grayscale *.pgm file. Use ImageMagick if needed to obtain one, as follows: $ convert logo: sample_grayscale.pgm Convert to djvu: $ c44 sample_grayscale.pgm sample_grayscale.djvu Finally: $ evince sample_grayscale.djvu (broken) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1936953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935581] Re: evince no longer shows bookmarks for DjVu files
** Description changed: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 + + Note that I would have reported this upstream, but I was unable to + register on gitlab.gnome.org. I forgot what the issue was, but I + probably failed some anti-bot test. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1935581 Title: evince no longer shows bookmarks for DjVu files Status in evince package in Ubuntu: New Bug description: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 Note that I would have reported this upstream, but I was unable to register on gitlab.gnome.org. I forgot what the issue was, but I probably failed some anti-bot test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1935581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935581] [NEW] evince no longer shows bookmarks for DjVu files
Public bug reported: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1935581 Title: evince no longer shows bookmarks for DjVu files Status in evince package in Ubuntu: New Bug description: Evince used to have no problem showing bookmarks when viewing a djvu file. Version 3.22.1 was fine. Now evince version 3.38.2 just shows a blank pane for bookmarks. I'm not sure if the bug is in evince or in djvused, so the bug report is mirrored for each package. The djvused bug report has more details: https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1935580 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1935581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933913] [NEW] "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64"
Public bug reported: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933913 Title: "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64" Status in xorg package in Ubuntu: New Bug description: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916341] [NEW] poppler-utils/pdfimages list function names the wrong color in output table
Public bug reported: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1916341 Title: poppler-utils/pdfimages list function names the wrong color in output table Status in poppler package in Ubuntu: New Bug description: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 910272] Re: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it
Same problem for me. I have an old parallel-only printer. It has been working with a dedicated printer server, but the printer server died and the PC has no parallel port. So I connected a USB-to-LPT cable. As I attach the cable /var/log/syslog shows: parport0: fix this legacy no-device port driver! lp0: using parport0 (polling) There does not exist a /dev/usb/lp0. I still set "DeviceURI parallel:/dev/usb/lp0" since that is what the instructions still say (https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_-.3E_Parallel_adapter), and indeed that fails. I also tried "DeviceURI parallel:/dev/parport0" and CUPS rejected it. Then I tried "DeviceURI parallel:/dev/lp0". CUPS accepted it, I sent a test print, and it just sits on the job queue with the msg "Printer not connected; will retry in 30 seconds". # usb_printerid /dev/lp0 Error: Invalid argument: GET_DEVICE_ID on '/dev/lp0' # usb_printerid /dev/parport0 Error: Invalid argument: GET_DEVICE_ID on '/dev/parport0' At another moment, I got a different error: # usb_printerid /dev/lp0 Error: Device or resource busy: can't open '/dev/lp0' This is on Bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/910272 Title: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it Status in cups package in Ubuntu: Fix Released Status in cups source package in Oneiric: Won't Fix Bug description: Parallel port dot matrix printer Panasonic KX-P2124 connected via usb- parallel cable to HP6600 PC; running Ubuntu 11.10 system located on external hard drive attached by usb. Worked on Ubuntu version 8 using URI "parallel:/dev/usb/lp0". Understand that usblp has been deprecated; replace with ??? Cups reports printer not connected. CUPS version is (from UbuntuSoftwareCenter) - "cups 1.5.0-8ubuntu6". #Researched existing bugs - lots of info - no results. No "Help" menu found by selecting upper right located "Gear"/"Printers; could not find any "Wizard." Thank you for your assistance, nvsoar w8@w8-FJ463AAR-ABA-a6528p:~$ uname -a Linux w8-FJ463AAR-ABA-a6528p 3.0.0-15-generic #24-Ubuntu SMP Mon Dec 12 15:25:25 UTC 2011 i686 i686 i386 GNU/Linux w8@w8-FJ463AAR-ABA-a6528p:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 067b:3507 Prolific Technology, Inc. PL3507 ATAPI6 Bridge Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader Bus 002 Device 002: ID 050d:0002 Belkin Components #Device immediately above is usb to parallel cable w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep lp lp 17455 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep ppdev ppdev 12849 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep parport_pc parport_pc 32114 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/* ls: cannot access /dev/usb/lp*: No such file or directory crw-rw-r-- 1 root root 189, 0 2011-12-30 15:04 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 2011-12-30 15:04 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 3 2011-12-30 15:04 /dev/bus/usb/001/004 crw-rw-r-- 1 root root 189, 128 2011-12-30 15:04 /dev/bus/usb/002/001 crw-rw-r-- 1 root lp 189, 129 2011-12-30 15:25 /dev/bus/usb/002/002 w8@w8-FJ463AAR-ABA-a6528p:~$ dmesg | grep par [0.00] Booting paravirtualized kernel on bare hardware [0.00] vt handoff: transparent VT on vt#7 [0.210399] hpet0: 3 comparators, 32-bit 25.00 MHz counter [ 28.754567] uss720: protocols (eg. bitbang) over USS720 usb to parallel cables [ 28.893725] type=1400 audit(1325286282.534:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=705 comm="apparmor_parser" [ 28.893736] type=1400 audit(1325286282.534:3): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=755 comm="apparmor_parser" [ 28.894175] type=1400 audit(1325286282.534:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=755 comm="apparmor_parser" [ 28.894324] type=1400 audit(1325286282.534:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=705 comm="apparmor_parser" [ 28.894438] type=1400 audit(1325286282.534:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=755 comm="apparmor_parser" [ 28.894592] type=1400 audit(1325286282.534:7): apparmor="STATUS" operation="profile_replace"
[Desktop-packages] [Bug 1817480] Re: Emacs color-theme package is gone from version 40.1
Still a problem in 42.2. No color-theme-* (thus no color-theme-modern that was proposed as a replacement). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs-goodies-el in Ubuntu. https://bugs.launchpad.net/bugs/1817480 Title: Emacs color-theme package is gone from version 40.1 Status in emacs-goodies-el package in Ubuntu: Confirmed Bug description: It seems that color-theme and other packages are missing from between versions 40.1 and 36.3ubuntu1 which is breaking existing emacs customizations. Any chance these could be reverted back? or a different package could be provided? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs-goodies-el/+bug/1817480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
