[Bug 1905065] [NEW] cryptsetup(8) man page confused about signals
Public bug reported: The cryptsetup(8) manual page says (spurious lines omitted): reencrypt or --active-name [] Run resilient reencryption (LUKS2 device only). [...] Reencryption process may be safely interrupted by a user via SIGTERM signal (ctrl+c). No: Control-C generates SIGINT. System shutdown generates SIGTERM. Nothing is said about the other two very similar signals: SIGHUP Generated by logout (historically, by modem hanging up). SIGQUIT Generated by control-\ (control-backslash). I do not know if cryptsetup worries about those two signals or not. Either way, the manual page should say something — in addition to un-confusing SIGTERM and control-C (SIGINT); see signal(7). N.b. To be pedantic, the keys which generate SIGINT and SIGQUIT can be configured (see, e.g., stty(1)), however, ^C and ^\ are the most common (and default, I think). Also, the package is technically "cryptsetup-bin" not "cryptsetup", but Launchpad claims "'cryptsetup-bin' does not exist in Ubuntu." ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cryptsetup-bin 2:2.2.2-3ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Nov 20 18:15:03 2020 InstallationDate: Installed on 2020-10-19 (32 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905065 Title: cryptsetup(8) man page confused about signals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1905065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902958] Re: Sorry, I dont speak English
Apologies, I forget: You may want to change the title from Sorry, I dont speak English to something about the problem. As an example: Программа установки завершила работу и отправила отчет (Installer crashed and sent this report) To change the title click on yellow circle next to the title. Извините, я забыл: вы можете изменить название с Sorry, I dont speak English к чему-то о проблеме. Например Программа установки завершила работу и отправила отчет (Installer crashed and sent this report) Чтобы изменить заголовок, щелкните желтый кружок рядом с заголовком. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902958 Title: Sorry, I dont speak English To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902958] Re: Sorry, I dont speak English
Sorry, I do not have any idea. Now that there is a description of what happened, perhaps someone who is an expert on the installation can study the problem. That may not happen quickly. >From my own experience, if the system is basically working despite the installer being upset, then the system is probably Ok. Translated into Russian by Google Translate: Извините, я понятия не имею. Теперь, когда есть описание того, что произошло, возможно кто-то знаток установки можете изучить проблему. Это не может произойти быстро. По собственному опыту, если система в основном работает, несмотря на то, что установщик расстроен, тогда система, вероятно, в порядке. Izvinite, ya ponyatiya ne imeyu. Teper', kogda yest' opisaniye togo, chto proizoshlo, vozmozhno kto-to znatok ustanovki mozhete izuchit' problemu. Eto ne mozhet proizoyti bystro. Po sobstvennomu opytu, yesli sistema v osnovnom rabotayet, nesmotrya na to, chto ustanovshchik rasstroyen, togda sistema, veroyatno, v poryadke. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902958 Title: Sorry, I dont speak English To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904075] Re: [NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all (or so KDE "thinks")
Attached is the output of dmesg(1) shortly after a cold cold-boot when the audio output seems Ok: The KDE thing knows about the H/W and functions as expected, and all seems happy. This is mostly for information and comparison with the report's log (when things (well, at least the module & KDE) didn't work). By "cold cold-boot" I mean a boot from power OFF ("cold-boot") after being OFF for perhaps 30 minutes ("cold" (i.e., let the system cool down, but I do NOT believe it was "hot")). As an aside, I tried using `apport-cli -u...' but it decided there was nothing new to report. Still searching for that incident when things changed from not-all-is-Ok to all-seems-Ok. ** Attachment added: "dmesg(1) output after a cold boot when the audio works Ok (NO obvious problems)" https://bugs.launchpad.net/ubuntu/+bug/1904075/+attachment/5433967/+files/dmesg-cold_boot-audio_Ok.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904075 Title: [NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all (or so KDE "thinks") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec
I had what I _thought_ originally was a very similar issue with Kubuntu 20.04.1 LTS on a Clevo-NJ70, but further investigation suggests my problem, despite the same-ish messages, is somewhat different. See bug #1904075 ("[NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all (or so KDE 'thinks'"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886626 Title: after login to gnome with snd_hda_intel :00:1f.3: No response from codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902958] Re: Sorry, I dont speak English
Please explain the problem in your language. You do not need to use English. Пожалуйста, объясните проблему на своем языке. Вам не нужно использовать английский. Pozhaluysta, ob"yasnite problemu na svoyem yazyke. Vam ne nuzhno ispol'zovat' angliyskiy. (Via Google Translate, I do not speak Russian.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902958 Title: Sorry, I dont speak English To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904075] [NEW] [NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all (or so KDE "thinks")
Public bug reported: This is an odd one (or so it seems to me)... Sometimes, after booting, my log is filled with messages similar to: [ 208.746660] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a3b000 [ 209.758633] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70740 [ 210.770511] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20bf0015 See bug #1886626 ("after login to gnome with snd_hda_intel :00:1f.3: No response from codec") for a very similar problem; or at least the same-ish message. The KDE volume thingy says there are no audio input or output devices. I cannot configure anything audio-H/w related with KDE. HOwEVER, whilst generating this bug report with apport-cli(1), the tests it ran clearly showed (heard!) the built-in (internal) speakers are working. Intrigued, I tried a wireless Bluetooth headset (it also worked), a wireless USB headset (also worked), and a wired headset (also worked). So there *is* sound, but KDE thinks there is no H/w... SOMETIMES. At other times, everything is fine. There is no known pattern here (e.g., warm- or cold-boot does not seem to matter, etc.). And then, just to confuse things further, at least once the system booted up in the KDE-no-sound state (complete with module "No response from codec"), but later (a few minutes?) began to work; a check of the log (dmesg(1)) showed those messages had stopped and everything from then on appeared normal. (I'll see if I can find that incident in the logs, *IF* I can, I'll attach it later.) That "not"-working to working does not usually seem to happen (that one incident may be the only time it has happened?) I have no idea if, when in the KDE-no-sound state, if I can control the volume from the computer. I have also NOT tested the input (microphone(s)) whilst in the KDE-no-sound state, but I presume it's like the output (works but KDE doesn't know it?). It sort-of looks like, at the moment, to me, there is sometime amiss in the "kernel sound stuff" which is having a knock-on effect on the "KDE sound stuff". Apologies I cannot be any more specific... ;-( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blf3447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Nov 13 00:30:59 2020 InstallationDate: Installed on 2020-10-19 (24 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blf3447 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ5x_NJ7xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd07/16/2020:svnNotebook:pnNJ5x_NJ7xLU:pvrNotApplicable:rvnNotebook:rnNJ5x_NJ7xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NJ5x_NJ7xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904075 Title: [NJ5x_NJ7xLU, Realtek ALC293, Speaker, Internal] No sound at all (or so KDE "thinks") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902311] Re: GNU sha256sum(1) &tc --check (-c) output depends on order of --quiet and --warn
** Summary changed: - GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn + GNU sha256sum(1) &tc --check (-c) output depends on order of --quiet and --warn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902311 Title: GNU sha256sum(1) &tc --check (-c) output depends on order of --quiet and --warn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1902311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902311] [NEW] GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn
Public bug reported: The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum, sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and --warn options. This is counter-intuitive, not documented in the man(1) pages, and unnecessary. Simple example: 1$ date >/tmp/data 2$ sha256sum /tmp/data >/tmp/sums 3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected) 4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"... /tmp/data: OK 5$ The manual page says (spurious lines omitted): The following five options are useful only when verifying checksums: --quiet don't print OK for each successfully verified file -w, --warnwarn about improperly formatted checksum lines There is no reason --warn should affect the operation of --quiet (nor visa-versa). The operations as documented are orthogonal. Attached is a bash(1) shell script written when puzzling over this inconsistent behaviour; it may be useful (use --help for a summary). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: coreutils 8.30-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Oct 30 21:34:31 2020 InstallationDate: Installed on 2020-10-19 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "GNU Bash(1) script to show various differing behaviours (--help for summary)" https://bugs.launchpad.net/bugs/1902311/+attachment/5429603/+files/sha-sum-chk.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902311 Title: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1902311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902311] Re: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn
Obviously, I meant sha256sum(1) in the bug's title! (*sighs*) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902311 Title: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1902311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878658] [NEW] Should use "$@" with double-quotes
Public bug reported: stegosuite(1) is a too-simple bash(1) script: 1 #!/bin/bash 2 3 DIRNAME="/usr/share/stegosuite" 4 STEGOSUITEJAR=$(echo $DIRNAME/stegosuite-*.jar) 5 6 # Setup the classpath 7 if [ ! -f "$STEGOSUITEJAR" ]; then 8 die "Missing required file: $STEGOSUITEJAR" 1st problem, `die' is neither a bash builtin nor an external command; it does not exist. 9 fi 10 11 STEGOSUITE_CLASSPATH="$STEGOSUITEJAR" 12 13 gtk3_version=`dpkg -s libgtk-3-0|grep '^Version' | cut -d'.' -f2` 14 swt4_version=`dpkg -s libswt-gtk-4-java|grep '^Version' | cut -d'.' -f2` 15 16 # Run with GTK2-fallback if swt<=4.8 and gtk>=3.22 17 if [ \( "$gtk3_version" -ge 22 \) -a \( "$swt4_version" -le 8 \) ]; then 18 env SWT_GTK3=0 java -jar $STEGOSUITE_CLASSPATH $@ 19 else 20 java -jar $STEGOSUITE_CLASSPATH $@ 21 fi 2nd problem (and the issue I ran into), both on lines 18 and 20, the $@ should be in double-quotes "$@". Because it is not, you cannot use a passphrase containing, e.g., spaces; that is, a command similar to the following does not work: $ stegosuite -d -e -k 'My *secret* phrase!' -f INPUT -- IMAGE.png (The `-d' is not necessary, but is useful to see what is going on.) What precisely happens seems a bit variable — there's also seems to be a poor command-line parser (3rd problem) — other than it "doesn't work", sometimes silently (4th problem), and usually exits with a 0 status (5th problem). And, of course, having a key on the command-line is rather poor security (6th problem). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: stegosuite 0.8.0-1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 14 19:19:47 2020 InstallationDate: Installed on 2016-10-07 (1315 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: stegosuite UpgradeStatus: Upgraded to bionic on 2018-08-18 (635 days ago) ** Affects: stegosuite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878658 Title: Should use "$@" with double-quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stegosuite/+bug/1878658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875194] [NEW] weborf(1) man page describes SIGUSR2 functionality, which does not (and never has?) existed
Public bug reported: The weborf(1) manual page says, when describing the --cache (-C) option, "[...] To flush the cache (empty that directory) you must send SIGUSR2 to the process. It is advised to flush the cache on reboot (manually or with kill) because some items might be invalid after a reboot but weborf would not know that." However, actually doing a `kill -SIGUSR2 ' will kill the `weborf' process; furthermore, an examination of the source code not only finds there is no current SIGUSR2 functionality, it appears there never has been! That man page statement was added in the original caching commit, https://github.com/ltworf/weborf/commit/f21ee4b1ac02 ("Added --cache option"), but no SIGUSR2 handler was added (or exists); and the (also-added) daemon control script (`daemon/weborf' in that commit) does *not* the SIGUSR2 (if the daemon is running). I consider this a highly confusing error in the end-user documentation; as such, I am (obviously) presuming the daemon works correctly if the contents of its cache dir are simply removed (even if it is running), which is what the control script is doing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: weborf 0.14-1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE Date: Sun Apr 26 15:13:00 2020 InstallationDate: Installed on 2016-10-07 (1297 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: weborf UpgradeStatus: Upgraded to bionic on 2018-08-18 (617 days ago) ** Affects: weborf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875194 Title: weborf(1) man page describes SIGUSR2 functionality, which does not (and never has?) existed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weborf/+bug/1875194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870839] Re: ModuleNotFoundError: No module named 'shatag.cli'
This 2018 problem report (with the same name as this report!), https://bitbucket.org/maugier/shatag/issues/9/modulenotfounderror-no-module-named indicates that the problem was found and fixed. It also mentions "shattr by @weakish clone shattr", which I seems to mean this clone/rewrite, https://github.com/weakish/shattr which seems to be in Redhat(?)'s Ceylon programming language. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870839 Title: ModuleNotFoundError: No module named 'shatag.cli' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shatag/+bug/1870839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870839] [NEW] ModuleNotFoundError: No module named 'shatag.cli'
Public bug reported: $ shatag --help Traceback (most recent call last): File "/usr/bin/shatag", line 11, in load_entry_point('shatag==0.4.1', 'console_scripts', 'shatag')() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2693, in load_entry_point return ep.load() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, in load return self.resolve() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2330, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) ModuleNotFoundError: No module named 'shatag.cli' $ Whilst the --help option was used in the above example, the same(?) "No module named ..." error appears to happen whatever one tries. Using locate(1), no "shatag.cli" file seems to exist (the package has been installed for awhile now, and so updatedb(1) should have catalogued the files). In addition, there is no "cli" (anything) listed as being part of the package ("dpkg-query -L shatag | grep -i cli" finds nothing). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shatag 0.5.0-2 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 4 22:34:59 2020 InstallationDate: Installed on 2016-10-07 (1275 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: shatag UpgradeStatus: Upgraded to bionic on 2018-08-18 (595 days ago) ** Affects: shatag (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870839 Title: ModuleNotFoundError: No module named 'shatag.cli' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shatag/+bug/1870839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869062] Re: Acer Aspire 7715 microphone not detected
Follow-up to #2 (again, please note I am NOT the originator of this report). Searching through some old notes/logs, I found the attached information about _my_ WiFi H/W (excerpted and slightly redacted because I have not checked the complete notes/logs for sensitive information). Abbreviated summary (from `hwinfo --all', see attachment for more details): 13: PCI 300.0: 0282 WLAN controller [...] Model: "Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter" Vendor: pci 0x168c "Qualcomm Atheros" Device: pci 0x0042 "QCA9377 802.11ac Wireless Network Adapter" SubVendor: pci 0x11ad "Lite-On Communications Inc" SubDevice: pci 0x0806 Revision: 0x30 Driver: "ath10k_pci" Driver Modules: "ath10k_pci" Device File: wlp3s0 Features: WLAN Memory Range: 0xf080-0xf09f (rw,non-prefetchable) IRQ: 47 (1789 events) HW Address: [REDACTED] Permanent HW Address: [REDACTED (same)] Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v168Cd0042sv11ADsd0806bc02sc80i00" Driver Info #0: Driver Status: ath10k_pci is active [...] Unfortunately, the (less likely to be detected) builtin USB Bluetooth was not detected. ;-( ** Attachment added: "Assorted WiFi-related excerpts from notes/logs of Jan-2020" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+attachment/5341708/+files/Aspire-E17-WiFi.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869062 Title: Acer Aspire 7715 microphone not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866561] Re: Okular in repository is ancient and crasjhes system
I also use okular v1.3.3 all the time without the described issue. It *might* have something to do with the _particular_ PDF you are trying to open. I would suggest that, if possible, you attach the failing PDF to this bug report. Also, it's unclear (to me) from your description if the PDF which is now failing used to work? *If* it did, *and* you still have a working copy, *and* it is possible to attach it, then I would also suggest attaching the (previously-)working PDF to this bug report. Please ensure it is clear which (attached) PDF is failing, and also which one is working. Finally, any idea if there is, e.g., "excessive" memory consumption or I/O? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866561 Title: Okular in repository is ancient and crasjhes system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1866561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869062] Re: Acer Aspire 7715 microphone not detected
NOTE: I am NOT the originator of this bug report, but have a similar(? identical?) problem. My machine is an Acer Aspire E17 E5-722-425Q, and the built-in microphone (and also the mouse pad) has never(?) been detected. (Since I use a USB mouse and a USB headset-with-microphone, neither problem has ever bothered me in the slightest.) Sometimes, the built-in WiFi is not detected (as is the case at the moment), and, usually, the built-in Bluetooth is not detected (also the case at the moment). However, I *have* observed that, at least in the case of the WiFi (the Bluetooth is not-so-clear) it seems to be related to the temperature (especially the external (ambient, i.e., room temperature)). Whilst no measurements have been made, if the ambient temperature is sufficiently cool (cold, actually, PROBABLY less than 10 degrees Celsius (estimated)), the WiFi is frequently detected. When it is warm, it is much more hit-and-miss. (There are some circumstantial reasons to think, for both the WiFi and Bluetooth (both are USB), that if there certain unclear external USB devices are also attached when the system is booted, than one or both is detected. Apologies for being quite vague here, I have never tried to confirm or characterise this incidental observation.) Attached is the RAW report generated by apport-cli(1); I do not know how to automagically append it to a bug which I did not originally create. However, please note that, at the moment, neither the built-in USB WiFi nor the built-in USB Bluetooth is currently detected (and the ambient temperature is currently quite warm). ** Attachment added: "1869062" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+attachment/5341699/+files/1869062 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869062 Title: Acer Aspire 7715 microphone not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869090] [NEW] Duplicate /usr/lib/debug/usr/lib/python2.7/dist-packages/pysqlite2/_sqlite.so
Public bug reported: $ sudo apt install ... [...] Unpacking python-pysqlite2-dbg (2.7.0-1) ... Selecting previously unselected package python-pysqlite2-dbgsym. Preparing to unpack .../22-python-pysqlite2-dbgsym_2.7.0-1_amd64.ddeb.deb ... Unpacking python-pysqlite2-dbgsym (2.7.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ZChtVH/22-python-pysqlite2-dbgsym_2.7.0-1_amd64.ddeb.deb (--unpack): trying to overwrite '/usr/lib/debug/usr/lib/python2.7/dist-packages/pysqlite2/_sqlite.so', which is also in package python-pysqlite2-dbg 2.7.0-1 Errors were encountered while processing: /tmp/apt-dpkg-install-ZChtVH/22-python-pysqlite2-dbgsym_2.7.0-1_amd64.ddeb.deb E: Sub-process /usr/bin/dpkg returned an error code (1) $ Originally, I had intended to only install -dbgsym and not -dbg, but the -dbg package was suggested (not sure by which package?), so tried to install both -- with the above results. Worked-around the problem by a simple `sudo apt remove python-pysqlite2-dbgsym', with allowed the installation to proceed and complete without any obvious problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python-pysqlite2-dbgsym (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 23:53:16 2020 InstallationDate: Installed on 2016-10-07 (1265 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: python-pysqlite2 UpgradeStatus: Upgraded to bionic on 2018-08-18 (585 days ago) ** Affects: python-pysqlite2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869090 Title: Duplicate /usr/lib/debug/usr/lib/python2.7/dist- packages/pysqlite2/_sqlite.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pysqlite2/+bug/1869090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846464] Re: pdfposter hangs with no output
Here is a hypothesis for what is going on: It's working, doing what it was told to do, but what it was told to do is probably not what is intended. First, a closer look at the example input PDF shows there is an oddity (not wrong, just odd): $ pdfinfo -box Micro-Magic_Plan_2016_V2.pdf [...] Page size: 2961.3 x 2094.21 pts [...] However, A4 paper is 210 x 297 millimetres, or more to the point here (excuse the pun), 595 x 842 pts. That means the full-sized image is already more than four times as large as a single sheet of A4 paper (portrait, which is the default). Hence, `--scale=4' is going to produce an image that is more than 16x the size of A4 width (and correspondingly as high): $ pdfposter --dry-run --verbose --verbose --verbose --scale=4 Micro-Magic_Plan_2016_V2.pdf /dev/null Mediasize : 1.0x1.0 a4 595.00 842.00 dots Scaling by: 4.00 processing page 1 - input dimensions: 2961.30 2094.21 (trimbox of input page) output dimensions: 11845.20 8376.84 (calculated) Pages w/o rotation 20 x 10 Pages w/ rotation 15 x 15 Decided for rotation: no Deciding for 20 column and 10 row of portrait pages. ^C [...] That's a BIG poster: 20 A4 pages wide (4.2 metres), and 10 A4 pages high (almost 3 metres), on a total of 200 sheets. I'm not surprised it's taking a long time to generate a very large output. (The use of `--dry-run' and `/dev/null' are attempts to avoiding having to ^C (unsuccessfully).) Presuming what is wanted is a poster four times the size of a sheet of A4, then, since the image already is about that size, my suggestion is to use `--scale=1': $ pdfposter -m2x1a4 --verbose --verbose --verbose --scale=1 Micro-Magic_Plan_2016_V2.pdf Plan1-landscape.pdf Mediasize : 2.0x1.0 a4 1190.00 842.00 dots Scaling by: 1.00 processing page 1 - input dimensions: 2961.30 2094.21 (trimbox of input page) output dimensions: 2961.30 2094.21 (calculated) Pages w/o rotation 3 x 3 Pages w/ rotation 4 x 2 Decided for rotation: yes Deciding for 4 column and 2 row of landscape pages. Creating page with offset: 0.00 1190.00 Creating page with offset: 0.00 0.00 Creating page with offset: 842.00 1190.00 Creating page with offset: 842.00 0.00 Creating page with offset: 1684.00 1190.00 Creating page with offset: 1684.00 0.00 Creating page with offset: 2526.00 1190.00 Creating page with offset: 2526.00 0.00 $ That's a full-size image on only 8 sheets (landscape), or just over one metre wide and sightly less than 500cm high (half a metre). Which seems, to me, reasonable. (I do NOT know if the `-m2x1a4' is actually useful?) And it does work, albeit it still takes a long time to process: On my system, 12 minutes (100% CPU), generating an 80 MiB output file. (I have not printed the output, but it looks Ok in a PDF viewer (Okular).) Scaling up to the original 200 sheets of `--scale=4' suggests it would take about 300 minutes (5 hours), and generate a 2000 MiB (2 GiB) output file. I do not intend to test these estimates! ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846464 Title: pdfposter hangs with no output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfposter/+bug/1846464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846464] Re: pdfposter hangs with no output
Now confirmed, using the PDF kindly attached in #3. There actually is some output, the output file `Plan.pdf' has been created and is --- slowly --- relentlessly growing. It grew to c.68MiB by letting pdfposter(1) run for 10mins (real-time) solid, fully occupying one of my cores (100% of one CPU). However, the memory usage did_not_ increase. When I finally gave up and ^C'ed, I got: $ pdfposter --scale=4 Micro-Magic_Plan_2016_V2.pdf Plan.pdf ^CTraceback (most recent call last): File "/usr/bin/pdfposter", line 9, in load_entry_point('pdftools.pdfposter==0.6.0', 'console_scripts', 'pdfposter')() File "/usr/share/pdfposter/pdftools/pdfposter/cmd.py", line 129, in run main(opts, *args) File "/usr/share/pdfposter/pdftools/pdfposter/__init__.py", line 340, in main outpdf.write(open(outfilename, 'wb')) File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 501, in write obj.writeToStream(stream, key) File "/usr/lib/python2.7/dist-packages/PyPDF2/generic.py", line 785, in writeToStream self[NameObject("/Length")] = NumberObject(len(self._data)) File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 2771, in _getData newdata.write(b_(operator)) KeyboardInterrupt $ Unsurprisingly, the output `Plan.pdf' is incomplete and/or corrupt. I do_not_ know whether it would complete if I had the patience and disc space to let in churn away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846464 Title: pdfposter hangs with no output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfposter/+bug/1846464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
Make sure your unit really is an r8169, and not an r8168. Whilst (as I understand it) the r8169 module is supposed to work with an r8168, at least on my laptop (Acer Aspire E17 (E5-722-425Q), currently 18.04 (up-to-date)), using the r8169 module has resulted in "flakely" behaviour for as long as I can remember, including becoming unusable after a (some?) warm reboot. (Sorry, I cannot recall any specific details, albeit I vaguely recall that was not the only problem I had.) Using the r8168 dkms module, there has not been any(?) problems. However, I believe the r8168 module (in package `r8168-dkms') is specific to r8168 hardware and will not work with an r8169 unit. Using `lspci' my r8168 is listed as: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846464] Re: pdfposter hangs with no output
I just tried (also 0.6.0 on 18.04 (up-to-date)) and it seemed to work. (Unfortunately, I canNOT attach the test PDF I used because it contains very sensitive information.) This suggests there is something in the PDF you used which is causing this behaviour. As such, if it is possible, perhaps you should consider attaching the causes-to-fail PDF? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846464 Title: pdfposter hangs with no output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfposter/+bug/1846464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853510] Re: "*** buffer overflow detected" when running atop
This problem does not seem to happen on 18.04: # lsb_release -a LSB Version:core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic # # atop -V Version: 2.3.0 - 2017/03/25 09:59:59 # # atop [... seems to work fine ...] Maybe try installing 18.04(or later) `atop'? You may or may not run into dependency issues. # ldd $(which atop) linux-vdso.so.1 (0x7ffc22968000) libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 (0x7f1902844000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f190261a000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f19023fd000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f190205f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f1901e57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1901a66000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1901862000) /lib64/ld-linux-x86-64.so.2 (0x7f1902d62000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1901643000) # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853510 Title: "*** buffer overflow detected" when running atop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1853510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855315] Re: Please upgrade it to 2019 on Ubuntu 18.04 LTS
I concur. Whilst 18.04's TeXlive-2017(?) is usually fine (for me), it's age is starting to present a few annoyances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855315 Title: Please upgrade it to 2019 on Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1855315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857762] Re: Kubuntu: No nice overlay for hotkeys (bluetooth, airplane mode, keyboard backlight
This has also annoyed me, and is perhaps more of an issue (for me) as sometimes some of the functions don't function. For instance, at the moment I've lost bluetooth completely; the lack of bluetooth button hotkey feedback just adds to the confusion. (The loss of bluetooth is known to unrelated to this bug; it seems to be a timing and/or temperature issue during kernel startup with the (internal USB) bluetooth unit is not always seen (Acer Access E17 (E5-722-425Q) laptop; Kubuntu 18.04 (up-to-date); unknown if there are any bugs specially about, or related to, this?) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to khotkeys in Ubuntu. https://bugs.launchpad.net/bugs/1857762 Title: Kubuntu: No nice overlay for hotkeys (bluetooth, airplane mode, keyboard backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/khotkeys/+bug/1857762/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1850608] [NEW] Segfaults trying to send crash report
Public bug reported: After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2" plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865), whoopsie repeatedly crashes with a segfault (in what seems to be libc?). An excerpt from /var/log/syslog (slightly redacted): Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon. Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: /var/lock/whoopsie/lock Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash. Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash. Oct 30 08:33:10 [REDACTED] kernel: [ 2129.099314] whoopsie[22414]: segfault at 7f4f878a4000 ip 7f4f866fe5e1 sp 7ffe348bed78 error 4 in libc-2.27.so[7f4f86591000+1e7000] Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Main process exited, code=dumped, status=11/SEGV Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Failed with result 'core-dump'. Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Service hold-off time over, scheduling restart. Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Scheduled restart job, restart counter is at 133. Oct 30 08:33:11 [REDACTED] systemd[1]: Stopped crash report submission daemon. The above sequence of logged events repeats endlessly, with only(?) the times and whoospie PID changing. The problem can be (temporarily) stopped by `service whoopsie stop'; using `service whoopsie start' resumes the above behaviour. Rebooting does not "fix". Manually running whoopsie shows the same behaviour: $ sudo /bin/sh -c 'export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f' [09:45:14] Using lock path: /var/lock/whoopsie/lock [09:45:14] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 [09:45:14] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash. [09:45:14] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash. Segmentation fault $ $ ls -la /var/crash/ total 33340 drwxrwsrwt 2 root whoopsie 4096 Oct 30 08:52 . drwxr-xr-x 16 root root 4096 Sep 14 2018 .. -rw-r--r-- 1 root whoopsie 281 Oct 30 08:55 kexec_cmd -rwxrwxrwx 1 root whoopsie0 Oct 30 08:22 .lock -rw-r- 1 blf whoopsie 17624101 Oct 30 08:53 _usr_bin_kdeinit5.1000.crash -rw-rw-r-- 1 blf whoopsie0 Oct 30 08:22 _usr_bin_kdeinit5.1000.upload -rw-r- 1 root whoopsie 398157 Oct 24 11:49 _usr_bin_sddm.0.crash -rw-r- 1 whoopsie whoopsie 15996866 Oct 30 08:22 _usr_bin_whoopsie.108.crash -rw-r- 1 root whoopsie99379 Oct 22 15:07 _usr_sbin_inetd.0.crash $ Because (as far as I know) the various `.crash' files MAY contain sensitive information, I have not attached them to this (public) bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: whoopsie 0.2.62ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 Date: Wed Oct 30 09:28:01 2019 InstallationDate: Installed on 2016-10-07 (1118 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to bionic on 2018-08-18 (438 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-false bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850608 Title: Segfaults trying to send crash report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1850608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821499] Re: [Feature request] /etc/init/zram-config.conf has no any options. Please add a few.
Starting with Disco Dingo (19.04) there is a new package `zram-tools' which is roughly configurable as per many of the above wishes. https://launchpad.net/ubuntu/+source/zram-tools >From eyeballing it, it seems like it should work on earlier releases (but see caveats below); however, I have not tried. Some caveats: 1. Have at most one of `zram-config' or `zram-tools' (NOT both) installed. 2. The `zram-tools' defaults are slightly different from `zram-config'. 3. The version of `zram-tools' currently proposed for Eoan E (19.10?) has some simple fixes and perhaps should be preferred? I am currently using 19.04's 0.3.2-1 with Disco Dingo but will probably switch to using 19.10's (Eoan's) 0.3.2-1-1 on that system to pick up the above-mentioned configuration fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821499 Title: [Feature request] /etc/init/zram-config.conf has no any options. Please add a few. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1821499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821499] Re: [Feature request] /etc/init/zram-config.conf has no any options. Please add a few.
I presume this is referring to the hardcoded calculations for NRDEVICES and the critical calculation using it: mem=$(((totalmem / 2 / ${NRDEVICES}) * 1024)) (There are a few others that perhaps should be more easily adjusted.) Yes, this also has annoyed me, albeit, to-date, the hardcoded values seem to be Ok for me on my system. I'd also like to be able to specify more zram devices; i.e., have some which are not used for swap. Currently (without testing) all those created are used for swap, and it's not possible to create additional devices (but I suppose one could then swapoff(1) one or more to get the desired "extra" device(s)?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821499 Title: [Feature request] /etc/init/zram-config.conf has no any options. Please add a few. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1821499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option
This is not a bug, it is expected & reasonable behaviour. The `-p DIR' and `--tmpdir[=DIR]' mktemp(1) options are the same, excepting that the argument is mandatory for -p and optional for --tmpdir. (See the manpage (`man mktemp') or try `mktemp --help'.) That is, the following are equivalent: mktemp -u -p / --tmpdir mktemp -u -p/--tmpdir mktemp -u --tmpdir=/ --tmpdir mktemp -u -p / -p "${TMPDIR:-/tmp}" All print "FOO/tmp." where is the value of TMPDIR (/tmp if not set (the usual case)). Clearly, the LAST (right→most) -p or --tmpdir option is being used, with all the preceding ones ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823709] Re: su-to-root(1) should support lxsudo(1) & friends
CORRECTION: Apologies, I just realised (when attempting to modify su-to-root) that lxsudo(1) & friends can only become superuser "root"; an arbitrary user is not supported. Despite the name, su-to-root can become an arbitrary user; i.e., it is not restricted to superuser "root". Hence, at least in Cosmic, su-to-root "cannot" use lxsudo &tc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823709 Title: su-to-root(1) should support lxsudo(1) & friends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menu/+bug/1823709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823709] [NEW] su-to-root(1) should support lxsudo(1) & friends
Public bug reported: The su-to-root script has a limited selection of "known" su(1)/sudo(1) front-ends. A missing front-end is lxqt-sudo(1), i.e., lxsudo(1) and lxsu(1), which would seem to be a "natural fix" for LXqt as used by Lubuntu 18.10 (cosmic). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: menu 2.1.47ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: LXQt Date: Mon Apr 8 13:49:31 2019 InstallationDate: Installed on 2019-02-25 (41 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: menu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: menu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823709 Title: su-to-root(1) should support lxsudo(1) & friends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menu/+bug/1823709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823542] Re: usbauth segfault
That fix (commit 9a081a80b7c9 ("fix segfault on strtol")), which is in usbauth v1.0.1, does seem to have fixed this problem. Ubuntu 19.04(? disco) contains usbauth v1.0.1, and installing that package on my 18.04 LTS (Ubuntu bionic) system fixed the segfault. Testing with invalid serial="..." values, and similar, confirmed it works; see attached usbauth.conf I suggest the usbauth 1.0.1+git20190123.5004f7d-1 Ubuntu disco package also be used for Ubuntu bionic LTS. ** Attachment added: "Now working (with usbauth v1.0.1) /etc/usbauth.conf" https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+attachment/5253740/+files/usbauth.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823542 Title: usbauth segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823542] [NEW] usbauth segfault
Public bug reported: Under not entirely clear conditions, usbauth(1) will segfault (see attached kern.log excerpt). In this particular case, it is known the segfault is caused by the serial="..." Attribute in /etc/usbauth.conf allow idVendor==0x059f idProduct==0x1061 serial=="75686ff51019" Without that serial="..." there is no segfault. (It is also not clear if the "double quotes" are necessary or allowed; either way there is a segfault (presumed to be the same).) In what I _think_ is the usbauth source at https://github.com/kochstefan/usbauth-all commit 9a081a80b7c9 ("fix segfault on strtol") MAY be the fix? https://github.com/kochstefan/usbauth-all/commit/9a081a80b7c9ed221b733e33d5fcd73b0da18f4d ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: usbauth 1.0~git20180214-1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Sun Apr 7 16:39:21 2019 InstallationDate: Installed on 2016-10-07 (912 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: usbauth UpgradeStatus: Upgraded to bionic on 2018-08-18 (232 days ago) mtime.conffile..etc.usbauth.conf: 2019-04-07T16:38:01.039187 ** Affects: usbauth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823542 Title: usbauth segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821941] [NEW] checkflac needs to be updated from upstream
Public bug reported: The current version of checkflac (in 18.10 LTS / Cosmic) is badly out- of-date: * It cannot handle filenames with spaces (fairly common for ripped .flac files). * It is hardwired to use /dev/hdc as the name of the CD drive. * It does not report what the invalid Disc-ID _is_ making it hard to withdraw bogus data from various websites. ALL of the above problems, and perhaps more, have been fixed upstream, https://sourceforge.net/projects/flactag/ E.g., "checkflac: make script more resilient for filenames containing spaces or colons", https://sourceforge.net/p/flactag/git/ci/346d0ad569d7f6bf0a8232975712a42991a5650c/ (which was done back in 2015). There have apparently been about six fixes since the last release (2.0.4), which is apparently the version in Ubuntu: 346d0ad (HEAD -> master, origin/master, origin/HEAD) checkflac: make script more resilient for filenames containing spaces or colons 827399c discid: exit non-zero on error cd14b51 Default to /dev/cdrom, allow override 264512e checkflac: exit non-zero on error or mismatch 6e81155 autotools: create uninstall-hook to remove symlinks to man pages 6f6e1eb (tag: 2.0.4) Fil updates in preparation for release ** Affects: flactag (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821941 Title: checkflac needs to be updated from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flactag/+bug/1821941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760724] Re: Konqueror becomes a zombie process after being closed.
Yes, I can confirm that once Konqueror is started - with "Always try to have one preloaded instance" enabled - a process (possibly the same one? (didn't check)) does stay around, even after an clicking quit. This is very annoying, since when shutting down the system (or possibly even when logging out?), it does not seem to respond (quickly enough?) to the (presumed) SIGTERM, and as a result, you get a Crash Report at the next login. Disabling "Always try to have one preloaded instance" appears to avoid the problem. As an aside, it's not technically a "zombie process" - it has not actually exit()ed - but an idling process which seems to interfere with things -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760724 Title: Konqueror becomes a zombie process after being closed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konqueror/+bug/1760724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
I can confirm this latest update also seems to be working fine (no blue background): Start-Date: 2019-02-26 18:47:20 Commandline: apt-get dist-upgrade Requested-By: [redacted] Upgrade: libldb1:amd64 (2:1.4.0+really1.3.5-2, 2:1.4.0+really1.3.5-2ubuntu0.1), libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.18.10.6, 9.26~dfsg+0-0ubuntu0.18.10.7), firefox:amd64 (65.0+build2-0ubuntu0.18.10.1, 65.0.1+build2-0ubuntu0.18.10.1), opera-stable:amd64 (58.0.3135.68, 58.0.3135.79) End-Date: 2019-02-26 18:48:57 This was on my Lubuntu18.10 "recovery" USB-based system (not my main Kubuntu18.04 LTS "main" HDD-based system); same printer (HP OfficeJet Pro 6970). Many Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
I also confirmed this upgrade FIXED the blue-background problem: Start-Date: 2019-02-23 19:52:39 Commandline: apt-get dist-upgrade Requested-By: [redacted] Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6), ghostscript-dbg:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6), ghostscript-doc:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.18.04.5, 9.26~dfsg+0-0ubuntu0.18.04.6) End-Date: 2019-02-23 19:54:46 Many thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1817308] Re: GhostScript Update causes Blue Background
Thanks for the tip! When I just tried that I got: # sudo apt install ghostscript=9.25~dfsg+1-0ubuntu1 libgs9=9.25~dfsg+1-0ubuntu1 libgs9-common=9.25~dfsg+1-0ubuntu1 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '9.25~dfsg+1-0ubuntu1' for 'ghostscript' was not found E: Version '9.25~dfsg+1-0ubuntu1' for 'libgs9' was not found E: Version '9.25~dfsg+1-0ubuntu1' for 'libgs9-common' was not found # Obviously I need to configure(?) something, but am at a bit of a loss as to what, as I don't really know much about the Debian/Ubuntu packaging system. (Any tips or pointers?) Fortunately, the "High Qualify Grayscale" CUPS workaround is Ok(-ish) for now cheers! -blf- On Fri, 22 Feb 2019 at 18:20, Jarl <1817...@bugs.launchpad.net> wrote: > I have downgraded to 9.25 using > sudo apt install ghostscript=9.25~dfsg+1-0ubuntu1 libgs9=9.25~dfsg+1-0ubuntu1 > libgs9-common=9.25~dfsg+1-0ubuntu1 > > That solved the problem. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1817308 > > Title: > GhostScript Update causes Blue Background > > Status in ghostscript package in Ubuntu: > Incomplete > > Bug description: > I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with > kernel 4.15.0-45-generic. > > Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and > was applied to two of my machines (One is an Intel and one is an AMD, > but both are kept fully updated) that share a networked HP OfficeJet > 6700 Printer. > > At some point following the update, I happened to print a document, > and ended up with a blue background on every page, even otherwise > blank second sides. This occured regardless of a variety of > originating applications I used, such as LibreOffice, various text > editors, and even the CUPS "print test page" option. > > It took me a while to troubleshoot this on that first machine (trying > different apps, reinstalling CUPS and so forth) until I realized the > new ghostscript update was the issue and that (after trying to print > from the second machine) it was affecting both machines. > > I should note that, using the "non-CUPS" appearance of the same > printer, no blue background is present, but of course this provides no > features like ink-level reporting, dual-sided printing, etc. > > I "restored" the ghostscript stuff from the last Timeshift backup and > that cured the issue but I think this is a serious matter that should > be addressed immediately (not the least because it's hard to read > black text on a blue background and it wastes a lot of ink). > > I first posted this at > <https://forums.linuxmint.com/viewtopic.php?f=47&t=288613#p159> > and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was > on the update information) who advised me to post this bug here. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- “How many surrealists does it take to| Brian Foster change a lightbulb? Three. One calms | somewhere in south of France the warthog, and two fill the bathtub | with brightly-coloured machine tools.” | -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
My printer does NOT auto-upgrade and it started having the problem immediately after the `ghostscript' "upgrade". There is no doubt about this, colour printing was working fine yesterday until the upgrade, then it went all blue-background. I have not (yet?) tried reverting `ghostscript', I am happy(?) with the "High Quality Grayscale" workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1817308] Re: GhostScript Update causes Blue Background
Not a bad idea, but I can confirm this is NOT what happened in my case. My printer (HP OfficeJet Pro 6970) does NOT auto-upgrade, and it was indisputably working fine until the `ghostscript' "upgrade" mentioned in the bug report. I was doing printing all day yesterday (in colour) and everything worked fine until after that upgrade. Also, asking the printer to generate reports (either on the front panel or via HPLIP from Linux) works fine, as does copying. Its very probably only stuff from Linux/CUPS which goes wrong. (Having said that, I haven't tried "raw" PostScript, but I also don't want to waste any more blue ink. cheers! -blf- On Fri, 22 Feb 2019 at 18:05, Matthew Covington wrote: > I started having the same problem today on an Ubuntu 16.04 machine and > an HP OfficeJet Pro 6978. However, I haven't updated ghostscript (or > anything else recently). I was wondering whether it was an HP update > that broke the printing. My printer is automatically installing HP > updates. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1817308 > > Title: > GhostScript Update causes Blue Background > > Status in ghostscript package in Ubuntu: > Incomplete > > Bug description: > I am running 64 bit Linux Mint 19.1, the Cinnamon desktop 4.0.9, with > kernel 4.15.0-45-generic. > > Two days ago an update to ghostscript dated 20 FEB 2019 appeared, and > was applied to two of my machines (One is an Intel and one is an AMD, > but both are kept fully updated) that share a networked HP OfficeJet > 6700 Printer. > > At some point following the update, I happened to print a document, > and ended up with a blue background on every page, even otherwise > blank second sides. This occured regardless of a variety of > originating applications I used, such as LibreOffice, various text > editors, and even the CUPS "print test page" option. > > It took me a while to troubleshoot this on that first machine (trying > different apps, reinstalling CUPS and so forth) until I realized the > new ghostscript update was the issue and that (after trying to print > from the second machine) it was affecting both machines. > > I should note that, using the "non-CUPS" appearance of the same > printer, no blue background is present, but of course this provides no > features like ink-level reporting, dual-sided printing, etc. > > I "restored" the ghostscript stuff from the last Timeshift backup and > that cured the issue but I think this is a serious matter that should > be addressed immediately (not the least because it's hard to read > black text on a blue background and it wastes a lot of ink). > > I first posted this at > <https://forums.linuxmint.com/viewtopic.php?f=47&t=288613#p159> > and then sent an e-mail to marc.deslauri...@ubuntu.com (whose name was > on the update information) who advised me to post this bug here. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- “How many surrealists does it take to| Brian Foster change a lightbulb? Three. One calms | somewhere in south of France the warthog, and two fill the bathtub | with brightly-coloured machine tools.” | -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
Also "(HP) Deskjet 1510 All in one", "HP Officejet 7310"; e.g., see https://h30434.www3.hp.com/t5/Inkjet-Printing/Printer-has-suddenly-started-printing-solid-blue-background/td-p/7027024 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
Some more info (in case it helps): Ubuntu 18.04.2 LTS x86_64 [fully up-to-date Kubuntu] HP OfficeJet Pro 6970 [has worked flawlessly] A bit of searching on the 'Net has found complaints this is happening for other printers not mentioned in _this_ bug report, including (but not necessarily limited to) "HP Photosmart C7280", "HP 3520 All-in-one"; e.g., see https://askubuntu.com/questions/1120379/my-printer-adds-a-blue-background I have not noticed/found any complaints (yet?) for non-HP printers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
I can also confirm setting "High Quality Grayscale" (in CUPS) works-around the problem. There's no colour (obviously), but also no wasting Blue ink on a useless background. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817308] Re: GhostScript Update causes Blue Background
I also can confirm this started happening after the following upgrade: Start-Date: 2019-02-21 20:42:54 Commandline: apt-get dist-upgrade Requested-By: [redacted] Upgrade: libgs9:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-dbg:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-doc:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), ghostscript-x:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5), libgs9-common:amd64 (9.26~dfsg+0-0ubuntu0.18.04.4, 9.26~dfsg+0-0ubuntu0.18.04.5) End-Date: 2019-02-21 20:45:26 There is no doubt it is due to that "upgrade". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817308 Title: GhostScript Update causes Blue Background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1817308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
Same result for 4.4.10 On Jun 9, 2016 3:56 PM, "Levente Ábrók" wrote: > Some news. > I updated the kernel to 4.4.13. Now I don't have error messages is dmesg. > Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if > everything is needed). > sudo update-grub and reboot > Although I still cannot switch between the cards with DDIS, but I can run > specific programs with the dedicated AMD, using DRI_PRIME=1 > programpathname. That is already quite good, because I don't need the > dedicated for browsing the web or so. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1581270 > > Title: > Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on > resume > > Status in xorg package in Ubuntu: > Confirmed > > Bug description: > dmesg shows issues with being able to use the discrete graphics card > (relevant dmesg lines attached). > > Grub does pass "radeon.modeset=1" but it doesn't seem to make a > difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to > the kernel, then it does not error (except for the VCE error -110, > which is probably harmless). > > Running `DRI_PRIME=1 glxgears`: > - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a > black window with a visible top bar. > - with just "radeon.modeset=1", error (attached as 'glxgears'). > > Results are similar on Ubuntu GNOME 16.04, except with > "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of > screen tearing. > > Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be > attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR: > > [ 22.916285] [drm] ring test on 0 succeeded in 2 usecs > [ 22.916289] [drm] ring test on 1 succeeded in 1 usecs > [ 22.916292] [drm] ring test on 2 succeeded in 1 usecs > [ 22.916299] [drm] ring test on 3 succeeded in 3 usecs > [ 22.916304] [drm] ring test on 4 succeeded in 3 usecs > [ 23.092271] [drm] ring test on 5 succeeded in 2 usecs > [ 23.092276] [drm] UVD initialized successfully. > [ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs > [ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs > [ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs > [ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs > [ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs > [ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence > wait failed (-35). > [ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: > failed testing IB on ring 5 (-35). > > lsb_release -rd: > Description: Ubuntu 16.04 LTS > Release: 16.04 > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Thu May 12 20:43:03 2016 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics > Controller [144d:c0e6] > Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD > 8670A/8670M/8750M] [144d:c0e6] > InstallationDate: Installed on 2016-05-13 (0 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed > root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash > radeon.modeset=1 vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/21/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P05ADH.017.140421.SH > dmi.board.asset.tag: No Asset Tag > dmi.board.name: NP680Z5E-X01US > dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.board.version: SEC_SW_REVISION_1234567890ABCD > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 9 > dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.chassis.version: N/A > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH: > bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: > dmi.pr
[Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
# /etc/default/grub ... GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1 radeon.runpm=0" ... Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth animation runs (no black window). ** Attachment added: "glxgears-2" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661667/+files/glxgears-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
** Description changed: dmesg shows issues with being able to use the discrete graphics card (relevant dmesg lines attached). - Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel. - I've tried all combinations and same results occur. + Grub does pass "radeon.modeset=1" but it doesn't seem to make a + difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to + the kernel, then it does not error (except for the VCE error -110, which + is probably harmless). + + Running `DRI_PRIME=1 glxgears`: + - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black window with a visible top bar. + - with just "radeon.modeset=1", error (attached as 'glxgears'). + + Results are similar on Ubuntu GNOME 16.04, except with + "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of + screen tearing. Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR: [ 22.916285] [drm] ring test on 0 succeeded in 2 usecs [ 22.916289] [drm] ring test on 1 succeeded in 1 usecs [ 22.916292] [drm] ring test on 2 succeeded in 1 usecs [ 22.916299] [drm] ring test on 3 succeeded in 3 usecs [ 22.916304] [drm] ring test on 4 succeeded in 3 usecs [ 23.092271] [drm] ring test on 5 succeeded in 2 usecs [ 23.092276] [drm] UVD initialized successfully. [ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs [ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs [ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs [ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs [ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs [ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35). lsb_release -rd: Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 12 20:43:03 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6] -Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6] + Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6] InstallationDate: Installed on 2016-05-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP680Z5E-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev
[Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661631/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
** Attachment added: "glxgears" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661633/+files/glxgears -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581270] [NEW] Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
Public bug reported: dmesg shows issues with being able to use the discrete graphics card (relevant dmesg lines attached). Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel. I've tried all combinations and same results occur. Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR: [ 22.916285] [drm] ring test on 0 succeeded in 2 usecs [ 22.916289] [drm] ring test on 1 succeeded in 1 usecs [ 22.916292] [drm] ring test on 2 succeeded in 1 usecs [ 22.916299] [drm] ring test on 3 succeeded in 3 usecs [ 22.916304] [drm] ring test on 4 succeeded in 3 usecs [ 23.092271] [drm] ring test on 5 succeeded in 2 usecs [ 23.092276] [drm] UVD initialized successfully. [ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs [ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs [ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs [ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs [ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs [ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35). lsb_release -rd: Description:Ubuntu 16.04 LTS Release:16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 12 20:43:03 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6] Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6] InstallationDate: Installed on 2016-05-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP680Z5E-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu May 12 20:35:57 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4845 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Attachment added: "dmesg | grep drm" https://bugs.launchpad.net/bugs/1581270/+attachment/4661608/+files/dmesg-grep-drm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERRO
[Bug 462478] [NEW] client freezes after a few minutes on IGS
Public bug reported: Binary package hint: cgoban I just switched from Windows to Ubuntu 9.04 OS, successfully installed cgoban, but every time I connect to IGS cgoban freezes up after a few minutes. It also crashes when I try to maximize the window. Can you help me? Thanks for your time, Brian Foster ** Affects: cgoban (Ubuntu) Importance: Undecided Status: New -- client freezes after a few minutes on IGS https://bugs.launchpad.net/bugs/462478 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs