[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
Same here.. I upgraded from 22.04 (upgrade failed but i managed to install missing packages with dpkg --configure -a, apt install -f, apt upgrade.. but it's not our issue in this thread) When we click on nautilus icon, nothing happen (on wayland) michael@michael-ubuntu:~$ nautilus ** Message: 22:29:35.550: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen MESA-INTEL: warning: Haswell Vulkan support is incomplete Erreur de segmentation If i close the session and start with xorg it's fine, nautilus opened. michael@michael-ubuntu:~$ nautilus ** Message: 22:29:35.550: Connecting to org.freedesktop.Tracker3.Miner.Files This happen with some other applications as gnome-control-center by example. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in wayland package in Ubuntu: Confirmed Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2061257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832414] Re: Removing document files spam from cups
Same problem here with Ubuntu Server 19.10 (cups 2.2.12-2ubuntu1) + LogLevel to debug. Thousands of lines per second as below... it happen when printing and fill badly the logs too. D [09/Dec/2019:11:00:16 +0100] [Job 50127] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50128] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50129] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50130] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50131] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) D [09/Dec/2019:11:00:16 +0100] cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" D [09/Dec/2019:11:00:16 +0100] [Job 50132] Removing document files. D [09/Dec/2019:11:00:16 +0100] cupsdMarkDirty(---J-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: Confirmed Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
Ok working, my problem was not directly related to this bug. Sorry,
please forget my comment #20 and #21!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
See my attachment please. System stuck on boot.
** Attachment added: "console detail on boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651/+attachment/5287976/+files/bug.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
Hi,
After this update (237-3ubuntu10.29) on this morning (11 sept.) my system no
more booting!
Black screen after grub, select other kernel but nothing works. I suppose it is
linked with this update...
...
Failed to start Network Manager
Dependency failed for Network Manager Wait Online
...
237-3ubuntu10.28 (ok) -> 237-3ubuntu10.29 (fail)
How to resolve that? I have no more network.. and my system is blocked.
Thanks for your help.
Ubuntu 18.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782719] Re: Duplex not working upon update to 2.2.7-1ubuntu2.1
I have not exactly the same problem but it is probably related. On Ubuntu 18.04.3, i choose Duplex "Long Edge" but it print a single- sided PDF document.. It was working on Ubuntu 16.04.x.. I tried Ubuntu 19.04 and it works too. I use Evince for my PDF. If i choose another pdf reader like qpdfview it's works like expected. I tried lp command for testing and it's work: lp -d MP-2352 -o Duplex=DuplexNoTumble testfile.pdf I also tried to print a text document from gedit with Duplex "Long Edge" and it's not working. I got one side page. A document printed with LibreOffice works like expected. We use Ubuntu 18.04 on our company and is important to fix it because we are now unable to print PDF documents with two-side.. Thanks. Below some log: ... Filetype: PDF Neither PDF renderer command line nor Ghostscript-based renderer command line found Driver does not understand PDF input, converting to PostScript Storing temporary files in /var/spool/cups/tmp Starting process \"pdf-to-ps\" (generation 1) Printer make and model: NRG MP 2352 PS3 Running command line for pstops: pstops 44555 john testfile.pdf 1 \' cups-browsed cups-browsed-dest-printer=\1137\ xxx.xxx.xxx.xxx:631/MP-2352\ Duplex=DuplexNoTumble finishings=0 InputSlot=Auto job-uuid=urn:uuid:8023a1dd-8f1f-3e58-58b2-eb77f271e0d5 JobType=Normal MediaType=Auto OutputBin=Default PageSize=A4 Password=None print-quality=0 StapleLocation=None UserCode=None pdftops- max-image-resolution=300 pdftops-renderer=pdftops job-originating-host- name=xxx.xxx.xxx.xxx date-time-at-creation= date-time-at-processing= time-at-creation=1566373945 time-at-processing=1566373945\' ... Found: %%BeginFeature: *Duplex None Option: Duplex=None Setting option Found: %% FoomaticRIPOptionSetting: Duplex=None Option: Duplex=None Setting option ... @PJL SET DUPLEX=OFF ... I also ask question here but not answer until now: https://askubuntu.com/questions/1167331/ubuntu-18-04-duplex-long-edge-printing-mode-selected-but-not-working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1782719 Title: Duplex not working upon update to 2.2.7-1ubuntu2.1 Status in cups package in Ubuntu: Confirmed Bug description: I am using ubuntu 18.04 LTS. After an automatic update of libcups (and related) from 2.2.7-1ubuntu2 to 2.2.7-1ubuntu2.1 I have been unable to print double-sided, e.g., printing a pdf from evince using the standard printer dialog. I have not changed the printer or printer drivers during this and before everything was working fine. I suspect that the option that is used for duplex printing is has changed and is wrong now. It seems to be "DuplexNoTumble", see $ lpoptions -l | grep -i duplex Duplex/Duplex: *None DuplexNoTumble DuplexTumble After using evince and the standard printer dialog to issue a print job where I selected "Long Edge (standard)" for the "Two Sided" option, I see the following in the cups error log: $ cat /var/log/cups/error_log | grep -i duplex D [20/Jul/2018:09:30:36 +0200] [Job 39] argv[5]="RPSBitsPerPixel=1BitsPerPixel InputSlot=Auto RPSRGBcorrect=DetailBright RPSDitherType=Auto RIwmSize=36 RIBannerPageMediaType=Auto LockedPrintPassword=None RIWMText=Confidential Rcmyksimulation=Off RIwmAngle=45Deg Booklet=None RPSColorRendDict=Auto RIPaperPolicy=PromptUser RPSBlackMode=gray noRPSColorUniversalDesign PageSize=A4.FullBleed JobType=Normal noRIBannerPagePrint RIPrintMode=0rhit MediaType=Auto RIRotateBy180=Off RIwmTextStyle=Gray RIPunch=None RIBannerPageInputSlot=Auto ColorModel=Gray Rimagesm=Off number-up=1 noRPSBlackOverPrint RIOrientOvr=Off StapleLocation=None Resolution=600dpi DocServerPassword=None RPSColorSep=None RIFoldType=None UserCode=None noCollate Duplex=DuplexNoTumble RIwmFont=HelveticaB RIWatermark=Off OutputBin=Default job-uuid=urn:uuid:10bf31c1-fbcf-31fd-4093-04b4cc248849 finishings=53 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1532071836 time-at-processing=1532071836" D [20/Jul/2018:09:30:36 +0200] [Job 39] Added option Duplex D [20/Jul/2018:09:30:36 +0200] [Job 39] Pondering option \'Duplex=DuplexNoTumble\' D [20/Jul/2018:09:30:36 +0200] [Job 39] Running command line for pstops: pstops 39 username \'filename\' 1 \'RPSBitsPerPixel=1BitsPerPixel InputSlot=Auto RPSRGBcorrect=DetailBright RPSDitherType=Auto RIwmSize=36 RIBannerPageMediaType=Auto LockedPrintPassword=None RIWMText=Confidential Rcmyksimulation=Off RIwmAngle=45Deg Booklet=None RPSColorRendDict=Auto RIPaperPolicy=PromptUser RPSBlackMode=gray noRPSColorUniversalDesign PageSize=A4.FullBleed JobType=Normal noRIBannerPagePrint RIPrintMode=0rhit MediaType=Auto RIRotateBy180=Off RIwmTextStyle=Gray RIPunch=None RIBannerPageInputSlot=Auto ColorModel=Gray Rimagesm=Off noRPSBlackOverPrint RIOrientOvr=Off StapleLocation=None Resolution=600dpi
[Touch-packages] [Bug 1829718] Re: Network printers (cups-browsed) disappear after each CUPS update on client side
Just a few more information about this issue. This is the cups-browsed's state just after a cups update... is dead... root@foo-ubuntu:/home/foo# service cups-browsed status ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: inactive (dead) since ven 2019-06-14 14:51:38 CEST; 2min 27s ago Main PID: 927 (code=exited, status=0/SUCCESS) jun 14 14:35:02 foo-ubuntu systemd[1]: Started Make remote CUPS printers available locally. jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally... jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally. And here the syslog just when update is applied... Jun 14 14:51:32 foo-ubuntu systemd[1]: Stopped Daily apt upgrade and clean activities. Jun 14 14:51:32 foo-ubuntu systemd[1]: Stopped Daily apt download activities. Jun 14 14:51:32 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:32 foo-ubuntu systemd[1]: Started CUPS Scheduler. Jun 14 14:51:32 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:34 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started CUPS Scheduler. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started Daily apt upgrade and clean activities. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started Daily apt download activities. Jun 14 14:51:37 foo-ubuntu gnome-session[1647]: debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped CUPS Scheduler. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:38 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally... Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally. Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping CUPS Scheduler... Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped CUPS Scheduler. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:38 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:39 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:41 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:42 foo-ubuntu systemd[1]: Started ACPI event daemon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1829718 Title: Network printers (cups-browsed) disappear after each CUPS update on client side Status in cups package in Ubuntu: New Bug description: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups- browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829718] [NEW] Network printers (cups-browsed) disappear after each CUPS update on client side
Public bug reported: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups-browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1829718 Title: Network printers (cups-browsed) disappear after each CUPS update on client side Status in cups package in Ubuntu: New Bug description: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups- browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596903] [NEW] Function Key F3 doesnt work so WIFI cant be enabled again
Public bug reported: Funftion + F3 in Ubuntu 16.04 doesnt work, WIFI cant be enabled Unity displays WIFI-Network as enabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 28 12:29:53 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-03 (55 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp8s0 proto static metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.1.0/24 dev enp8s0 proto kernel scope link src 192.168.1.21 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp8s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 94b51aed-9145-445d-ab42-7f9ea5fbd7d1 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp7s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug functionkey wifi xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1596903 Title: Function Key F3 doesnt work so WIFI cant be enabled again Status in network-manager package in Ubuntu: New Bug description: Funftion + F3 in Ubuntu 16.04 doesnt work, WIFI cant be enabled Unity displays WIFI-Network as enabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 28 12:29:53 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-03 (55 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp8s0 proto static metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.1.0/24 dev enp8s0 proto kernel scope link src 192.168.1.21 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp8s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 94b51aed-9145-445d-ab42-7f9ea5fbd7d1 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp7s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1596903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
