of Cups. Of course, this is not a solution for end users and only
sensible if the problem doesn't occur too often.
- Menno
** Attachment added: Ireshark trace
http://launchpadlibrarian.net/25767402/printertrace
--
CUPS does not print to LPD printer
https://bugs.launchpad.net/bugs/213081
You
It is over a year ago, but maybe nevertheless useful for anyone.
To get another Epson scanner running, I had to add the path to the firmware in
file /etc/sane.d/snapscan.conf.
In my case, the firmware file was called esfw41.bin. It was located at
/usr/share/iscan, where it was placed by package
time the sound of the first fragment started to play
again, without video; now, the second time there is neither video nor sound.
Best regards,
Menno Tjoelker
me...@tjoelker.org
--
plugin not properly unloaded
https://bugs.launchpad.net/bugs/237795
You received this bug notification because you
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/34795797/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34795799/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/34795800/Disassembly.txt
** Attachment
This seems a duplicate of https://bugs.launchpad.net/bugs/675039
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704123
Title:
PIN is asked despite it's configured into the system connection
To
This seems to be duplicated by https://bugs.launchpad.net/bugs/704123
which has a fix committed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/675039
Title:
NetworkManager asks pin code numerous
There is a simple bypass, as the man page shows. The option '--stdout' will use
STDOUT instead of STDERR.
Don't forget to change the redirection.
I noticed this problem too. What wonders me:
- Xdialog is complaining about a module that is there!
- Why does Xdialog need libcanberra in the first
On Tue, 05 May 2009 20:56:04 -
smurf luca_...@hotmail.it wrote:
Yes Menno, I know that I can redirect the output on STDOUT instead of STDERR
(standard), I wrote it in the first message.
Anyway, I found a workaround, setting to true (or 1) the environment
variable XDIALOG_NO_GMSGS all
-etc repository does not found it
4.- Curious thing libcanberra IS INSTALLED.
so te solution is...
Hi,
Changing Xdialog to use STDOUT instead of STDERR is a matter of adding
an option to the command: --stdout. See the man page!
Menno
--
Failed to load module libcanberra-gtk-module.so
https
the output stream has now
changed, things referring to the output stream must be changed too.
For instance, the examples have something like 'Xdialog 2file ...'.
This can be replaced by 'Xdialog file ...' (redirection of standard out
is the self-evident way).
Kind regards,
Menno Tjoelker
--
Failed
by:
$DIALOG --title photo control --clear --stdout\
--inputbox write your number 8 25 $tempfile
The command option has been added, the redirection of stderr (2)
has been changed in redirection of stdout.
Kind regards,
Menno
--
Failed to load module libcanberra-gtk-module.so
https
Public bug reported:
Binary package hint: update-manager
I like to update to 8.04 LTS but there was a fatal error (9??) and the
system can not update.
ProblemType: Package
Architecture: i386
Date: Mon May 23 13:46:20 2011
DistroRelease: Ubuntu 8.04
ErrorMessage: ErrorMessage: SystemError in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/786965
Title:
package update-manager 1:0.87.24 failed to install/upgrade:
ErrorMessage: SystemError in cache.commit(): E:Sub-process
/usr/bin/dpkg
Occasionally Cups is not started after boot.
As far as I have noticed, this always coincides with runlevel 'unknown'.
The problem occurs randomly, as if the system is throwing a dice at each system
start.
System: AMD Athlon 64 X2 dual core 3800+, 2GB DDR2 memory
A remark to my fellow reporters:
On Thu, 01 Jul 2010 22:14:43 -
John Edwards john-ubu...@cornerstonelinux.co.uk wrote:
Menno, it's not just CUPS. The server I met this problem with does not
even have CUPS installed.
If runlevel 2 is not entered then it is *all* services that are started
by rc scripts that fail
It looks like the problem in my case has disappeared after replacing kernel
version 2.6.32-23 by version 2.6.32-24.
I am not absolutely sure, it could be a coincidence and it could also be caused
by some other system modification or software upgrade - my usual procedure is
to install updates
I have this bug too.
Kubuntu 12.04 64-bit.
HP Photosmart 6510.
Shows up twice (in http://localhost:631/printers/):
Photosmart_6510
Photosmart_6510_series
Removing the one not marked as default results in removal of both.
Cups version 1.5.3-0ubuntu4
Please let me now if more information is
Public bug reported:
While upgrading the system with the EnablementStack this error was
reported.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
Uname: Linux 3.2.0-40-generic x86_64
Christopher, adding ahci.marvell_enable=1 did not work at first. Than
I got serious doubts is maybe the disk itself could be faulty. So i put
it in a WinXP box and formatted it as one FAT32 partition. Put is back,
and NOW it is recognized with the marvell_enable workaround. I still
have to see if
Hi!
I promised to get back on the stability issue: well it is NOT stable. One boot
it works, the next is doesn't - behavior is unpredictable
I supply two logs:
1) the successful boot:
[2.274525] ata3: SATA max UDMA/133 irq_stat 0x0240, PHY RDY changed irq
16
...
[2.274525] ata3:
This bug also shows up in Mint KDE 13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344796
Title:
Remote printers showing up twice in local printer menu
To manage notifications about this bug go
Hi!
Since my server is a production system, I am somewhat reluctant to update to
a new version. I therefore tried to find a way to test the latest kernel
without having tot upgrade the whole system. Up to now I did not find a safe
and easy way to do so. Can you point me to instructions on how
Upgraded from 10.4 LTS to 12.04LTS; kernels versions 2.6 to 3.2. System
has two 1T disks in RAID1, boots from RAID volume. This setup worked
perfectly. After upgrade, system won't boot, defaults to
busybox/initramfs; mentioning a faild RAID system. Option to continue
with degraded RAID is
Hi!
I finally came around to updating the kernel. Tested with the 12.04 LTS
version / 3.2 kernel. Unfortunately mij RAID system won't boot on this
3.2 kernel. Had to fall back to the original 2.6 kernel. Problem.
however, still remains. Any activity on this bug?
Regards, Menno
--
You received
Christopher, thanks for reacting to my post. I would really like to help in
solving this pesky problem. Please inform me of all the info logs etc. you
need.
From your tag I suspect you want some hardware info:
PC with motherboard: Jetway J7F2 C7 1.2GHz J7F21G2ES P expansion
card JETWAY 4 x
some 5 minutes it gives up and boot continues
normally. I assume that ATA6 is the first SATA port of the
daugtherboard with the Marvell 88SE6145 controller. Can anyone give me
directions how to check this assumption and how to proceed from this
point?
Regards, Menno
--
You received this bug
=-16)
[ 143.084055] ata2: soft resetting link
[ 148.112037] ata2: SRST failed (errno=-16)
[ 148.112043] ata2: reset failed, giving up
[ 148.112053] ata2: EH complete
Regards, Menno
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
On my system (Kubuntu 12.04.1) , authentication in gksu-properties is
already set to sudo, so for me this does not solve this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1033295
Title:
Crash
On my system, I get the message:
Invalid problem report - Apport KDE
You are not allowed to access this problem report
Not even an option to type the root password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10.04.4 LTS server:
$ uname -a
Linux PARIJS 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24 17:32:45 UTC 2012 i686
GNU/Linux
Hope someone can help.
Regards, Menno
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Added expansion/daughterboard to motherboard. Daugtherboard is recognised
propperly - seems to be funtioning normally.
$ lspci -v
(...)
02:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE6145 SATA II
PCI-E controller (rev a1) (prog-if 8f)
Subsystem:
Christopher, I did as you requested. files as Bug #1094288
regards, Menno
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/463242
Title:
11ab:6145 Marvell 88SE6145 SATA II PCI-E controller
*** This bug is a duplicate of bug 997470 ***
https://bugs.launchpad.net/bugs/997470
I don't know if this is related and should be reported here, but on my
system apport tels me:
You are not allowed to access this problem report.
on a dialogbox with title Invalid problem report - Apport KDE
This also happens for programs started as ordinary users.
On my system I have a few apps that never run, but crash instead, thus
presenting me with the no access bug.
These are nvclock, which I could imagine running with root permissions and the
game Yo Frankie, about which I am not sure if it
** Changed in: eccodes (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754596
Title:
New upstream release: 2.7.0
To manage notifications about this bug
Public bug reported:
https://software.ecmwf.int/wiki/display/ECC/ecCodes+version+2.7.0+released
Package for eccodes-2.7.0 is in Debian testing/unstable
** Affects: eccodes (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Public bug reported:
Error installing linux-image-5-4.0-28-generic
Installed linux-image-5.40.0-28-generic package post-installation script
subprocess returned error exit status 1
And on another attempt:
Error removing initramfs-tools
Installed initramfs-tools package post-installation script
I am experiencing this on Kubuntu 20.04.
Version: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: GL; VCL: kf5;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: CL
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Also experiencing this bug on Kubuntu 20.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766648
Title:
baloo_file crashes after some time in Ubuntu Bionic
To manage notifications about this bug
Summarising what we know so far and adding a few more details:
1. We understand why mongo was continually restarting. jujud currently
restarts mongo every time it starts so every time jujud panicked (~
every 10s), upstart would restart jujud and jujud would restart mongo.
This explains the
No rt73sta.dat is created when I run the above steps:
[EMAIL PROTECTED]:/home/menno/sources/rt73-cvs-2007060205/Module# cp
rt73sta.dat /etc/network/drivers/
cp: kan de rechten van `rt73sta.dat' niet veranderen: Bestand of map bestaat
niet
Which is Dutch for: can't change rights, file does
Package: packagesearch 2.2.5build1
PackageArchitecture: amd64
ProcCmdline: packagesearch
ProcCwd: /home/menno
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=nl_NL.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: packagesearch
StacktraceTop
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7599659/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7599660/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7599661/Disassembly.txt
** Attachment
Good.. 'cause the replaced firmware caused all kinds of connection
instability, sometimes to the point of sheer inuseability. No
disconnects though ;) My solution: replace the rt61 card with a atheros
based one. All is running well with the madwifi drivers.
--
rt61pci drops connection and cannot
I think I had the same issue, rt61pci dropping connection and not
reconnecting with the AP without any notice and tried several solutions
without much luck, until, in an (unsuccessful due to API changes)
attempt to compile the official Ralink drivers from their site
Summarising what we know so far and adding a few more details:
1. We understand why mongo was continually restarting. jujud currently
restarts mongo every time it starts so every time jujud panicked (~
every 10s), upstart would restart jujud and jujud would restart mongo.
This explains the
Please advice: I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS that is
very much related to this bug, but it might not be quite the same. So I
can either file a new bug report or reopen this one.
The issue I'm having is that although the VPN auto-connects for
connections that are marked as such.
** Changed in: juju (Ubuntu)
Assignee: (unassigned) => Menno Smits (menno.smits)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654116
Title:
Attempts to write leadership settings w
This was fixed a long time ago as part of bug 892552. Bug 1579593 still
remains.
** Changed in: juju
Milestone: 2.1.0 => None
** Changed in: juju
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Milestone: None => 1.25.7
** Changed in: juju-core
Status: New => Triaged
** No longer affects: juju
** Changed in: juju-core
Importance: Undecided => Medium
--
You received this bug
It's worth noting that this is unlikely to be a problem with Juju 2.0 as
we no longer have all the agents in each environment logging to
rsyslogd. Juju agent logs are now sent to the controller machines over
the Juju API and are stored in MongoDB.
This is really just a Juju 1.25 issue.
This sounds like there needs to a tweak to the rsyslogd process limits
to allow more open file handles and/or a change to the maximum number of
connections in rsyslogd's config.
** No longer affects: juju-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
After the latest KDE's update to 4.8.5 the crashes happen more rarely.
And, while the crash logs are stored in /var/log/kdm.log I'm quite unsure if
this is a X.org bug or a KDM bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching logfile to this message, this is /var/log/kdm.log. After
today's X.org crash I found there more information (backtrace) that
might be useful.
** Attachment added: kdm.log file from /var/log
Replaced KDM with LightDM to determine whether these crashes are X fault
or KDM. Seems it X, because today I've encountered a crash again. But
this time I haven't found anything in logs (grepped it for
segmentation fault closed unxpectedly — nothing).
--
You received this bug notification
I've something like that, but with fglrx and KDE.
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1042327
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980519
Title:
Random log off in
I think I got some similar bug on Kubuntu 12.04.
It happens randomly.
I found this in /var/kdm.log
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x37) [0xb7749627]
1: /usr/bin/X (0xb75c1000+0x18c3aa) [0xb774d3aa]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb759e40c]
3: /usr/lib/dri/fglrx_dri.so
I use Kubuntu 12.04 with fglrx driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740785
Title:
Caught signal 11 (Segmentation fault). Server aborting
To manage notifications about this bug go
Public bug reported:
1) lsb_release -rd gives Ubuntu 12.04.1 LTS (I actually use Kubuntu)
2) The version of the package you are using: X.Org X Server 1.11.3 Release
Date: 2011-12-16
3) What you expected to happen: No crashes, just it.
4) What happened instead: xorg crashed, I tried to write a
Public bug reported:
While update-manager (on ubuntu 16.10) is running..
Opening the details window should give me a list of updating files.
However the containing window is improperly sized. I can barely see one line of
the list.
See the attached screenshot as illustration of this bug.
The previous juju-mongodb3.2 version was 3.2.12. 3.2.13 and 3.2.14
contains numerous bug fixes, some of which are important to Juju. Of
particular interest are:
https://jira.mongodb.org/browse/SERVER-25318
https://jira.mongodb.org/browse/SERVER-26076
https://jira.mongodb.org/browse/SERVER-26381
** Description changed:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.
Symptoms:
* BIOS settings cannot be saved
* USB
Public bug reported:
(minor issue)
Steps to reproduce:
- Install a snap application, e.g: sudo snap install retroarch
- Open application menu and go to group where apllication is supposed to show
up, e.g. games
What should happen:
- An entry to run the application should be shown
What happens
Public bug reported:
Steps to reproduce (verified on clean Lubuntu 18.10 install):
- Launch lxqt-config-monitor
- Alter display resolution, accept resolution
- Save configuration
- Restart pc
- Wait up to one minute
What happens:
- The display fades to black (Approximately 10 sec after showing
I haven't tried restarting the LXQt panel, but I suppose it would work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801423
Title:
snap applications only show up in the applications menu after a
I am unsure what do you mean by "make the changes"? It only happens when
I save a configuration and restart the pc. If I change the display
resolution, but don't save it then it doesn't happen (neither
immediately and neither after I restarting the PC). I hope this answers
your question...
--
** Changed in: lxqt-config (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801421
Title:
lqxt-config-monitor saved altered display resolution triggers
try with:
xhost +SI:localuser:root
sudo synaptic
after use close with:
xhost -SI:localuser:root
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771158
Title:
Synaptic doesn't open with
I disabled screensaver (Mode, select Disable Screen Saver).
After it turns black, it stays black.
I have installed Lubuntu 19.04 and I noticed the same issue. However, I
also noticed that the screen fades to black on if auto login is enabled.
I searched the internet for autologin and black
Ubuntu 20.04 will install fine on the XPS15 9560. However you will need
to set nouveau.modeset=0 and disconnect any monitor connected to HDMI.
Also after 20.04 is installed, you still cannot boot when a monitor is
connected to HDMI. You will stay at the Ubuntu splash screen with the spinner
I wish i could add some more info regarding this problem. @guiverc
apport-collect 1874194 just says No additional information collected.
If anyone from the Ubuntu team needs more information and can tell me
how to provide them, i am more than happy to provide the needed
information.
--
You
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874194
Title:
Ubuntu 20.04 HDMI connected, no boot
To manage notifications about this bug go to:
apport-collect 1874194 is not really effective since this problem
happens before ubuntu is even booted up. Like i mentioned ubuntu is
stuck at the splash screen only showing a spinning circle and the ubuntu
logo.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just wondering. I am still using rtl8821ce-dkms on Ubuntu 20.04. This is
not needed anymore now and 5 Ghz Wifi DFS protetcted channels are now
available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
$ apt-cache policy evince
evince:
Installed: 40.1-1
Candidate: 40.1-1
Version table:
*** 40.1-1 500
500 http://nz.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100
It turns out this is due to some weird interaction with the alacritty
snap (https://snapcraft.io/alacritty). evince wasn't the only software
to do this. Other GUI apps such as nautilus and eog when started from
the terminal did the same thing.
Closing this.
** Changed in: evince (Ubuntu)
Is it possible a regression has occurred? Right now I do not have the
possibility to select Wayland when using the nVidia 5.10 drivers. I only
can use X11? I was using Wayland without major problems, but after
updating I can only use X11.
--
You received this bug notification because you are a
77 matches
Mail list logo
